Not able to upgrade to 1.5 from 1.4.26 and 27 Not able to upgrade to 1.5 from 1.4.26 and 27
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Not able to upgrade to 1.5 from 1.4.26 and 27

Started by lars_4, September 21, 2010, 09:23:14 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

lars_4

Hi!

I am having serious issues of when upgrading to the latest 1.5 version.
It seems that the SQL query's are only partially being applied in the database.
I have tryed to run some SQL upgrade query's directly into the DB, some of them work and some not.
Most of the query's that fail manually are marked as "already done / applied" on the upgrade.php page.
The MySQL user has full privileges to that database.
I have now tryed to upgrade 5 times, and rolled back 5 times since i get Fatal errors on all the tries.

This is the first fatal error: accesslevel column is missing in the usergroups table (somewhat like that)

I have fixed that through manually pushing this update into the DB, then another issue pops up.
Also the third SQL statement in the update.sql seems to error manually, the INDEX (EXTENSTION) does not excist.

Server Info:
Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny9 with Suhosin-Patch
MySQL client version: 5.0.51a
PHP extension: mysql

The files on disk are removed by the script, but 99% of the SQL query's for the update are marked as Already done / applied by the update.php script.

Does anyone has any suggestions?

I have used PHP / MySQL for years, i have never come across this issue before...

ΑndrĂ©

Quote from: lars_4 on September 21, 2010, 09:23:14 PM
I am having serious issues of when upgrading to the latest 1.5 version.
Moving from cpg1.5 install to cpg1.5 upgrading ::)


Quote from: lars_4 on September 21, 2010, 09:23:14 PM
This is the first fatal error: accesslevel column is missing in the usergroups table (somewhat like that)
[..]
Also the third SQL statement in the update.sql seems to error manually, the INDEX (EXTENSTION) does not excist.
I assume those are the queries that doesn't work:
ALTER TABLE CPG_usergroups ADD access_level tinyint(4) NOT NULL default '3';
ALTER TABLE CPG_usergroups ALTER access_level SET DEFAULT '3';
[..]
ALTER TABLE CPG_filetypes DROP INDEX `EXTENSION`, ADD PRIMARY KEY ( `extension` );



Quote from: lars_4 on September 21, 2010, 09:23:14 PM
The MySQL user has full privileges to that database.
I suggest to review that.