Invoking the update.php URL does not update, control is transferred to core via drupal_bootstrap in update.php and never returns.

install.php is loaded instead of upgrading.

Turned off all non-core modules.
Reset theme to bluemarine.
Set $update_free_access = TRUE;

Comments

bryansd’s picture

I witnessed something similar last night too. I didn't see this problem with RC1, but experienced it with RC2. I'm going to run through everything again tonight and see if I run into the same problem (I'm hoping this is user error).

ByteEnable’s picture

Its caused by database.inc:

if (empty($db_url)) {
include_once 'includes/install.inc';
install_goto('install.php');
}

Its because db_url empty.

Byte

andycowl’s picture

I note the same issue upgrading from (vanilla) 5.3 and 5.6.

Worse, site is inaccessible after failed upgrade and I needed a full DB restore.

I am not complaining as this is beta and the warnings are already there. Just stressing the fact that a DB backup (that can be restored) is absolutely required.

gábor hojtsy’s picture

Status: Active » Closed (works as designed)

On upgrades, you need to restore the database settings in a settings.php (as documented), or otherwise Drupal will think it is going to be installed, not updated. This is documented in the upgrade instructions.

ByteEnable’s picture

My database settings are correct in sites/default/default.settings.php.

Byte

ByteEnable’s picture

Status: Closed (works as designed) » Active

Bumping back to active bug.

scoutbaker’s picture

Status: Active » Closed (works as designed)

The UPDATE.txt specifically states, in part,

...the configuration file is the "settings.php" file...

I have had no issues when I followed the update directions correctly.

(By design as noted by Gábor previously.)

andycowl’s picture

Mea culpa. When I used my existing 'settings.php', my upgrade worked too. Hurrah !