The SQL statements created for the error log should not have the table prefixes included.
Process to create/demonstrate the error:
Clean install of Zen-Cart v1.5.6a 01042019
Upload ZCA-Responsive-Classic-for-Zen-Cart-1.5.6-v1.0.0-master
Select the zca_responsive_classic_tpl template.
Receive a notice:
Some configuration settings are different from the ZCA Responsive Classic template's default settings. See SITE/logs/zca_responsive_classic_20190417081356.log for details.
The log shows:
The ZCA "Responsive Classic" template (or a clone) was activated on 2019-04-17 08:13:56 and some of its default settings are different than those currently set. You can copy and paste the following SQL into your admin's Tools->Install SQL Patches to change those defaults:
UPDATE PFX_configuration SET configuration_value = '0', last_modified = now() WHERE configuration_key = 'SHOW_CATEGORIES_SEPARATOR_LINK' LIMIT 1;
UPDATE PFX_configuration SET configuration_value = '1', last_modified = now() WHERE configuration_key = 'SHOW_SHOPPING_CART_DELETE' LIMIT 1;
UPDATE PFX_configuration SET configuration_value = '1', last_modified = now() WHERE configuration_key = 'PRODUCT_LIST_PRICE_BUY_NOW' LIMIT 1;
UPDATE PFX_configuration SET configuration_value = '0', last_modified = now() WHERE configuration_key = 'PRODUCT_LISTING_MULTIPLE_ADD_TO_CART' LIMIT 1;
Attempting to run the commands as directed, generates the following errors:
Failed: 4
ERROR: Cannot execute because table PFX_configuration does not exist. CHECK PREFIXES!
ERROR: Cannot execute because table PFX_configuration does not exist. CHECK PREFIXES!
ERROR: Cannot execute because table PFX_configuration does not exist. CHECK PREFIXES!
ERROR: Cannot execute because table PFX_configuration does not exist. CHECK PREFIXES!
Note: 4 statements ignored. See "upgrade_exceptions" table for additional details.
And, in-page, it shows:
BE SURE TO DO A FULL DATABASE BACKUP BEFORE RUNNING SCRIPTS HERE
If you are installing 3rd-party contributions, note that you do so at your own risk.
Zen Cart® makes no warranty as to the safety of scripts supplied by 3rd-party contributors. Test before using on your live database!
Query Results:
UPDATE PFX_configuration SET configuration_value = '0', last_modified = now() WHERE configuration_key = 'SHOW_CATEGORIES_SEPARATOR_LINK' LIMIT 1;
UPDATE PFX_configuration SET configuration_value = '1', last_modified = now() WHERE configuration_key = 'SHOW_SHOPPING_CART_DELETE' LIMIT 1;
UPDATE PFX_configuration SET configuration_value = '1', last_modified = now() WHERE configuration_key = 'PRODUCT_LIST_PRICE_BUY_NOW' LIMIT 1;
UPDATE PFX_configuration SET configuration_value = '0', last_modified = now() WHERE configuration_key = 'PRODUCT_LISTING_MULTIPLE_ADD_TO_CART' LIMIT 1;
The commands, however will work in phpMyAdmin (or from the mysql
CLI client)
1 row affected. (Query took 0.0004 seconds.)
UPDATE PFX_configuration SET configuration_value = '0', last_modified = now() WHERE configuration_key = 'SHOW_CATEGORIES_SEPARATOR_LINK' LIMIT 1
1 row affected. (Query took 0.0002 seconds.)
UPDATE PFX_configuration SET configuration_value = '1', last_modified = now() WHERE configuration_key = 'SHOW_SHOPPING_CART_DELETE' LIMIT 1
1 row affected. (Query took 0.0002 seconds.)
UPDATE PFX_configuration SET configuration_value = '1', last_modified = now() WHERE configuration_key = 'PRODUCT_LIST_PRICE_BUY_NOW' LIMIT 1
1 row affected. (Query took 0.0002 seconds.)
UPDATE PFX_configuration SET configuration_value = '0', last_modified = now() WHERE configuration_key = 'PRODUCT_LISTING_MULTIPLE_ADD_TO_CART' LIMIT 1
As the first error messages indicated, the problem is with the prefixes. If the query is to be entered into the admin's Tools->Install SQL Patches page, then the prefixes should not be included as the Zen-Cart query factory adds them automatically, most of the time, and the database actually receives a double prefixed table name in this case. I.e.: PFX_PFX_configuration
As an extra point, probably an error with the factory and not the template, the error message says to See "upgrade_exceptions" table for additional details. That table does exist, but remains empty.
Note: This is probably created in the same, or similar, place as the same problem in the Responsive Bootstrap template: See Issue #150.