Evan Herman

Ben Rothman

<p>Post Cloner will create a quick to access action button on the post/page edit screen alongside ‘Edit’, ‘Quick Edit’, ‘Trash’ and ‘View’.</p>
<p>All cloned posts, pages and custom post types will have ‘- Clone’ appended to the end of their title. All cloned posts, pages and custom post types will also be set to draft so they don’t appear anywhere on your site until you decide to publish them.</p>
<blockquote>
<p><strong>Features</strong></p>
<ul>
<li>Clone posts, pages and custom post types</li>
<li>Full control over what is clone-able (Example: Enable cloning pages but disabled for posts)</li>
<li>Works with Easy Digital Downloads</li>
<li>Complete clone of posts/pages including taxonomies and meta data (includes featured images, categories, tags and any custom metadata assigned to the post/page/custom post type)</li>
<li>Lightweight, compact solution</li>
<li>Nonce checks implemented for security</li>
<li>High quality code adhering to <a href="https://make.wordpress.org/core/handbook/best-practices/coding-standards/" rel="nofollow ugc">WordPress Coding Standards</a></li>
</ul>
</blockquote>
<p><strong>FuturePlans</strong></p>
<ul>
<li>Additional settings to adjust post data of the new cloned post</li>
</ul>


Post Cloner

Too simple, Too good. Post and Pages ready in a few seconds.



Simple and Fast

The one issue I have found is that when creating custom post types with PODS, that when a custom field such as "Relationship [type: pick]" where the value is another post type, the selected values are not copied over.



Does 99.9 % of the job

Works perfectly!

Post cloner allows you to easily make complete duplicates of any post on your site. That includes posts, pages and custom post types.

migrate

nick843

<p><strong>Try it out on your free dummy site: Click here => <a href="https://tastewp.com/plugins/wp-clone-by-wp-academy" rel="nofollow ugc">https://tastewp.com/plugins/wp-clone-by-wp-academy</a>.</strong><br />
(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)</p>
<p>WP Clone is a great way to backup, migrate or clone a WordPress site to another domain or hosting server.</p>
<p>You can also use it to backup, migrate or clone your site to/from local server hosting, to create backup of your site for development or testing purposes, and to install pre-configured backups of WordPress.</p>
<p>WP Clone is a superior to other backup & migrate plugins for the following reasons:</p>
<ul>
<li>It does not require FTP access to backup files you migrate or clone, neither the source or destination site; just install a new WordPress on the destination site, install our backup plugin, and follow the prompts to migrate or clone your site.</li>
<li>It does not backup or restore the WordPress system files (it just creates user content and database backups); reducing upload time for migration and improving security of your site</li>
<li>It fetches the site backup via your host’s direct http connection, which saves you from having to upload large backup files, making it easier to migrate.</li>
</ul>
<h4>What are today’s limitations?</h4>
<p>Today:</p>
<ul>
<li>90% of cases: Backups & migrations work flawlessly (we fixed some key bugs in the most recent version)</li>
<li>9% of cases: Backups or migrations fail due to your hoster’s configurations (most likely limits in up- and downloads) which is typically the case when you backup or migrate very large sites. However, there’s a workaround: simply do a “Database Only” backup (use “Advanced Settings”), transfer the wp-content directory over with FTP, and then restore new site. Then backup and migration also works.</li>
<li>1% of cases: Your site/hosting is abnormal (pardon our French) and backup or migration doesn’t work. However: that’s what we’ll now be working on, so that eventually backups and migrations will work in all cases.</li>
</ul>
<p>The 1% case means:</p>
<ul>
<li>Basic rule: DO NOT use it as your only backup solution! Only use it for migrations (so that if something fails, you still have the files on your old site as backup).</li>
<li>If you want to use it as backup, test it by restoring the backup file on a new site. If that works fine you should be safe.</li>
<li>In any case, we cannot take any responsibility if backup or migration fails.</li>
</ul>
<p>Note:<br />
* There is never an issue in damaging the source installation (i.e. on the site where you create the backup). So backup sites at your pleasure. If your backup succeeds then chances are good that the migration (i.e. restore on another site) will also succeed. But don’t take any chances.<br />
* If backup or migration (restore) fails, just try it again. Often it works on second attempt.</p>
<h4>Other tips how to backup and migrate</h4>
<ul>
<li>NEVER overwrite an installation for which you do not have an alternate backup source (e.g. a cPanel backup). Normally you would restore the backup onto a fresh WP installation on another host or on a subdomain. If the restore fails your destination site might become unusable, so be prepared to enter cPanel and then destroy / recreate the new installation if necessary.</li>
<li>DO NOT use our backup plugin on WP Engine or any hosting system with proprietary operating system. Instead, use their built-in backup tools.</li>
<li>Large sites (>2GB) might take as long as an hour to backup and migrate. Sites of 250 MB or less should take no more than a minute or two to backup, depending on your server.</li>
<li>We recommend you deactivate and delete page caching, security and maybe redirection plugins before you migrate, and re-install them on the new site, if necessary. In general, delete all unnecessary plugins and data from your site before you backup. You can also use the “Exclude directories” option if you have large media files, which you can then copy back to the new site with FTP.</li>
<li>How to copy from local server to your hosted website: Create a backup of the local site in the usual way, then save the backup file (right-click > Save) to your local disk. Upload this file to the root directory of your destination website and then use this url in the “Restore” dialog of the new site: http://yourdomain.com/.</li>
</ul>
<h4>Help Video</h4>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/xN5Ffhyn4Ao?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h4>Credits</h4>
<p>WP Clone uses functions from the “Safe Search and Replace on Database with Serialized Data” script first written by David Coveney of Interconnect IT Ltd (UK) http://www.davidcoveney.com or http://www.interconnectit.com and released under the WTFPL http://sam.zoy.org/wtfpl/. Partial script with full changelog is placed inside ‘lib/files’ directory.</p>
<p>This plugin is part of the Inisev product family – <a href="https://inisev.com" rel="nofollow ugc">check out our other products</a>.</p>


Post Cloner vs Clone