Version 1.19 (checked in on 2010/01/28 at 07:09:03 by webchick)
// $Id: UPGRADE.txt,v 1.19 2010/01/28 07:09:03 webchick Exp $
Prior to upgrading, you should ensure that:
1. Backup your database and Drupal directory - especially your "sites" directory which contains your configuration file and added modules and themes, any contributed or custom modules in your "modules" directory, and your "files" directory which contains uploaded files. If other files have modifications, such as .htaccess or robots.txt, those should be backed up as well.
Note: for a single site setup, the configuration file is the "settings.php" file located at sites/default/settings.php. The default.settings.php file contains a clean copy for restoration purposes, if required.
For multisite configurations, the configuration file is located in a structure like the following:
sites/default/settings.php sites/example.com/settings.php sites/sub.example.com/settings.php sites/sub.example.com.path/settings.php
More information on multisite configuration is located in INSTALL.txt.
2. If possible, log on either as a user with the "Administer software updates" permission or as the user with user ID 1, which is the first account created (also known as the site maintenance account). Only these accounts will be able to automatically access update.php in step #10. There are special instructions in step #10 if you are unable to log on as one of these users. Do not close your browser until the final step is complete.
3. Place the site in "Offline" mode, to let the database updates run without interruption and avoid displaying errors to end users of the site. This option is at http://www.example.com/?q=admin/config/development/maintenance (replace www.example.com with your installation's domain name and path).
4. If using a custom or contributed theme, switch to Garland.
5. Disable all custom and contributed modules.
6. Remove all old files and directories from the Drupal installation directory.
7. Unpack the new files and directories into the Drupal installation directory.
8. Copy your backed up "files" and "sites" directories to the Drupal installation directory. If other system files such as .htaccess or robots.txt were customized, re-create the modifications in the new versions of the files using the backups taken in step #1.
9. Verify the new configuration file to make sure it has correct information.
10. Run update.php by visiting http://www.example.com/update.php (replace www.example.com with your Drupal installation's domain name and path). This step will update the core database tables to the new Drupal installation.
Note: if you are unable to access update.php do the following:
11. Ensure that the versions of all custom and contributed modules match the new Drupal version to which you have updated. For a major update, such as from 5.x to 6.x, modules from previous versions will not be compatible and updated versions will be required.
12. Re-enable custom and contributed modules and re-run update.php to update custom and contributed database tables.
13. Return the site to its original theme (if you switched to a core theme in step #4). If your site uses a custom or contributed theme, make sure it is compatible with your version of Drupal.
14. Finally, return your site to "Online" mode so your visitors may resume browsing. As in step #3, this option is available in your administration screens at http://www.example.com/?q=admin/config/development/maintenance (replace www.example.com with your installation's domain name and path).
For more information on upgrading visit the Drupal handbook at http://drupal.org/upgrade