By dapmcc on

Hello, I'm hoping someone can help me. I'm relatively new to all this, and self-taught from the forums and books, so I apologize in advance if I'm being thick. I had updated a module when I realized that I was logged in as an admin and not user1, so while the site was offline, I logged out. Big Mistake.

So I went to .../user, and got the login screen, but it didn't like my password, so I tried again with a few different passwords, finally went into phpMyAdmin to update the password there, tried that one, and it seemed to work, but sent me to the site offline page. When I go to /update.php, all I get is a blank white window - no error, no nothing. The only thing that might be telling about that screen is that the URL changes into .../update.php?op=info

So I went to .../?q=user, to try logging in again, and got the site offline page.
so I went to .../index.php?q=user, and still got the site offline page.
so I went into phpMyAdmin and ran

UPDATE variable SET value = 's:1:"0";' WHERE name= 'site_offline';
DELETE FROM cache WHERE cid = 'variables';

and still got the site offline page.
So I emptied the sessions table, and am still getting the site offline page. - to be clear, this is, unfortunately, the technical problems site offline page.

Are there any other tricks I can try? Am I actually logged in, but having some other problem? Is there a limit to the number of times you can try to log in, so maybe I locked myself out of the admin interface? I should still get the login page, though, shouldn't I? MySQL server is running fine. I haven't touched settings.php. any ideas would be greatly appreciated.

Thanks very much.

⋅ Categories: Drupal 6.x

Comments

bredi’s picture

bredi commented

same here. and have client presentation!

dapmcc’s picture

dapmcc commented

Hi bredi, I hope you're able to fix it as "quickly" as I ended up being able to. I finally paid attention to the "check settings.php" instruction, to see if anything had changed. It turned out that, somehow, the site had been operating off of a settings.php.bak file, but there was no settings.php file. So I copied settings.php.bak, removed the .bak from the new file, and insto presto, the site worked again! *cheering wildly*

If only it hadn't taken me weeks of poking at it in different ways to figure out where the problem lay. FWIW, I was tipped off to settings.php being the real problem by my Chrome browser on a PC. I normally work on a Mac, and was only getting the site-offline message, or the WSOD, even in Chrome. Wierd, but hey - it works now.