Have trouble debugging the following error:
Fatal error: Call to a member function validate() on a non-object in /home/syu/public_html/modules/views/includes/admin.inc on line 910
This was on the 2.12 version, while on the 2.x-dev is on line 914.
That corresponds to the call to $form_state['view']->validate();
But apparently the whole $form_state['view'] have gone missing and this happens on all my views not only the one i was editing.
Without the $form_state['view'] the save() function will throw a similar error.
This happened inmediately after fixing the issue at http://drupal.org/node/759082#comment-3842226 that was solved with a patch.
Went back to editing and added a display, and the views_ui submitted fine, but then went back to add an argument and the error showed up.
From that point none of my views can be saved nor can add new ones.
The only thing that looks suspicious is that while patching for the first issue the caches were cleared including cache_form.
Also, the save button is not grayed out for views that have not been edited.
As far as i know the only other module that changed that day was views_bulk_operations.
No other modules were changed so no disabling of modules have been tested.
The form module is not installed.
I'd check the usual steps (clean install, revert to backup, export the view or disable modules) but i'd like to ask you if have had a similar problem or know where to start checking for $form_state['view] or any info on changes made to the dec 15 versions.
Thanks
Comments
Comment #1
inforeto commentedApparently i had either an upgrade mismatch or a corrupted module.
Reinstalling imagefield module made the site work again and couldn't find the cause.
While disabling modules one by one i found that disabling imagefield module removed the error, and reenabling it made the error reappear.
I had the 3.9 version of december 12, then i downgraded to version 3.8 of december 10 and the site kept working.
Then checked the patches of imagefield 3.9 and didn't find something that may give problems so tried upgrading again.
The site so far kept working so it might have been something with filefield 3.9 that lingered but is not happening using the latest 3.x-dev version of filefield of january 5.
Closing this issue for now.
Comment #2
alexbk66- commentedI have the same problem, when I save a view, I get
I've got no idea what to do, I gues I start disabling modules...
BTW, where did you get the dev version of imagefield? I think I should give it a try.
Comment #3
inforeto commentedThe dev version i mention was of filefield, the imagefield was 6.x-3.9.
Be careful with the filefield dev version because you can't undo them as there's dependencies on other modules.
Comment #4
alexbk66- commentedI managed to get my hosting provider to increase max_allowed_packet to 16M and the problem is gone!
Comment #5
dawehnerSo this is fixed.
Comment #7
Footeuz commentedI have the same problem since I've updated my module Filefield.
I'm now using the 6.x-3.10 version
Does anyone have another solution than disabling filefield ?
Comment #8
inforeto commentedPerhaps check that image module is up to date and/or corresponds to the filefield version.
The disabling is just during the troubleshooting, you can disable, check that views work, then enable them again.
Or at least that's what i did.
Comment #9
niner94949 commentedI am also receiving this error.
I upped the max_allowed_packet to 512M and the issue still persists.
I disabled the filefield module and I was able to successfully save the view. With filefield enabled, the view will not save.
Did anyone have luck with fixing/patching/work around?
Comment #10
niner94949 commentedI ended up removing Filefield 6.x-3.10 and removing Imagefield 6.x-3.10. I added Filefield 6.x-3.7 and added Imagefield 6.x-3.7. I was then able to save my views without receiving the
Fatal error: Call to a member function validate() on a non-object in ...profiles/drupal_commons/modules/contrib/views/includes/admin.inc on line 910