System inspection does not offer database upgrade

[badarac]

A clean install was done of 1.5.5a. A database was exported from a live 1.5.0 install and imported to the 1.5.5a database with drop tables. Started zc_install again to do a database upgrade from 1.5.0 to 1.5.5a. System inspection indicates that config files exist and shows a button for clean install only. Four log files were created during the clean install and one log file during the second system inspection. The database tables project_version and project_version_history both indicate 1.5.0 after the import. Table upgrade_exceptions is empty.

PHP Version: 7.0.6 (Zend: 3.0.0)
Database: MySQL 10.1.14-MariaDB

Added: Admin has a message "Your database appears to need patching to a higher level. See Tools->Server Information to review patch levels.".
Server info page shows:

Zen Cart 1.5.5a
Database Patch Level: 1.5.0
v1.5.0 [2012-04-12 04:48:40] (Fresh Installation)
v1.5.0 [2012-04-12 04:48:40] (Fresh Installation)

[badarac]

Just a little additional info. I uncommented the echos in zc_install/includes/modules/pages/index/header_php.php at lines 42-45. This is what the system inspection page is finding for those vars string(5) "1.5.5" bool(true) bool(true) bool(true). Looks like the $dbversion is being set incorrectly.

If I set $dbversion to 1.5.0 it works as expected offering the upgrade button.

[badarac]

Just for chuckles I did this install in a local wamp environment to see if it might be related somehow to MariaDB. I had the same issue running the install on MySQL 5.5.

[mc12345678]

In all of the process to do the upgrade, was the database restore with 1.5.0 performed while zc_install was not being accessed?

Ie. No session info present.

[badarac]

No but I'll try it now

[badarac]

I just imported the database and opened the zc_install in the browser. It detected that config files exist but did not off the upgrade.

[badarac]

Same result on the MariaDB install

[mc12345678]

What happens if you change/move this line from 180 to just after the next closing curly bracket? Or revise it to break 2?

        if (isset($version)) break;

That was an initial thought which I now don't think will resolve the issue. The reason that I think that is because as I continued to review the yml file for version checking, I see some information related to each specific ZC version. I can translate this more, but if I'm somewhat hoping that I can just copy and paste it and perhaps you'll understand (on a cell phone at the moment). The thing to identify is if in your 1.5.0 database, the following characteristics of the database are true:

      - checkType: configValue
            fieldName: CC_ENABLED_DEBIT
            expectedResult: 'Credit Card Enable Status - Debit'
          - checkType: fieldSchema
            tableName: admin
            fieldName: reset_token
            fieldCheck: Type
            expectedResult: 'VARCHAR(255)'
          - checkType: fieldSchema
            tableName: orders
            fieldName: shipping_method
            fieldCheck: Type
            expectedResult: 'VARCHAR(255)'
          - checkType: configValue
            fieldName: CURRENCY_SERVER_PRIMARY
            expectedResult: 'Currency Exchange Rate: Primary Source'

For example, the first one to verify that in the configuration table that the key: CC_ENABLED_DEBIT has the value that is shown as expected. This could be because of other database actions taken to keep the store "up-to-date" or to support some other plugin, etc... but curious if all of those conditions match for this DB.

[DrByte]

Sounds like the DB_PREFIX doesn't match what's in the imported database

[badarac]

All of these match in the imported database

What happens if you change/move this line from 180 to just after the next closing curly bracket? Or revise it to break 2?

        if (isset($version)) break;

That was an initial thought which I now don't think will resolve the issue. The reason that I think that is because as I continued to review the yml file for version checking, I see some information related to each specific ZC version. I can translate this more, but if I'm somewhat hoping that I can just copy and paste it and perhaps you'll understand (on a cell phone at the moment). The thing to identify is if in your 1.5.0 database, the following characteristics of the database are true:

      - checkType: configValue
            fieldName: CC_ENABLED_DEBIT
            expectedResult: 'Credit Card Enable Status - Debit'
          - checkType: fieldSchema
            tableName: admin
            fieldName: reset_token
            fieldCheck: Type
            expectedResult: 'VARCHAR(255)'
          - checkType: fieldSchema
            tableName: orders
            fieldName: shipping_method
            fieldCheck: Type
            expectedResult: 'VARCHAR(255)'
          - checkType: configValue
            fieldName: CURRENCY_SERVER_PRIMARY
            expectedResult: 'Currency Exchange Rate: Primary Source'

For example, the first one to verify that in the configuration table that the key: CC_ENABLED_DEBIT has the value that is shown as expected. This could be because of other database actions taken to keep the store "up-to-date" or to support some other plugin, etc... but curious if all of those conditions match for this DB.