Default training installation for wizzlern.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.

UPGRADE.txt 4.9KB

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