WPSiteSync for Content

Description

WPSiteSync for Content helps Designers, Developers and Content Creators Synchronize Blog Post and Page Content between WordPress installs, in Real Time, with a simple Click of a button!

  • Local -> Staging
  • Staging -> Live
  • Local -> Staging -> Live

Support Details: We are happy to provide support and help troubleshoot issues. Visit our Contact page at http://serverpress.com/contact/. Users should know however, that we check the WordPress.org support forums once a week on Wednesdays from 6pm to 8pm PST (UTC -8).

The WPSiteSync for Content plugin was specifically designed to ease your workflow when creating content between development, staging and live servers. The tool removes the need to migrate an entire database, potentially overwriting new content on the live site, just to update a few pages or posts. Now you can easily move your content from one install to another with the click of a button, reducing errors and saving you time.

WPSiteSync for Content is fully functional in any WordPress environment. We recommend using DesktopServer, but it is not a requirement.

This benefits the Development Workflow in more ways than one:

  • Real-Time LIVE Sync eliminates data loss such as Comments.
  • Saving development time with No files to backup, download and upload.
  • Limit mistakes copying and pasting.
  • Client Approval on Staging site is now Faster and Easier than ever.
  • Getting paid before Project Delivery is even Easier!

In the Free Version, WPSiteSync for Contents synchronizes the following:

  • Blog Post Text Content
  • Page Text Content
  • Content Images
  • Featured Images
  • PDF Attachements
  • Meta-Data (including Advanced Custom Fields)
  • Taxonomy such as Tags and Categories
  • And much much more

In our Early Adopter Trailblazer Program, you will also Receive:

  • WPSiteSync for Bi-Directional Pull (Syncing from Live to Staging)
  • WPSiteSync for Custom Post Types
  • WPSiteSync for Author Attribution
  • WPSiteSync for Comments
  • WPSiteSync for BulkActions
  • WPSiteSync for BeaverBuilder
  • WPSiteSync for Genesis Settings
  • WPSiteSync for WooCommerce Products
  • FULL access to ALL future Premium Extensions

For more perks such as Early Access and Exclusive Preview of upcoming Features, please visit us at WPSiteSync.com

ServerPress, LLC is not responsible for any loss of data that may occur as a result of WPSiteSync for Content’s use. However, should you experience such an issue, we want to know about it right away.

Screenshots

  • Configuration page.
  • WPSiteSync for Content metabox.

Installation

Installation instructions: To install, do the following:

  1. From the dashboard of your site, navigate to Plugins –> Add New.
  2. Select the “Upload Plugin” button.
  3. Click on the “Choose File” button to upload your file.
  4. When the Open dialog appears select the wpsitesynccontent.zip file from your desktop.
  5. Follow the on-screen instructions and wait until the upload is complete.
  6. When finished, activate the plugin via the prompt. A confirmation message will be displayed.

or, you can upload the files directly to your server.

  1. Upload all of the files in wpsitesynccontent.zip to your /wp-content/plugins/wpsitesynccontent directory.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.

You will need to Install and Activate the WPSiteSync for Content plugin on your development website (the Source) as well as the Target web site (where the Content is being moved to).

Once activated, you can use the Configuration page found at Settings -> WPSiteSync, on the Source website to set the URL of the Target and the login credentials to use when sending data. This will allow the WPSiteSync for Content plugin to communicate with the Target website, authenticate, and then move the data between the websites. You do not need to Configure WPSiteSync for Content on the Target website as this will only be receiving Synchronization requests from the Source site.

FAQ

Installation Instructions

Installation instructions: To install, do the following:

  1. From the dashboard of your site, navigate to Plugins –> Add New.
  2. Select the “Upload Plugin” button.
  3. Click on the “Choose File” button to upload your file.
  4. When the Open dialog appears select the wpsitesynccontent.zip file from your desktop.
  5. Follow the on-screen instructions and wait until the upload is complete.
  6. When finished, activate the plugin via the prompt. A confirmation message will be displayed.

or, you can upload the files directly to your server.

  1. Upload all of the files in wpsitesynccontent.zip to your /wp-content/plugins/wpsitesynccontent directory.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.

You will need to Install and Activate the WPSiteSync for Content plugin on your development website (the Source) as well as the Target web site (where the Content is being moved to).

Once activated, you can use the Configuration page found at Settings -> WPSiteSync, on the Source website to set the URL of the Target and the login credentials to use when sending data. This will allow the WPSiteSync for Content plugin to communicate with the Target website, authenticate, and then move the data between the websites. You do not need to Configure WPSiteSync for Content on the Target website as this will only be receiving Synchronization requests from the Source site.

Do I need to Install WPSiteSync for Content on both sites?

Yes! The WPSiteSync for Content needs to be installed on the local or Staging server (the website you’re moving the data from – the Source), as well as the Live server (the website you’re moving the data to – the Target).

