Hmm, WordPress 2.3 is starting to piss me off, or should I blame the plugins? I don’t know, but all of a sudden my blog started spewing out error 500 “premature end of header: index.php” At first I thought this was a server problem so I waited a few hours. It then just dawned on me that my other websites that run on php are working just fine so it can’t be a global php issue. Then I send a trouble ticket on to my hosting company (http://www.expedioweb.com) and the tech support guy was like “hmm it must be something with the wordpress installation, you just might have to reinstall it”. I said “no way in hell I want to do that..” (I do have backups but what a pain in the ass it is to do that).
Then I get the bright idea to move all my plugins to “test” directory, disable wp-cache and then magically the blog loaded. I then went through each plugins and enabled them one at time. So far so good the blog is working okay, but I still have no clue as to what failed. My guess is that it may have had something to do with the XML Google sitemap plugin taking to long to do its thing (execution time) – just maybe. Realistically I won’t know for sure until the blog fails again.
Sorry folks for this downtime. If you get an error 500 when you try to load this blog then know that WordPress pooped out again. What sucks about this situation is that I already ran the database-upgrade script that came with 2.3 so my db is now 2.3 compliant and I effectively can’t just upload the 2.2 files and expect everything to work as before. I do have backups but I will be losing some posts.
Let’s wait and see what happens.