Hurrah! Finally, I have managed to get over the demons of the past 24 hours, and get everything LOOKING as if it’s running OK. I had fears of having to completely restore my installation of wordpress and all sorts of troubles restoring the database… thankfully, this looks to have been diverted.
It was all caused by a caching plugin which had, for some unknown reason, gone up the spout. I remember playing about with the configuration of it the other day (Sunday, I think it was), and I’d noticed that there were a few error messages coming up from the site, permissions issues, etc.
I didn’t give them a second though,as it sometimes happens if the site fails to communicate with the database. After showing Richard some of the features of Wordpress, and the post I’d made about his new blog, he suddenly said my site had stopped working. And, you know what? It had. Bugger.
It was, for whatever reason, trying to access a non-existant HTML file, resulting in my custom 404 message. I’d then remembered playing with the plugin, and the .htaccess file. Fair enough, I’ll just disable the plugin, and rewrite the .htaccess file.
Logical steps to take, wouldn’t you think? Well, I’m sure they were, but it didn’t help me out any.
Now, after trying everything I could think of, I just moved all of the files from here into another directory, including the .htaccess file. And, it was STILL redirecting to this non-existant HTML file, even on a different browser, on a different machine which has never accessed my website, on a different OS, etc, etc.
Piece of crap.
Oddly, it stopped appending this file to the end, and oddly enough, I was able to move the files back in, and the front page loaded and appeared as it should. That was when I updated my site to say that it was “partially” fixed. The directories on the ste are dynamic, so for example, isn’t actually really there. Luckily, the update fixed the problem, and everything appears to be working fine.
I’d normally ask for a quick email if the website misbehaves, but as normal, nobody ever does.
I don’t know why I would require a cache plugin anyway. This site is never going to get slashotted / dugg / regaularly viewed. The only time I have ever had a rush of hits was when Jeremy Beadle died. Everything slowed down to a crawl for 10 minutes, and I had a peak in my webstats like never before, but the hits soon withered away like Jeremy’s little hand… oh, that was terrible, I apologise for that.
Technorati Tags: broken, fixed, jeremy beadle, wordpress