Minimum Version To Upgrade To 4.3.5

triplets · January 7, 2016, 12:00am

I want to upgrade one of my stores using 2.0.11. What is the minimum version I need to upgrade to before I can jump to 4.3.5?

Any hints or suggestions?

David

thetool · January 7, 2016, 12:00am

2.2.4

tbirnseth · January 7, 2016, 12:00am

And just to add... I think the max version that supports store_import addon is 4.2.5 so you would be importing to that version, then you will have to upgrade to each subsequent release. Note that earlier versions of 4.3.x have many bugs in the upgrade process. Work-arounds exist, but they can be tedious.

Suggest you search the knowledge base for 'store_import'. It will provide you with the relevant details and limitations.

triplets · January 8, 2016, 12:00am

Oh, that's right, I forgot they eliminated the Store Import addon. Darn.

thetool · January 8, 2016, 12:00am

I think the max version that supports store_import addon is 4.2.5 so you would be importing to that version.

4.3.2

triplets · January 8, 2016, 12:00am

I want to do this conversion on my local WAMP server. Anyone know what version PHP and MySQL cs-cart [font=arial]2.0.11 requires?[/font]

Am I going to have to switch sometime during the upgrade?

triplets · January 8, 2016, 12:00am

Anybody know what the correct Updates Server is for cs-cart 2.0.11. I tried http://updates.cs-cart.com and it shows nothing.

ANSWER:

For 2.0.15, your upgrade server should be "helpdesk.cs-cart.com".

At 2.2.1, this changes to "updates.cs-cart.com".

tbirnseth · January 8, 2016, 12:00am

Probably PHP 5.2 for 2.0, 5.3 for 2.1 and up to somewhere around 4.1, then 5.4.

No clue on mySQL.

thetool · January 8, 2016, 12:00am

I don't think it really matters if all you are doing is updating.?

triplets · January 14, 2016, 12:00am

OK, I've gotten pretty far. But I have hit a wall.

I upgraded from 2.0.11 to 2.2.5 PROFESSIONAL.

I installed 4.3.2 and am using the Store Import addon. It runs for about half an hour and then it stops. No errors in any logs. I have already maxed out all the PHP settings that I can think of.

Below is the last few lines from the Store Import Log

1452731089 -
Importing data

1452731089 -
Creating table: store_import_views

1452731089 - 13

1452731089 -
Importing data

1452731089 -
Creating table: IF

1452731090 -
Importing data

1452731092 -
Importing data

1452731093 -
Importing data

1452731093 - 1

1452731093 - Updating add-ons

1452731094 - 1

1452731094 - Updating data

Any thoughts or insights?

CS-Cart_team · January 14, 2016, 12:00am

OK, I've gotten pretty far. But I have hit a wall.

I upgraded from 2.0.11 to 2.2.5 PROFESSIONAL.

I installed 4.3.2 and am using the Store Import addon. It runs for about half an hour and then it stops. No errors in any logs. I have already maxed out all the PHP settings that I can think of.

Below is the last few lines from the Store Import Log

1452731089 -
Importing data

1452731089 -
Importing data

1452731089 -
Creating table: store_import_views

1452731089 - 13

1452731089 -
Importing data

1452731089 -
Creating table: IF

1452731089 -
Creating table: IF

1452731090 -
Importing data

1452731090 -
Importing data

1452731090 -
Importing data

1452731092 -
Importing data

1452731092 -
Importing data

1452731092 -
Importing data

1452731092 -
Importing data

1452731092 -
Importing data

1452731092 -
Importing data

1452731092 -
Importing data

1452731093 -
Importing data

1452731093 -
Importing data

1452731093 - 1

1452731093 - Updating add-ons

1452731094 - 1

1452731094 - Updating data

Any thoughts or insights?

Have you enabled the development mode during import? Add the following code to the end of the config.local.php file and run the import:

define('DEVELOPMENT', true);
error_reporting(E_ALL);
ini_set('display_errors', 'On');

If it fails again with no errors, it is definitely some time-out issues.

tbirnseth · January 14, 2016, 12:00am

Check your Apache 'Timeout' value. It should be 300 or more (suggest 600 which is 10 minutes of wall clock inactivity on the connection). Some hostings modify this by lowering to absurdly low levels.

Another thing is to try to determine the exact runtime on your server. I.e. how long the upgrade ran before it died. You can do this by removing the upgrade log file (or copy it to a new name) and then looking at the difference between the create time and modification time of the newly created log.

triplets · January 15, 2016, 12:00am

Thanks for all the help.

I finally was able to successfully upgrade this old store from 2.0.11 to 4.3.2

The problem was one of the early upgrade scripts (from 2.0.11 to 2.2.5) left out some important database fields that the new Store Import Addon was utilizing. Once I added these fields to the MySQL tables the import script ran all the way.

I was only able to figure this out after I installed a clean version of 2.2.5 and compared it to the one I just upgraded to 2.2.5. I noticed several tables in the database did not match.

CS-Cart_team · January 15, 2016, 12:00am

Thanks for all the help.

I finally was able to successfully upgrade this old store from 2.0.11 to 4.3.2

The problem was one of the early upgrade scripts (from 2.0.11 to 2.2.5) left out some important database fields that the new Store Import Addon was utilizing. Once I added these fields to the MySQL tables the import script ran all the way.

I was only able to figure this out after I installed a clean version of 2.2.5 and compared it to the one I just upgraded to 2.2.5. I noticed several tables in the database did not match.

We are glad to hear that you managed to resolve the issue yourself. Thank you for sharing this information.