Host DadaWPBuild

Changes and publishing

Live-site conflicts and busy sites

When the live site changed too, and sites that take orders, bookings or comments.

What a conflict is

Staging is a copy of your live site taken at one moment. If something on the live site changes afterwards (you edit a page in WordPress, a plugin updates a setting, a product's stock goes down), staging doesn't know about it. Sending staging's version of that item would overwrite the live change.

So when you press Check what changed, and again just before sending, WPBuild compares the live site now with the live site when staging was copied. Any page, post, setting or file that changed on both sides is:

  • shown with Also changed on live since the copy, and what changed;
  • left unticked, so it isn't sent by accident.

What to do

  • Leave it unticked and send the rest. The live version stays as it is.
  • Refresh staging: if the live site has changed a lot, send what you want to keep, then use Copy live again and ask for the change again on the fresh copy.
  • Send it anyway: tick Send even if live changed the same items since the copy. Only do this when you're sure staging's version should replace the live one.

Shops, bookings and other busy sites

Sites that receive new data all the time need more care. Here is exactly what happens:

On your live siteEffect of a send
Orders, refunds, subscriptionsNever sent or changed.
Comments and reviews stored as commentsNever sent or changed.
Customer and user accountsNot part of a normal send. Only users you or the AI changed on staging are listed, and only sent if ticked.
A product, booking item or other page you sendIts content, custom fields (such as price and stock) and categories are replaced with staging's.
Settings you tickReplaced with staging's value.

For a shop: if a product's stock changed on the live site since the copy, it's flagged as a conflict. Don't force it through, or the stock goes back to staging's figure. Sending a product that sold nothing since the copy is fine. After a product is sent, WooCommerce's shop filters, price sorting and stock status are refreshed for it automatically.

Rolling back a product puts back its stock figure from before the send. If it sold in between, check its stock in WooCommerce afterwards. Orders themselves are never touched.

The same applies to plugins that keep data in pages or settings: bookings calendars, membership levels, event tickets. If in doubt, untick it, or refresh staging first.

Timing

  • Send soon after making a change: the fresher the copy, the fewer conflicts.
  • For a busy shop, send at a quiet time.
  • Check what changed again if some time has passed since you last checked. It's checked again automatically when you send.