ealab

⚠️ Warning: Experimental plugin. Please make a full backup before use and test thoroughly.
<h4>About</h4>
The WordPress ecosystem has never offered a simple solution for managing content between environments. Since its inception, one problem persists: granular deployment of content and configurations.
You develop on a test site and want to send only certain content to your production site. With existing tools, two scenarios often occur: creating duplicates… or having to overwrite the entire database. The constraints imposed by the diversity of plugin ecosystem operations have already caused several attempts to fail.
We are convinced that a solution is possible.
That’s why we designed Deploy & Sync Content: a new approach, designed to finally offer selective synchronization between your environments.
<h4>Main Features</h4>
The free version offers unidirectional synchronization (Production → Staging/Local), ideal for simply transferring your content and media between your sites.
For bidirectional synchronization and advanced features, check out the Pro version(https://wp-deployer.io/en/features).
Intelligent database merging: The plugin detects existing content to update or create it as needed. You thus maintain the consistency of your environments and avoid any loss of information.
Unidirectional synchronization (free version): Production → Staging/Local: quickly transfer your content and media between your sites.
Data conflict management: The tool identifies and allows you to resolve differences before import, ensuring updates without loss.
Automatic ID mapping: Avoid duplicates and inconsistencies related to page builders and ID references.
Preservation of content relationships: Posts, taxonomies, media and metadata remain correctly linked after each synchronization.
<h3>Terms of use and External Services</h3>
Deploy & Sync Content is free to use and relies on the following services:
<ol>
<li>
Online Configuration Service (wp-deployer.io)
<ul>
<li>Purpose: Configures and updates the export/import system. This service is optional, but recommended until alternatives are provided by the community.</li>
<li>Data Collection:
<ul>
<li>IP address of your WordPress instance</li>
<li>Production URL (from plugin settings)</li>
<li>Site URL</li>
</ul>
</li>
<li>When Used:
<ul>
<li>During plugin activation</li>
<li>For configuration updates</li>
<li>For license verification (Pro version)</li>
</ul>
</li>
<li>Security: This data is used to protect our systems from spam and malicious use</li>
<li>Privacy: Data is not shared with any business partners</li>
<li>Terms & Privacy: <a href="https://wp-deployer.io/en/general-terms-and-conditions-use-gtcu" rel="nofollow ugc">https://wp-deployer.io/en/general-terms-and-conditions-use-gtcu</a></li>
</ul>
</li>
<li>
Local Data Storage
<ul>
<li>Purpose: Temporary storage for content synchronization</li>
<li>Location: in the <code>uploads</code> directory of your WordPress installations</li>
<li>Security: Data is stored on your servers and is not transmitted to any external services</li>
</ul>
</li>
</ol>
<h3>Credits</h3>
Deploy & Sync Content is developed by EA Lab.
Deploy & Sync Content includes the plugin.json file from the WP Optimize plugin 
(GPLv2+ licensed).
Deploy & Sync Content includes various software dependencies taken from the packagist 
repository, listed in vendor and vendor-prefixed directories. Most 
of them are unaltered in functionality. The only patched library is 
 jfcherng/php-diff, which has been patched for translation and customized 
rendering.

Deploy & Sync Content

Move your content easily from your production instance to your development instance.

jwong.dayspring

Copy Post removes the tedium of having to copy content, comments, and tags manually from one instance to another. It also preserves the original post author and date.
Copy Post was originally written when we were preparing to launch a public blog and wanted to pre-populate it with content from our in-office blog that we had been using for the past two years. If our marketing team thinks that something originally posted to our in-office blog would be helpful or meaningful to others outside of our company, they can easily copy it to the public blog. 
Copy Post could also be used in a situation where multiple WordPress instances are used in a development/staging/production setup.
First, a few assumptions and caveats.
<ul>
<li>You must have access to the MySQL database of the destination blog.</li>
<li>The author of the post you are copying must have an account on the destination blog with the same login name, though the IDs don’t have to be the same.</li>
<li>Categories assignments are not copied over, mainly because in our case the categories on the two blogs are different and were going to be edited anyway.</li>
<li>Comments attributed to registered users retain this attribution only if the commenter has an account on the destination blog (just like the author). If the commenter doesn’t have an account, the comment is still copied, but it’s treated as if it were made by an unregistered visitor.</li>
</ul>
Use the copy post feature to send a post to a destination blog. You’ll need the post ID, which is available by looking at the edit link for the post. The plugin will copy the post content, tags, and comments. The original author and post date will be retained. All category information will not be copied over. The resulting post will be set as a “private” post to allow you to set the categories and make edits before it goes live. Also, you’ll need to be an admin on the source blog to use the plugin.
The settings for the destination blog are configured directly in the WordPress Admin interface, making it possible for us to distribute the plugin to anyone who would need it.

Copy Post

Copy Post allows you to copy posts from one instance of WordPress to another.

Deploy & Sync Content vs Copy Post