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