WordPress.org

Ready to get started?Download WordPress

Forums

Upgrade Steps (28 posts)

  1. jose
    Member
    Posted 3 years ago #

    I have a 2.1.1 install running. I want to migrate to 3.1 but I wish to do so by moving to a new server in the process.

    Please confirm my approach or otherwise share some advice:

    (1) take a full backup of the DB on server 2.1.1
    (2) restore full backup of DB on server 3.1
    (3) download and install WP 3.1 on server 3.1
    (4) walk through setup and have it update/upgrade MySQL DB form 2.1.1 to 3.1

    Will this approach essentially work?

    Thanks.

  2. govpatel
    Member
    Posted 3 years ago #

    No you will have to upgrade in steps as You have very old version You will find them here

    http://wordpress.org/download/release-archive/

    each time upgrading your database.

  3. esmi
    Forum Moderator
    Posted 3 years ago #

    Try something like: 2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.1

    Remember to:
    - deactivate all plugins first
    - switch to the default theme
    - backup your database before you begin and again after every successful upgrade step.

    Good luck :-)

  4. jose
    Member
    Posted 3 years ago #

    Ok, so it sounds like I also have to put a copy of WordPress 2.1.1 on server 3.1 and then step through the upgrades. I was thinking that just having the 2.1.1 Database would be enough for WP 3.1 to figure out what to do. But I also need to put a copy of the software on the new server as well. Ok...that is enlightening because my interpretation of the upgrades I have been doing on other servers was that the new version worked solely against the existing database. I was not aware that it touched the software too.

  5. govpatel
    Member
    Posted 3 years ago #

    yes with each version there are some changes made to core files as well that is reason why you have to upgrade in steps.

  6. jose
    Member
    Posted 3 years ago #

    Ok, thanks "govpatel".

    Also, "esmi" states "Try something like: 2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.1"

    Is that just a suggested path or is that the actual path?

    I guess if I needed to step through each version the migration would look something like this "2.1.1 > 2.1.2 > 2.1.3 > 2.2 > 2.2.1 > 2.2.2 > 2.2.3 > 2.3 > 2.3.1 > 2.3.2 > 2.3.3 > 2.5 > 2.5.1 > 2.6 > 2.6.1 > 2.6.2 > 2.6.3 > 2.6.5 > 2.7 > 2.7.1 > 2.8 > 2.8.1 > 2.8.2 > 2.8.3 > 2.8.4 > 2.8.5 > 2.8.6 > 2.9 > 2.9.1 > 2.9.2 > 3.0 > 3.0.1 > 3.0.2 > 3.0.3 > 3.0.4 > 3.0.5 > 3.1"

  7. jose
    Member
    Posted 3 years ago #

    Something else that's curious to me.

    On another server I have that I have kept the versions updated on a more regular basis, WP offers me the ability to automatically upgrade to the newest version. So I have been doing that (through the auto FTP feature). But I know for sure that I have skipped a version/sub-version 'here and there'.

    So does the auto update process know to step through sub-versioning updates on its own, or have I been jeopradizing my upgrades by not doing it manually sub-ver to sub-ver?

  8. govpatel
    Member
    Posted 3 years ago #

    the ones Esmi suggested are main upgrades and others are updates when found some problem or bug so as long as you update as Esmin suggested you will be fine.

  9. jose
    Member
    Posted 3 years ago #

    How did you know which ones were "upgrades" and which ones were "updates"? I didn't see any sort of tagging or indication on the download page...

  10. jose
    Member
    Posted 3 years ago #

    Ok, here's a good one...

    I inherited this very old WP version (2.1.1). My WP experience started with 3.0. In WP 3.0 I could upgrade right within the dash board. But in the 2.1.1 dashboard there is not obvious place to kick-off the upgrade to 2.2.1 (which I have downloaded from WP.org and uploaded to my server).

    Can you tell me how to upgrade to this interim version? Thanks.

  11. jose
    Member
    Posted 3 years ago #

    Silly me...I guess I should have searched the forums first. Here's how to update if anyone is following this thread:

    http://codex.wordpress.org/Upgrading_WordPress#Detailed_Instructions

  12. jose
    Member
    Posted 3 years ago #

    esmi states

    "Remember to:
    - deactivate all plugins first
    - switch to the default theme"

    If I use the automatic (ftp) upgrade feature in WP, will it deactivate plug-ins > switch theme to default > do upgrade > switch theme back > re-activate plug-ins?

    Or do I need to handle the plug-ins and themes before/after the auto upgrade?

  13. govpatel
    Member
    Posted 3 years ago #

    You will need upgrade manually as You will not find upgrades in automatic upgrade in steps.

    I have video and article on my website on how to upgrade manually

    You will have download each one and replace like I have done and upgrade your database as needed and then go next version.

    Backup database as well for each version just to be on safe side.

  14. jose
    Member
    Posted 3 years ago #

    Ok, so since the auto (ftp) update does not "deactivate all plugins first" and does not "switch to the default theme", then I should manually upgrade when a new version is an "upgrade" but let WP auto update then the new version is an "update"? How can I tell if a new version is an "update" or an "upgrade"?

    Also, I already manually stepped through each upgrade per esmi's instructions. My site is not at 3.1. I am asking this for future updates/upgrades.

    Thanks for the clarification...

  15. jose
    Member
    Posted 3 years ago #

    typo in above s/b "My site is now at 3.1.".

  16. govpatel
    Member
    Posted 3 years ago #

    If your site is updated now and working with 3.1 when ever there is update or upgrade you will get update available for wordpress and plugins with in admin panel you can stay updated so you do not fall behind.

  17. jose
    Member
    Posted 3 years ago #

    But my questions are:

    • since the auto (ftp) update does not "deactivate all plugins first" and does not "switch to the default theme", then I should manually upgrade when a new version is an "upgrade" but let WP auto update then the new version is an "update"?
    • how can I tell if a new version is an "update" or an "upgrade"?
  18. esmi
    Forum Moderator
    Posted 3 years ago #

    1. Let WordPress carry out all upgrades /updates via the automatic updater. But, for maximum peace of mind, deactivate all plugins, switch to the default theme and backup your database before triggering the automatic update.

    2. They're one and the same.

  19. jose
    Member
    Posted 3 years ago #

    (1) that makes sense.

    (2) then why was I instructed to take this path 2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.1 rather than this path 2.1.1 > 2.1.2 > 2.1.3 > 2.2 > 2.2.1 > 2.2.2 > 2.2.3 > 2.3 > 2.3.1 > 2.3.2 > 2.3.3 > 2.5 > 2.5.1 > 2.6 > 2.6.1 > 2.6.2 > 2.6.3 > 2.6.5 > 2.7 > 2.7.1 > 2.8 > 2.8.1 > 2.8.2 > 2.8.3 > 2.8.4 > 2.8.5 > 2.8.6 > 2.9 > 2.9.1 > 2.9.2 > 3.0 > 3.0.1 > 3.0.2 > 3.0.3 > 3.0.4 > 3.0.5 > 3.1

  20. esmi
    Forum Moderator
    Posted 3 years ago #

    Because, as explained above, we've tried to cut the upgrade steps down to those where we know there were major database changes. Feel free to follow the more extensive upgrade route if you prefer.

  21. Marj Wyatt
    Member
    Posted 3 years ago #

    I just wanted to give a thanks to esmi for listing the mandatory upgrade stepping stones and to govpatel for providing the link to WordPress archives.

    I used the manual update procedure to bring a site forward in time from version 2.6.3 and this thread was very helpful. :)

  22. govpatel
    Member
    Posted 3 years ago #

    You are welcome

  23. segovia
    Member
    Posted 3 years ago #

    Thanks, I just did the upgrade on one of my really old sites running 2.2.1 and the following was my upgrade path. I got a little lazy after so many rinse and repeat steps so I skipped 2.9, 3.0 and 3.1.

    2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 3.1.1

    Once I got as far as 2.7 I just did the auto-upgrade from within WP to 3.1.1 and it worked like a charm.

    All toll, this process took several hours (including a few file permission snags I ran into), but in the end it worked out great.

  24. jose
    Member
    Posted 3 years ago #

    Need help with migration path from 3.0.4 to 3.1.2

    What interim versions contain the database upgrades so I can just step through the upgrade to those versions.

    Thanks.

  25. govpatel
    Member
    Posted 3 years ago #

    I think you should be fine upgrading and if there is database update the program will take care of it.
    Back up database just in case you have problem a safety net.

  26. jose
    Member
    Posted 3 years ago #

    But according to esmi, version 3.1 contained a database change so I believe I need to go from 3.0.4 to 3.1 first.

    Then I can go to 3.1.2, unless 3.1.1 also has a database update in it.

    Is my understanding of the process and my inventory of versions that have database updates correct here?

    Thanks govpatel.

  27. esmi
    Forum Moderator
    Posted 3 years ago #

    The upgrade path I have is 2.9 -> 3.0.4 -> 3.1

    At least that's what I believe to be the safest route.

  28. jose
    Member
    Posted 3 years ago #

    Ok, thanks "esmi".

    For those tracking how to upgrade from version to version in order to maintain database structural integrity, here is the latest upgrade path:

    2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.0.4 -> 3.1 -> 3.1.2

    UPGRADE PROCESS

    1. backup database
    2. disable plug-ins
    3. switch theme to default
    4. delete /wp-admin directory from server
    5. delete /wp-includes directory from server
    6. check-in /wp-admin directory from local machine to server
    7. check-in /wp-includes directory from local machine to server
    8. check-in everything from /wp-content directories from local machine to server EXCEPT {your theme} directory
    9. update wp-config.php using wp-config-sample.php
    10. check-in everything from / directory from local machine to server
    11. enable plug-ins **only after last upgrade
    12. switch theme to {your theme}
    13. review and test site

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags