I had a WSOD and followed the instructions to run wsod_emergency.php (couldn't log in). After running the script I was able to get the Access Denied screen in maintenance mode but could not login from my laptop, but was able to connect remotely to another computer whose cookies were intact. I logged in and was able to take the site out of maintenance mode and I was back in business. (HOORAY, THANK YOU!)

Now I cannot log into the site from either computer. I am user/1. The client cannot login either. I have tried dumping all domain, session and path cookies on two browsers with no luck. The error log shows multiple instances of the following:

PHP Fatal error: Call to undefined function drupal_get_headers() in /mydomain/sites/all/modules/dtools/wsod/wsod.module on line 102

Was I supposed to un-install Dtools to avoid this? I don't see this fatal error noted in the README.txt.bCan I simply remove Dtools from the module directory or is an "uninstall" protocol necessary? Please advise.

Comments

kenorb’s picture

kenorb commented
Status: Needs review » Active

Hi,
Uninstall of DTools is not necessary, so you can remove it.
If you're using 1.1, probably 1.x is more up-to-date.

Milkrow’s picture

Milkrow commented

Thank you for that info. I removed Dtools and ran update.php (changed settings.php to gain access) and I still am unable to to login. I've submitted a support ticket to the host to determine if there is some sort of protection on the server that would prohibit me from this operation of accessing the login, but some other issue may be at hand. I tried changing the default theme to minelli in settings.php and I got the WSOD again, but that clears up when I use my customized version of Zen. I'm unusre what that means or if Dtools can play any part in my salvation at this point. Any suggestions are welcome.

kenorb’s picture

kenorb commented

Some hosting providers allow to create php.ini on your local account (also .htaccess with some PHP memory changes). You could check that and eventually try to increase some memory and what's important, to enable displaying of the errors.
See:
http://drupal.org/node/158043
http://drupal.org/node/207036

Milkrow’s picture

Milkrow commented

Update: I tried increasing memory and set up the display of errors, but after removing Dtools, I wasn't getting any fatal errors. I still could not determine why I was not able to log in. Eventually, I decided to create a new sub folder, install 6.26 and hook it to a new database then import a backup to see if I could access the new install. It worked! I had only a few days of possible content to account for (luckily this site doesn't change too frequently). Thank you for all your help. I wish I'd tamed the savage beast of this login issue, it would have felt satisfying. Alas, I conquered another demon instead. For anyone reading this string who might be intimidated by the "fresh install" approach, doing so in tandem with any compromised site can be liberating, but not necessarily a solution for everyone, I realize. Thanks for the help kenorb, I appreciate it.

kenorb’s picture

kenorb commented
Status: Active » Closed (fixed)

That's great it worked. You welcome.