WordPress puts food on my table.

Some WordPress 2.0.5 users reporting Server 500 error

If you are part of the small minority of WP users seeing 500 error messages (or anything about 302) after upgrading to WordPress 2.0.5, listen up.

First, download this plugin, upload it to your wp-content/plugins/ directory and activate it by going to the “Plugins” menu and clicking “Activate” next to the “WordPress 2.0.5 Tuneup” listing. If you get the error message after logging in and thus cannot click the “Plugins” tab, manually type {WPDIR}/wp-admin/plugins.php into your address bar.

Second, that was my fault. Very sorry about that. This bug was reported for WordPress 2.1 on Trac, and it slipped my mind that the same change had gone into 2.0.5

The good news is that it’s a small minority of people that is affected, and the problem can be fixed with a plugin. I’m not sure if this means a version 2.0.5.1 will be coming out… I’ll discuss it with Matt and Ryan. Please let me know if the plugin fixes the issue for you, and spread the word to other affected people, if it does! If you see anyone recommending that people stay on 2.0.4, point them to this post. 2.0.4 has security issues, so staying on that version would be very foolish.

Forgive my commentary.
But that was one hell of an issue which “slipped” your mind.
Please consider reissuing this update as opposed to only relying on a plug-in as it is the more professional and secure thing to do. WordPress should never rely on quick fixes. Microsoft implements the same strategy with Explorer and look at how many problems they constantly have with hackers and script kiddies.

Please consider reissuing this update as opposed to only relying on a plug-in as it is the more professional and secure thing to do.

Reissuing the update with the same version number is a bad idea. People who have already downloaded it won’t know which version they have. That leads to confusion. If the software changes, the version number should change too.

There’s no security issue here. It’s a PHP bug that WordPress will have to work around.

WordPress should never rely on quick fixes.

Unfortunately, the change that caused this problem was needed for another group of people (another very small minority). So one group needs the change, or WP is broken, and for another group the change breaks WP. We obviously want a solution that works for both of them (and of course continues to work for the vast majority unaffected by these issues) but it’s a tricky issue, and there isn’t an immediately obvious solution. So the plugin is here for the small amount of people who are having a problem, so their blogs at least work (and have the security updates in 2.0.5) until we can come up with a solution that works for all server setups.

If you are one of the people affected, we’d appreciate it if you’d speak up on the wp-testers list so we can work with you to develop that solution.

hi mark…
i haven’t upgrading my 2.0.4 to 2.0.5 cause of this bug…
why don’t u relelease the fix with WP 2.0.5.1 for example?? so the people don’t get worry to upgrading their wordpress to 2.0.5 to fix the security issues that u mentioned before.

why i can’t publish my post??
all works fine….but after i finish writing and click publish, it’s fine..
but there’s no new post in my blog??what’s wrong??i’ve already upgraded to 2.0.5 and install your plugins

Because the change that caused this problem was needed for other people. We could just revert, but then they’d be having problems again. We need to find a solution that works for both groups of people before releasing a new version. That’s why I released this plugin… I didn’t want people to be forced to stay back on 2.0.4 in the interim.

I don’t know what issue you’re having with publishing posts, but if it persists with all plugins disabled, you should file a ticket on Trac. Be specific about your setup and the steps to reproduce.

After upgrading from 204 to 205 wordpress seems to work as usually, but every time I try to change or delete an existing post I get the 500 internal server error. Installed your plugin but it still don’t work. Had the same error when upgrading from 203 to 204 and fixed it by deleting all files in the cache directory without any additional changes to wordpress files. This time it won’t help. What else can I do?

i’m still getting the error. I actually had it already before the 2.0.5 upgrade. turned of al the plugins except this one, still get the error. For example: when I save the edit of a link the 500 internal server error returns. Also with a plugin to generate google sitemaps, if i try to make a sitemap it returns me the %@*# error :S

has it something to do with the chmod on the ftp server? or an mysql configuration? I have no clue what is causing this error. i’m going to search for my server error logs if there are an :S

Warning: Cannot modify header information – headers already sent by (output started at /home/ekowanz/public_html/wp-config.php:24) in /home/ekowanz/public_html/wp-content/plugins/wordpress-2.0.5-tuneup.php on line 25

I have upgraded from 2.o4 to 2.05. When trying to rebuild the database I get the internal error. I loaded the plugin. When entering {WPDIR}/wp-admin/plugins.php in the adressbar I get the same message that my database is out of date. What should I do????

