Every time I try to upgrade my store it times out on
Backing up data for: phinxlog1486101903
The time-out check done before the upgrade, says all is ok.
I have
optimized the DB ahead of time.
Made backups of the DB
Disabled all 3rd party add-ons
Cleaned my logs in Administration - Logs
Set Compress to 'false' in App/Tygh/UpgradeCenter/App.php
I am trying now to upgrade from v 4.4.3 to v4.5.1
Last time I gave up and handed the task over to CS-Cart team for a lot of support credits but this is ridiculous. We must be able to upgrade our site ourselves.
I have about 4 tables in the DB named phinxlogxxxxxxx
Are they part of core CS-Cart or do they belong to an add-on ?
Perhaps an old add-on not used any more... Can I delete them ? They doesn't seem to contain more than a few dates and version numbers...
Any hints in the right diection would be appreciated.
Every time I try to upgrade my store it times out on
Backing up data for: phinxlog1486101903
The time-out check done before the upgrade, says all is ok.
I have
optimized the DB ahead of time.
Made backups of the DB
Disabled all 3rd party add-ons
Cleaned my logs in Administration - Logs
Set Compress to 'false' in App/Tygh/UpgradeCenter/App.php
I am trying now to upgrade from v 4.4.3 to v4.5.1
Last time I gave up and handed the task over to CS-Cart team for a lot of support credits but this is ridiculous. We must be able to upgrade our site ourselves.
I have about 4 tables in the DB named phinxlogxxxxxxx
Are they part of core CS-Cart or do they belong to an add-on ?
Perhaps an old add-on not used any more... Can I delete them ? They doesn't seem to contain more than a few dates and version numbers...
Any hints in the right diection would be appreciated.
These tables contain phinx log. They are created during the upgrade. I guess the issue is not related to these tables, it is just the last message that you see before upgrade script dies.
Please contact us via Customer Help Desk and provide temporary access to your server by clicking on the Add record link on the Access information page of your Help Desk account so that we could examine the issue.
If an upgrade completes successfully, why aren't the phinxlog* tables removed? I understand if there was a problem, but if it's successful they shouldn't be being left in the DB. Even on failure, I'm not sure how useful they would be. Minimally they should be exported and put with the upgrade backup.