Upgrading WordPress

By Shamus Posted Tuesday Sep 8, 2009

Filed under: Notices 17 comments

I’m upgrading to the new version of WordPress, which invariably means a new version will come out in about two days.

Things may be a little wonky until I get everything sorted out. Please bear with me.

UPDATE: And done. That sucked in several interesting ways. The “automatic upgrade” worked as well as it always does, which means I had to do it manually. There were files for which I could not change permissions, and could not overwrite despite having permissions to do so. I could have blown away the entire tree structure and re-uploaded clean, but my images directory is (hang on let me look) 80MB. My upstream bandwidth is such that it would take a good 20 mins just for that one directory, at least. Eventually I had to re-name some directories, then delete them, then upload new ones. Hopefully I didn’t miss anything.

Now I’ve got to upgrade a bunch of plugins. Your continued patience is appreciated.

 


From The Archives:
 

17 thoughts on “Upgrading WordPress

  1. WILL says:

    Somebody mentioned a bear? Are we expecting bear problems?

    I crack myself up, I know.

  2. Rutskarn says:

    What are the benefits of upgrading? I think I might kind of sort of be a few months behind.

    1. Shamus says:

      Rutskarn: http://wordpress.org/development/2009/09/keep-wordpress-secure/

      Short version: Upgrading keeps hackers from turning your blog into a stealth malware provider. Ew. Cooties.

  3. Matt T. says:

    I feel ya. All of my WordPress upgrades are manual ones. Not because I want them to be, but because my ISP is pretty locked down. Of course, I prefer the command line and wget, so it works for me!

    I suppose it also helps that my personal blog has an ‘audience’ that can be counted on one hand. Thus, if I mess things up, no big whoop.

  4. Blurr says:

    Your salmon don’t swim upstream very quickly Shamus? I’ve heard there are pills for that now. :D

  5. SoldierHawk says:

    Hey, good for you getting it all taken care of, though. Best of luck, and I hope the work on it you have left goes well. We’ll all be right here when you’re done. :)

  6. pwiggi says:

    I must be the only person in the world for whom the WordPress automatic update has worked flawlessly every time I’ve used it. I consider myself lucky.

  7. Rosseloh says:

    Sweet, more width.

    Wish I had the patience and know-how to run stuff on my own, instead of using wordpress’ servers.

  8. Heron says:

    Any chance you could use the opportunity to fix the “Home” link? (Right now the “Home” link is always the current page instead of the main page.)

  9. Dev Null says:

    I could have blown away the entire tree structure and re-uploaded clean, but my images directory is (hang on let me look) 80MB. My upstream bandwidth is such that it would take a good 20 mins just for that one directory, at least.

    So you did it manually, which took much less than 20 minutes? (Sorry, couldn’t resist. I too know the pain of trying to do it the way it _should_ work, instead of the way you know it will end up working…)

  10. Chris says:

    Not to gloat… OK, I’m gloating… but automatic updates have worked flawlessly for a number of highly trafficked sites I manage. The only problems I have are with plugins – usually when the plugin dev rewrites their API without making it clear in the update notes. Good times.

    Also, upgrading is a pretty easy process if you can ssh. Assuming www/public_html, you can just set up your clean install next to it, cp your wp-content, wp-config.php and .htaccess, rename public_html to public_html.bak and wordpress to public_html. Run upgrade.php and you’re done. Takes all of about a minute and a half, keeps your permissions intact and you don’t have to mess with uploading anything other than a zip file.

    You can do a similar install using FTP, but I find the command line quicker.

  11. Bryan says:

    Re: the permissions…

    I’m assuming this is some sort of *nix environment (though if not, another set of rules apply :-) ). You can’t change the permissions on a file unless you own it. (From the manpage: “The effective UID of the calling process must match the owner of the file, or the process must be privileged”. “Privileged” here means, basically, root.)

    Replacing files can also be a bit tricky. If your replacing program simply truncates the file and writes new contents, then having write permission to the file is enough. But if it tries to delete the file (which is *MUCH* safer, since you can delete a file while programs have it open, and the old copy will stay on disk until the last handle closes — so the file doesn’t change out from under any program that has it open, like say the webserver trying to run the PHP), and then create a new file with the same name, that can fail if you don’t have write permission to the containing directory.

    (Deleting and creating files is a modification to the containing directory, so you need write permission there. Truncating a file, or extending a file, is a modification to the file, so you only need write permission there.)

    Obviously I don’t know how the permissions were set up, but if you didn’t own these files in the first place, it’s entirely possible you didn’t have any permission on the containing directories either. But of course, that can be granted via groups, where the change-mode requirement is user *only*.

  12. Viktor says:

    Possibly off-topic, but I clicked “WordPress Classic” under the theme selector. The new theme seems to work, but the theme selector vanished. Is it in an odd location under this one or something?

  13. MuonDecay says:

    It would take you 20 minutes to upload 80gb? I’d think someone as active online as you are would be using an FTTH connection or something comparable.

  14. MuonDecay says:

    Er, either I meant “80mb”, or am otherwise an idiot. It’s the former, I promise.

  15. Wow. So far all my automatic WordPress updates worked flawlessly and I’m thankful for that. Every once in a while a plugin or two will break but those are minor things.

    Also, my host has a “one-click-upgrade” feature which will do the manual upgrade for you in case the automatic doesn’t work. I actually used it once to jump from 2.0.5 to 2.7. For some odd reason it worked flawlessly but it was a bit nerve wracking – I was actually biting my nails during the database upgrade. Since then I’ve been hitting the auto-upgrade button as soon as it shows up on my WP dashboard. I don’t want to lag behind seven versions again. :P

    Edited to add: there is a downside – my host is slower than slow, and goes down like clockwork every few weeks. :P

  16. sidslothh says:

    i am posting in the hopes to get to know people and get membership to the servers im a mid aged man married and fun and i also like to joke around feel free to email me or catch me in game and chat

Thanks for joining the discussion. Be nice, don't post angry, and enjoy yourself. This is supposed to be fun. Your email address will not be published. Required fields are marked*

You can enclose spoilers in <strike> tags like so:
<strike>Darth Vader is Luke's father!</strike>

You can make things italics like this:
Can you imagine having Darth Vader as your <i>father</i>?

You can make things bold like this:
I'm <b>very</b> glad Darth Vader isn't my father.

You can make links like this:
I'm reading about <a href="http://en.wikipedia.org/wiki/Darth_Vader">Darth Vader</a> on Wikipedia!

You can quote someone like this:
Darth Vader said <blockquote>Luke, I am your father.</blockquote>

Leave a Reply

Your email address will not be published.