I install today on my hosting site, from scratch, WordPress 2.0.5 and noticed the 500 internal server errors too. After install the WordPress 2.0.5 Tuneup fix, I have now by default the 500 internal server error. I can’t even login as wp-admin (500 internal server error)

I tried posting this at the site with the plugin but there was an error so i will post it here:

Thanks for this! I was banging my head against the wall trying to access WP’s dashboard when hosting with Yahoo.

So, for anyone who is using Yahoo web hosting and is getting the following error:

The document has moved here.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

This solved it.

The trick is, since you can’t access the dashboard, you can’t activate the plugin. so i had to go into phpMyAdmin and add the following line to my wp-options > active_plugins row.

i:0;s:26:”wordpress-2.0.5-tuneup.php”;

Add that to the end right before the last bracket ‘}’. you’ll need to change the 0 to the correct number. just look for the last ‘i:’ in that line and look at the number after it. add one and change 0 to that number.

Heads up for anyone affected by this bug. I’ve put fixes into the SVN repository for /trunk/ and /branches/2.0/ Testing would be appreciated! Be sure to remove the tuneup plugin and revert any changes you made to WP core. Let me know how it goes!

I’m wondering if all the problems I’ve been getting with WordPress can be fixed with this plugin. I am planning to set up the blog on a different host and kept getting the 500 errors and can’t log in. And sometimes when I do log in, when I’m supposed to be in the dashboard, I still see my main page. Is this going to fix that?

Also, it seems to be so terribly slow to update. Could this also fix that as well? I’ve been scratching my head since I wasn’t sure if it was my new host or whatever.

Argh!!! I think I’m getting this error thing. I have installed the plug-in fix, but everything’s still the same.

Here’s what’s happening – I have two feeds: a worpress feed and a feedburner feed. The feedburner feed, I think, is getting the 500 error – in bloglines, it shows a red exclamation point, and the error states that “The feed does not appear to exist. This can be caused by the feed URL being incorrect, or it can be caused by a configuration issue with the server hosting the feed.”.

The wordpress feed just doesn’t seem to be doing much – in bloglines and in google reader, my most recent post is not appearing. Two people using netvibes as their aggregator DID receive my latest post.

The server error goes away, but there is a feed parsing error. Seems that there is extra white space in the xml declaration. Most of the site works without this plugin, so i’m leaving it disabled so feeds work…

Somewhat late I know – but it was only now that I (a) got round to upgrading to 2.0.5 and (b) working out why it didn’t work😉

Having found that the 302 errors I was seeing went away after reverting to “PHP4 Apache module mode” from “PHP4 FastCGI mode”, I (fortunately) found your plugin, which meant I avoided having to decide whether to downgrade my WordPress version, or continue to run without the benefits of FastCGI.

I also have the Problem, with the 500. So I downloaded the plugin and loaded it up again. I tried to aktivate it, but i can’t enter any pages of my wordpress. So I changed the file pluggable-funktions.php as u said. But it is still not working. Help me please!!

I just realised, that I already installed the 2.0.6 Version. So how can I still get this Problem?? It always appears first, after I have been in Settings and PErmalinks. I also changed the link appearance once. Could this be the Prob??

Thanks for the plugin, it worked a treat on my blog … it took me quite some time finding the fix, now I have I’m over the moon.The 500 error only occured when adding new blog posts in my case. Thanks again.

Disable this by placing two forward slashes in front of that line, like so:

// status_header($status); // This causes problems on IIS

After I added the two forward slashes, I saved and closed ftp. Now when I look at that code again in ftp it is completely blank. Is that a problem? I’m not sure I’ve done anything positive here…please advise. Little worried I may have messed something up, though the site seems to be okay thus far.

My other site didn’t fair as well…I uploaded the plugin and got a 500 error upon trying to write a new post. Then I manually changed the code in the pluggable.php (not pluggable-functions.php) adding the two forward slashes and I ended up with a white screen on the new post page. It would load the top portion of the new post page quickly, but it couldn’t seem to finish the bottom of the post page…it would white out the bottom portion, though there was no error code.

Ask a WordPress Dev

Do you have an interesting WordPress-related question? Submit your questions, and I'll periodically pick the best one and answer it here on my blog! It can be anything from usage tips to hardcore WP development questions.