Wordpress 2.7.1 update and the old Wordpress Automatic Update plugin

Written February 11, 2009 in wordpress

Jump to comments

Wordpress 2.7 included a new automatic update feature — tools -> upgrade — that replaces the functionality that was previously only available from a plugin. Unfortunately, the new feature is completely incompatible with the plugin.

If you’re trying to auto-upgrade your plugin and you get a hang at “Unpacking the core update”, then you need to deactivate AND delete the old “Wordpress Automatic Upgrade” plugin (most recent version: 1.2.2) before you can successfully use the new upgrade function in Wordpress.

9 comments on ' Wordpress 2.7.1 update and the old Wordpress Automatic Update plugin '

Thanks, this has been discussed in a more detailed manner here:

http://kramfs.com/web-20/wordpress-automatic-upgrade-fatal-error-cannot-redeclare-pclziputilpathreduction/

Written by Andy Lau on February 13, 2009 at 1:26am
Even with that (non buggy, perfectly functional) plugin removed, many people are still getting hung at “Unpacking the core update”. Removing the update plugin only got us past the download problem. Even deactivating all plugins doesn’t get past the unpacking.

Written by Exceptjoe on February 13, 2009 at 2:46pm
Agreed with Exceptjoe: I had to not just deactivate, but delete entirely the plugin on all three of my Wordpress installs.

Written by karlkatzke on February 13, 2009 at 3:55pm
Deleting it didn’t work for me, and there’s no .maint file. Still looking for an “automatic” solution. Shame the perfectly good plugin god ruined

Written by Exceptjoe on February 13, 2009 at 7:46pm
In fact, I’ve now deleted ALL plugins, and it still won’t update

Written by Exceptjoe on February 13, 2009 at 9:04pm
Hmn. It worked for me after I deleted it. Check that either your webserver user is the owner AND group or that you have permissions set to 777 on your entire directory… and that zip utilities are installed on the server. I wish that Wordpress had included more debug functions to tell us what was wrong…

Written by karlkatzke on February 14, 2009 at 12:11am
Thank you. It was OK for me just deactivating the plugin.
Congrats

Written by serantes on February 14, 2009 at 3:01pm
Nope, this didn’t work for me. Why did the WP people have to mess up such a good thing?

Written by Mitch on February 17, 2009 at 1:50pm
Deactivating all plugins on my site worked for me. Even I had not the update plugin installed…

Written by Vicente on June 17, 2009 at 11:49am