Solution to Error 500 after upgrading to WordPress 2.7

by Ajit Gaddam on December 30, 2008

After I recently upgraded my blog to the latest version of WordPress v2.7, I noticed an Error 500 – Internal server error.

This seems to be a problem for WordPress blogs which are hosted by 1&1

The solution to the Error 500 – Internal Server error

1. Create a file called “php.ini” in the /wp-admin/ directory of your blog

2. In the file add the text “memory = 20MB” without the quotes

This should fix the problem

Similar Posts:

{ 21 comments… read them below or add one }

shawn January 2, 2009 at 6:16 pm

Thanks that was exactly what i needed

Reply

Gareth January 22, 2009 at 3:48 pm

What determines the 20mb? I have this issue of a 500 Error which is not specific to a task being actioned but anything updating post, normal browsing, plugin activation/deactivation. Re-Installed WP2.7 with new DB and started with the basics of plugins but still getting the error. I tried the php.ini in the wp-admins and have still received this issue.

At this point my only major changes since already running WP2.7 was upgrading to PHP5 from 4. I am not saying it is PHP5 only but perhaps and issue with PHP5 and WP2.7?

Server version: 5.0.32-Debian_7etch8-log
PHP Version: 5.2.0-8+etch10
WP Version: 2.7 (Current Release as of 20th Jan 2009)

Reply

KC January 26, 2009 at 10:03 am

Tried it but it didn’t work. I upped the memory to 30Mb, still no joy.

Reply

ashutosh February 13, 2009 at 8:39 am

solution from error 500 that occur for solaris webserver

Reply

Clay February 27, 2009 at 1:57 pm

You’re a genius! thank you thank you thank you!!

I was looking like an idiot – you saved me!

Clay
Richmond, VA

Reply

Jason March 7, 2009 at 8:18 pm

Did you have to wait a bit of time for the php.ini to kick in? Hosting off godady here, but same problem.

Reply

andy March 21, 2009 at 5:16 am

I am having the same problem, unless I use the admin email address when posting (without logging in first) in which case the result is just a blank page with no post. Please help, it’s unbelievably frustrating and I’ve been looking for days…

Reply

andy March 21, 2009 at 5:17 am

oh by the way, it only happens in IE7, it’s fine with other browsers…

Reply

rl July 3, 2009 at 5:41 pm

You saved me!

Reply

Alex July 6, 2009 at 2:22 am

Had this problem after installing atahualpa theme. Your solution worked fine. Thanks for posting this :-)

Reply

Dana July 8, 2009 at 5:03 am

My problem is solved now. Thanks.

Reply

Lilmad October 10, 2009 at 5:51 am

Thanks a lot for this tips cause i was desperate to find the solution.

Reply

garrett October 22, 2009 at 8:38 pm

Your ROCK!!! you have fixed the only problem i’ve been having with wordpress.

Reply

Luciano October 24, 2009 at 6:09 am

I have the same error :
The website cannot display the page
HTTP 500
Most likely causes:
The website is under maintenance.
The website has a programming error.

The ini file did’nt fixed the problem.
Other suggestions?
thnx!

Reply

Ajit Gaddam October 24, 2009 at 5:22 pm

my guess would be an issue with plugins. I would start by deactivating all your plugins. If you can’t access them using Wordpress GUI, just SFTP to your web server and rename the plugins folder. That should deactivate them all. Then start enabling them one by one. Usually the problem plugins are wpcache and sitemaps.

Reply

bill January 5, 2010 at 12:00 am

thank you so much for posting this. It cleared up a real problem for me!!

Reply

Vi January 13, 2010 at 2:42 am

Thank you Ajit. I got such problem after WP upgrade from 2.8 to 2.9, but “memory = 20MB” fixed it.

Reply

Julien February 10, 2010 at 11:39 am

Cleared the problem for my Wordpress 2.9 admin section. Thank you for taking the time to post this fix.

Reply

Accidd April 2, 2010 at 2:15 pm

Finally! Thanks a lot! Upgrade to WP 2.9 gave me that error. This fixed my problem.

Reply

Website Flipping Advice June 24, 2010 at 11:34 pm

Thanks soooo much. I was scared for a moment there. Worked like a charm, your a champ!

Reply

fb August 25, 2010 at 2:07 pm

I don’t know how or why but it WORKED. THANKS SO MUCH FOR THIS QUICK FIX.

Reply

Leave a Comment

Previous post:

Next post: