Featured Link

Live Blog Stats
«  
  »

WordPress Automatic Upgrade: Fatal error Cannot redeclare pclziputilpathreduction()

By kramfs, on June 11th, 2009

There is a minor WordPress update today, version 2.7.1. Since v2.7, they have introduced an automatic update feature that is part of the core WP. It will detect and compare your current installed version against the latest available in WordPress repository.

If you have v2.7, you should see the following once you login as admin.

image

Clicking on the “Please update now” link should bring you to the upgrade page:

image

As a precautionary move, I first check that I have the latest backup including DB and I hit “Upgrade Automatically”. Normally it should update say upgrade successfully but instead I encountered this error:

Downloading update from http://wordpress.org/wordpress-2.7.1.zip

Unpacking the core update

Fatal error: Cannot redeclare pclziputilpathreduction() (previously declared in /home/myhome/public_html/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php:5421) in /home/myhome/public_html/wp-admin/includes/class-pclzip.php on line 5498

 

I tried it on my other WP sites and encountered the same issue. I guess it has something to do with plugins as most issues encountered on WP are related to plugins. I went to the plugin page and inspected each and every plugin I have installed. And there you go, It may be conflicting with WPAU or WordPress Automatic Upgrade plugin by Keith Dsouza.

image

This plugin has the functionality as the name says to upgrade WordPress automatically. You just follow a series of questions and you will end with an upgraded version. This plugin has done its job perfectly prior to v2.7 version.

I deactivated WPAU and tried the upgrade again using the functionality provided by WP core. This time, it went without a hitch:

image 

This just means the function provided by WPAU is so important that it got incorporated in the WP core. I very much agree. I guess I can say that WPAU can retire now and thank you very much.

  • Share/Bookmark

Related posts:

  1. WordPress image upload http error If you’re one of the frustrated users who are...
  2. WordPress MySQL database error: Table is marked as crashed and should be repaired Technorati Tags: mysql database error,table marked as crashed,repair mysql...
  3. Issue with Theme Test Drive Plugin after upgrading to WordPress 2.8 After upgrading to WP2.8, I found out that I...
  4. Manage WordPress blog via mobile phone If you’re looking to manage your WordPress install via...
  5. Turbo-charge your WordPress blog using Google Gears What is Google Gears? Google Gears (or GG) is...
  6. Upgrading to the latest dd-wrt firmware version If you’re one of those who braved to install...

June 11th, 2009 | Category: Web 2.0, blog | View Comments
  • Thank you, I did as you suggested and it worked perfectly.
  • Steve
    In fact, I've now deleted ALL plugins, and it still won't update. just gets to "Unpacking the core update" and stops
  • Steve
    Even deleting said plugin many people still can't get past the "unpacking the core update" step. Webpage goes straight to done. File is downloaded and complete, archive tests ok. Even then manually deactivating every other plugin results in the same fail with no error message.
  • Thanks by the explanation. I didn't know that WP incorporated this fuction, but that is logical.

    I updated my version of WP. Thank you so much :D
  • ena
    I didn't know that WP has its own auto-update function now. I got the same error and found your post. WPAU was an invaluable plugin and I'm happy it's function is integrated WP core at last.
  • Thank you SO MUCH!!!! I really appreciate it :) ;)
  • Thank you for sharing this solution.

    Much appreciated that you took the time.

    regards,
    patrick
  • Chris
    Hey thanks, I found this via a Google search and was able to figure the problem out and now my blogs are updated. Good work, thanks for posting this.

    Chris
  • Satya
    Nice Post. Helped me upgrade WP on my domain inetminds.com .
  • Dude,thanks a lot man. I was looking for the cause of this problem but bah your solution did work. I didnt know that the plugin itself was the cause of the problem itself !
  • I was having the same problem. Thank you for confirming my suspicions.
blog comments powered by Disqus