Upgrade Steps

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”?

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.

(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

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.

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. ??

You are welcome

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.

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.

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.

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.

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.

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