WordSync allows you to synchronise posts, pages, users, taxonomies, attachments and settings between two WordPress installs.
|Author:||Brave Digital (profile at wordpress.org)|
|WordPress version required:||4.0|
|WordPress version tested:||4.7.4|
|Added to WordPress repository:||23-03-2017|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Click to start download
The main WordSync interface showing the choice of processors available.
The review stage of a sync job in progress.
The plugin is required to be installed and activated on both the source and target sites.
Install the plugin as per usual, through the WordPress plugin repository or by uploading the zip file manually to your site and activate it on both sites.
Once activated, you can find the plugin under Tools -> WordSync
You will need to go into the WordSync Settings on each site (by clicking the ‘Settings’ button in the header) and set a identical Secret Key for both sites. Both sites will check that the other site’s key is identical to their own key before they authorize syncing.
On the target site you will need to enable Syncing (Write Permission) and on the source site you will need to enable Pushing (Read Permission).
How are the different site URLs handled?
As the sync process occurs, the source data is run through conversion filters which replace all instances of the source site’s URL with the target site’s URL.
WordSync doesn’t sync my data correctly!
WordSync is still in ALPHA and as such we still need to iron out all the different syncing scenarios and it is impossible to be able to test all eventualities. If you find a bug, please open a support ticket on our GitHub page or even better, submit a pull-request which fixes the issue to our GitHub repo.
Do both sites need to be online for syncing to work?
No, but the source site needs to be accessible from the internet. So you can sync your localhost with a source site on the internet, but a site on the internet would not be able to sync with your localhost unless you set up your home internet to allow public connections to your localhost server.
- User processor now handles user roles correctly.
- User processor now based on user_logins and not user_emails as logins are not changable after creation.
- Added settings postprocessing and excluded some settings which were harmful to migrate.
- Changed admin screen to use POST instead of GET to avoid URI too long messages.
- Changes are now processed in type order (update then delete then create)
- Added better error handling while processing changes.
- Added Cannot delete the current user check.
- Initial release