? patch-570572.txt Index: install.php =================================================================== RCS file: /cvs/drupal/drupal/install.php,v retrieving revision 1.202 diff -u -p -r1.202 install.php --- install.php 25 Aug 2009 21:53:46 -0000 1.202 +++ install.php 8 Sep 2009 00:44:10 -0000 @@ -1556,7 +1556,7 @@ function _install_configure_form(&$form_ ); $form['admin_account'] = array( '#type' => 'fieldset', - '#title' => st('Administrator account'), + '#title' => st('Site Maintenance acount'), '#collapsible' => FALSE, ); Index: update.php =================================================================== RCS file: /cvs/drupal/drupal/update.php,v retrieving revision 1.302 diff -u -p -r1.302 update.php --- update.php 7 Sep 2009 15:43:54 -0000 1.302 +++ update.php 8 Sep 2009 00:44:10 -0000 @@ -201,12 +201,12 @@ function update_info_page() { function update_access_denied_page() { drupal_set_title('Access denied'); - return '

Access denied. You are not authorized to access this page. Please log in as the admin user (the first user you created). If you cannot log in, you will have to edit settings.php to bypass this access check. To do this:

+ return '

Access denied. You are not authorized to access this page. Please log in as the site maintenance account (the first account you created). If you cannot log in, you will have to edit settings.php to bypass this access check. To do this:

  1. With a text editor find the settings.php file on your system. From the main Drupal directory that you installed all the files into, go to sites/your_site_name if such directory exists, or else to sites/default which applies otherwise.
  2. There is a line inside your settings.php file that says $update_free_access = FALSE;. Change it to $update_free_access = TRUE;.
  3. As soon as the update.php script is done, you must change the settings.php file back to its original form with $update_free_access = FALSE;.
  4. -
  5. To avoid having this problem in future, remember to log in to your website as the admin user (the user you first created) before you backup your database at the beginning of the update process.
  6. +
  7. To avoid having this problem in future, remember to log in to your website as the site maintenance account (the account you first created) before you backup your database at the beginning of the update process.
'; }