Fixing The WordPress 2.7.1 Upgrade Glitch

by Michael Johnston on 02/11/2009

One of the most eagerly awaited features in WordPress 2.7 is its automatic update function. Where WordPress upgrades have historically been, to say the least, a pain, version 2.7 and beyond promise to erase the memory of that pain with just one click.

This is fantastic – when it works. Today WordPress 2.7.1 was released and immediately I decided to put the new automatic update feature to the test. Alas, it didn’t work as advertised. After clicking on “Upgrade Automatically,” I encountered a puzzling Connection Information screen that seemed to want FTP credentials. No further documentation on what those credentials should be could be found. After digging around, I discovered the problem was a permission issue: all the WordPress files and directories need to be owned by the same user id as that of the web server process; in my case, this was Apache. Executing the following Linux command in my WordPress directory cleared up the problem.

chown -R apache.apache *

After running that command, the automatic update feature worked exactly as advertised. So, if you’re running WordPress 2.7 and are having problems with automatic updates, checking and correcting the ownership of your WordPress files might clear up the problem. Bear in mind that you need to be root in order to run the command shown above. If you’re running on a shared web hosting account, chances are that you’ll have to perform the upgrade manually. As always, don’t forget to backup your files and your database before performing the upgrade.

  • Thank you, thank you, thank you. I had tried to use the auto update before, but always ran into the connection problem issue. Doing the above fix solved the problem for me! Thanks for posting.

    Kirby
  • Michael Lyman
    I run command line through ssh command line. so for example:

    ssh username@myserver.com

    from putty on windows or terminal on a mac will get you to the command line. You might have to ask your host for ssh access and some shared hosts do not provide ssh access. Another great way to run update is with svn. I've moved to the svn method on most of my installs. Mainly because I setup svn update before 2.7 was released so old habits die hard. The article Installing/Upgrading Wordpress with SVN is a great tutorial. Setting up svn is a little tricky but once complete it works great. If you're not on svn update then I recommend sticking to the 2.7 auto update features.
  • taylor
    Very nice! This fixed my problem.
  • kevin
    Hi, I've never done this before...

    How exactly do you run this command on a host?
blog comments powered by Disqus