I’ve been having this problem for some time now and I’d really like to know how to fix it. This is, I think, the third upgrade I would have to do manually and while that’s not a problem in itself, the auto-updater would really make life easy when it comes to plugin updates.
So while manually updating does solve the immediate problem, I’d really be grateful if somebody could help me out fixing the auto-updates.
I’ve also been having this same issue, please, if anyone knows what’s causing the fail please help.
Thanks.
on some servers you can chmod /wp-content to 777
do an upgrade then chmod back to 755
should work after that
Unfortunately, that doesn’t work. I’ve tried chmoding the dirs before, but it makes no difference for the error.
Thanks anyway, though 🙂
I, too, have tried the 777 route to no avail. One is forced to wonder when this/these annoying bug/s will be squashed. It’s been frustrating for many, many WP versions, both for upgrading WP and for plugins. There seems to be little rhyme nor reason to which installations of WP on my server upgrade properly and which do not.
:-/
Mac OS X Server 10.5.x
