Views not saving
Quartz - November 9, 2009 - 03:38
| Project: | Views |
| Version: | 6.x-2.7 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Upgraded to 6.x-2.6 on D6.14 and since are getting white screens upon saving or editing a view. ie can't save anything.
Checked permissions: admin can administer views - otherwise I guess I couldn't have created or edited one in the first place.
Any ideas folks?
#1
Enable error display and tell what is displayed.
#2
Error reporting is set to screen and log.
As above - screen is white.
Nothing in logs.
It would appear that the new view that was created, saved, despite the WSD.
#3
If you are getting a whitescreen there must be an error of some kind, somewhere. Either your apache logs, or your watchdog logs, or if your site has a separate php error log, perhaps there.
#4
Sorry but I don't have access to the clients apache logs.
Can you tell me about the 'separate phperror log' ? Is this something I can set up for future reference?
#5
The php.ini file contains an error_log directive. Most systems set this to 'syslog' but it can be set to a separate file. I don't know for sure but you might be able to use ini_set() in your settings.php file to change this to a file. That could be useful for doing temporary error reporting.
There is another value you can set (I forget which one it is, but google should be able to find it for you) that lets PHP report errors to the client, and that might help as well. You do not ordinarily want to run with it on, but it could be handy while debugging.
#6
BTW, just to doublecheck -- you did hit update.php, right? This kind of error *could* happen if changes to the database need to be made.
#7
Thanks merlinofchaos. I will look at those files. Yes, did update.php ;) In fact just ran another one now for good measure and the WSD remains.
#8
Ok wrote the output to a file. (Interesting learning opportunity!)
This is what I get trying to save the view the first time.
[11-Nov-2009 22:40:55] PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/php4/Zend/Optimizer/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0[11-Nov-2009 22:41:01] PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/php4/Zend/Optimizer/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0
[11-Nov-2009 22:41:03] PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/php4/Zend/Optimizer/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0
[11-Nov-2009 22:41:11] PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/php4/Zend/Optimizer/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0
[11-Nov-2009 22:41:14] PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at '/usr/local/php4/Zend/Optimizer/php-5.2.x/ZendOptimizer.so') - try reinstalling the Zend Optimizer in Unknown on line 0
[11-Nov-2009 22:41:18] PHP Fatal error: Out of memory (allocated 58982400) (tried to allocate 82 bytes) in /htdocs/drupal/includes/menu.inc on line 965
Trying to save it a second time simply repeats the top line, adding it to the log file.
#9
I coded out the Zend lines, from the php.ini, as I found out that the server is 64 bit running FreeBSD and therefore not compatible anyway with the Zend Optimizer, so possibly a 'red herring' to this issue.
So I guess its a PHP memory issue in general not just a Views one?
#10
Hmm. Yeah, looks like it's running out of memory trying to rebuild the menu after save. There's some resources on drupal.org to help you increase the amount of memory available, which can be necessary on sites with a lot of modules.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.