Deleting Shipping & Payement Modules Before Upgrade

Rather than upgrade I want to rebuild my site, since I will be entirely changing my template to a responsive one.

If I follow the instructions here and here I will start with a clean install. Then I will overwrite the new database with a backup from my live store and run an upgrade. I will add and test all of my template customizations, add-ons, language edits, ect. And have a brand new test-store looking and working perfectly before applying this to my live site. (I've done this once before with a past upgrade - worked great!)

My question is - where, in all of this, would I follow the step in the upgrade instructions that tells me to remove the payment and shipping modules from my current store before upgrading? To my thinking this is impossible because I won't ever have a test version of my live store admin where I can remove these modules.

I've done this before and simply can't remember doing this step. Thanks a million, in advance, for your advice!

I truly had searched the forum for this answer before asking... But the related posts below my question seemed to have presented the answer in this thread.

So, although the upgrade docs say to remove the shipping & payment modules BEFORE upgrading according to swguy I can actually do this after the upgrade as well.

I'll go that route unless someone here stops me soon. :)

From within the modules->shipping area, you would disable or "remove" the shipping modules which would make them inactive and then uninstall them which would remove their database entries (requiring reentry of the applicable information upon reenabling them).

Okay, I may have not provided the exact verbiage, but that is where the process is followed, and then the database backup from that point is what is restored to your new site. Otherwise you run the possibility that you may 1) have to do this on the new store or 2) not be able to access portions of the shipping settings because of the attempt through the database information of ZC to load something that doesn't exist.

Yeah, sometimes a search doesn't make finding an answer as easy as the "associated" search once posted. :) generally speaking the occurrence of a problem after the upgrade/rebuild is low, but it does happen. :)

OK - but in that case, that means I have to remove the modules from my live store and then make the database backup for the test store after which I will need to reinstall the modules to my live store so I can continue sales as normal while I work on the new test store. Am I getting you right?

More recent modules are being written smarter to avoid the need to remove/reinstall them.
So, can you list which payment/shipping modules you're using? and which ZC version you're upgrading "from" and "to"?

I'm going from version 1.5.1 to 1.5.5a

The modules are not many:

PayPal Payments Pro
PayPal Express Checkout
FREE SHIPPING!
Zone Rates

Thing is, I'm just not really liking the thought of removing them from my live site. Although, I certainly can buck up and do it if the remove and install cannot be done on the test site AFTER the upgrade.

Three Sisters:

I'm going from version 1.5.1 to 1.5.5a

The modules are not many:

PayPal Payments Pro
PayPal Express Checkout
FREE SHIPPING!
Zone Rates

Thing is, I'm just not really liking the thought of removing them from my live site. Although, I certainly can buck up and do it if the remove and install cannot be done on the test site AFTER the upgrade.
In the case of those modules, and going from v151 to 155a, you can skip the step of removing/reinstalling those modules. The only module in that list that adds/changes configuration settings is the EC module, but it's also smart enough to add the new stuff without requiring a reinstall. So, no special treatment required.

Three Sisters:

I'm going from version 1.5.1 to 1.5.5a

The modules are not many:

PayPal Payments Pro
PayPal Express Checkout
FREE SHIPPING!
Zone Rates

Thing is, I'm just not really liking the thought of removing them from my live site. Although, I certainly can buck up and do it if the remove and install cannot be done on the test site AFTER the upgrade.

And I'm not 100% backing the direction that said to uninstall them either. I would rather work out what issues I might come across, determine the way to overcome them, make that a "quick shot" solution for that store, try it again and verify that the quick shot works and then apply to the new upgrade at final run.... that way the live store truly is maintained operational through and through and only at the last "ready, set, go" does it go temporarily silent while the database is upgraded, and the final "patches" applied.

Guess was just saying, there could be problems, but nothing non-recoverable. :)

mc12345678:
Ah yes - Good point about addressing an issue if and when it arises. I have to remember that careful backups and careful planning do prevent complete, permanent disaster. :)

DrByte:

In the case of those modules, and going from v151 to 155a, you can skip the step of removing/reinstalling those modules. The only module in that list that adds/changes configuration settings is the EC module, but it's also smart enough to add the new stuff without requiring a reinstall. So, no special treatment required.

Ok - I'm going to move ahead hoping for perfect success!

Thanks bunches for all your help!