I have recently downloaded and installed Drupal 7.2 on a test site but it keeps crashing with error relating to views see error message below. The error is created when you click on content in the admin menu although sometimes this just gives a blank screen but if you then click on find content button it goes to content but produces the error below. I have not created any views. I have now uninstalled views from module menu and things seem to have settled down.
Notice: Undefined property: views_plugin_display_system::$current_display in views_page_alter() (line 422 of /Applications/MAMP/htdocs/drupal/sites/all/modules/views/views.module).
Notice: Undefined property: views_plugin_display_system::$current_display in views_page_alter() (line 422 of /Applications/MAMP/htdocs/drupal/sites/all/modules/views/views.module).
Notice: Undefined property: views_plugin_display_system::$current_display in views_page_alter() (line 422 of /Applications/MAMP/htdocs/drupal/sites/all/modules/views/views.module).
Notice: Undefined property: views_plugin_display_system::$current_display in views_page_alter() (line 422 of /Applications/MAMP/htdocs/drupal/sites/all/modules/views/views.module).
Comment | File | Size | Author |
---|---|---|---|
#15 | admin-menu-admin_views-update-for-views-7.x-3.0-beta3-1177202-14.patch | 2.11 KB | das-peter |
#15 | views-admin_views-update-for-views-7.x-3.0-beta3-1177202-14.patch | 555 bytes | das-peter |
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedWhat's interesting is that views_plugin_display_system isn't a class provided by Views. It's possible that some module is misbehaving.
From looking at it, the error would indicate that views_set_page_view() is being called in appropriately. I am guessing by whatever module is providing views_plugin_display_system
And since that module didn't properly namespace its class, I can't tell what module it's coming from. You're going to have to figure out which module this is (grep for views_plugin_display_system should find it) and file an issue against that module.
Comment #2
merlinofchaos CreditAttribution: merlinofchaos commentedAhh, it's admin_menu
And it's probably because we recently fixed views_set_page_view to work like it says it does, so admin_menu needs to catch up.
Comment #3
paulgemini CreditAttribution: paulgemini commentedSubscribing. I'm having some weird behavior with Administration menu since my upgrade (it loads late...the browser loads endlessly until I click "stop" and the admin menu appears) and want to see if this is related.
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedDitto on this issue.
Comment #5
kreven CreditAttribution: kreven commentedSame for me too. This was my first step into Drupal 7 from Joomla and I'm still not convinced I want to switch over...
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commented@kreven,
Yes you do.
Comment #7
acrollet CreditAttribution: acrollet commentedsubscribe. I've disabled the administration views module, and it brought back the content and user admin pages.
Comment #8
Dig1 CreditAttribution: Dig1 commentedYes, when I install D7.2, ctools dev, views dev, views_bulk_operations dev eveything is ok.
As soon as I enable admin_views I get a list of error messages stating:
''Notice: Trying to get property of non-object in user_access() (line 774 of /var/www/d7test1/modules/user/user.module''
And I can't list users etc. until I disable admin_views.
So this is probably as per #2.
Dig
Comment #9
sunComment #10
grahamtk CreditAttribution: grahamtk commentedsubscribe
Comment #11
restyler CreditAttribution: restyler commentedadmin_views is unusable for me because of the problem. subscribing
Comment #12
bancarddata CreditAttribution: bancarddata commentedsubscribe
Comment #13
marcvangendVBO has changed quite a lot in the alpha2 release. Quoting from #1182540: VBO missing after installation: "there is no VBO style plugin anymore. VBO is now a field."
Comment #14
das-peter CreditAttribution: das-peter commentedThe notice
Notice: Trying to get property of non-object in user_access() (line 774 of drupal/modules/user/user.module'
is caused by following code of admin_views inviews_plugin_display_system::execute_hook_menu()
:Since
views_menu_alter()
tracks all changes made to the callbacks by views and doesn't allow another full change of an already changed callback we end up with a nearly unmodified menu callback if a system view is a menu child of another system view (E.g.admin/content
<->admin/content/comment
).Unfortunately I'm not sure what the above inherit code is thought for. Thus I'm not able to provide a patch. For now I commented out this code and everything, what I need, seems to work atm.
Comment #15
das-peter CreditAttribution: das-peter commentedOk I was wrong - there were trouble :)
Drilled down a little more and I guess I understand the intention of the construct now.
To solve that issue views itself needs a patch - I'll discuss this with Daniel asap.
Meanwhile you find both patches attached here.
Don't be confused - the admin_menu patch also contains an indent fix (tab to spaces) ;)
Comment #16
das-peter CreditAttribution: das-peter commentedOh, and of course this needs review :)
Comment #17
dawehnerAltering variables via references makes things also a bit easier to understand.
This is just tabs to spaces, so it's fine, got confused a bit here.
Comment #18
das-peter CreditAttribution: das-peter commented@Daniel Thank you very very much for your review. Awesome how fast you are :D
As discussed in IRC, I've created a related Views issue #1309518: Allow more complex scenarios in execute_hook_menu() by passing $callbacks as reference
Comment #19
sunThanks for reporting, reviewing, and testing! Slightly adjusted and committed to 7.x-3.x.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.