I have spent a large amount of time trying to determine the WSoD issue with OpenPublic. Continuing research shows that it is a server side issue and is not specific to a particular browser, as I originally thought. All my server memory and php settings are even more generous than the settings recommended on the openpublicapp.com site.
Even more frustrating, Apache is not throwing any errors, other than the "lost favicon" error that happens to most Drupal7 installs. What makes it particularly maddening is the seemingly random nature of the error. Time seems to be a factor. When one gets the WSoD, you can refresh the page and everything will begin to work. This "refresh" also seems to help other browsers display the site correctly, as if a cache is being refreshed. In fact, flushing all caches is another way to "get things working" for awhile.
But as time goes by, the site breaks yet again, usually after 10-15 minutes or so. To my knowledge, my server is properly set up, and I DO NOT have this issue with any other Drupal or Drupal 7 install, so it is specific to OpenPublic.
This is a SHAME because I was planning to use the excellent OpenPublic profile as the base for a commercial site to launch in a few weeks, but it looks like I'll have to abandon that if I cannot resolve this issue soon.
Any help or hints would be greatly appreciated!
Comments
It's not a memory issue
Just for "fun" I upped my php memory from 256M to 512M temporarily and then rebooted. That didn't help, so it's not a memory issue at least.
PHP Error Reporting
If you haven't already, enable PHP error reporting on your server. This should give you an error message on your WSoD. Would help in identifying the issue.
How to?
I've got virtual hosting setup with specified error log files. Are you suggesting something else? I'm not familiar with the procedure. How do you do it? :-)
BTW, I DID enable error reporting in Drupal by including the following code in index.php:
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
That didn't result in any new errors being printed though.
php.ini
Is anything showing up in your error log files?
If not try un-commenting or adding this line in your php.ini file:
error_reporting = E_ALLerror reporting was already set to E_ALL
The only error I'm getting in my error log file is "file does not exist, favicon.ico" in openpublic root. This is a pretty common Drupal 7 error. That's it.
Figuring that my Linux dev server could be misonfigured, I copied the openpublic site to my Windows computer. (I have xampp installed there) On that server I get an intermittent critical apache error: "The apache server has gone away."
There are no errors in the apache err_log file.
This might have something to do with it
The following site: http://www.apachefriends.org/f/viewtopic.php?f=16&t=41137&start=0&view=p...
...talks about the very error I am now getting when running OpenPublic on xampp (my Win7 machine)
Don't know if this helps or
Don't know if this helps or hurts, I am now getting a WSOD when I click on my modules menu item. I haven't dug into it, I am just going to go back to last night's backup.
General gripe: Not a huge fan of the overlay. Seems much slower to me. I disable it on other sites.
php memory
Typically, if you are only getting the WSoD on the module page, that's a php memory issue. Just go to your php conf file and up the memory limit to 256M.
The other WSoD's are something altogether different, since they can appear on ANY page.
Upped my memory. Let's see
Upped my memory. Let's see if that solves the problems.
Thanks!
WSOD Issue
I have been facing the same issue.. I am not able to enable any module apart from CCK. If I try to put the extracted folders at "all" folder and try to enable it, I get the WSOD. Its bugging me from last 3- 4 days and have tried all memory upping/ permission sorting things.. Just can not get over it... :(
Sarang