TEXO HELP CENTRE

Cloning and Staging with WordPress Toolkit

Cloning a WordPress website involves creation of a full website copy with all website files, the database, and settings.

You may want to clone your WordPress website in one of the following situations:

  • You maintain a non-public (staging) version of a WordPress website on a separate domain or subdomain, and you want to publish it to a production domain to make it publicly available.
  • You have a publicly available (production) WordPress website and you want to create a non-public (staging) copy of it, to which you can make changes without affecting the production website.
  • You want to create a "master" copy of a WordPress website with pre-configured settings, plugins, and theme, and then clone it to start a new development project for a client.
  • You want to create multiple copies of a WordPress website and make different changes to each one (for example, to show them to a client so that he or she can choose the one he or she likes best).

1. Go to WordPress Toolkit  in your cPanel and then click "Clone" on the card of the WordPress installation you want to clone:

2. Choose the target for the clone:

  • Keep "Create subdomain" selected to have WordPress Toolkit create a new subdomain with the default "staging" prefix or type in a desired subdomain prefix.
  • Select "Use existing domain or subdomain" and then select the desired domain or subdomain from the list.

3. Click "Start"

 

Copying Data from One WordPress Website to Another

You can copy the content of your WordPress website including files and database to another WordPress website.

Let us say you maintain a non-public (staging) version of a WordPress website on a separate domain or subdomain and a publicly available (production) version of this website on a production domain. You may want to copy data from one website to another in the following situations:

  • You want to copy the changes you have made to the staging version to the production version.
  • You want to copy the data from the production website to the staging website to see how the changes (for example, a new plugin) work with the production data. After checking that everything works fine, you may copy your changes to your production website.
  • You have made some changes (for example, installed a new plugin) to the staging website, and these changes resulted in new tables being added to the database. You want to copy only these tables to the production website without affecting other data.
  • You have upgraded the staging website to a newly released version of WordPress and fixed the post-upgrade issues (if any). You now want to push these changes to the production website.
  • You can choose to copy the WordPress files, the WordPress database, or both the files and the database. When copying the database, you can choose to copy all tables, or tables that are present on the source but absent from the target, or you can specify individual database tables to be copied.

When performing the copying, keep in mind the following:

  • The selected data are copied from the source website to the target website. Any files and/or database tables present both on the source and the target that are not identical are copied from the source to the target. Files and database tables present only on the target are not affected unless you select the "Remove missing files" option during copying.
  • During copying, the target website enters maintenance mode and becomes temporarily unavailable.
  • If the WordPress version on the target website is earlier than on the source website, WordPress Toolkit first upgrades WordPress on the target website to match the version installed on the source website, and then runs copying.
  • If the WordPress version on the source website is earlier than on the target website, copying is aborted. To copy data, you need to upgrade WordPress on the source to the version installed on the target or a later version.
  • If the database prefix on the source and the target differs, WordPress Toolkit will change the database prefix on the target website to match that on the source during copying.
  • Copying of data between a regular WordPress installation and a multisite one is not supported. We recommend that you use cloning instead.

To copy data of one WordPress website to another:

1. Go to WordPress Toolkitg in your cPanel and then click "Copy Data" on the card of the WordPress installation which data you want to copy:

2. Next to "Target", select the target WordPress installation you want to copy the data to.

3. Under "Data to Copy", select which data you want to copy to the target WordPress website:

  • "Files Only" - copies only the website files, including the WordPress core files and the files related to themes and plugins.

    Note: By default, the htaccessweb.config, and wp-config.php files are not copied because modifying these files may disrupt the operation of WordPress. You can have WordPress Toolkit copy the wp-config.php file by selecting the "Copy wp-config.php" checkbox. To make the checkbox visible, go to WordPress, click "Settings", select the "Allow to copy wp-config.php when using Copy Data feature" checkbox, and then click OK.

    Note: Even if you choose to copy the wp-config.php file, the information related to the database will not be copied. This prevents the target WordPress installation from corruption. Custom settings specified in the wp-config.php file on the target will be overwritten with those from the source.

  • "Database Only" - copies only the database. You can select to import all, new, or selected database tables (for details, see step 5 below).
  • "Files and Database" - copies both the website files and the database. You can choose to import all, new, or selected database tables (for details, see step 5 below).

4. If you selected "Files Only" or "Files and Database" during step 3, two more options become available:

"Replace files modified on target" - by default, if a file with the same name exists both on the source and the target, the file from the source will be copied and will replace the file on the target even if the source file is older. To prohibit overwriting files on the target with the files from the source that are older clear the checkbox.

"Remove missing files" - by default, if a file exists on the target but is missing from the source, the file is untouched. Select this checkbox to remove files on the target that are missing from the source.

Note: You can hide these options, making them unavailable to yourself and your customers. To do so, go to WordPress, click "Settings", clear the "Use rsync for file copy operations" checkbox, and then click OK.

5. If you selected "Database only" or "Files and Database" during step 3, select which database tables you want to copy:

  • "All Tables" (the default option). If you want to copy all changes except for pages, posts, and users, keep the "Except: _postmeta, _posts, _usermeta, _users" checkbox selected.
  • New tables only
  • Selected tables. Click "Select tables to copy", select those tables you want to copy, and then click Select.

6. Before copying data, WordPress Toolkit suggests creating a restore point. You can use it to roll back the changes made during copying. If you do not want to create a restore point, clear the "Create a restore point" checkbox. Learn how you can recover your WordPress installation using the restore point in "Restoring a WordPress Installation" section below.

Note: Every WordPress installation can only have a single restore point. Creating a restore point overwrites the existing restore point, if any.

7. When you are satisfied with the selected options, click Start to start copying data.

© Texo Webhosting cc
Reg No: 2008/030306/23 | VAT No: 4910258476 | B-BBEE
Tel: 021 782 3401 | Fax: 086 298 8141
cloud-sync