Upgrade from 4.13 to 4.xx compiled

[smallfri]

I was comtemplating an upgrade from 4.13 to 4.14 or the latest version of compiled merchant.

My site is doing great, but I want to take advantage of some modules that are not available for 4.13, like Search Engine Tweak Pro.

Am I nuts? Can anyone tell me advantages or disadvantages I haven't thought of?

I'm hosted with dotcomhost, so I'm not concerned about host support.

Thanks,

Russell

[Vic - WolfPaw Computers]

The only concerns are cost of module upgrades and loss of archived order data.

A bug in the upgrade script from 4.13 to 4.14+ has a bug in it that requires the orders.dbf be cleared out.

There is a change in the database structure of the orders.dbf.

This isnt a significant problem for most. Just export your orders to a flat file and download them...then clear out the orders.dbf and upgrade.

Of course, your hosting account also has to have access to run using the Empresa 4.x or 5.x engine.

[ILoveHostasaurus]

Vic, what is this bug that you're referring to? I don't think I've ever seen a customer need to clear out their orders to upgrade from uncompiled to compiled. The structure of orders.dbf changes but the upgrade handles that fine with the exception of needing a special procedure if you have a third party paypal module in use.

[Vic - WolfPaw Computers]

Vic, what is this bug that you're referring to? I don't think I've ever seen a customer need to clear out their orders to upgrade from uncompiled to compiled. The structure of orders.dbf changes but the upgrade handles that fine with the exception of needing a special procedure if you have a third party paypal module in use.

We reported it as a bug quite a while ago. In fact, within a couple weeks of the release of 4.16.

There is a javascript function in the upgrade.mvc that fails at about 91-93%. The javascript functions Upgrade_Finished() and Upgrade_Finished_With_Errors() fail to return a value and causes the script to hang. The status bar on the browser shows "Done." but the status bar on the upper frame is stuck at either 91% or 93%.

I went 12 rounds with MIVA support on this and they finally conceeded there was in fact a problem, but they could not track it down. It seemed to only occur in stores with third party modules, but we could not isolate which modules would trigger it.

Here is a link to the original post when Bruce found the error about the time we did:
http://www.mvdevelopment.com/mvlists2/10/145930.html

[ILoveHostasaurus]

Only time I've seen an upgrade hang there has been because the store was using the older Emporium Plus paypal mod when it was still named paypal.mv and that's the point at which the upgrade tried to integrate the third party paypal data using the now built-in paypal.mvc module. Using the upgrade procedures in Bill's compiled module will work around that though without the need to purge the orders. I haven't seen an upgrade hang there otherwise, assuming the databases pack clean prior to trying the upgrade.

[Marc Anderson]

If you are moving from uncompiled to compiled and have invested in numerous modules, you may want to consider what it is going to cost to purchase compiled modules to accomplish those features that you need to carry forward to the compiled store.

[DesignExtend-MSI]

We reported it as a bug quite a while ago. In fact, within a couple weeks of the release of 4.16.

There is a javascript function in the upgrade.mvc that fails at about 91-93%. The javascript functions Upgrade_Finished() and Upgrade_Finished_With_Errors() fail to return a value and causes the script to hang. The status bar on the browser shows "Done." but the status bar on the upper frame is stuck at either 91% or 93%.

I went 12 rounds with MIVA support on this and they finally conceeded there was in fact a problem, but they could not track it down. It seemed to only occur in stores with third party modules, but we could not isolate which modules would trigger it.

Here is a link to the original post when Bruce found the error about the time we did:
http://www.mvdevelopment.com/mvlists2/10/145930.html

Is this only when upgrading online? I've not seen this problem, but just about every upgrade we've done has been done offline, via db tools and MIA.

[Vic - WolfPaw Computers]

Some of the stores we've seen it occur on do not use any of the paypal modules, bundled version or third party.

The only thing they did have in common was the use of third party modules themselves. Although we never tracked them to the point of identifying WHICH particular third party modules they had in common.

Hasnt been much of an issue anymore, we just clean out the orders.dbf before hand and go on about the upgrade.

[DesignExtend-MSI]

Some of the stores we've seen it occur on do not use any of the paypal modules, bundled version or third party.

The only thing they did have in common was the use of third party modules themselves. Although we never tracked them to the point of identifying WHICH particular third party modules they had in common.

Hasnt been much of an issue anymore, we just clean out the orders.dbf before hand and go on about the upgrade.

Hmm, maybe we upgrade differently then. I can't think of a single upgrade we've done without third-party modules installed.

[jason - jmh web services]

I was comtemplating an upgrade from 4.13 to 4.14 or the latest version of compiled merchant.

My site is doing great, but I want to take advantage of some modules that are not available for 4.13, like Search Engine Tweak Pro.

Am I nuts? Can anyone tell me advantages or disadvantages I haven't thought of?

I'm hosted with dotcomhost, so I'm not concerned about host support.

Thanks,

Russell

Search Engine Tweak Pro isn't needed. Just use the viking templates and do even more.
Category Page Templates (http://www.jmhonline.net/mivamerchantmodules/Category_Screen_Modules/)
Product Page Templates (http://www.jmhonline.net/mivamerchantmodules/Product_Screen_Modules/)