[support] So fed up with Drupal 7

[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
>>
>>
>>
>