Staging lets you try plugin updates, a new design or new content on a private copy of your site before the live site sees them. Clonex Pro copies the files and the database of the whole site to a folder of the same site, such as example.com/staging, with its own database tables. When the copy is ready, you push the parts you choose back to the live site; see Push a staging copy to live and undo a push.
Where to find it: ARN Smart → ARN Clonex → Staging. Only administrators see it.
Staging is for single sites. On a multisite network there is no Staging screen; a network administrator copies whole sites under Network Admin → ARN Clonex instead. See Copy, split out and bring in network sites.
Staging copies stay on your server. Clonex uploads nothing anywhere.
Create a staging copy
- Open Staging. The New staging copy card is titled Copy the whole site to a private staging site.
- Enter a Folder name: lowercase letters, digits and hyphens, at most 40 characters, starting with a letter or a digit. Address of the copy shows where the copy will open, for example
https://example.com/staging. WordPress's own folder names (such aswp-admin,wp-contentandwp-includes) and common server paths (such asadmin,loginandcgi-bin) cannot be used. - Click Create staging copy.
The Running task card shows each step, for example Copying the database tables and Changing addresses in the copy. When the copy is finished, the card says The staging copy is ready, followed by its address.
Keep the page open while the task runs. If the page closes or the connection drops, open Staging again: the task goes on where it stopped. If the server stops answering, check the connection and click Continue. Cancel task stops the task after the piece of work it is doing now; a copy that is not finished can then be deleted.
A site can have up to 3 staging copies. With three copies the card says that the site has the most it can have; delete one to make a new one.
Your staging copies
Each copy in Your staging copies shows its folder name, the date it was made and its status:
| Status | Meaning |
|---|---|
| Ready | The copy is finished. Open opens its admin area in a new tab, and Push to live… is available |
| Being made | Clonex is still creating the copy |
| Being deleted | Clonex is removing the copy |
| Not finished | The task stopped or was cancelled. Delete the copy and make a new one |
Delete asks for a confirmation and then removes the copy with all its files and tables. This cannot be undone.
What the copy is like
| Area | On the staging copy |
|---|---|
| Who can open it | Only administrators of the copy. Visitors are sent to the login page; logged-in users who are not administrators see This is a private staging copy. Only its administrators can open it. The REST API answers administrators only, and XML-RPC is off |
| Users | The copy starts with the users of the live site at the time it was made, so you sign in with your usual administrator account |
| Search engines | Pages carry noindex and nofollow, and Discourage search engines from indexing this site stays on |
| No e-mail leaves the copy: order e-mails, password resets and notifications are not sent | |
| Scheduled tasks | No scheduled event runs by itself, including WooCommerce's Action Scheduler queue. Backups, webhooks and e-mails of the live site stay on the live site. An administrator can still run an action by hand |
| Admin bar | A red STAGING label, so the copy is never taken for the live site |
| Addresses | The site address and folder are changed everywhere in the copy, also inside serialized, JSON, URL-encoded and base64 data and page builder data. A longer host name, such as example.com.tr next to example.com, is never touched |
Inside the copy, the Staging screen only says that this is a staging copy: pushes are always started from the live site.
ARN licences on the copy
ARN Pro plugins keep working on the staging copy with the live site's licence; no new activation is needed. Licence changes are blocked on the copy: Activate and Disconnect in ARN Center show that the copy uses the live site's ARN licence and that licences are activated or disconnected on the live site. This keeps the live licence from being released from the copy. Refresh still works.
Servers that run nginx
nginx does not read .htaccess files. On an nginx server the New staging copy card says so, and the copy uses plain links (?p=123) until your host adds a rewrite rule for the copy's folder. After the host has added the rule, choose your link structure again in the copy's Settings → Permalinks. A push never changes the link settings of the live site.
Sites that cannot be copied
Clonex copies only sites that keep WordPress's folders in their usual places. Instead of the form, the Staging screen shows a message when:
- Clonex cannot read the site's
wp-config.php; - the Site Address and the WordPress Address in Settings → General are different (WordPress in its own folder);
- the
wp-content, plugins, must-use plugins, themes or uploads folder is outside the WordPress folder.
These site layouts are not supported, and there is no setting to change this.
Large sites and shared hosting
- The work runs in short steps of at most 20 seconds (or half of the server's PHP time limit, if that is shorter), and large files are copied in pieces of 1 MB. This also works on shared hosting.
- Before it copies, Clonex checks the free disk space. If there is not enough, the task stops with the space it needs and the space that is free; free some space or ask your host for more.
- If the uploads folder is larger than 5 GB, the task asks whether to Copy the uploads folder or Show the live site's media. A copy that shows the live site's media is marked so in its row, and its push has no Media files part.
- If a database table of the site has a name so long that its copy would exceed the MySQL limit, the task stops and names the table.
- Very large database rows whose addresses cannot be changed safely on the server keep the old address; the finished message says how many there are.
When you delete the plugin
Deleting Clonex Pro does not delete staging copies. Delete the copies you no longer need under Staging first. See Debug Console, plugin data and support.