Comments

  1. “Deactivate” WPAU, and then try again to upgrade from within WordPress. It worked for me.

    December 10, 2008 at 10:18 pm |
  2. […] Den schlausten Menschen der Welt gefragt und Google brachte dann auch gleich diesen Artikel, der beschreibt, wie man damit umgehen muss. Einfach WordPress Automatic Update (WAU) […]

    December 11, 2008 at 7:39 am |
  3. Yes, it worked for me too. Thank you!

    December 11, 2008 at 11:28 am |
  4. […] 升级到wordpress2.7汉化版时出错Fatal error: Cannot redeclare pclziputilpathreduction […]

    December 14, 2008 at 5:03 am |
  5. Ah, yes. That fixed it for me. Thanks for sharing.

    Anthony

    December 18, 2008 at 6:34 am |
  6. Wow. Thanks for the tip. Absolutely fixed my issue.

    December 18, 2008 at 8:44 am |
  7. JD:

    Many thanks! This did the trick for me!

    December 22, 2008 at 10:26 pm |
  8. Thanks for the fix it has worked for me :)

    December 23, 2008 at 5:25 pm |
  9. Thanks a lot, it worked :D

    January 24, 2009 at 11:03 pm |
  10. jack:

    thank you!

    February 10, 2009 at 5:33 pm |
  11. Perfect! Worked for me upgrading to 2.7.1. Thank you very much!

    By the way, you’re the first result in Google when searching for this error. Congrats! ;)

    February 10, 2009 at 6:49 pm |
  12. Thanks! That saved what probably would have been a lot of hassle tracking this one down.

    February 11, 2009 at 12:38 am |
  13. Thanks. Helped me out as well. But it makes me recall I guess something I read about making the automatic upgrade plugin as part of the core code. Is that it or am I just day dreaming?

    February 11, 2009 at 1:46 am |
  14. […] to this topic and this post it was caused by the WP Automatic Upgrade plugin wich i forgot to remove when upgrading to WP2.7, […]

    February 11, 2009 at 6:51 am |
  15. Thanks for the fix. WordPress is getting easier and easier to upgrade at last.

    February 11, 2009 at 10:10 am |
  16. Dan:

    Wow, thanks… that worked!

    February 11, 2009 at 10:44 am |
  17. how do you upgrade to WP 2.7 with in wordpress?

    February 11, 2009 at 12:12 pm |
  18. I sure hope WP eventually makes their auto-update as easy to use as WPAU. I kept getting very unhelpful error messages and finally got it to work, but not before being left with several directories’ worth of files with wide open permissions. Not anywhere near as easy to use as WPAU was.

    February 11, 2009 at 1:33 pm |
  19. Beautiful, upgrade worked in a few seconds after i followed your advice. Hope WPAU gets an upgrade soon as well, as I had used that for the better part of the year before this error happened.

    Thanks!

    February 11, 2009 at 5:20 pm |
  20. […] To fix this I had to turn off the ‘WordPress Automatic Upgrade Plugin’ that was formerly required for automatic updates.  More details here. […]

    February 12, 2009 at 6:55 am |
  21. Thanks!

    February 12, 2009 at 4:31 pm |
  22. Tks! Deactivate WPAU, and then try again to upgrade from within WordPress. It worked for me too.

    February 12, 2009 at 6:44 pm |
  23. Thanks, it worked for me. For a sec, i was afraid of what was happening before i yahooed the error and came to your site.

    February 13, 2009 at 2:39 pm |
  24. Jason:

    Brilliant! Thanks a ton

    February 13, 2009 at 2:51 pm |
  25. Thanks! Worked great!

    February 13, 2009 at 6:05 pm |
  26. […] 最开始以为是服务器的链接有问题,试了很多次仍是如此。交给狗狗后知道原来是以前的自动升级插件与现在Wordpress自带的升级系统冲突,将WPAU插件取消激活后问题得到解决。升级时Dashboard上的侧边菜单在完成Upgrade的那瞬间在Firefox下显示完好,但完成后还是跟之前一样,下拉菜单仍然乱乱的。 […]

    February 13, 2009 at 9:44 pm |
  27. Thanks mate, worked.

    February 14, 2009 at 7:41 am |
  28. Wow. That was ridiculously simple. I cant believe all the other stuff I’ve read got so technical.

    Thanks.

    February 14, 2009 at 11:44 pm |
  29. Thank you so much. I have been banging my head for a couple of days now trying to upgrade to 2.7.1. Feel kinda silly it was that simple, although I have come across several plugin incompatibility issues with 2.7. Should have known to go straight to deactivating plugins.

    Anyway, thanks again!

    February 16, 2009 at 3:07 pm |
  30. […] La solución sin embargo no fue tan difícil, basta con desactivar ese poderosísimo plugin llamado WPAU (WordPress Automatic Upgrade) y luego intentar nuevamente actualizar automáticamente y no nos aparecerá ningún error. […]

    February 16, 2009 at 11:43 pm |
  31. Thanks so much – worked just fine for me!

    February 18, 2009 at 6:23 am |
  32. Worked like a charm for me too. Thanks for the post! 2.7.1 working perfectly!

    March 4, 2009 at 7:14 pm |
  33. Thank you for sharing this – I was pulling my hair out – brilliant!

    March 10, 2009 at 12:18 am |
  34. Worked like a champ. Thanks for the research!

    March 12, 2009 at 8:19 pm |
  35. […] 参考的这篇文章,正如这篇文章讲的 If you have the formerly wonderful plugin WordPress Automatic Upgrade, deactivate it. Then proceed to update WordPress. It’ll work without errors. WordPress 2.7 introduces a new feature: no need to update by hand. So in otherwords, the WPAU plugin is no longer needed! (But thank you, WPAU plugin, for all of your hard work.) […]

    March 14, 2009 at 12:27 pm |
  36. darcy @ lwm3b:

    Thank you! This was the upgrade fix.

    I appreciate you posting the update and fix. Thanks!

    April 27, 2009 at 4:45 pm |
  37. Socks:

    Thanks – didn’t have a problem with 2.7, but 2.7.1 vexed me mightily! Appreciate the fix!

    May 21, 2009 at 8:10 am |
  38. it’s so nice to find instant solutions – thx Ryan!

    also (could be coincidence ??), but it didn’t work right away for me – i had to also deactivate WP Database Backup plugin. Of course, i also deactivated other plugins at the same time but since they’ve given me no conflicts previously, I’m guessing it was a tandem solution with WPAU and WPDB – at least, in my case…

    THANKS again!

    PS

    …it seems that i had to deactivate ALL of my “WP-” plugins to get rid of the error, then re-activate them afterwards. (hmmm)

    …haven’t had this problem with any other of my blogs..???

    May 25, 2009 at 8:43 am |
  39. Phil:

    Thank you, thank you, THANK YOU!!!! I was racking my brain over this one. Found you via Google search–you were first result for the error message.

    June 18, 2009 at 9:12 pm |
  40. Manuel:

    Thanks for the hint!

    July 23, 2009 at 9:22 am |
  41. Thank you so much!! I was confounded by that message too – didn’t imagine the solution would be this simple. Followed your advice and it worked like a charm.

    August 14, 2009 at 5:14 pm |
  42. Thanks this helped

    August 28, 2009 at 8:05 am |
  43. Thanks, this fixed it without any problems.

    September 1, 2009 at 12:28 am |
  44. It really worked for me as described above, on a Windows Server hosting isqsolutions.com.

    November 19, 2009 at 5:27 am |
  45. wow thanks! so WPAU is the culprit! this post helped me a lot. thank you so much again! :D

    July 8, 2011 at 3:39 pm |
  46. dvb:

    Thank you, thank you, me too. My wordpress update was foiled and you done had the answer.

    July 30, 2011 at 2:54 pm |
  47. nitesh:

    thank you for the tip

    September 24, 2011 at 7:56 am |

Leave a Reply

You must be logged in to post a comment.