Not getting the Upgrade button when zc_install is run

I've made all the changes to both the configure.php files and started zc_install. I verified that the database, user and password entries are correct, but when I run zc_install I get the message that it appears that my database is current and I might be trying to do this on a live site. The reason the database appears to be current is that I just imported it into the new database from today's backup of the existing one.

The only step in the upgrade instructions that I couldn't follow is the one to use the same DB_PREFIX value from the old site’s configure.php file. It is null in the old store's configure.php file, so I left it null in the new one.

What am I doing wrong?

If you are upgrading from a to b, b to c, c to d in the same version set (i.e. 1.5.7), there is generally no need to update the database.

dbltoe:

If you are upgrading from a to b, b to c, c to d in the same version set (i.e. 1.5.7), there is generally no need to update the database.

No, upgrading from 1.5.5. Sorry, I ticked that off in my post but it doesn't seem to be showing up.

When you run the zc_install and are presented only with the install button, there are (or should be!) text towards the bottom of the page that identifies why only the install process is available. For instance, if an existing configure.php isn't found.

lat9:

When you run the zc_install and are presented only with the install button, there are (or should be!) text towards the bottom of the page that identifies why only the install process is available. For instance, if an existing configure.php isn't found.

The only text, under "Some Issues" is

The GZip Extension in PHP is not enabled
[ NOTE: This may not be relevant if you are using Nginx and handling GZip within Nginx. ]

I didn't think any zipped files were involved in this.

This is what I see:

Per that image, check that (a) the database and associated credentials are valid and (b) there's no /includes/local/configure.php that's overriding the settings in the base /includes/configure.php.

lat9:

Per that image, check that (a) the database and associated credentials are valid and (b) there's no /includes/local/configure.php that's overriding the settings in the base /includes/configure.php.

I've done that multiple times and don't see any problems. But I'll look again. If I start out with a fresh empty database, it installs fine. It's only when I import our current database and want to upgrade that the install won't continue.

Check that the dates are correct in your database. Also that admin passwords and cusrtomer passwords are both varchar 255.

It could be similar to whaat was happening at https://www.zen-cart.com/showthread.php?228672-Errors-on-1-5-1-to-1-5-7c

dbltoe:

Check that the dates are correct in your database. Also that admin passwords and cusrtomer passwords are both varchar 255.

It could be similar to whaat was happening at https://www.zen-cart.com/showthread.php?228672-Errors-on-1-5-1-to-1-5-7c

I'm pretty certain I've added no plugins that would affect date fields, or added a new date field. Definitely neither of the two that are mentioned in the date standardization section.

But do I understand correctly that you can't go up more than one major version at a time? If so, that's my first problem, trying to go from 1.5.5 to 1.5.7.

I've looked all through zc_install/includes/systemChecks.yml and compared each of the checks with the logfiles. In every attempt at upgrading, all the checks passed up through the htaccess, and the log ended there. Does it not record the fails as well as the passes, or does it just stop at the first fail?

I can't connect to my host to check the admin and customer password field types right now, so I'm trying to get a better overall understanding of what's happening during the upgrade process.

HeleneWallis:

But do I understand correctly that you can't go up more than one major version at a time? If so, that's my first problem, trying to go from 1.5.5 to 1.5.7.

You can go straight from 1.5.5 to 1.5.7.
If I had to guess what was happening I would say that you have your configure file pointing to a test database that's already at 1.5.7.

Download each of the configure files into empty folders and check them. Sometimes when you attempt to upload a configure file but there's already one there, the upload fails.

swguy:

You can go straight from 1.5.5 to 1.5.7.
If I had to guess what was happening I would say that you have your configure file pointing to a test database that's already at 1.5.7.

It shouldn't be. I just imported the database from my 1.5.5 live store.

I just checked the orders file in my test database. I have only three fields with a datetime type: last_modified, date_purchased and orders_date_finished. The default value for these is NULL, which I take it is incorrect. There were no fields with a 'date' type. The problem is that I don't know whether any of these is from a plugin. I did at one time attempt to use the Edit Orders plugin, but it never worked correctly and I removed it. But I didn't specifically uninstall it, so any changes it made to the orders file, in terms of fields added, would probably still be there.

It looks to me as though I need to run the command

UPDATE orders SET [fieldname] = '0001-01-01 00:00:00' WHERE [fieldname] < '0001-01-01' and [fieldname] is not null;

for all three of those fields. Does that look right?

This field: orders_date_finished is a new date field.
You have to follow the date update guidance here:

https://docs.zen-cart.com/user/upgrading/date_standardization/

Background:
https://docs.zen-cart.com/user/upgrading/could_not_upgrade/

Also review this if you have trouble once you're done fixing the initial issue:
https://docs.zen-cart.com/user/upgrading/unknown_column/

swguy:

This field: orders_date_finished is a new date field.
You have to follow the date update guidance here:

https://docs.zen-cart.com/user/upgrading/date_standardization/

Background:
https://docs.zen-cart.com/user/upgrading/could_not_upgrade/
Huh? That field's been in the database as far back as zc154 (haven't checked older installs).

LOL you're right. Apparently Stabucks needs to add a "Super-Venti" to the menu to wake me up sufficiently.

lat9:

Huh? That field's been in the database as far back as zc154 (haven't checked older installs).

What about the 'last_modified' field? That's the one I thought was most likely to have been added by the Edit Orders plugin. If all three of those fields are part of the original database, then the date and datetime field default contents should have been modified by the upgrade process.

HeleneWallis:

What about the 'last_modified' field? That's the one I thought was most likely to have been added by the Edit Orders plugin. If all three of those fields are part of the original database, then the date and datetime field default contents should have been modified by the upgrade process.
last_modified is also a default Zen Cart field; it's updated when/if an order's status is updated.