WSOD after installing Drupal.org testing profile
webchick - June 22, 2008 - 20:50
| Project: | Drupal.org Testing |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
When you install Drupal.org testing profile, under certain circumstances you end up with a blank white screen on every single page.
I traced this to:
<?php
variable_set('devel_error_handler', DEVEL_ERROR_HANDLER_BACKTRACE);
?>Reading further into the Devel module code, it sounds like this option is only intended for use with the Krumo library, which I do not have, so that's probably why it happened. I deleted this variable from my variables table and was able to use my site again, but this would actively prevent anyone from using this profile. :(
Note that this only affects 5.x and for whatever reason does not affect 6.x. I'm not sure if this is a devel bug or a drupalorg_testing bug, but we can fix it from drupalorg_testing.
#1
Here's a real simple fix, that just comments out the line like the line above it.
#2
I'll try to investigate this more shortly, but I think this comes about because you were using an older version of devel. I believe that the current -dev releases for devel (both D5 and D6) include the entire Krumo library, so this wouldn't have been a problem if you had also updated devel before installing the profile.
#3
I can confirm that I did download the official release of Devel module, which is not exactly uncalled for, if I was interested in ensuring that I had the most stable dependent code.
#4
You mean http://drupal.org/node/237836
This is a rather old release.
The problem with profiles is that we can't specify a certain version of the contributed modules that are used with the profile. I wouldn't necessarily expect that the profile would work with earlier versions of project* other than dev, so I'm not sure we should expect it to work with older versions of the other required modules.
I guess we could create a bunch of branches to work with stable versions of the various modules the profile uses. But you thought keeping your jquery update module synced with the proper version of jquery was difficult...
That said, not turning on debug backtrace by default isn't that big of a deal, so if that's the only way to address the problem I'm probably ok with that.
#5
Another option is pressuring the devel maintainers to releasing a new official version.
I wouldn't expect to use this profile with the stable versions of Project and Project issue tracking either; that's sort of the point of this profile is to test the dev versions. :) I was trying minimize bugs being introduced from things other than those though, so I went with stable releases of the other dependencies.
But for now, I'd recommend commenting the line out, and then marking this postponed to fix once Devel works.
#6
Let's try this instead. This way if the krumo library is present the setting will default to use the backtrace error handler, otherwise the standard error handler.
I tested this patch with the DRUPAL-5 dev release as well as the 5.x-0.3 official release of the devel module, in both cases with and without the krumo library installed, and the setting is set to the correct value in each case and there is no WSOD.
If someone can give this a quick review I'll commit it today.
#7
Awesome! Works for me. :)
#8
Committed. http://drupal.org/cvs?commit=123680
Thanks webchick.
#9
Automatically closed -- issue fixed for two weeks with no activity.