Upgrading from 1.5 to 3.0

Have you reviewed this yet: Upgrading WordPress

The “semi-official” WordPress major upgrade path:

1. Backup the files and the database.

2. Download WordPress 1.7.

3. Do a manual upgrade to WordPress 1.7.

4. Repeat step 1, but don’t replace the previous backup (keep both on hand).

5. Download WordPress 1.9.

6. Do a manual upgrade to WordPress 1.9.

7. Repeat step 1, but don’t replace the previous backup (keep both on hand).

8. Download WordPress 2.1.

9. Do a manual upgrade to WordPress 2.1.

10. Repeat step 1, but don’t replace the previous backup (keep both on hand).

11. Download WordPress 2.3.

12. Do a manual upgrade to WordPress 2.3.

13. Repeat step 1, but don’t replace the previous backup (keep both on hand).

14. Download WordPress 2.5.

15. Do a manual upgrade to WordPress 2.5.

16. Repeat step 1, but don’t replace the previous backup (keep both on hand).

17. Download WordPress 2.7.

18. Do a manual upgrade to WordPress 2.7.

19. Repeat step 1, but don’t replace the previous backup (keep both on hand).

20. Use WP’s automated upgrade to system to upgrade to 3.0.

I need to upgrade from 1.52 to 3.0 also. I am not having any problems with my blog but I want to prevent future issues. When I go to the download link(s) mentioned above in steps 2 and 5, for example, there is no version 1.7 and 1.9 to download in order to do those incremental upgrades. Does that mean I just go directly from 1.5.2 —-> 2.1, then do 2.3, then 2.5, then 2.7?

I don’t want to make an error doing this significant upgrade. Advice is appreciated.

I have been trying without success to upload 3.01 to 3.00 on my site. The automatic installation keeps failing with this message: “could not create directory:/public_html”
Can someone please help me sort this out.

@byjane you are suppose install wordpress in your public_html(root) or a folder in public_html

When I go to the download link(s) mentioned above in steps 2 and 5, for example, there is no version 1.7 and 1.9 to download in order to do those incremental upgrades. Does that mean I just go directly from 1.5.2 —-> 2.1, then do 2.3, then 2.5, then 2.7?

That’s correct. There were no releases between 1.5.2 and 2.0, so it’s safe to jump from 1.5 to 2.1.

Thank you, James, for the clarification. I am a bit nervous about doing this but I know that it will probably be for the best.

Are the instructions correct that I need to back up my database and files after each incremental upgrade (not just before starting the process?)

Your help is much appreciated.

Are the instructions correct that I need to back up my database and files after each incremental upgrade (not just before starting the process?)

It’s not necessary, but I highly recommend it. If an upgrade fails for some reason, you won’t have to start over from the beginning of the whole process.

I just finished upgrading two sites to 3.0.2; one was running 1.5.2, the other 2.0. In both cases I did more or less stick to the “two major release” interim steps mentioned by James (above). I backed up both database and WP files at the start, but didn’t bother doing interim backups of either (was willing to start over if something failed). It all went smoothly with the process of: 1) Delete all recommended files/dirs, saving stuff like wp-content, wp-config.php, .htaccess, et al.; 2) upload newer version; 3) merge newer stuff in wp-content/plugins, wp-content/themes; 4) run wp-admin/upgrade.php.

All went smoothly EXCEPT FOR THE FOLLOWING: I didn’t have success with using automated update at 2.7. It appeared to work, but then none of the plugins would successfully auto-update, and I ultimately in both cases did a manual upgrade from 2.7 to 3.0.x. I wanted to be sure I had a complete set of files.