For a good few weeks all of my automatic upgrades stopped working. Meaning that they were working fine and then the next upgrade (which so happened to be for aplugin) didn’t work. I thought it was a WP 3.0.1 issue so I waited for 3.0.2 to come out and bummer. I was still getting: could not create directory wp-content/upgrade/wordpress-3.tmp/wordpress
So here I was google-ing the net for a solution, not finding one since everyone kept saying it’s a directory permission issue, which I eliminated like 3 times (including recreating the “upgrade” directory, then something hit me: I was reading in a few posts that people de-activated all plugins. I said, let’s try that. And you know, it worked.
So obviously I tried to track down the culprit and obviously I did: AskApache Password Protect plugin. Don’t ask me when that got broke or how but thing is, that one killed the upgrades.
So, I’ve done what any “sane” sysadmin would do: I deactivated the plugin and added the ap-admin with a directory apache restriction based on my local IP (which works fine since I only administer from home). Other people can add all their used IP’s (unless you’re behind a dynamic IP in case you should probably usea dyndns service)
Thank you so much! That helped me 2. The AskApache-plugin did something awful with the update-core of WP. Now my updates are working again and I’m using a directory apache restriction based on my local IP instead. That works better for me! Thank again! //David, Malmö, Sweden
Thank you.
I was also playing around the permissions for while and then i found that post…
Look in my installed plugin and bingo! the AskApache plugin was there.
Just deactivated it and the upgrade worked.
Thank you very much. Solved the issue after 2 days of trial and error. Just a small note, even though WordPress created upgrade folder I had to chmod it to 755 for it to work.