Like, don’t do that

Posted by joy

Well, the one thing I wanted to do today with the blog was to update WordPress. I have Web hosting which largely allows me to run free and all that, so I don’t have WordPress automatically updating. So, anyway, after taking a look see at the online WordPress upgrade docs, I thought I may try to take the easy way out by just making backups of the WordPress files I’ve edited and use an upgrade script provided by my host which would backup the rest of the files and install the new version of WordPress.

Uh, yeah, let’s just say that didn’t work. The upgrade script timed out twice and in the process I exceeded my hosting disk quota. At that point, I had my wonderful hosting company support involved and in the ensuing hours, there were a few restores made from last night backups, some account maintenance performed which I should have done a while ago, and for a little while my email didn’t work. And after that was fixed, the blog was throwing errors presumably because the script resumed upgrading. Oops.

At this point, everything has been restored, but I haven’t yet upgraded like I had originally hoped. Apparently, I will have to do that manually.

7 Responses to “Like, don’t do that”

  1. davermont Says:

    Ouch, that sounds pretty painful. I’ve been putting off upgrading to the latest WP; it seems like a pretty simple process (upload the new version, untar, copy in my plugins and theme, rename directories and run the updater) but it still seems to take way too long. Then a day later I feel the need to update my clients’ WP as well, and go thru the process all over again.

    Good luck with the upgrade, I hope it goes much better the next time!

  2. joy Says:


    It seems like my upgrade process will take a little longer due to the fact I’ve got a few non-clever hacks going on with the theme and the workaround I had to do concerning the podcasts. I don’t even want to think what could happen to the redirects I’ve got going on. :-)

    I’ve just got to sit down and do it at some point in the near future. My host did point me to a dead simple table backup method, so at least I’m good to go in that way.

  3. cctech Says:

    That sounds like something I would do - start out on a big, arduous undertaking and, when its all said and done, end up right back where I was originally. D’oh! Its nice to have company :)

  4. Paul OFlaherty Says:

    I’m a little confused by your explanation, but I would wonder if you could clarify if its the WordPress script that failed or the script your host is using (Cpanel?).

    I’ve upgraded about 30 sites to the latest WordPress without issues, except this one creating a lot of 302 and 500 errors.

  5. joy Says:

    Good question. The Fantastico upgrade script failed - and I think the reason why is because I have a number of hacks in my installation including some very large podcast files probably where they should not be. I’ve been running various versions of WordPress since 2004, and haven’t yet blown away what I have for a purely clean install.

    For example, in order to get the podpress plugin up and running, I had to place my podcasts within a sub directory of the WP-Content directory… and yeah, that subdirectory is quite huge. As far as I know Fantastico backs up the whole darn deal - one can’t customize Fantastico.

    I actually did have successful upgrades with Fantastico in the past (but before playing with podcasts and a few other plugins for example) so that’s why I tried it.

  6. Arthur Says:

    I used to have a couple of shell scripts running to do my updates.

  7. Drew Says:

    That sound pretty painful and scarry. I think we trust all of the upgrades to work flawless.

Leave a Reply