We detect that you currently have v1.5.2, and must perform the updates to get to...

[badarac]

I just reinstalled and generated a valid set of log files. I confirmed that they contained the errors before I sent them. Sorry. Emailed to Dr b and Cindy.

[DrByte]

[18-Mar-2016 15:06:35 America/Chicago] MySQL error 1067 encountered during zc_install:
Invalid default value for 'pwd_last_change_date'
ALTER TABLE zen_admin MODIFY admin_pass VARCHAR( 255 ) NOT NULL DEFAULT '';

As an update to the previous SQL I posted, I think the following will work better, since it forces all the schema changes in one statement so the validator doesn't fail due to other column format mismatches, and this also updates existing "bad" data so errors aren't triggered to bad dates already in the table records:

ALTER TABLE admin MODIFY COLUMN pwd_last_change_date datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_modified datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_login_date datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_failed_attempt datetime NOT NULL default '0001-01-01 00:00:00';
UPDATE admin SET pwd_last_change_date='0001-01-01' where pwd_last_change_date < '0001-01-01';
UPDATE admin SET last_modified='0001-01-01' where last_modified < '0001-01-01';
UPDATE admin SET last_login_date='0001-01-01' where last_login_date < '0001-01-01';
UPDATE admin SET last_failed_attempt='0001-01-01' where last_failed_attempt < '0001-01-01';

This would go into the top of the upgrade SQL files for 151, 153, 155, above any other statements making alterations to the admin table.

[badarac]

As an update to the previous SQL I posted, I think the following will work better, since it forces all the schema changes in one statement so the validator doesn't fail due to other column format mismatches, and this also updates existing "bad" data so errors aren't triggered to bad dates already in the table records:

ALTER TABLE admin MODIFY COLUMN pwd_last_change_date datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_modified datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_login_date datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_failed_attempt datetime NOT NULL default '0001-01-01 00:00:00';UPDATE admin SET pwd_last_change_date='0001-01-01' where pwd_last_change_date < '0001-01-01';
UPDATE admin SET last_modified='0001-01-01' where last_modified < '0001-01-01';
UPDATE admin SET last_login_date='0001-01-01' where last_login_date < '0001-01-01';
UPDATE admin SET last_failed_attempt='0001-01-01' where last_failed_attempt < '0001-01-01';

This would go into the top of the upgrade SQL files for 151, 153, 155, above any other statements making alterations to the admin table.

The good news is that it's a different error now. I've attached the logs here.

[DrByte]

MySQL error 1406 encountered during zc_install: Data too long for column 'reason' at row 1
ALTER TABLE zen_admin MODIFY COLUMN pwd_last_change_date datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_modified datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_login_date datetime NOT NULL default '0001-01-01 00:00:00', MODIFY COLUMN last_failed_attempt datetime NOT NULL default '0001-01-01 00:00:00';UPDATE admin SET pwd_last_change_date='0001-01-01' where pwd_last_change_date < '0001-01-01';

1. Why does your "admin" table contain a column named 'reason'?
2. It appears my post missed a carriage-return before the UPDATE statement tacked onto the end of the long ALTER TABLE statement.

[DrByte]

A new zip for v155, dated 03-21-2016, was just posted, which includes numerous updates to zc_install, and should address the issues discussed in this thread.

[badarac]

A new zip for v155, dated 03-21-2016, was just posted, which includes numerous updates to zc_install, and should address the issues discussed in this thread.

I downloaded the 3/21 zip and did a clean install in my wamp environment. The clean install went fine. I then imported the 1.5.0 database and started the install again to do the database upgrade. It gives me this message "An existing configure.php file was found. However your database seems to be current. This suggests you are on a live site. Proceeding with Install will wipe out the current database contents! Are you sure you want to install? ". It does not give me the database upgrade option. I checked the project_version and project_version_history in the DB and both say1.5.0.

[badarac]

I want to retract that last post. I've done several more clean installs, database imports of 1.5.0, and upgrades. For some reason it is no longer giving me that message. Perhaps there was something left over from some iteration that was causing it. In the most recent installs I deleted all file folders and dropped all tables prior to starting the install. It now goes through the clean install, import of the old db, restart upgrade. It does require an upgrade of the config files even though they are already at 1.5.5 but it does so with no problems. Then upgrade the database and all upgrades complete successfully. No erros or debug logs generated. Thanks all!

[DrByte]

Woot! Thanks Rick. Appreciate your patience and willingness to test.

[badarac]

Woot! Thanks Rick. Appreciate your patience and willingness to test.

I did the easy part

[mcubedpe]

A new zip for v155, dated 03-21-2016, was just posted, which includes numerous updates to zc_install, and should address the issues discussed in this thread.

FYI - thought I'd mention I had similar problems - saying unable to upgrade to 1.5.3 - as it was stuck at 1.5.2...

This Thread was helpful tried everything... still didn't work.

I reviewed the logs/ folder and found very helpful error messages that led me to run these queries:

ALTER TABLE customers MODIFY COLUMN customers_password datetime NOT NULL default '0001-01-01 00:00:00';
ALTER TABLE customers MODIFY COLUMN customers_dob datetime NOT NULL default '0001-01-01 00:00:00';

UPDATE customers set customers_dob = '0001-01-01 00:00:00' where customers_dob = '0000-00-00 00:00:00';
UPDATE customers set customers_password = '0001-01-01 00:00:00' where customers_password = '0000-00-00 00:00:00';

As well as I had to delete the duplicate entry into the countries table... and then the upgrade proceeded normally.

This was a rather old Zen-Cart that has been updated periodically since at least 2009... this latest upgrade where I ran into these problems was 1.5.1 to 1.5.5.

-Michael