Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Apr 2011 at 10:10 UTC
Updated:
8 Jun 2012 at 00:11 UTC
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
Comment #1
dawehnerCan 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.
Comment #2
ragesoft commentedi've allready teste the dev-version, without success! stay the same.
Why it is a huge mistake?
Comment #3
dawehnerCan you please show us the full error message? There is probable a bad place where this function is called.
Comment #4
jmary commentedFatal 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
Comment #5
dawehnerThis is really not our fault :)
There is get_plugin('cache') which you can use. Sadly there is no issue queue for drupal.org here.
Comment #7
Grayside commentedI can confirm for 6.x-3.x that switching get_cache_plugin() for get_plugin('cache') works.
Comment #8
jthomasbailey commentedI can also confirm that #7 works
Comment #9
freescholar commentedFresh 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.
Comment #10
Grayside commented@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.
Comment #11
appaulmac commentedI can confirm #7 fixed it for me too, and this on atrium 1.2 as well. :/
Comment #12
jamps3 commented#7 fixes this for me too(Open Atrium 1.4).
Comment #13
jamps3 commentedComment #14
dawehnerSo 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.