0

I have a lot of trouble with the WSOD and have looked around quite few posts; like WSOD with Devel module and How to see the error messages when I get the white screen of death? as well as https://www.drupal.org/node/1692262

After reading the posts the best thing to do was to uninstall the the devel module, once i did that the WSOD is gone, but what if you need the devel module?

I'm struggling to get the errors up and work out where i have gone wrong. Doesn't Krumo need devel?

  • 2
    Find out what the actual error message is (using the info in the posts you linked to, every WSOD will have one), then work out what it's complaining about, and go about fixing it...that might involve reporting a bug to the devel (or other) module if that's the problem, changing your server config, removing other modules that are conflicting, etc. There isn't enough information in your question to give anything other than guesses, a person with access to the server needs to do the initial debugging work – Clive Aug 17 '15 at 15:52
  • Hi Clive thanks for that I will edit my question, sorry for the mix up. – jelly46 Aug 17 '15 at 15:54
  • 1
    /update.php can sometimes be helpful in getting information about WSOD as well. – sareed Aug 17 '15 at 15:57
  • 1
    Is the WSOD site wide or a single page like the first links question? – sareed Aug 17 '15 at 16:10
  • 1
    If you check your web server logs (apache/nginx/fpm) you should find the real error (WSOD is a fatal that Drupal can't recover from basically, so Drupal itself won't be able to tell you what's wrong). Krumo does need Devel in this context, but devel won't be catching the errors – Clive Aug 17 '15 at 16:54
2

This is not a complete solution, but can help.

If you want to look at something but dont want to spend the time investigating your site's aversion to the devel module, then drupal core's watchdog call can be helpful. Also, I am assuming you have dblog or weblog module enabled to catch the error messages. To make it more readable, like a krumo output, I often add my Explain function to a custom module somewhere. Then in the place where I would have used krumo($target); I use watchdog('bug_hunt', explain($target, 5, 'target') ); and go to /admin/reports/dblog and filter for bug_hunt. That 5 is arbitrary in this case; 4 steps into something can get you target->field_one[und][0][value] = Content.Since I have that function terminating the recursion with html line breaks, it reads well in the log pages.

I started doing this when I was trying to expound on processes that did not have a page for krumo to inject into (maestro module workflows, etc). Since then, it has been a reliable fall-back method for me.

The better solution would be to spend the time finding why devel crashes your site, as it might be an issue that will appear again later on.

  • Hi and thanks @DeveloperWeeks where would i place the watchdog code? No I don't have dblog or weblog. – jelly46 Aug 18 '15 at 9:59
  • 1
    Install dblog module. This will let you go to /admin/reports/dblog and see all the entries of errors and notices that drupal records. It will also enable you, if you have command line and drush, to use the command drush ws --tail and see the errors come in while you load the page. – DeveloperWeeks Aug 18 '15 at 15:23
  • thanks for that, i don't have drush yet, but all I know is now that i have uninstalled devel things work fine. – jelly46 Aug 20 '15 at 9:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.