Raj Agrawal

Learnings from software and technology

  • Home
  • Technology
  • Software
  • Work
  • Play

Connect

  • GitHub
  • LinkedIn
  • YouTube

Powered by Genesis

You are here: Home / Technology / Upgrade To WordPress 3.0 Manually And Successfully

Upgrade To WordPress 3.0 Manually And Successfully

June 19, 2010 by Raj Agrawal 28 Comments

6 essential steps to be followed for manually upgrading to WordPress 3.0 or any other version, the error free way

WordPress Logo

WordPress 3.0 a.k.a ‘Thelonious’ was released yesterday with a huge bag of improvements like Custom post types, MU merge, menu editor, Twenty Ten theme, over 1200 bug fixes making it more stable, secure and faster than ever before. But, my upgrade attempt wasn’t quite smooth.

On an average, every 4 out o f 10 WordPress upgrades are not successful in the first attempt. This is not a official stats but is in accordance with what is observed on WordPress related forums. I ran into a problem while upgrading to 3.0 where my Admin Panel was not accessible at all and it barfed up a 404 error. My first thought was to re-install WordPress (I never followed the etiquette of disabling all plugins before the upgrade process), but I decided to play wiser this time. I disabled only those plugins that were active in frequent communication with the database like WP Super Cache, WP Database backup and some security plugins to save my efforts. Deleting cached pages from wp super cache did not help. Surprisingly, WP Security Scan plugin was causing all the mayhem!

In simple words, always follow these essential steps before any manual WordPress upgrade/re-install:

  • Put your blog in maintenance mode with a easy to use Maintenance Mode plugin. Follow BloggingWithSuccess’s steps on how to install and use this plugin. Though this is optional, i recommend using it as it communicates with the readers clearly about what is going on
  • Like i said earlier, disable only those plugins that are active in frequent communication with the database like WP Super Cache, WP Database backup and security plugins. If you do not understand what this means, you should disable all plugins before the upgrade to be on a safer side
  • Login to your blog’s ftp server with your preferred FTP program
  • Overwrite all extracted files from the zipped WordPress file except for WP Content folder (It contains your blog’s themes and plugins which you don’t want to lose) and wp-config.php file
  • After the files have been overwritten, append /wp-admin/upgrade.php to your blog’s home url in the address bar and hit the enter key. This is to perform the final step in the WordPress upgrade process. So, you should be directed to the upgrade page which will look like this:
Click “Upgrade WordPress” and you are all done.

Update: I have noticed that on this version of WordPress, the links in admin panel are breaking down when a “certain number” of plugins are activated. If is the case for you then you should deactivate the unnecessary plugins and active only the important ones until a patch is available.

So, how has your WordPress installation experience been ever since you started using it?

Filed Under: Technology Tagged With: wordpress

About Raj Agrawal

A professional Mobile Software Engineer by profession, an M.C.A and M.C.P by qualification. A guitar hobbyist and an appreciator of Indian classical, folk, metal and baroque music.

