So fed up with Drupal 7
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, mayo theme fully updated drupal 7 core and 43 additional modules. 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
Hi, Have you looked at your php error log. IF it doesn't get logged by watchdog then it will always be logged in the php error log. Gordon. On 25/02/2013, at 10:53 AM, Roger <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, mayo theme fully updated drupal 7 core and 43 additional modules. 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/ ]
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> 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/ ]
WSOD? What is that? I don’t know, but its probably a good thing I have not seen one. Bob From: Bill Fitzgerald Sent: Sunday, February 24, 2013 7:08 PM To: 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> 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/ ]
On 13-02-24 08: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.
"White Screen Of Death" was my guess since that's what you often get when the script dies before output and you have display_errors set to off :) Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized.
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/ ]
On 2/24/13 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
White Screen Of Death When the page terminates with just an empty white screen, normally caused because of some sort of fatal error in PHP when processing the page. There should be an error logged on the server about the problem (if PHP was set up as normal with error logging only to the logs). It is possible (suggested only for private development sites) to have PHP print the error also to the requesting browser, but that runs the risk of revealing vulnerabilities. -- Richard Damon
Hi Roger, You're not seeing anything because you have display_errors set to false in your php.ini. You can change that and restart apache, or add | error_reporting(E_ALL);| ini_set('display_errors','1'); |see http://php.net/manual/en/function.ini-set.php for more. -Don- | On 2/24/2013 6:53 PM, Roger 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, mayo theme fully updated drupal 7 core and 43 additional modules. 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
Thanks I switched display_error on and html_error on and now have the ever faithful..... Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 3759910 bytes) in /var/www/html/eal/includes/cache.inc on line 463 So at least I'm back to an endemic php memory problem. So I know that: the problem exists on 3 different OS installations, Is php related because all systems have the latest update of php. Is virtually identical on each That it occurs in the same drupal site copy installed on all 3. I am suspicious that it is an underlying problem with token module because under some circumstances token keeps on regenerating tokens, filling memory to the pc's physical limit, not the php limit. This can be witnessed in Firebug. The WSOD also happens when drupal doesn't correctly read some field in the database. To switch of token module requires several other modules to be disabled, thus affecting the site so it's not a good option. Back to square 1 and am still puzzled. Thank you for any and all assistance Roger
Hi Roger,
You're not seeing anything because you have display_errors set to false in your php.ini.
You can change that and restart apache, or add | error_reporting(E_ALL);| ini_set('display_errors','1'); |seehttp://php.net/manual/en/function.ini-set.php
for more.
-Don-
|
On 2/24/2013 6:53 PM, Roger 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, mayo theme fully updated drupal 7 core and 43 additional modules. 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
what is your max memory limit set to in php.ini? Sometimes it's set to 64M out of the box. http://drupal.org/node/207036 -Don- On 2/24/2013 9:43 PM, Roger wrote:
Thanks I switched display_error on and html_error on and now have the ever faithful..... Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 3759910 bytes) in /var/www/html/eal/includes/cache.inc on line 463
So at least I'm back to an endemic php memory problem. So I know that: the problem exists on 3 different OS installations, Is php related because all systems have the latest update of php. Is virtually identical on each That it occurs in the same drupal site copy installed on all 3. I am suspicious that it is an underlying problem with token module because under some circumstances token keeps on regenerating tokens, filling memory to the pc's physical limit, not the php limit. This can be witnessed in Firebug. The WSOD also happens when drupal doesn't correctly read some field in the database.
To switch of token module requires several other modules to be disabled, thus affecting the site so it's not a good option. Back to square 1 and am still puzzled.
Thank you for any and all assistance Roger
Hi Roger,
You're not seeing anything because you have display_errors set to false in your php.ini.
You can change that and restart apache, or add | error_reporting(E_ALL);| ini_set('display_errors','1'); |seehttp://php.net/manual/en/function.ini-set.php
for more.
-Don-
|
On 2/24/2013 6:53 PM, Roger 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, mayo theme fully updated drupal 7 core and 43 additional modules. 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
It's set to 128M I have experimented from 32M to 512M in 8M increments restarting after each attempt but the php out of memory error does not change except for the amount it tries to allocate which I had down to 6k at one stage with memory_limit set to 512M. Roger
what is your max memory limit set to in php.ini? Sometimes it's set to 64M out of the box. http://drupal.org/node/207036
-Don-
If you have Rules, Token, and Entity API enabled, you could be exhausting your memory due to issues with Entity Token. https://drupal.org/node/1203018 is a starting point. Also, if you are running PHP 5.4, there are bugs (some Drupal, some PHP) that cause unpredictable results. Cheers, Bill On Sun, Feb 24, 2013 at 7:06 PM, Roger <arelem@bigpond.com> wrote:
It's set to 128M I have experimented from 32M to 512M in 8M increments restarting after each attempt but the php out of memory error does not change except for the amount it tries to allocate which I had down to 6k at one stage with memory_limit set to 512M. Roger
what is your max memory limit set to in php.ini? Sometimes it's set to 64M out of the box. http://drupal.org/node/207036
-Don-
-- [ Drupal support list | http://lists.drupal.org/ ]
there might be an endless loop. where i normally see problems is when you bring up the modules page, and it's much worse in D7. I've read about some combinations of modules that cause problems, but i don't remember which right now. UUID often seems to be in the middle of it. If you do php you can always try to put some trace information in the php error handler. or walk through with a debugger like phpEd. -Don- On 2/24/2013 10:06 PM, Roger wrote:
It's set to 128M I have experimented from 32M to 512M in 8M increments restarting after each attempt but the php out of memory error does not change except for the amount it tries to allocate which I had down to 6k at one stage with memory_limit set to 512M. Roger
what is your max memory limit set to in php.ini? Sometimes it's set to 64M out of the box. http://drupal.org/node/207036
-Don-
* Roger <arelem@bigpond.com> [130224 14:56]:
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, mayo theme fully updated drupal 7 core and 43 additional modules. 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. FYI: I am new to drupal and PHP, but I have been a programmer for 25 years. Have you written any custom modules? If so, have you run syntax check (php -l)?
:) I like drupal, although I would have written it in python. However, even python will give you a WSOD if you haven't included the right module.... Also, I don't note where you said what OSes you are using. I recently transitioned from linux to mac and mac has got some gotchas with PHP and mysql. Best of luck. Here's hoping you get some more replies. -- Tim tim at tee jay forty nine dot com or akwebsoft dot com http://www.akwebsoft.com
participants (8)
-
Bill Fitzgerald -
Bob＠TurnerPCC.com -
Don -
Gordon Heydon -
Richard Damon -
Robert Cummings -
Roger -
Tim Johnson