• Resolved ofmarconi

    (@ofmarconi)


    Hi!

    I wanted to know how your plugin works in this scenario:

    I will duplicate the site to make some changes (staging) after the updates, something that can take weeks, I need to return these changes to Production.

    In that time, for sure sales will be made, and the database will be updated.

    If I copy the PRODUCTION sales table and paste it into STAGING when I finish making changes, will it duplicate previous sales?

    Or recognize and will not duplicate a sale that is already in the installation.

    Sorry for the English GT.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author WP All Import

    (@wpallimport)

    Hi @ofmarconi,

    If you’re importing orders and worried about duplicating them, there are a couple of options:

    • Use an “Existing Items” import to create new orders and leave the “Update existing orders with changed data in your file” option disabled.
    • Or, use a “New Items” import along with custom code that uses our API to stop duplicates from being created (see example for products import)

    If I misunderstood, please elaborate/rephrase and I’d be happy to advise further.

    Thread Starter ofmarconi

    (@ofmarconi)

    Hey! Many thanks for the reply!
    I think that would solve it.

    My reasoning:
    1 – I would duplicate my site in PRODUCTION for a new installation (STAGING);
    2 – I would make the changes I need;
    3 – On the PRODUCTION website I use WP ALL EXPORT to export ORDERS;
    4 – At STAGING I use WP ALL IMPORT to receive the most recent ORDERS;
    5 – In conclusion, I migrate the updated site to Production.

    Does that make sense?

    My store is a digital download store, importing Orders, would Woo generate download authorizations?

    Thanks.

    Plugin Author WP All Import

    (@wpallimport)

    Hi @ofmarconi,

    Yes, that makes sense if you’re only wanting to sync orders.

    As for download permissions in the orders, there’s currently a bug related to that, but it should be fixed in the next release.

    Thread Starter ofmarconi

    (@ofmarconi)

    Thx!!!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Staging to Production – Database replace’ is closed to new replies.