Reviewed installation guide
This commit is contained in:
parent
bf48d8890d
commit
8133d7f116
6 changed files with 135 additions and 305 deletions
|
|
@ -6,14 +6,12 @@ Prior to upgrading, you should ensure that:
|
|||
* Your system meets or exceeds Drupal's minimum requirements as shown at
|
||||
http://drupal.org/requirements.
|
||||
* You have a backup of all your relevant data (#1).
|
||||
* Custom and contributed modules have been checked for compatibility (#11).
|
||||
* Custom and contributed themes have been checked for compatibility (#11).
|
||||
* You have read through this entire document.
|
||||
|
||||
Let's begin!
|
||||
|
||||
1. Back up your Drupal database and site root directory. Be especially sure
|
||||
to back up your "config" directory which contains your configuration file,
|
||||
1. Back up your Drupal database and site root directory. Be especially sure to
|
||||
back up your "config" directory which contains your configuration file,
|
||||
added modules and themes, and your site's uploaded files. If other files
|
||||
have modifications, such as .htaccess or robots.txt, back those up as well.
|
||||
|
||||
|
|
@ -24,9 +22,9 @@ Let's begin!
|
|||
For multisite configurations, the configuration file is located in a
|
||||
structure like the following:
|
||||
|
||||
config/default/settings.php
|
||||
config/example.com/settings.php
|
||||
config/sub.example.com/settings.php
|
||||
config/default/settings.php
|
||||
config/example.com/settings.php
|
||||
config/sub.example.com/settings.php
|
||||
config/sub.example.com.path/settings.php
|
||||
|
||||
More information on multisite configuration is located in INSTALL.txt.
|
||||
|
|
@ -42,8 +40,8 @@ Let's begin!
|
|||
option is at http://www.example.com/?q=admin/settings/site-maintenance
|
||||
(replace www.example.com with your installation's domain name and path).
|
||||
|
||||
4. If using a custom or contributed theme, switch
|
||||
to a core theme, such as Garland or Bluemarine.
|
||||
4. If using a custom or contributed theme, switch to a core theme, such as
|
||||
Garland.
|
||||
|
||||
5. Disable all custom and contributed modules.
|
||||
|
||||
|
|
@ -53,8 +51,8 @@ Let's begin!
|
|||
|
||||
8. Copy your backed up "files" and "config" 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.
|
||||
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.
|
||||
|
||||
|
|
@ -64,43 +62,35 @@ Let's begin!
|
|||
|
||||
Note: if you are unable to access update.php do the following:
|
||||
|
||||
- Open your settings.php with a text editor.
|
||||
|
||||
- There is a line that says $update_free_access = FALSE;
|
||||
* Open your settings.php with a text editor.
|
||||
* There is a line that says $update_free_access = FALSE;
|
||||
Change it to $update_free_access = TRUE;
|
||||
|
||||
- Once update.php is done, you must change the settings.php file
|
||||
* Once update.php is done, you must change the settings.php file
|
||||
back to its original form with $update_free_access = FALSE;
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
- For contributed modules, check http://drupal.org/project/modules
|
||||
* For contributed modules, check http://drupal.org/project/modules
|
||||
for the version of a module matching your version of Drupal.
|
||||
|
||||
- For custom modules, review http://drupal.org/update/modules to
|
||||
* For custom modules, review http://drupal.org/update/modules to
|
||||
ensure that a custom module is compatible with the current version.
|
||||
|
||||
12. Re-enable custom and contributed modules and re-run update.php
|
||||
to update custom and contributed database tables.
|
||||
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 like Garland or Bluemarine in step #4). If your site uses a
|
||||
custom or contributed theme, make sure it is compatible with your
|
||||
version of Drupal.
|
||||
13. Return the site to its original theme (if you switched to a core theme like
|
||||
Garland or Bluemarine in step #4). If your site uses a custom or contributed
|
||||
theme, make sure it is compatible with your version of Drupal.
|
||||
|
||||
- For contributed themes, check http://drupal.org/project/themes
|
||||
for the version of a theme matching your version of Drupal.
|
||||
|
||||
- For custom themes, review http://drupal.org/update/theme to ensure
|
||||
that a custom theme is compatible with the current version.
|
||||
* For contributed themes, check http://drupal.org/project/themes for the
|
||||
version of a theme matching your version of Drupal.
|
||||
* For custom themes, review http://drupal.org/update/theme to ensure that
|
||||
a custom theme is compatible with the current version.
|
||||
|
||||
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/settings/site-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
|
||||
|
|
|
|||
Reference in a new issue