Hi,

trying to update the standard views-module shiped with the latest Atrium-Packed i get the following error:

Call to undefined method views_plugin_display_block::get_cache_plugin()

(after turning error-reporting on, before white screen of death => empty page, without any html)

So i try to fix it with the dev-version, situation remains the same!
So back to the 2.12 and all works fine!

what happend?

Thx!

Comments

dawehner’s picture

Can you please test the 6.x-3.0-dev version? It should be fixed there already.

In general from my perspective it's a huge mistake to pack 6.x-3.x-alpha3 with openatrium.

ragesoft’s picture

i've allready teste the dev-version, without success! stay the same.

Why it is a huge mistake?

dawehner’s picture

Status: Active » Postponed (maintainer needs more info)

Can you please show us the full error message? There is probable a bad place where this function is called.

jmary’s picture

Fatal error: Call to undefined method views_plugin_display_block::get_cache_plugin() in /var/www/......./profiles/openatrium/modules/atrium_features/atrium_activity/atrium_activity.views.inc on line 97

dawehner’s picture

Version: 6.x-3.0-alpha3 » 7.x-3.x-dev
Status: Postponed (maintainer needs more info) » Fixed

This is really not our fault :)

There is get_plugin('cache') which you can use. Sadly there is no issue queue for drupal.org here.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Grayside’s picture

I can confirm for 6.x-3.x that switching get_cache_plugin() for get_plugin('cache') works.

jthomasbailey’s picture

I can also confirm that #7 works

freescholar’s picture

Fresh install of Atrium 1.0
upon install updates were needed:
Views
Diff
Token

After updating to Views 3x Rc and Dev = error message:
Fatal error: Call to undefined method views_plugin_display_block::get_cache_plugin...

After reverting to Views 2x no error.

Grayside’s picture

@DrupalConnection reread #7.

Also, Open Atrium is not necessarily Views 3 compatible. It is an advanced, development-oriented decision to actually apply any updates from the status page. While those module versions are newer, and the page declares them to be "recommended", they were not packaged as part of Atrium's current suite of Contrib and Custom modules.

appaulmac’s picture

I can confirm #7 fixed it for me too, and this on atrium 1.2 as well. :/

jamps3’s picture

#7 fixes this for me too(Open Atrium 1.4).

jamps3’s picture

Status: Closed (fixed) » Needs work
dawehner’s picture

Status: Needs work » Fixed

So what is the point? That's still some kind of "bug" of open atrium, but they have views2 in their installation profile so i guess the version you should better use is 2.x as well.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.