In update.php instructions, move database backup after maintenance mode.

Created on 9 August 2012, over 12 years ago
Updated 1 December 2023, about 1 year ago

update.php currently instructs administrators to back up their database before putting the site into maintenance mode. This means that updates can still be made to the database during and after the backup. It would be better if the database backup were made after putting the site into maintenance mode.

Details follow:

update.php?op=info currently reads:

  1. Back up your database. This process will change your database values and in case of emergency you may need to revert to a backup.
  2. Back up your code. Hint: when backing up module code, do not leave that backup in the 'modules' or 'sites/*/modules' directories as this may confuse Drupal's auto-discovery mechanism.
  3. Put your site into maintenance mode.
  4. Install your new files in the appropriate location, as described in the handbook.

It would better read:

  1. Back up your code. Hint: when backing up module code, do not leave that backup in the 'modules' or 'sites/*/modules' directories as this may confuse Drupal's auto-discovery mechanism.
  2. Put your site into maintenance mode.
  3. Install your new files in the appropriate location, as described in the handbook.
  4. Back up your database. This process will change your database values and in case of emergency you may need to revert to a backup.
🐛 Bug report
Status

Fixed

Version

7.0 ⚰️

Component
Database update 

Last updated 4 days ago

No maintainer
Created by

🇺🇸United States charles belov San Francisco, CA, US

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024