By graeme smith on

Yesterday I noticed I had to upgrade a module (as it happens, filefield up to 6.x-3.10). I say that only for reference - I don't think the issue is filefield. I think it's more me being bloody stupid :-(.

I was in a hurry. Yes, a bad time to do anything. I didn't set the site into maintenance mode. Yes, I'm stupid. Anyway, when I tried to do an update.php - well. Yes. WSOD.

PHP memory is at 100 M. The site still operates, and I've tried reverting back to the previous filefield. No joy. I've tried to track any error messages, but without much luck. I removed Garland (following some of the searchable WSOD items). No joy.

The site has a fair amount of data. Books, Book pages, forums, comments, users, access permissions, passwords... the usual sort of stuff. So, if I decided to stop tearing out what little hair I have left, are there any modules that would allow me to preserve all the above, but scram the site and rebuild it module-wise? Alternatively, can I just preserve the current default/settings.php, scram the Drupal install, re-install, recover the default/settings.php and retain access to the current database?

⋅ Categories: Drupal 6.x

Comments

G Gavitt’s picture

G Gavitt commented

Have you tried clearing the cache table? Have you seen this page ? http://drupal.org/node/158043

graeme smith’s picture

graeme smith commented

I had indeed seen that page, and attempted to follow some of it's directions. However, the guidance on cache clearing appears to be:

"Clearing the Cache Table

Depending on the problem, clearing the cache table (via phpmyadmin for example) can resolve a WSOD."

since this (currently - I'm still looking and trying to learn :-) ) leaves me saying a variation of 'er... duh... how do I clear cache then? Where's phpmyadmin?', I undoubtedly come over as a total idiot and make little progress. I'll keep trying to work through that page, and my thanks sir for your guidance :-).

---
The Idiot
or
Jack's shadow
or
Charlie's Driver

ayathullah’s picture

ayathullah commented

Your host should allow you to access your databases via some sort of interface such as phpmyadmin. Once you find the drupal databse look for the tables preceeede by cache_... and then clear the data in those tables.

If you want i'm happy to lend a hand

G Gavitt’s picture

G Gavitt commented

Here is a demo page for phpmyadmin.. good app to know... but see my BTW below for maybe? a quicker solution..

http://www.phpmyadmin.net/home_page/try.php

Its most likely that your provider has it setup for your site in its control panel somewhere.

Here is a thread that talks about cleaning the cache from a few angles..phpmyadmin is in there as well...

http://drupal.org/node/17620#comment-1056943

BTW most of the solutions are aimed at users with a constant wsod.. yours happens after an update... so you can also try clearing the cache from /admin/settings/performance ...

graeme smith’s picture

graeme smith commented

I took me to Admin/ Settings/ Performance, cleared cache, tried to do an update.php... and I regret, the curse of the White remains.

I'll see if I can uncover any invisible errors - I just hope they're not like invisible runes. Like Granny Weatherwax says (Witches Abroad):

She heard Nanny say: 'Beats me why they're always putting invisible runes on their doors. I mean, you pays some wizard to put invisible runes on your door, and how do you know you've got value for money?'
She heard Granny say: 'No problem there. If you can't see 'em, you know you've got proper invisible runes.'

---
The Idiot
or
Jack's shadow
or
Charlie's Driver

graeme smith’s picture

graeme smith commented

I know not if they might make things any more clear, but I've managed to uncover the following errors. They seem a little confusing to my poor wit, because I thought I'd removed Garland after reading some WSOD comments relating to it:

php
05/01/2011 - 18:56
array_keys() [function.array-keys]: The first argument should be an array in /home4/peladonn/public_html/foolandfair/includes/theme.maintenance.inc on line 220.

Invalid argument supplied for foreach() in /home4/peladonn/public_html/foolandfair/includes/theme.maintenance.inc on line 220.

include(./themes/garland/maintenance-page.tpl.php) [function.include]: failed to open stream: No such file or directory in /home4/peladonn/public_html/foolandfair/includes/theme.inc on line 1066.

include(./themes/garland/maintenance-page.tpl.php) [function.include]: failed to open stream: No such file or directory in /home4/peladonn/public_html/foolandfair/includes/theme.inc on line 1066.

include() [function.include]: Failed opening './themes/garland/maintenance-page.tpl.php' for inclusion (include_path='.:/usr/lib64/php:/usr/lib/php') in /home4/peladonn/public_html/foolandfair/includes/theme.inc on line 1066.

---
The Idiot
or
Jack's shadow
or
Charlie's Driver

G Gavitt’s picture

G Gavitt commented

Those errors are referring to a missing maintenance page. Not sure if this will help but what is your admin theme set to @ /admin/settings/admin ?

graeme smith’s picture

graeme smith commented

... system default, which is currently Acquia Slate.

---
The Idiot
or
Jack's shadow
or
Charlie's Driver

G Gavitt’s picture

G Gavitt commented

http://drupal.org/node/158043#comment-3046368

That sounds a lot like whats going on here and it looks like its a worth a shot to replace the missing maintenance page with the one in that thread .

Hopefully doing that combined with the cache clearing that you did earlier will get rid of the wsod after update.

graeme smith’s picture

graeme smith commented

.. Cleared cache, tried he update.php - same WSOD, error set.

I set Garland as the maintenance theme, cleared cache, tried update.php, same WSOD, same error set.

---
The Idiot
or
Jack's shadow
or
Charlie's Driver