On a WordPress multisite network, Clonex Pro copies whole sites. A network administrator finds three tools on one screen:
- Copy a site: copy a site of the network to a new site of the same network.
- Site to single site: take a site out as a single WordPress site in a folder of the same server.
- Single site to network: take a single WordPress site on the same server into the network.
Where to find it: Network Admin → ARN Clonex. The screen is called ARN Clonex — Network copies. Only network administrators can open it. Clonex Pro must be active for the network with an active licence; a network administrator manages the licence under Network Admin → Settings → ARN Center.
Everything stays on your server. Clonex does not move sites to another server or host.
Content copies (the Copy action, Simple Mode, Duplicate and Production) still work inside each site and copy content within that site. Staging copies are for single sites; see Make a private staging copy of the whole site.
How the tasks run
Each tool starts a task. The Running task card shows its steps; keep the page open while it runs. If the page closes, open Network Admin → ARN Clonex again and the task goes on where it stopped. Cancel task stops it after the piece of work it is doing now. Only one task runs at a time. Recent site copy tasks lists the latest tasks.
Like staging, the work runs in short steps, so it also works on shared hosting. Before it makes a single site, Clonex checks the free disk space.
Copy a site
- In Copy a site, choose the Site to copy.
- Enter the Address of the new site: lowercase letters, digits and hyphens, at most 63 characters. The help line shows the full address:
<slug>.example.comon a subdomain network,example.com/<slug>/on a subdirectory network. - Optional: enter a Title.
- Click Copy site.
The new site gets the content, settings and media of the source site, and the users of the source site get the same roles on the new site. When the task finishes, it says The new site is ready, followed by the address. The source site does not change.
The address is refused when WordPress reserves it, when a site with this address already exists, or when a file or folder with this name in the WordPress folder would hide the new site.
Site to single site
Take a network site out as a separate WordPress installation, for example to hand it to a client.
- In Site to single site, choose the Site.
- Enter a Folder name: lowercase letters, digits and hyphens, at most 40 characters. The help line shows the address, the network's address followed by the folder.
- Click Make single site.
A new folder on this server gets WordPress, the network's themes and plugins, the site's content and media, and its users. The site in the network stays as it is. The finished single sites are listed under the form with their address; Delete removes one with all its files and tables after a confirmation.
When the task finishes:
- Search engines are kept away until you turn them on in the single site's Settings → Reading.
- The single site keeps the network's limits. Plugin and theme installs and unfiltered HTML are off in its
wp-config.php, and the source site's administrators arrive as editors; you are its administrator. - It still uses the network's database user. Give it its own database user in your hosting panel before you hand it to someone else, then make its administrators administrators again.
- ARN Pro plugins need their own licence there. The network's licence is not taken along; activate the plugins on the single site with their own licences.
- Own domain. To give the single site its own domain, point the domain at its folder in your hosting panel and change its address in Settings → General.
- nginx servers. On nginx the single site uses plain links (
?p=123) until your host adds a rewrite rule for its folder.
If the network's wp-content, plugins, themes or uploads folder is outside the WordPress folder, WordPress is in its own folder, or Clonex cannot read the network's wp-config.php, a message replaces the form and sites cannot be taken out.
Single site to network
Take a WordPress site that lives in another folder of the same server into the network as a new site.
- In Single site to network, enter the Folder of the site on this server, the folder that holds its WordPress files.
- Enter the Address of the new site, as for Copy a site.
- Optional: enter a Title. Without one, the new site gets the title of the source site.
- Click Take into network.
Clonex reads the source site's database settings from its wp-config.php and reads its database without changing anything there. It adds the site's users to the network: users with an e-mail address the network already has are matched to those accounts, and the others keep their passwords. It copies the site's media and the plugins and themes the network does not have yet. When the task finishes, it says that the site is now part of the network; activate the copied plugins and themes for the new site if they are not active.
The users get new user IDs in the network. If plugin data of the site has columns that look like user IDs, Clonex leaves them as they are and names them in the finished message, so you can check them.
The source site keeps running unchanged in its folder. Remove it yourself when you no longer need it.
Sites that cannot be taken in
Clonex shows a message and starts nothing when:
- the folder does not exist, holds no WordPress, or is the network's own folder;
- no
wp-config.phpis found in the folder or one level above it; - the site is a network itself;
- its Site Address and WordPress Address are different (WordPress in its own folder);
- its
wp-config.phpsets its own place forwp-content, plugins or uploads; - its database settings in
wp-config.phpare written with PHP code instead of plain values, or Clonex cannot connect to its database with them; - it shares the network's database tables.