WordPress.org

Ready to get started?Download WordPress

Codex

Attention Interested in functions, hooks, classes, or methods? Check out the new WordPress Code Reference!

User:MichaelH/Upgrading WordPress hold

Contents

The latest version, WordPress 3.9.2, has been released to the public. The information below describes a Five-Step upgrade process and a more detailed upgrade process. Please follow one these guideline to upgrade to the WordPress Version 3.9.2.

How to Upgrade in Five Steps

Read the Detailed Upgrade Instructions if you want more intricately scripted steps!!!

Upgrading WordPress can be a little tricky, but fear not, this guide will help make quick work of upgrading your jazzed-up WordPress! This process will provide pointers to protect you against disasters (other software providers might call "user errors").

Before starting, you need to understand WordPress is easy to upgrade. Preserving any customizations you might have made is what makes this a 5-step process instead of 3-step one. It would be nice to believe this is a 5-minute process, but the part about backing up your data and file might take a little more than 5 minutes if you are a prolific blogger.

The steps to a healthy upgrade are as follows:

Let us assume your blog has a URI like http://example.com/wordpress/.

Step 1: Backup Database Tables and Files including .htaccess

Here, the objective is to save the data, and your customizations.

Step 1a: Save Data

Use phpMyAdmin or other appropriate tools provided by your webhost, to backup the database used by WordPress.

Step 1b: Save Customizations

Basically, save the files that you have changed or added since you installed the standard WordPress. Use an FTP tool to download a copy of all the files on the server, in the directory where you installed WordPress, including the .htaccess files if you have been playing with it. Backup at least the .htaccess file, the files used by your current theme (which will be in the /wp-content/ directory), the /wp-images/ directory with your uploaded images and files, any WordPress core files that you modified to use some "hack" directory, and the wp-config.php file which contains your database username, password etc.

Step 2: Deactivate Plugins

