Upgraded to WordPress 2.0.2
I finally got enough time to upgrade Nomadig.com journal to the latest version of WordPress. The transition was soothingly smooth — these guys seem to know what they are doing — as there were not even minor hiccups.
To serve my readers, I decided duplicate the WP installation and upgrade the duplicate. After I found the duplicate working well, I switched the blogs.
The process required also duplicating the database, as otherwise the production blog would have gone haywire.
Follow these easy steps to upgrade from WP 1.5 to 2.0.2 with a duplicate settings.
- Make a copy of the WP directory, for example, cp -a journal journal2.
- Dump MySQL database to a file, mysqldump -u user -ppassword –opt database > ~/wp_backup.sql.
- Create new MySQL database.
- Add use new_database; in the beginning of the dumped file.
- Upload the edited dump to MySQL mysql -u user -ppassword < ~/wp_backup.sql.
- Change the blog and WP admin URLs in the new database to refer to the new WP directory. I used phpMyAdmin to find the rows and edit them.
- Edit wp-config.php file in the new WP directory to refer to the correct database.
- Edit .htaccess in the same directory to use correct rewrite URLs.
- Test that you can view and log in the new WP installation.
- Upgrade WP as instructed in codex.wordpress.org.
- Test everything.
- Change the blog and WP admin URLs in the new database to refer to the old WP directory.
- Dump the new database to file, mysqldump -u user -ppassword –opt new_database > ~/wp_2_backup.sql.
- Add use database; (the old database name) in the beginning of the dumped file.
- Edit wp-config.php to refer back to the old database.
- Edit .htaccess to use correct rewrite URLs.
- Upload the version 2 db over the old database, mysql -u user -ppassword < ~/wp_2_backup.sql.
- Rename the old WP directory, mv journal journal_old.
- Rename the new WP directory, mv journal2 journal.
- Test that everything still works.
- Write an entry about the upgrade. Remember to be specific.
1. — Aug 29 2008