Today I was doing some minor tweaks via standard admin settings to my theme (Garland) on www.whatsthatpicture.com
I was also doing some layout changes to the embedded Gallery2 (2.3.1) installation.
I didn't install/remove any modules. Nor did I upload any files or make any content changes.
I think it was whilst I was changing the default theme in Gallery2 that it suddenly hung and all I could do was go back and try again. But from then on I started getting memory errors (which I have encountered from time to time before) but also the dreaded White Screen of Death (most noatbly the home page). For a while the embedded Gallery pages were working fine, including all the Drupal derived elements like the navigation. But now they are not.
I have increased the memory in php.ini (at one point to 512MB), cleared all the cache tables in the db, and also via the db disabled all but the essential modules (including disabling the Gallery2 module). But still memory errors. Oddly the standalone access to the Gallery, which in the past has given me memory errors, is working fine (www.whatsthatpicture.com/gallery2)
So every Drupal derived page is now returning a message along the lines of:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 74 bytes) in /usr/home/mysite/public_html/includes/database.mysql.inc on line 160
I have tried just quite a few of the fixes described on http://drupal.org/node/158043
Unfortunately I don't seem to be able to get to my host's error logs, or at least when I do they appear empty!
Can anyone suggest how I might investigate this further please? I just have a feeling that whilst doing those config changes in Gallery something somewhere has been corrupted.
Thanks, James
Comments
FIXED, finally!
Hi, after much head scratching, several re-installs, and more htaccess/php/mysql database config changes than you could possibly imagine, I finally have this fixed.
It looks like there was some corruption in the database, or at least incompatibility.
In essence this is what I ended up having to do:
- In settings.php change the following to TRUE so I didn't have to login:
$update_free_access = FALSE;
- Then called /update.php?op=info and updated the database for four modules, including Views
After that I was then able to access everything, login, and re-enable in the admin screens all the modules that I had previously disabled in the 'system' database table.
I'm guessing I simply tried to do too many things at once, and without keeping notes, and hence didn't have enough of a clue what I had done that had made things go wrong!