Jul
02
2007

WordPress Upgrade Path

After yesterday’s adventure in update to the newly secured WordPress 2.2.1, I was curious about when new versions would be coming out. According to the official WP Roadmap site, version 2.2 may be released in the middle of July and 2.3 in mid-August. I was planning on waiting for version 2.3 but there are some serious security bugs fixed by version 2.2.1.

If you need to update your WordPress, here is the upgrade instructions. In a nut shell, there are five steps:

    1) Basically backing up your database files. I also copied all of the files related to my blog to my home computer as part of the backup.

    2) Deactivate ALL of the plug-ins. At this point, I went ahead and logged out of my WordPress admin. I remained logged into my Bluehost account so that I could work with the files. I also have a file called iron.html . I rename it to index.html and this will show up instead of my blog. It announces to my visitors that I’m in the process of upgrade (or in the case yesterday, having technical difficulties) and to come back later. Just a courtesy. If you would have visited yesterday, you would have been greeted with this.

    3) Replace all files that are listed in the upgrade process. One thing that the process doesn’t mention is deleting wp-content\themes\classic and wp-content\themes\default directories, and then adding the newer versions of those directories that come in the WordPress update ZIP file.

    4) Run the wp-admin/upgrade.php file from your browser’s address bar (as in http://yourBlogNameAddress/wp-admin/upgrade.php).

    5) I then log back into my site’s admin page. After renaming index.html to index.htm_ , I then open my blog site in another window as a visitor. This way, as I activate each plug-in ONE AT A TIME, I can refresh my visitor window to make sure nothing crashes.

Anyway, the instructions are much clearer than I have briefly written here. I just wanted to make notes for future reference. I hope that this helps both of us! :D

Popularity: 20% [?]

After yesterday’s adventure in update to the newly secured WordPress 2.2.1, I was curious about when new versions would be coming out. According to the official WP Roadmap site, version 2.2 may be released in the middle of July and 2.3 in mid-August. I was planning on waiting for version 2.3 but there are some serious security bugs fixed by version 2.2.1.

If you need to update your WordPress, here is the upgrade instructions. In a nut shell, there are five steps:

    1) Basically backing up your database files. I also copied all of the files related to my blog to my home computer as part of the backup.

    2) Deactivate ALL of the plug-ins. At this point, I went ahead and logged out of my WordPress admin. I remained logged into my Bluehost account so that I could work with the files. I also have a file called iron.html . I rename it to index.html and this will show up instead of my blog. It announces to my visitors that I’m in the process of upgrade (or in the case yesterday, having technical difficulties) and to come back later. Just a courtesy. If you would have visited yesterday, you would have been greeted with this.

    3) Replace all files that are listed in the upgrade process. One thing that the process doesn’t mention is deleting wp-content\themes\classic and wp-content\themes\default directories, and then adding the newer versions of those directories that come in the WordPress update ZIP file.

    4) Run the wp-admin/upgrade.php file from your browser’s address bar (as in http://yourBlogNameAddress/wp-admin/upgrade.php).

    5) I then log back into my site’s admin page. After renaming index.html to index.htm_ , I then open my blog site in another window as a visitor. This way, as I activate each plug-in ONE AT A TIME, I can refresh my visitor window to make sure nothing crashes.

Anyway, the instructions are much clearer than I have briefly written here. I just wanted to make notes for future reference. I hope that this helps both of us! :D

Popularity: 20% [?]

Written by sprezzaturon in: ,Ron Popeil,voting |

3 Comments »

RSS feed for comments on this post. TrackBack URL


Leave a Reply

*

Powered by WordPress. Theme: TheBuckmaker. Schufa KSV, How To

Bad Behavior has blocked 50 access attempts in the last 7 days.