By walden on

I'm getting the dreaded white screen of death on a node/add/mycustomcontenttype screen and am at a total loss for how to fix it. I went through the recommended steps http://drupal.org/node/158043 but they haven't solved the problem.

There isn't a php error being generated and there isn't anything in Drupal's log. Any suggestions on how to isolate this problem?

This problem started around the same time that maybe my hosting provider, pair.net upgraded the server OS to FreeBSD 7.2 . They suggested upgrading from Drupal 5.2 to 5.22, but that would take a great deal of time, so I have been reluctant to do it. I did copy the site to a local server, and the problem went away.

⋅ Categories: Drupal 5.x

Comments

arhak’s picture

arhak commented

1- do you have clean URLs?
does your hosting keep having mod_rewrite?
try manually disabling clean URL through phpMyAdmin

2- do you have poormanscron, elysia_cron or super_cron modules?
check those modules' issue queue for WSOD
there have been WSOD problems with poormanscron & search module at the same time

3- the only way to get a WSOD without any PHP error is when some code directly invokes exit
check for those places where core & modules invoke exit or drupal_goto (since it lead to an exit call)

walden’s picture

walden commented

#1 manually disabled clean urls and problem persisted

#2 Don't have any of those modules

#3 not sure how to do this

I did find that when the menu module is disabled I do not receive the wsod. Problem with this module?

walden’s picture

walden commented

This issue went away after upgrading to the latest 5.x release of Drupal