Some weeks back, I tried to upgrade to WordPress 2.7.1. It all worked perfectly, until it didn’t. I got a message saying “Fatal error: Cannot redeclare pclziputilpathreduction”. Now, most software terminology sounds Greek to me anyway, but this particular statement seemed to be trying too hard. Pclziputilpathreduction indeed. No, don’t ask me how to pronounce that.
I googled around and found that all it means is that you still have the WordPress Automatic upgrade plugin. Deactivate the plugin and everything should be fine, a website informed me. Which turned out to be great advice. It made a lot of sense – after all, I told myself, doesn’t WordPress 2.7 already incorporate the Automatic Upgrade feature? I don’t need a separate plugin anymore.
But the Automatic Upgrade plugin remained in my “Inactive Plugins” list, as I didn’t have the heart to banish it forever. Today, I find this – ” There is a new version of WordPress Automatic Upgrade available. View version 1.2.5 Details or upgrade automatically.”
Investigation reveals that this is what the new update does : (I am quoting from here):
Update Feb 19th 2009: If you are having issues with upgrading WordPress 2.7 and above, or if WPAU is not displaying a nag to upgrade, we have released a newer version, please read the release post for WordPress Automatic Upgrade 1.2.5.
What I don’t understand though, is this if I can manage perfectly well without the plugin, why should I have the plugin, and then have to upgrade it to fix the issue? Are the creators of WP-Automatic Upgrade simply not willing to accept that the plugin is redundant in WP 2.7 ?