When your work on a staging copy is finished, push it to the live site from the live site's Staging screen. You choose which parts go live, Clonex shows what changed on the live site since the copy was made, and the most recent push can be undone for 7 days. To make a copy first, see Make a private staging copy of the whole site.
Where to find it: on the live site, ARN Smart → ARN Clonex → Staging, then Push to live… under a copy with the status Ready. A push cannot be started from inside the staging copy.
What a push can bring
Open Push to live…. Clonex first shows Checking what changed…, then lists:
- how many items changed in the staging copy;
- the items that changed on the live site after the copy was made, which Content and design would replace (or Nothing changed on the live site after the copy was made.);
- how many new comments the live site has; they stay where they are.
Then choose the parts to push:
| Part | Ticked at first | What it does |
|---|---|---|
| Content and design | Yes | Posts, pages, products, media library entries, menus, categories and tags, and the theme, widget and menu settings (also the front page and posts page, the site icon and Elementor settings) |
| Theme files | Yes | Each theme folder that changed in the copy replaces the live one as a whole |
| Media files | Yes | New and changed files of the uploads folder. Not offered when the copy shows the live site's media |
| Plugin files | No | Each plugin folder that changed in the copy replaces the live one as a whole. Plugins are not activated on the live site; activate a new plugin yourself under Plugins. ARN Clonex itself is never pushed |
| Plugin data tables | No | Offered when the copy has database tables of plugins. Each table you tick replaces the live table |
Because a changed theme or plugin folder is replaced as a whole, the live site never runs a half-copied theme or plugin.
What is never pushed
- Users, comments, orders and other shop records, sessions and logs. Tables whose names show that they hold orders, payments, customers, sessions, logs, API keys, webhooks or downloads are never offered.
- The live site's own settings, such as its address, licences and active plugins.
- Product stock, sales counts, rating counts and coupon use counts keep their live values, so orders placed on the live site while you worked on the copy stay correct.
- Files and theme or plugin folders that changed on the live site after the copy was made are left as they are and listed.
Push to live
- Tick the parts to push.
- If content changed on the live site after the copy was made, tick I understand: the staging version replaces the live content listed above. Clonex does not push until you confirm.
- Click Push to live and confirm. The confirmation says that the live site shows a maintenance page for a short time.
The Running task card shows each step. The live site shows WordPress's maintenance page only while its tables are switched; Clonex's own steps keep running. At the end, the maintenance page goes away, caches are cleared and the card says The push is complete. You can undo it for 7 days.
When ARN DualFix is active, the push form reminds you that a DualFix backup taken before the push adds one more way back. When ARN SiteWatch is active, the form says that SiteWatch will list the pushed files as changed files; that is expected.
Undo the last push
After a push, the copy's row shows Last push, with its date and the date until which it can be undone.
- Open Undo last push…. Clonex lists the items that changed on the live site after the push, because undo puts back the content from before the push and these changes go (or Nothing changed on the live site after the push.).
- If items are listed, tick I understand: the live changes listed above go back to how they were before the push.
- Click Undo last push and confirm.
Undo switches the tables and the theme and plugin folders back, puts the saved live files back and removes the files the push added. The live site shows the maintenance page while the tables switch. Orders and stock stay as they are now.
Remove undo copy deletes the saved tables and files of the push after a confirmation. The push can then no longer be undone.
Limits of undo
- 7 days. A push can be undone until the date in its row. After that the undo period is over, and Clonex removes the undo copy the next time you open Staging.
- Only the most recent push. Only the most recent push of all staging copies can be undone. If another copy pushed later, undo that push first, or remove this push's undo copy.
- One undo copy per staging copy. A new push from the same copy replaces the undo copy of that copy's previous push.
- A push or undo that stopped. If a push stopped halfway, the live site may be partly changed: the row says so, and no new push starts until you undo it, or remove its undo copy to keep the live site as it is now. A push that stopped halfway can always be undone. If an undo stopped, undo again to complete it.
- Saved data must stay in place. The saved live files are kept in the
clonex-undofolder of the uploads folder and the saved tables in the database. If a saved table is missing, the push cannot be undone. - Disk space. The undo copy takes space in the database and in the uploads folder until it is removed.
When a push stops with a message
| Message (short form) | What to do |
|---|---|
| Choose at least one part to push | Tick at least one part |
| The last push from a staging copy did not finish | Undo that push, or remove its undo copy, before a new push |
| Clonex cannot move a folder between the uploads folder and another disk | Nothing was changed. Push again without Theme files and Plugin files |
| The live table got so many new rows since the copy was made that ids would collide | Make a new staging copy and push from it |
| A folder is outside the WordPress folder | Clonex does not push folders outside the WordPress folder |
| A folder could not be moved or a file could not be written | Check the folder permissions on the server, then try again |