Does this plugin Synchronize all of my content at once?

No. WPSiteSync for Content will only synchronize the Page or Post content that you are editing. And it will only Synchronize the content when you tell it to. This allows you to control exactly what content is moved between sites and when it will be moved.

Will this overwrite data while I am editing?

No. WPSiteSync checks to see if the Content is being edited by someone else on the Target web site. If it is, it will not update the Content, allowing you to coordinate with the users on the Target web site.

In addition, each time Content is updated or Synchronized on the Target web site, a Post Revision is created (using the Post Revision settings). This allows you to recover Content to a previous version.

Does WPSiteSync only update Page and Posts Content?

Yes. Support for Custom Post Types is coming very soon. Additional plugins for User Attribution, Synchronizing Comments and Pulling content are in the testing stage and will be released soon as well.

More complex data, such as WooCommerce products, Forms (like Gravity Forms or Ninja Forms), and other plugins that use custom database tables will be supported by additional plugins that work with those products.

Reviews

Really isn’t ready for production

I’ve been trying to use this plugin package since July 2016. Having signed up for the VIP thing, I was kind of hoping that some of my support requests would have been answered.

However, that aside, the problem with this setup is that it is largely dependent on site owners deactivating security plugins to allow access – you might think that’s reasonable, but security is there for a reason!.

Even if you decide to identify and deactivate those watchful plugins (hardly a time saver) there are still countless problems getting the plugin to work.

And working from local to live is a nonsense as the so-called “pull” plugin can not pull content unless it already exists on the target site.

As mentioned above, the support is non-existent, and the documentation vague and about as constructive as the Daily Mail.

The internet if full of ways to waste time and money and this plugin successfully does both.

Bugs!!

In file classes/apirequest.php
Line 710 better be:
'post_status' => 'inherit',

(following code will upload all related attachments to the new site however it’s NOT compatible with Attachments Plugin,and also has lots of bugs. So the following code is not recommended)

foreach ($post_children as $child_id => $child_post) {
	$attach_id = $child_id;
        if($attach_id != 0)
	$this->send_media($child_post->guid, $post_id, $post_thumbnail_id, $attach_id);
}

And same file Line 716 -> Line 789 has a logic bug! what if the image is just an external link? and what if image is not added by Add Media then class attribute does not generate?

Actually Line 716 -> Line 789 can be removed if you DO NOT need upload files to new site.
Meanwhile, you should also remove line 330 in file classes/apicontroller.php.
Then links(images) will become external links refered to the old site’s media library.

The answer to many problems

This is a product that dreams are made of. Create the content on a stage server, then press a button to have it go live! Amazing! I have it installed on an intranet server that is very complicated (SSO with active directory, no TLD, Visual Composer), and so far it works like a charm. Support helped me get around a few issues, but well worth the effort.

Read all 11 reviews

Contributors & Developers

“WPSiteSync for Content” is open source software. The following people have contributed to this plugin.

Contributors

“WPSiteSync for Content” has been translated into 1 locale. Thank you to the translators for their contributions.

Translate “WPSiteSync for Content” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.3.2 – Oct 12, 2017

  • fix: improve checking for sync-specific meta data to be ignored
  • fix: only set user id if available in SyncApiController->push()
  • fix: improved code that recovers from errors displayed within JSON response data
  • fix: set $media_id property during ‘upload_media’ API calls to media type after create/update of image
  • fix: adjust parameter for wp_get_attachment_image_src()
  • fix: check parameter passed to debug_backtrace() in case of old (< 5.3.6) versions of PHP
  • fix: handle empty post content and featured images correctly (Thanks to Lucas C.)
  • fix: correct taxonomy term lookup on Target to preserve naming (Thanks to Calvin C.)
  • fix: when changing Target or Username configs, require passwords (Thanks to Erin M.)
  • fix: javascript compatibility issue with Visual Composer backend editor (Thanks to Carlos)
  • fix: set taxonmy type for each taxonomy entries when processing hierarchical taxonomies
  • fix: recover and continue from failures of media attachments rather than aborting
  • fix: add Source to Target URL fixups in meta data and excerpt (Thanks to Bryan A.)
  • enhancement: add hook to notify add-ons that images have completed processing
  • enhancement: allow add-ons to modify HTTP post content during ‘upload_media’ API calls
  • enhancement: allow authentication to check for email address, in addition to user name
  • enhancement: add detection and circumvention of ‘Coming Soon’ / ‘Maintenance Mode’ plugins during API calls
  • enhancement: allow add-ons to modify allowed mime types during ‘upload_media’ API calls
  • enhancement: allow add-ons to modify content_type column in sync table
  • enhancement: make display of error messages via UI easier
  • enhancement: add callback to remove data from WPSS tables when content is deleted
  • enhancement: add appropriate headers for AJAX responses
  • enhancement: add ‘match-mode’ option to allow users to perform new content lookups on target by post title or slug; deprecate SyncApiController::get_post_by_title()
  • enhancement: add fallback encryption when mcrypt is not available

