<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Roger,<br>
<br>
You're not seeing anything because you have display_errors set to
false in your php.ini.<br>
<br>
You can change that and restart apache, or add <code><span
class="pln"><br>
error_reporting</span><span class="pun">(</span><span
class="pln">E_ALL</span><span class="pun">);</span></code>
<span class="pln">ini_set</span><span class="pun">(</span><span
class="str">'display_errors'</span><span class="pun">,</span><span
class="pln"> </span><span class="str">'1'</span><span
class="pun">);</span><span class="pln"> <br>
</span>
<pre style="" class="lang-php prettyprint prettyprinted"><code><span class="pun">see <a class="moz-txt-link-freetext" href="http://php.net/manual/en/function.ini-set.php">http://php.net/manual/en/function.ini-set.php</a>
for more.
-Don-
</span></code></pre>
<br>
On 2/24/2013 6:53 PM, Roger wrote:<br>
</div>
<blockquote cite="mid:512AA7FB.2040602@bigpond.com" type="cite">
<pre wrap="">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
</pre>
</blockquote>
<br>
</body>
</html>