Fatal error: Call to a member function [#229983]

fresh install, 6.1, no mods works perfect until i created a block and clicked saved

Fatal error: Call to a member function on a non-object in /homepages/3/d180706684/htdocs/modules/views/includes/plugins.inc on line 446

now when i try to access views i get
Fatal error: Call to a member function on a non-object in /homepages/3/d180706684/htdocs/modules/views/includes/plugins.inc on line 267

Comments

Comment #1

ezra-g CreditAttribution: ezra-g commented 5 March 2008 at 14:40

It might help if you describe your view either verbally or by exporting it and pasting the export here.

Comment #2

Anonymous (not verified) CreditAttribution: Anonymous commented 13 March 2008 at 16:03

Hi there! I installed Drupal 6, and have updated to version 6.1. I just installed Views Module. I have never used Views before, but I don't think I did anything weird. I got the exact same error (Fatal error: Call to a member function on a non-object ... /modules/views/includes/plugins.inc on line 446), so I went to see what could have caused it. Here's what I found...

I added a new view called "test" keeping it as default "node". Clicked next, didn't touch anything, and saved it as it was. All was good - I could click "edit" on the main view's page (where it lists the views) and could get back into the options for that view.

So I went edited "test", clicked on "add display" on the left, and saved, and went back to View's main page. Now I get the 446 error when I click on edit. Actually, now I get that same error when I click the "views" button on the navigation menu. Can't access that page at all!

Hopefully that helps a bit to narrow the possible cause.

Sonia Wilkinson
Drupal 6.1

Correction: When I click "views" I get the "modules/views/includes/plugins.inc on line 267" message that yosemite mentioned. Can't get into the views menu at all.

Comment #3

ezra-g CreditAttribution: ezra-g commented 15 March 2008 at 00:25

I can't replicate this. Are you still having this issue? If so, it might help if you paste an export of the affected View into this issue.

Comment #4

merlinofchaos CreditAttribution: merlinofchaos commented 16 March 2008 at 03:16

Status:

Active

» Postponed (maintainer needs more info)

Does this error still exist in alpha3?

Comment #5

abamarus CreditAttribution: abamarus commented 1 September 2008 at 08:21

I am experiencing this bug too. I have no idea which view might be causing it so exporting it is kinda difficult!

I did clone a view and I believe this is when the problem began. Deleting that cloned view did not make the problem go away though.

Comment #6

abamarus CreditAttribution: abamarus commented 1 September 2008 at 08:51

I made a little modification to the module code to work around this problem.

On line 649 of plugins.inc I changed the test from

if ($display->handler->has_path()) {

if (is_object($display->handler) AND $display->handler->has_path()) {

and now I have my list of views back. This just gets around the symptom though - still no idea why the variable is not an object in this one instance.