You would not believe the hours I've put into trying to beat this. I have searched and searched for a solution and nothing works.
1) I'm not running postgres, I'm running mysql.
2) I have tried uninstalling every views related module that I have installed recently / since the time this could have broke.
3) I have cleared and turned of the Drupal cache.
4) No....I don't I have admin_menu or whatever it's called!
5) I have tried upgrading from 6.3 alpha 2.
I need to be running on 6.3x because I need the groupby/calulation tools that it offers. I am unsure if I could ever add new views since installing 6.3x
*PLEASE* help me here. This is driving me potty and it's holding up new development on new views. I can't just keep adding displays to existing views!
Many Thanks.
Comments
Comment #1
chrisdbarnett commentedOK...after a hell of a lot of pain and swearing (I lost a load of displays which need time and effort putting back into them), the real culprit turned out to be the secure pages module. Adding an exception for admin/build/views seemed to fix it.
Also, I couldn't clone and save a view before....I could after I uninstalled and reinstalled all of my views modules, so there might have been 2 gremlins there.
Comment #2
jeffleeismyhero commentedI'm getting the same problem; however, adding the exclusion to securepages does not help.
My log shows the following:
This occurs when I add a new view or try to clone an existing one. All of the updates were run.
Adding the missing fields (is_cacheable and view_php) fixes the issue. I'm not sure why or where these were removed.
Comment #3
bojanz commentedThey were removed because they are no longer used. Updating the code to -dev will solve your error.
(did you use -dev, then downgrade to alpha3? Because your schema is newer than your code)