My upgrade procedure...
1. Installed a test version of my live 1.3.9h store to a new folder and a new database. Checked that everything was working fine. OK.
2. Uninstalled all addons. Checked core functions. OK.
3. Uploaded 1.5.1 files (overwrite all) and started /zc_install
4. System check = all green --> Upgrade.
5. Checkboxes 1.3.9-->1.5.0 and 1.5.0-->1.5.1 checked. Prefix (no change): zen_ . Upgrade database.
6. Errors:
7. These errors are stored in table zen_upgrade_exceptionsCode:SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist. SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist. SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists. SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.
8. Screen from admin_activity_log after above
8. If I then try to install a SQL update through the admin interface (say http://www.zen-cart.com/downloads.php?do=file&id=868) the following errors turn up:
The same error (ERROR: Cannot insert configuration_key "" because it already exists) is displayed regardless of which 1.5.1 addon I try to install.
9. The errors from admin sql are then stored in exceptions with double prefixes
What's up? My configures.php files defines "define('DB_PREFIX', 'zen_');". I've even tested to change and remove the prefix in step 5 above to no avail. The prefix (zen_) stays in the database.
My database account has all privileges.
Note that I recover my 1.3.9 database every time between tests.


Reply With Quote

