Lee Odden

Updated to WordPress 2.1 with minor injuries.

Lee Odden     Blogging Strategy

I did it, I took the jump to WordPress 2.1 here at BloggerDesign and it wasn’t quite as slick as I had hoped. I have done the upgrade on a few other blogs with no issues, but for some reason this one freaked out a bit.

I think it all surrounds the fact that I didn’t deactivate my plugins. You know they say to do that, but I forgot. Guess what, they mean it. When I went to run the update script, it wouldn’t do its thing. And I couldn’t deactivate the plugins as I already had the files updated on the server. To get around it, I renamed the plugin folder and then it worked great.

After getting my plugins back up and running the blog seems realllly slow. I tried to track down the issue and I think it was Headspace2. I updated it and it seems better now. If you notice it’s slow, or if it seems fine, let me know. I’m a bit paranoid now.

The more I use WordPress 2.1 the more I see what has changed. Minor things but yet not all good things. I’ll have to whip up a post on that next week.

PoorSo SoOKGoodAwesome (No Ratings Yet)
Loading...

Subscribe

Subscribe

  • This field is for validation purposes and should be left unchanged.

Please read the Online Marketing Blog comment policy

Lee Odden About Lee Odden

@LeeOdden is the CEO of TopRank Marketing and editor of Online Marketing Blog. Cited for his expertise by The Economist, Forbes and the Wall Street Journal, he's the author of the book Optimize and presents internationally on integrated content, search, social media and influencer marketing. When not at conferences, consulting, or working with his talented team, he's likely running, traveling or cooking up something new.

Comments

  1. Well your blog seems to be running fast right now *crosses fingers*.

    I’ll be looking foward to your “what’s different in 2.1” post. I upgraded and I couldn’t tell any difference other than new login screen styling.

  2. Joe Dolson says:

    Yeah, I had a similar experience – most of the blogs I upgraded had no problems at all; then WHAM…one of them fell to pieces in the upgrade.

    Don’t think it was the same issue – my problem was that 90% of the blog’s Pages were converted into posts in the default category, inexplicably. All I had to do was reload my backup of the database, then upgrade the database again and it was fine…but inexplicable, nonetheless.

  3. Things seem good now. 🙂 Thanks for the responses. I still may have an issue or two with a comment plugin though.

  4. I hope the following might be helpful for your future upgrades: The first upgrade I did wasn’t smooth at all, so for all other blogs to be upgraded, I created an identical copy of my LIVE website and called it my development environment (DEV). Then I upgraded wordpress on DEV and once all problems were worked out, plugins tweaked, db updated, etc., I “published” DEV to LIVE with a script (mysqldump + rsync combo). You can find the script along with some explanation here: http://www.andrejciho.com/wordpress/production-and-development-environments/
    (You have to have shell access to your hosting server to run the script)

  5. Andrej – Your way sounds much more complicated as you’d need to have two copies of the database and then you risk loosing comments that may come after you make the database copy. I think that WordPress does it’s best to make upgrading easy, it’s just how well the instructions are followed. 🙂

  6. Thomas, you are right about the comments thing – it would especially matter on a high traffic blogs. Not so much though if you used WordPress just as a CMS. You could, however, modify the script to skip the wp_comments table – or, really, to skip db changes altogether and let WordPress in your LIVE environment run the upgrade script instead. I had to customize WordPress code in places where it wasn’t “pluggable” and that’s what brought me to using this setup.

    And yes, this does require two databases, so that if you poke around there too, you’re not messing with live data. It gives paranoid people such as myself a little more peace of mind 🙂 WordPress itself is not the hard part if you follow the instructions, you’re right about that 🙂 – it’s if a not-so-well-written plugin stops working in a new version and you have to scramble to make it work because “the whole world sees your errors.” 🙂

    Yes, I admit, the way I’m doing it is a little complicated and isn’t for everyone, but works great in my setup – from DEV to LIVE in 10-20 seconds.