Active
Project:
Signup
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Oct 2010 at 21:46 UTC
Updated:
20 Feb 2014 at 22:01 UTC
Jump to comment: Most recent
Fatal error: Call to undefined method stdClass::preview() in /contrib/signup/includes/node_output.inc on line 149
I get this error when I try to create, edit, or view a node.
Comments
Comment #1
socialnicheguru commentedline 149 is
Comment #2
ezra-g commentedThis can happen if you've got the "View to embed for the signup administrative list" (and probably also the "View to embed for the signup user list") setting set to a view that doesn't exist on your system.
As a solution, you can go to /admin/settings/signup and select views that do exist and save the form.
In general we can avoid this PHP error by checking if the $view is empty after calling views_get_view() and return some helpful error text instead of attempting to preview a view that doesn't exist.
Comment #3
escoles commentedI believe this error is also getting thrown if the view displays no content. (I.e., I'm receiving it for the 'View to embed for the signup user list', and have verified that the view exists and is enabled.)
Comment #4
redndahead commentedGoing to /admin/settings/signup and clicking save without making any changes fixed this error for me. Maybe a default value isn't being set?
Comment #5
kepford commentedI can concur with what @redndahead says. Going to /admin/settings/signup and clicking save fixed it for me too.
Comment #6
walkerwilliams.3net.net commentedAm using the cod(conference organizing distribution)
I get the following error when i click on signups in the event node.
The solution is to click on save configurationtab without making any changes in http://127.0.0.1/admin/settings/signup
Replace 127.0.0.1 with your domain name e.g "example.com"
I hope this post will assist somebody
Comment #7
gregglesbetter title (I think?).
Comment #8
raycascellaSince this ticket remains open, I'll add my two cents, for posterity.
Our company encountered the same error and clearing the cached did the trick for us. Our issue had to do with memcache and views going crazy when 3,000+ users went to register around the same time, after a conference. According to our lead developer, it was alike 3,000 mini DDoS attacks. =-D
Hope that helps someone.