Comments

  1. Justin Germino says

    June 19, 2010 at 1:05 AM

    Excellent manual tips, I myself usually do things manually or through SimpleScripts via my hosting provider. I almost never use WordPress automatic upgrade except for some point releases. Taking a backup of your SQL database is critical, but also backing up your local stored (themes/plugins…etc) are also a good idea.

    Even if you don’t have shell access to your account via your hosting provider, there usually is a way to download your site to make a backup.

    Reply
    • Raj says

      June 19, 2010 at 2:01 AM

      Hi Justin, thanks for reading this article. The backing up of wp-content folder is indeed helpful at times , especially for the theme and plugin settings.

      Reply
  2. Ishan says

    June 19, 2010 at 1:32 AM

    Automatic updates have always gone well for me. However, I have never tried the manual method. It’s not my fault actually, I started using WordPress since version 2.7 when automatic upgrades started!
    I will keep this article bookmarked.
    Thanks for including Blogging With Success post. I’m glad that you found it useful.

    Reply
    • Raj says

      June 19, 2010 at 2:07 AM

      You’re welcome Ishan. You have a great blog. Keep writing such useful articles.

      Reply
  3. Selurus says

    June 19, 2010 at 2:22 AM

    Thanks for sharing your experience, its always wise to back up database and other important files before an upgrade.

    Reply
  4. Ileane @ Ms. Ileane Speaks says

    June 19, 2010 at 8:37 PM

    Thanks for the tips. I only saw a handful of folks having problems, so I will share this with them!

    Reply
    • Raj says

      June 20, 2010 at 2:24 PM

      You are welcome Ileane 🙂

      Reply
  5. Guilherme Vaz says

    June 20, 2010 at 11:39 AM

    Thanks a lot for all those tips. I’ll be upgrading the blog from the company where I work. Sadly their blog is still in 2.5.1 version of WordPress. I’ll be painful, I know so hahaha. I’m thinking about upgrading into a middle version, between the current version and the 3.0. What do you think? Thanks adain!

    Reply
    • Raj says

      June 20, 2010 at 2:39 PM

      Hi, Guilherme. You can easily and safely upgrade the wordpress application to any of the recent versions. The only condition being that the upgradation process will be in your control only if the blog is on a self hosted domain and like http://www.domain.com. Blogs hosted on WordPress.com are maintained automatically. If it’s a self hosted domain, you may follow the steps in the above post to carry out the upgradation.

      Reply
      • Guilherme Vaz says

        June 23, 2010 at 12:36 AM

        Yes, I know. The blog is a self hosted blog. It’s not my blog I’m talking about. I’ve just started the upgrade and backed up the database. I’m sure your tips will be helpful! Thanks.

        Reply
        • Guilherme Vaz says

          June 29, 2010 at 10:36 PM

          Worked like a charm! Fantastic! Great tutorial!! Not even one problem!

          Thanks!

          Reply
          • Kashif says

            August 31, 2010 at 7:59 AM

            Happy to find these tips and even more happy to find discussion under this comment.
            Today, I am going to upgrade from 2.5.1 to latest version and was thinking that it’ll be painful. But after coming to this page, I am feeling that it would “Work like a charm!”:)

            Thanks Raj and GV,

  6. donnyien says

    June 21, 2010 at 6:28 PM

    Great tips,but i still working on it and hopefully it wil be okay later.

    Reply
  7. Sachin @ Web Design Mauritius says

    June 21, 2010 at 8:01 PM

    I’m still waiting to see what the major issues and bugs will be with “Thelonious” before upgrading to it. I’ve had too many bad surprises with previous updates that I think that I’ll do it after all is cleared. Thanks for the manual installation tips though.

    Reply
    • Raj says

      June 22, 2010 at 9:37 PM

      I agree with you. That would be wiser.

      Reply
  8. Keith Davis says

    June 23, 2010 at 2:08 AM

    Hi Raj
    I’ve always upgraded using Cpanel and Fantastico but I have always wanted to do it manually… never quite had the bottle.
    This article may be just the thing to make me have a go!

    Reply
  9. Gagan says

    June 23, 2010 at 9:47 PM

    I havent upgraded to 3.0 yet, fearing to face any issue with it. 🙁

    Reply
  10. Erin says

    June 24, 2010 at 9:24 PM

    Thank you so much you saved the day with this post!

    Reply
  11. Danang Sukma | Surabaya Web Design says

    June 27, 2010 at 4:31 PM

    This first time im upgrade manually my wordpress. Thanks for your tips, that is save my day… ^^)

    Reply
  12. Raj says

    June 27, 2010 at 5:46 PM

    @ Erin and Danang: You’re Welcome 🙂

    Reply
  13. Chanon says

    July 6, 2010 at 8:45 AM

    Hey Thanks Raj,
    I’m not sure what’s happening but I can’t do an automatic upgrade for from 2.9 to 3.0

    Your tips work great!
    Btw, apart from /wp-content/ and wp-config.php, some people may also need to copy .htaccess in case that they did not install wordpress on the root of website.

    Thanks again, your tips save my time 🙂

    Reply
    • Raj Agrawal says

      September 5, 2010 at 5:41 PM

      😀 Im glad that the manual upgrade worked out for you and i agree, backing up the .htaccess (the ones that are located within the ‘to be upgraded’ folders) must be backed up.

      Reply
  14. Blog Techno says

    July 7, 2010 at 4:43 PM

    some of my plugin still not compatible with worddpress

    Reply
  15. ex3m.al says

    August 23, 2010 at 10:57 PM

    hi Ray

    i hawe a free hosting service that i use and i cant upgrate from the wordpress upgrade system for i dont know reason

    so thnx for this help

    but all i want to know is if this method can punish all my posts or users????

    Reply
  16. Ed says

    August 29, 2010 at 6:22 PM

    Hello,

    Just to come here to tell you that your instructions helped me a lot. WP’s instructions are comprehensive, but they might be too detailed.

    Thanks for the added human touch in the way of writing the instructions 😀

    Reply
    • Raj Agrawal says

      September 5, 2010 at 5:36 PM

      You are welcome Ed 😉

      Reply
  17. angie says

    September 5, 2010 at 2:48 PM

    Thank you so much! Your instructions were perfect. I tried following the instructions on wordpress.org and almost overwrote my wp-contents folder. So lame.

    Reply
    • Raj Agrawal says

      September 5, 2010 at 5:27 PM

      Thanks Angie, i appreciate that 🙂 By the way, the entire artwork set on your website is very interesting. Keep up the coolness!

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *