[Summary view] [Print] [Text view]

   1  // $Id: UPGRADE.txt,v 1.12.2.1 2010/05/11 09:39:36 goba Exp $
   2  
   3  UPGRADING
   4  ---------
   5  
   6  Prior to upgrading, you should ensure that:
   7  
   8   * Your system meets or exceeds Drupal's minimum requirements as shown at
   9     http://drupal.org/requirements.
  10   * You have a backup of all your relevant data (#1).
  11   * Custom and contributed modules have been checked for compatibility (#11).
  12   * Custom and contributed themes have been checked for compatibility (#11).
  13   * You have read through this entire document.
  14  
  15  Let's begin!
  16  
  17  1.  Back up your Drupal database and site root directory. Be especially sure 
  18      to back up your "sites" directory which contains your configuration file, 
  19      added modules and themes, and your site's uploaded files. If other files 
  20      have modifications, such as .htaccess or robots.txt, back those up as well.
  21  
  22      Note: for a single site setup, the configuration file is the "settings.php"
  23      file located at sites/default/settings.php. The default.settings.php file
  24      contains a clean copy for restoration purposes, if required.
  25  
  26      For multisite configurations, the configuration file is located in a
  27      structure like the following:
  28  
  29        sites/default/settings.php
  30        sites/example.com/settings.php
  31        sites/sub.example.com/settings.php
  32        sites/sub.example.com.path/settings.php
  33  
  34      More information on multisite configuration is located in INSTALL.txt.
  35  
  36  2.  If possible, log on as the user with user ID 1, which is the first account
  37      created and the main administrator account. User ID 1 will be able to
  38      automatically access update.php in step #10. There are special instructions
  39      in step #10 if you are unable to log on as user ID 1. Do not close your
  40      browser until the final step is complete.
  41  
  42  3.  Place the site in "Off-line" mode, to let the database updates run without
  43      interruption and avoid displaying errors to end users of the site. This
  44      option is at http://www.example.com/?q=admin/settings/site-maintenance
  45      (replace www.example.com with your installation's domain name and path).
  46  
  47  4.  If using a custom or contributed theme, switch
  48      to a core theme, such as Garland or Bluemarine.
  49  
  50  5.  Disable all custom and contributed modules.
  51  
  52  6.  Remove all old files and directories from the Drupal installation directory.
  53  
  54  7.  Unpack the new files and directories into the Drupal installation directory.
  55  
  56  8.  Copy your backed up "files" and "sites" directories to the Drupal
  57      installation directory. If other system files such as .htaccess or
  58      robots.txt were customized, re-create the modifications in the new
  59      versions of the files using the backups taken in step #1.
  60  
  61  9.  Verify the new configuration file to make sure it has correct information.
  62  
  63  10. Run update.php by visiting http://www.example.com/update.php (replace
  64      www.example.com with your Drupal installation's domain name and path). This
  65      step will update the core database tables to the new Drupal installation.
  66  
  67      Note: if you are unable to access update.php do the following:
  68  
  69        - Open your settings.php with a text editor.
  70  
  71        - There is a line that says $update_free_access = FALSE;
  72          Change it to $update_free_access = TRUE;
  73  
  74        - Once update.php is done, you must change the settings.php file
  75          back to its original form with $update_free_access = FALSE;
  76  
  77  11. Ensure that the versions of all custom and contributed modules match the
  78      new Drupal version to which you have updated. For a major update, such as
  79      from 5.x to 6.x, modules from previous versions will not be compatible
  80      and updated versions will be required.
  81  
  82        - For contributed modules, check http://drupal.org/project/modules
  83          for the version of a module matching your version of Drupal.
  84  
  85        - For custom modules, review http://drupal.org/update/modules to
  86          ensure that a custom module is compatible with the current version.
  87  
  88  12. Re-enable custom and contributed modules and re-run update.php
  89      to update custom and contributed database tables.
  90  
  91  13. Return the site to its original theme (if you switched to a core
  92      theme like Garland or Bluemarine in step #4). If your site uses a
  93      custom or contributed theme, make sure it is compatible with your
  94      version of Drupal.
  95  
  96        - For contributed themes, check http://drupal.org/project/themes
  97          for the version of a theme matching your version of Drupal.
  98  
  99        - For custom themes, review http://drupal.org/update/theme to ensure
 100          that a custom theme is compatible with the current version.
 101  
 102  14. Finally, return your site to "Online" mode so your visitors may resume
 103      browsing. As in step #3, this option is available in your administration
 104      screens at http://www.example.com/?q=admin/settings/site-maintenance
 105      (replace www.example.com with your installation's domain name and path).
 106  
 107  For more information on upgrading visit
 108  the Drupal handbook at http://drupal.org/upgrade