I try to follow cardinal rules of data management that were drilled into me since I got into computers at university by (#1) taking backups often and (#2) keeping stuff organized. Well, the first one caused my site to go down today because I didn’t really follow the second one.
I try to keep on top of things by doing a full site backup at least once a year, on top of doing periodic database and blog backups. When I finished the full backup today, it stored the tarball (a compressed .tar.gz archive) in my hosted account right next to two other huge ones from last year that I forgot to delete, and it put me over the storage limit. This had the effect of returning ERROR 500 when trying to reach my site. However, I could still get into cPanel from my host’s server address, and support advised me to check the error log and replace core WP files.
The error log was full of lines containing the following:
PHP Warning: Use of undefined constant DATABASE_SERVER - assumed 'DATABASE_SERVER' (this will throw an Error in a future version of PHP)Then I noticed that the file size of the wp-config.php file was 0 bytes.
So I downloaded the tarball from the backup I had made earlier and extracted wp-config.php. I replaced the one on the server, and everything seems to be working again.
The PHP warning above is not specific to my host or WordPress configuration, but I couldn’t immediately find a search result describing this exact problem. Then again, Google search really sucks these days, so maybe this post won’t help anybody in any case.
Here is a photo of a statue in a downtown Maha Sarakham canal that’s supposed to be the tail of a mythical river monster of ancient Thai legend, but is jokingly called “the asparagus” by everyone and has become a national symbol of corruption (the city supposedly paid over 100 million baht for it):
It has nothing to do with the server problem above; I’d just wanted to post the photo for a long time.