Deactivate all the Plugins you use at the Plugin Management Page ( http://example.com/wordpress/wp-admin/plugins.php ). Some Plugins might not work with WordPress 3.9.2, and that is why you want to deactivate them all. This will ensure that you don't end up with an upgraded-but-broken installation of WordPress after the upgrade process.

Step 3: Overwrite Files

Get the latest and greatest WordPress and upload it to the WordPress directory, overwriting all the files that exist there. This will preserve your images and themes. What if something goes wrong, you ask? Well, did you not create a backup of all files in Step 1? You can fall back upon them in the worst case scenario.

Step 4: Run the upgrade script

Visit your blog's Upgrade Page ( http://example.com/wordpress/wp-admin/upgrade.php ) and follow the instructions that are displayed.

Step 5: Reactivate Plugins one by one

Awaken the monsters, one by one, at the Plugin Management Page ( http://example.com/wordpress/wp-admin/plugins.php ). Check if everything works as expected. There is a list of Plugins that are known to work with WordPress 2.0 here. If some Plugins do not work, deactivate the plugin, then contact the plugin author to encourage the author to upgrade the plugin.

There, that does it.

Something went wrong, you say? No worries. Since you backed everything up earlier, restore the files and database tables you backed up, and this time, consider following the Detailed Instructions below.

Detailed Instructions

Before You Start

  1. Backup your database.
  2. Backup ALL of your WordPress files, including .htaccess if you have one.
  3. Verify that the backups you created are there and usable.
  4. Deactivate ALL your Plugins.

Important Note: if you haven't completed the steps above, do not attempt the upgrade.

Overview of the Upgrade Process

  1. Backup your database. Read Backing Up Your Database for a detailed explanation.
  2. Backup ALL your WordPress files in your WordPress directory. Don't forget your .htaccess file.
  3. Verify the backups you created are there and usable. This is essential.
  4. Deactivate ALL your Plugins.
  5. Ensure first four steps are completed. Do not attempt the upgrade unless you have completed the first four steps.
  6. Download and extract the WordPress package from http://wordpress.org/download/.
  7. Delete the old WordPress files on your site, but DO NOT DELETE
    • wp-config.php file;
    • wp-content folder; Special Exception: the wp-content/cache folder should be deleted.
    • wp-images folder;
    • wp-includes/languages/ folder--if you are using a language file do not delete that folder;
    • .htaccess file--if you have added custom rules to your .htaccess, do not delete it.
  8. Upload the new files from your computer's hard drive to the appropriate WordPress folder on your site.
  9. Run the WordPress upgrade program and follow the instructions on the screen.
  10. Update Permalinks and .htaccess. Update your Permalink Structure and merge the custom rules, if necessary, into your .htaccess file.
  11. Install updated Plugins and Themes. Please review the list of Plugins that work in Version 2.0 and check if your Theme author has a new version.
  12. Reactivate Plugins
  13. Review what has changed in WordPress.

That's the overview of the upgrade process. Please continue reading the Detailed Upgrade Instructions.

Remember, if you do encounter problems, re-read the Instructions below to insure you've followed the proper procedures and consult Troubleshooting: Common Installation Problems.

Detailed Upgrade Instructions for 1.5.x to 2.0.1 and 2.0 to 2.0.1

The following are the instructions that explain the above steps in more detail. Please read all of the instructions before starting.

Step 1: Back up your database

Perform a backup of your database. All of your WordPress data, such as Users, Posts, Pages, Links, and Categories, are stored in your MySQL database. Please read Backing Up Your Database for a detailed explanation of this process.

It is extremely important to back up your database before beginning the upgrade. If, for some reason, you find it necessary to revert back to the 'old' version of WordPress, you may have to restore your database from these backups.

Step 2: Back up ALL your WordPress files

Back up ALL of your files in your WordPress directory and your .htaccess file. Typically, this process involves using an FTP program to download ALL your WordPress files from your host to your local computer. Please read Backing Up Your WordPress Site for further explanation.

If you have made changes to any core WordPress files, or if you've got customized Plugins or Themes, you will want to have a good backup of those files. It is extremely important to back up your files before beginning the upgrade. If for some reason you find it necessary to revert back to the 'old' version of WordPress you will need to upload these files.

Step 3: Verify the backups

Verify that the backups you created are there and usable. This is the most important step in the upgrade process! The verification process involves making sure you can see the backup files on your local computer (or wherever you've stored them) and that you can navigate into any sub-folders. If the files are in a zip file, make sure you can open the zip file.

Step 4: Deactivate ALL your Plugins

In your Administration panel, under the Plugins choice, deactivate any Plugins. Because of the changes to WordPress, some Plugins may conflict with the upgrade process.

Step 5: Ensure first four steps are completed

If you have not completed the first four procedures, STOP, and do them! Do not attempt the upgrade unless you have completed the first four steps.

The best resource for problems with your upgrade is the WordPress Support Forums, and if you have problems, the volunteers at the WordPress Support Forums will likely ask if you have completed the first four steps.

Step 6: Download and extract the WordPress package

Download and unzip the WordPress package from http://wordpress.org/download/.

  • If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with your favorite web browser and unzip the package.
  • If you have shell access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your web server. You can do so using wget , lynx or another console-based web browser, which are valuable if you want to avoid FTPing. Then unzip the package using: gunzip -c wordpress-3.9.2.tar.gz | tar -xf - or by using: tar -xzvf latest.tar.gz

The WordPress package will be extracted into a folder called wordpress.

Step 7: Delete the old WordPress files

Why Delete? Generally, it is a good idea to delete whatever is possible because the uploading (or upgrading through cPanel) process may not correctly overwrite an existing file and that may cause problems later.

DO NOT DELETE these folders and files:

  • wp-config.php file;
  • wp-content folder;
  • wp-images folder;
  • wp-includes/languages/ folder--if you are using a language file, do not delete this folder;.
  • .htaccess file--if you have added custom rules to your .htaccess, do not delete it;
  • Custom Content and/or Plugins--if you have any images or other custom content or Plugins inside the wp-content folder, do NOT delete them.

Delete these Files and Folders:

  • wp-* (except for those above), readme.html, wp.php, xmlrpc.php, and license.txt; files; Typically files in your root or wordpress folder. Again, don't delete the wp-config.php file.
  • wp-admin folder;
  • wp-includes folder; If using a language file remember don't delete the wp-includes/languages/ folder
  • wp-content/cache folder; You only see this folder if you are upgrading FROM WordPress 2.0.

How to Delete? There are several ways to delete the files from your WordPress site. You can use your FTP Client, or if you have access to Telenet or SSH you can use that. Some host providers also provide the ability to delete files and folders.

Using FTP to delete files and folders 
The same FTP client you use for uploading can be used to delete files and folders. If your FTP client does not appear to permit you to delete non-empty folders, check the available options for your FTP client. You'll usually find an option that permits deleting non-empty folders. Deleting non-empty folders is a quick and thorough method cleaning out an old installation of WordPress. It is recommended that once the deleting is done, you switch back to the original setting for safety reasons.
Using Telnet or SSH to delete file 
If you have a command-line login (telnet or ssh), you can enter the following commands to delete ONLY the wordpress files in your directory (plus .htaccess):
  • mkdir backup
  • cp wp-config.php .htaccess wp-layout.css index.php wp-comments.php wp-comments-popup.php backup
  • cp -R wp-content backup
  • rm wp*.php wp-layout.css .htaccess license.txt readme.html xmlrpc.php
  • rm -rf wp-admin wp-includes
  • cp backup/wp-config.php .
  • After you have finished with the upgrade, you can restore any customizations to your templates or plugins from your backup directory. For example, cp backup/index.php.

Step 8: Upload the new files

With the new upgrade on your local computer, and using FTP, upload the new files to your site server just as you did when you first installed WordPress. See Using FileZilla and Uploading WordPress to a remote host for detailed guidelines in using an FTP Client to upload.

NOTE: If you did not delete the wp-content folder, you will need to overwrite some files during the upload.

The wp-content folder holds your WordPress Themes and Plugins. These should remain. Upload everything else first, then upload only those WordPress files that new or changed to your new wp-content folder. Overwrite any old versions of default plugins with the new ones.

The WordPress default theme has changed so you will want to upload the wp-content/themes/default folder. If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade.

Step 9: Run the WordPress upgrade program

Run the WordPress upgrade script by accessing wp-admin/upgrade.php in your favorite web browser and follow the instructions presented on your screen.

  • If WordPress is installed in the root directory, point your browser to: http://example.com/wp-admin/upgrade.php
  • If WordPress is installed in its own subdirectory called blog, for example, point your browser to: http://example.com/blog/wp-admin/upgrade.php

Step 10: Update Permalinks and .htaccess

In your Options->Permalinks panel update your Permalink Structure and, if necessary, place the rules in your .htaccess file. Also see Using Permalinks for details regarding Permalinks and the .htaccess file.

Step 11: Install updated Plugins and Themes

Please review the list of Plugins that work in Version 2.0. You will want to upload and install any new versions of your Plugins and Themes. Check with the author of those Plugins and Themes for the updated versions.

Step 12: Reactivate Plugins

Use your Administration Panel, Plugins, to activate your Plugins.

Please note that if you are using the new WordPress Database Backup Plugin you may need to change the permissions on your wp-content folder to make it writeable by your webserver (either mode 666 or even 777). See Changing File Permissions for more details.

Step 13: Review what has changed in WordPress

As of now, there is no official list in Codex that describes all the new features, but look at these resources:

Upgrade Instructions in Other Languages

Troubleshooting

Scrambled Layout or Errors 
If your blog looks scrambled now or features line errors, an old plugin that doesn't work with the new code may be the culprit. In your WordPress Administration Panel, deactivate all plugins that do not come with WordPress by default. Re-activate them one by one.
Made Custom Changes/Hacks? 
If you have made changes to other WordPress files ("hacked" WordPress), you are supposed to keep track of your changes. You will have to transfer your edits into the new code. WordPress Versions lists the files that have changed in each release.
Resist Using Old Code 
Upgrading gives you the newest and best code. Using your old code, no matter how much you have customised it, almost certainly will cause problems. The temptation just to use your old modified code will be great, but the chances of errors are much greater.
Can I Go Back to Old Versions 
You can, but it is usually not recommended to rollback (revert) your current version to an older version. That is because newer versions often include security updates and a rollback may put your site at risk. Second, the change between the database structure between versions may cause complications in maintaining your site content, posts, comments, and plugins that are dependent upon the information stored in the database. If you are still intent on this, proceed at your own risk. Please note, that without a backup of your entire site and your database, made prior to your upgrade attempt, a successful rollback is near impossible. Delete all WordPress files except for wp-config. Upload the files from your backup to your server and restore your database backup. Remember, you must have good backups for the rollback to work. For older WordPress versions, a rollback might not work.
Get More Help 
If you get any errors following an upgrade, check Troubleshooting: Common Installation Problems, Troubleshooting, and the Codex Installation Category of Articles. If you can't find an answer, post a clear question on the WordPress Suppport Forums. You will be asked if you have used any old code. You'll be told to change it then, so you may as well change it now :)

Old Upgrade Information

If you are considering upgrading to WordPress Version 2.0.1, but you are at Version 1.2, then follow the 1.2 to 1.5 upgrade as describe in Upgrading From WordPress Version 1.2 to 1.5. Once you are upgraded to Version 1.5.x, then follow the instructions as listed above to upgrade from 1.5 to 2.0.1.