1.3.1 – Jan 11, 2017

  • Fix: add placeholder file to force creation of languages/ directory.
  • Enhancement: Additional changes in preparation for WPSiteSync for BeaverBuilder.
  • Enhancement: Better error messages when empty or missing post content is encountered.
  • Enhancement: Improved Media Library image lookup for use by BeaverBuilder add-on.
  • Enhancement: Added pre processing hook for use by ACF add-on.

1.3 – Dec 22, 2016

  • fix: fix author assigned on revisions when Pushing Content to Target
  • fix: add/update text domain used on some translation strings (Thanks Pedro M.)
  • fix: change to handling of featured image data (Thanks Josh C.)
  • fix: handle attachments for WP installs in subdirectories (Thanks Rudi L.)
  • fix: change to permissions checking that sometimes resulted in the inability to push Content (Thanks Rudi L.)
  • fix: update ‘unique_filename_callback’ filter to work with WP 4.7
  • enhancement: add features for WPSiteSync for Beaver Builder
  • enhancement: display better error messages if authentication process fails on Target (thanks Chris F.)
  • enhancement: check user capabilities when authenticating on Target
  • enhancement: return error if auth token cannot be saved on Target site
  • enhancement: optimizations to licensing system (Thanks Dominick K.)
  • enhancement: better handling of serialized postmeta data

1.2.2 – Oct 7, 2016

  • Fix: Add missing file.

1.2.1 – Oct 7, 2016

  • Fix: Update collation on created table for some hosts.
  • Enhancement: Add checks for updates to add-ons via WPSiteSync.com site.
  • Fix: Sanitize password hash for encryption algorithms. (thanks Jonah W.)
  • Enhancement: Specify timeout for API calls.
  • Enhancement: Remove any error output interfering with JSON data in API calls.
  • Enhancement: Improve error handling/recovery on API calls.
  • Fix: Update checks for allowed post types. (thanks Cathy E.)
  • Enhancement: Improve UX for License Keys.

1.2 – Sep 7, 2016

  • Fix: Changes to resolve authentication issues. (thanks to Craig S., Cathy E., Josh C. and Jason H.)
  • Enhancement: Some optimizations and code cleanup.
  • Enhancement: Updates in the Settings page for validating URLs. (thanks to Craig S.)
  • Fix: Fixing a table name reference when removing tables on uninstall.
  • Enhancement: Code to protect JSON data being returned via API calls when third-party plugins throw runtime errors.
  • Fix: Fix URL references in the Help text. (thanks to Pedro M.)
  • Fix: Fix text domain reference. (thanks to Pedro M.)
  • Fix: authentication token save. (thanks to Jeff C.)
  • Enhancement: Changes to allow new features in upcoming add-ons.
  • Enhancement: Change API code to work with any Permalink setting on Target site.

1.1.1 – Jul 20, 2016

  • Fix for authentication issues that sometimes occur after initial credentials are entered.

1.1 – Jul 8, 2016

  • Add features to Settings page and extensibility of APIs in preparation for add-on functionality.
  • Fixed several bugs in Settings, data migration after update, admin UI and runtime errors.
  • Add response object to API filters; allows display of API warnings in UI.

1.0 – Jun 29, 2016

  • Official Release.
  • UI improvements.
  • Image attachments sync title, caption and alt content.
  • Allow PDF attachments.
  • Updates to support Pull operations.
  • Change name of API endpoint to ensure uniqueness.
  • Add Target Site Key to settings and change database structure.
  • Turn on checks for Strict Mode.
  • Small bug fixes.

0.9.7 – Jun 17, 2016

  • Release Candidate 2
  • Fix some authentication issues on some hosts.
  • Improve mechanism for detecting and syncing embedded image references within content.
  • Fix duplicated messages in Settings.
  • Check mime types of images to ensure valid images are being sent.
  • Optionally remove settings/tables on plugin deactivation.
  • Other minor bug fixes, improvements and cleanup.

0.9.6 – May 20, 2016

  • Release Candidate 1
  • Add authentication token rather than storing passwords.
  • Fix issue with not removing Favorite Image on Target when image removed on Source.

0.9.5 – May 2, 2016

  • Fix CSS conflict with wp-product-feed-manager plugin; load CSS/JS only on needed pages and make CSS rules more specific.

0.9.4 – Apr 29, 2016

  • Fix media upload for images referenced within the Content and for featured images.

0.9.3 – Apr 26, 2016

  • Fix taxonomy sync issue when taxonomy does not exist in some conditions on Target.

0.9.2 – Apr 22, 2016

  • Fix runtime error when embeded images are in content.

0.9.1 – Apr 20, 2016

  • Work around for missing apache_request_headers() on SiteGround; fix misnamed header constant.

0.9 – Apr 18, 2016

  • First release – BETA