Upgrade from 2.2 to 3.1

[acabiya]

I started a store about 3 years ago. I want to Upgrade to the newest version. I have not seen documentation on upgrades. I'm upgrading from 2.2. to 3.1

 

Can someone tell me where to find documentation on how to upgrade.

 

I don't want to loose data doing this.

[Guest]

Angel,

 

 

There is currently NO stable release of v3.x. The available download of v3.0.1 is so developers can build on the existing framework. The latest stable release is v2.3.1 and includes upgrade instructions to go from v2.2 RC2a to v2.3.1.

 

 

 

 

Chris

[acabiya]

Angel,

 

 

There is currently NO stable release of v3.x. The available download of v3.0.1 is so developers can build on the existing framework. The latest stable release is v2.3.1 and includes upgrade instructions to go from v2.2 RC2a to v2.3.1.

 

 

 

 

Chris

 

 

THANKS A LOT. I'LL UPGRADE TO THE v2.3.1. Looks easier.

 

Angel

[w2vy]

The latest stable release is v2.3.1 and includes upgrade instructions to go from v2.2 RC2a to v2.3.1.

 

I recall in the MS2.2 days the upgrade included upgrade.sql files to go from version to version.

 

I do not see that with v2.3.1

 

Is there a non-manual way to apply the sql changes?

So far the only way I see is to copy and paste from upgrade_guide.pdf and that would be *very* error prone

 

Tom

[burt]

The simplest way to upgrade is to diff the SQL for 2.3.1 and the SQL dump of your existing DB (let's call this XYZ).

 

Then;

 

1. add any in from 2.3.1 that do not exist in XYZ.

2. change any that exist in both 2.3.1 and XYZ (eg, some of the varchar lengths)

 

Then;

 

You have a 2.3.1 compatible DB that also works with your old store.

 

Then;

 

Upload 2.3.1 into a folder on your live shop, and set up the configure files correctly

 

Then;

 

Test 2.3.1

 

Then;

 

Add in any desired contributions from your old shop to 2.3.1 (some go in easy, some not so easy)

 

Then;

 

Skin your new 2.3.1 to match your old shop

 

Then;

 

Have a beer. Or three.

[w2vy]

The simplest way to upgrade is to diff the SQL for 2.3.1 and the SQL dump of your existing DB (let's call this XYZ).

 

Then;

 

1. add any in from 2.3.1 that do not exist in XYZ.

2. change any that exist in both 2.3.1 and XYZ (eg, some of the varchar lengths)

 

Then;

 

You have a 2.3.1 compatible DB that also works with your old store.

 

Then;

 

Upload 2.3.1 into a folder on your live shop, and set up the configure files correctly

 

Then;

 

Test 2.3.1

 

Then;

 

Add in any desired contributions from your old shop to 2.3.1 (some go in easy, some not so easy)

 

Then;

 

Skin your new 2.3.1 to match your old shop

 

Then;

 

Have a beer. Or three.

 

Wow that has gotten a lot harder... back in osc 2.1 and 2.2 days we provided scripts to update the database

 

sigh

[burt]

In the old days, the Team did not go missing for months on end ;)

 

All that is not a lot of work actually. Anywhere between a couple of hours and a week (depending upon number of addons to reintegrate and theme of shop).

[w2vy]

In the old days, the Team did not go missing for months on end ;)

 

All that is not a lot of work actually. Anywhere between a couple of hours and a week (depending upon number of addons to reintegrate and theme of shop).

 

Yeah I know... (blush) I used to be one of them :)

[guidemesingapore]

Cool info available here.