When the automatic (push button) upgrade of plugins within WordPress first became available, it was the best thing since sliced bread or maybe even WordPress itself.
But over the last few weeks, I’ve noticed that first one then several, then almost all of my plugin upgrade attempts were failing. It started with the xml sitemap generator plugin. For some reason, it just couldn’t update itself anymore, when I clicked on the option to update it from within WordPress.
Soon after that, several other plugins on several different servers on several different WP installs started having some difficulties updating too. Now, I’m just about at the point where every single plugin on every single WordPress install doesn’t seem to work.
I get a failure that looks something like this:
Downloading update from http://downloads.wordpress.org/ plugin/all-in-one-seo-pack.zip
Unpacking the update
Could not copy file: /home/Yoursite/public_html/wp- content/upgrade/all_in_one_seo_pack/all-in-one-seo-pack/all_in_one_seo_pack-pt_BR.mo
Installation Failed
After doing a little research, I came across a few people struggling with similar, if not the same problems. After catching up on the threads and the support tickets, there appears to be 3 different solutions, which I’ll list in reverse order of how they are presented (thus saving you some time).
- Upgrade to WordPress 2.8 as this is a bug cemented in my 2.7.1
- But EVEN THIS won’t work for everyone
- If it doesn’t work for you, then you will need to download this replacement file for http.php which resides in your wp_includes folder of WP
- UPDATE – This step did work for me!
- add "72.233.56.139 downloads.wordpress.org" to the "/etc/hosts" file.
- I have no idea what that means
- Disable cURL using the "Core Control" plugin ( http://wordpress.org/extend/plugins/core-control/ ) after activating the "HTTP Access Module 0.6" within Core Control.
- Note this plugin probably should not be used by people not terribly experienced at programming in a WP environment (not talking html, I mean real programming)
So that all points to step number 1 for your average user. This may be the MAIN reason to go upgrade to WordPress 2.8 if you are the type that typically sits on the fence for 3-4 weeks (like I usually do).
Resources
http://core.trac.wordpress.org/ticket/9998
http://wordpress.org/extend/plugins/core-control/
http://wordpress.org/support/topic/231500
Related posts:- Looking for Solution to Fantastico Upgrade Failure for WordPress 2.7? Today, I was working to do an upgrade on a WordPress installation created with Fantastico. This was an upgrade from 2.6 to 2.7. It should...
- Did that FireFox Upgrade Break my WindowsLiveWriter Plugin? Maybe Not! Back in December, Joe Cheng from the What Ever Blog, who also happens to be a developer on one of my favorite blogging tools, WindowsLiveWriter,...
- Looking for the Best WordPress Plugin for Managing Internal & External Nofollow Links A partial plugin solution for managing nofollol links on internal links within WordPress....
- Two Very Cool Things Coming to WordPress in 2009: Handbook and Plugin Compatibility I’m sitting at a WordCamp in Las Vegas today listening to the keynote address by Matt Mullenberg, the founder of WordPress (the software that powers...




or greeeat that sounds complicated. I’m having the exact same issue, however I upgraded to 2.8.5 and I am still getting that error.
UPDATE, what worked for me was downloading the pluggin manually, unzipping it, FTPing my site, finding the pluggins folder on the WP installation, and just drag and drop the pluggin into the pluggin folder. The same as you would do to add a new “theme” to your site.