ServerPress

Hi Natalia,

Thanks for your interest in WPSiteSync. At this time we do not have a feature for Syncing Content to more than one Target site at a time. This is something that we’ve had a few requests for and we do have plans to add it as a feature in the future. We would be happy to let you know when it’s available.

All the best.

Hello again.

I don’t quite understand your comment: “now I have to quickly change the Author ( post there is without Author) to admin”.

Do you mean that your user contributed content does not have an author id associated with it?

When WPSiteSync synchronizes the post, we use the user/author ID that you have configured as the Target site’s authentication user. So if you have a ‘contributor’ username on the Target and you use this when you authenticate, that user’s ID will be used for the Content on the Target site.

If this doesn’t suit your purpose, we do have a WPSiteSync for Authors plugin here https://wpsitesync.com/downloads/wpsitesync-for-authors/ which allows you to select which Author on the Target site to be used when syncing. But this may not work for you if you’re looking for automated syncing of the content since it does require user interaction.

Not sure why the post would disappear after a while. That must be caused by something else. Is the Content still in the database? Maybe there’s something else just filtering out the posts after they’ve been sync’d.

Hi jaroslawistok,

Thanks for your interest. While WPSiteSync does effectively copy/paste the Content of your page/post from one site to another, it does do a lot more. It also automatically copies all of the “extra” information associated with your post, such as taxonomy data, meta data and image references (both featured image, plus any images referenced within the post content). So it does save you some time when you have more complicated Content.

The reason you have to save the data and then send is because when you save it, all the information is written to the database. This is required because many plugins can add metaboxes and additional data to the post edit page. Saving to the database allows all these other plugins to save their data as well. Once that’s done, we can take a copy of it all and move it over to the Target site.

The “Site Key” is used to identify each site. If you have a setup where you have multiple Source sites all Pushing data to a single Target site, we identify each piece of content being sync’d by it’s post ID and the Site Key it came from. That way, we can properly track which Content has already been sync’d and where it came from.

WPSiteSync is not a backup plugin. We provide on-demand synchronization of Content and meta data between two sites. There are plenty of other solutions for backups and if that’s your need, we encourage you to look at those solutions.

We intentionally do not automatically sync Content. We have designed the tool for Content creation and management. So this helps with a couple of different workflows: to create and manage Content on a local development site and then Push that to a Staging site. Or, to allow creation of Content on a Staging site (possibly by multiple authors) and then, after approval or confirmation, easily move this data to a live site. It sounds like your workflow is outside of this since you have users creating content.

If you have some suggestions on some changes we can implement to help make the tool more useful for your workflow, we would like to hear those.

We’re sorry to hear that you’re not finding the tool very useful for your situation and we hope you keep us in mind when you do find a situation where this tool can be of more benefit for you.

Hi saschinger,

Thanks for writing to us.

The WPSiteSync plugin syncs Content only – no comments. To sync comments, you will need an additional plugin which we have been working on. But it sounds like you don’t want that anyway.

To sync the Content to multiple sites, you can either chain them by Pushing from Site 1 to Site 2, and then from Site 2 to Site 3, and so on. Or, you would have to change the configuration of the Source site to point to your different Target sites. We are working on a new plugin that will allow you to Push to multiple Target sites all at the same time, but that is not available yet.

Please let us know if you have any further questions.

Hi shgotlib,

So sorry, we didn’t see this question until now.

The ‘spectrom_sync_api_push_content’ is a filter, so you need to return the $data variable at the end of your callback function.

Try that and let us know how that works for you.

Hi samjco,

You can already push from multiple Source sites to a single Target site. Just configure each Source site to use the Same Target site in the WPSiteSync Configuration settings. WPSiteSync keeps track of which site sync’d the data so there is are no duplicates created. And we also handle all of the domain fixups no matter what the Source site is.

To allow multiple Target sites from a single Source site will require some code changes internally on how the API requests are handled in order to allow for Pushing the Content to multiple Targets. We can add these and make them available in our next update which will be released soon.

The biggest difficulties we can see in implementing this is how to design the UX and how to handle errors. For example, if you’re pushing to three sites and there’s an error on the second site, how do you communicate that back to the user via the UI? And do you keep trying to Push to site #3 or stop on the error for site #2? If there are multiple Targets configured, how do you indication which sites are to be updated during the next Push? There is a lot of UI that would need to be added in order to manage all of these options and clearly indicate success or failure for each Target to the user.

We’d be very happy to work with you on this. If you contact us on our support page at https://serverpress.com/contact/ we can send you code and instructions, as well as discuss the implementation details and UX.

Hi Svetlana,

Thanks for your inquiry.

The short answer to your questions is yes. But even so, WPSiteSync for Content may not be the right tool for you.

Whenever you Push your Content via WPSiteSync, the Target site requires a working copy of WordPress to be installed – with the WPSiteSync plugin activated. So your comment about “There are only DB and file directory with current data on the target server where the WP blog used to be” makes us think that you are not intending to have WordPress installed on this “backup” server. WPSiteSync will not be compatible with this set up.

We hope that answers your question. If you need anything more, feel free to reach out to us.