White Screen of Death. :)
yep, not seeing that is always a good thing. -Don-
On 2/24/2013 8:01 PM, Bob@TurnerPCC.com wrote:
WSOD? What is that? I don't know, but its probably a good thing I have not seen one. Bob *From:* Bill Fitzgerald mailto:bill@funnymonkey.com *Sent:* Sunday, February 24, 2013 7:08 PM *To:* support@drupal.org mailto:support@drupal.org *Subject:* Re: [support] So fed up with Drupal 7 Generally, a WSOD is caused by an out of memory error. What do the apache/php logs say? Have you tried turning on mysql slow query log? Have you looked at your max execution time? But, re: "mayo theme fully updated drupal 7 core and 43 additional modules Any one of the 43 modules could be causing an issue here. Or, if there is any custom theming, it could be some bad code in your theme. Additionally, what version of PHP are you running? If you are running 5.4, that could part of the problem. In short, there are a slew of potential causes here. I hope this helps get you started. Cheers, Bill On Sun, Feb 24, 2013 at 3:53 PM, Roger <arelem@bigpond.com mailto:arelem@bigpond.com> wrote:
As the subject line says, I am getting rapidly disenchanted with Drupal 7 but there are no valid alternatives. The problem: <Administration><Structure><Content Types><Select any content type> <Edit> WSOD. No error messages, no log messages, no way to isolate what may be the problem. There is no way to enter the edit mode of any content type in my system. This started with 2 content types and now since I switched on Book module, is all of them. Switching off Book module has no effect. Problem exists with the site copy on 2 different operating systems. What puzzles me is that WSOD is only for edit selected content type, everything else seems ok. I have a basic mysql database, . Been having this problem to various extent for over a month. I suspect it may again be a php memory error but have no way of knowing. Have ini_set() to 128M in /settings.php, have memory_limit in php.ini set to 128M and in this Fedora 16, at least do not get the dreaded php memory error mentioned in my previous emails. Is there any way to ascertain exactly what may be causing the WSOD or is it simply a function of the way php works. I notice that php reads the config files on startup but not again unless restarted. could the problem be caused by memory overload through php, I'm grasping at straws here. I would appreciate some understanding on what's going on and how to resolve it. Many thanks Roger -- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]