.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Thank you :)
Hi,
When we are happy with the new shop, our next step is to do a backup again of the latest live database live_database2.sql as well as new_database.sql. Then drop the tables in new_database.sql and load live_database2.sql. Then re-run /new_shop/zc_install to upgrade the current data again to include new orders, customers, products etc.
My question is:
Will we lose the third party module changes to database after re-importing live_database2.sql to new_database.sql? If we will, what is the best way to do this so that we don't miss any orders?
Yes. So make a detailed list of those changes so you can make them again quickly by following a checklist.
You can even do a practice run ahead of time, to be sure you've got a thorough list, and that way your actual down-time for the live site will be minimal ... possibly only a few minutes.
As for going live, I'm a firm believer of using the actual live database for the upgrade ... BUT ONLY AFTER you've first done all the testing you already mentioned. Explained here: http://www.zen-cart.com/entry.php?3-...d-of-upgrading ... This still has the same issue you mentioned in your last post, but you remove the risk of lost data because you're not dropping anything, and not exporting/importing either. Just safer that way. Of course, having solid backups is important also.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Hi DrByte
Getting a bit confused... Am I right that there are two ways of upgrading?
A. Rebuild everything in a separate folder new_shop. When everything is satisfied, upgrade live site directly based on the changes recorded from the new_shop. This is from this article http://www.zen-cart.com/entry.php?3-...d-of-upgrading
B. Rebuild everything in a separate folder new_shop. When everything is satisfied, move live site to a separate folder old_shop and change new_shop to live site. This is from this article http://www.zen-cart.com/content.php?148
I am more comfortable with the second method. It might be more tedious but it seems safer and cleaner. So my next questions is that after I drop the tables in the new database and reload the live database a second time, do I simply re-run the install.sql files of 3rd party modules since the files are still in new_shop. Is there anything else to redo or reinstall?
While I can't comment specifically on every change you've made to your site, yes that's the concept. Simply run whatever setup/install process is relevant to the modules/plugins/addons/whatever you've added/changed/upgraded. zc_install takes care of the main core data and structure. And *you* take care of whatever additional components you've decided to integrate on top of it.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.