Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Setup the dummy test gateway then test the workflows to ensure everything is still working as expected. You need to review everything carefully.How can you REALLY test this on a clone site, when your live site is constantly processing credit card payments and sending emails? We have disabled the mailer on our clone "DEV" server, but how can we be sure that CBsubs is functioning properly?
Create a backup which you'll be able to restore to if something goes wrong.Once we roll the live site over to CB2, there is "no going back", as we would lose tons of live data and paid subscriptions - ones which would be paid for, but nonexistent if we had to roll back.
So if this upgrade fails, it's an unmitigated disaster.
Test it on your dev site and get familiar with CB 2.x, its changes, and its new features. Once you're comfortable with it and are sure it'll work as you need it to then backup your live site, take it offline (give 24hrs notice that it will be offline at XYZ time for an upgrade), then perform the upgrade.As we're a subscription service site and we have users in every time zone around the globe, we can not get away with taking the live site offline for hours at a time for backup, testing, restore. We have to test the migration on the DEV site... any suggestions?
Please Log in or Create an account to join the conversation.