CMS MADE SIMPLE FORGE

CMS Made Simple Core

 
Back Back to List

[#2831] Upgrade process continue even if database not available

avatar
Created By: Olivier Guerrier (wolog)
Date Submitted: Sat Jan 03 16:03:29 -0500 2009

Assigned To: Alberto Benati (alby)
Version: 1.5.1
CMSMS Version: None
Severity: Minor
Resolution: Fixed
State: Closed
Summary:
Upgrade process continue even if database not available
Detailed Description:
When running install/upgrade.php, at step 5 my database was not reachable
(password changed in mysql server, and config.php not updated) but the script
just display 'database updated to version 31'. and the continue button was
accessible. Obviously, the step 6 just failed...


History

Comments
avatar 
Date: 2009-01-05 06:44
Posted By: Ronny Krijt (ronnyk)

I couldn't reproduce this issue. When trying an upgrade from 1.4.1 to 1.5.1 with
an incorrect password in the config.php, the upgrade didnt start, as after the
language-choice in the upgrade-script, the connection to the DB failed. So it
didnt start the upgrade process.
avatar 
Date: 2009-01-05 10:33
Posted By: Olivier Guerrier (wolog)

I fill the bug from memory, and seems I missed something. I've done it again
from start, and found the error in my report: the old mysql account was still
valid, but empty (no more tables inside)

Here is the exact error message I get at step 5:
"
 Upgrade schema
 Invalid query: SELECT version from cms_version
 The CMS database is up to date. Using schema version 31
"

Of course, after updating the config.php with the new account information, it
run well.
avatar 
Date: 2009-01-24 06:09
Posted By: Alberto Benati (alby)

You must use upgrade process with a running (and work) system.
A empty database is the same as new system, then you must use install process

Alby
avatar 
Date: 2009-01-24 08:11
Posted By: Olivier Guerrier (wolog)

I agree the issue was caused by an error on my side, but I report it to help
improve the quality of the installer. This is a "Error: success" message. Any
user providing the wrong mysql credentials (wrong as in pointing the wrong
database) will get the same error message.
Olivier.
avatar 
Date: 2009-03-17 19:03
Posted By: Alberto Benati (alby)

Fix in revision 150 of CoreInstaller
Updates

Updated: 2009-06-26 15:29
state: Open => Closed

Updated: 2009-03-17 19:04
resolution_id: 5 => 7

Updated: 2009-01-03 16:18
resolution_id: => 5
assigned_to_id: 100 => 112