No sense for only 2 sites

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.

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,

It sounds like something is wrong then. We do assign an Author ID on the Target when the Content is Pushed. So if that’s empty, there may be an issue.

I would like to ask that you submit a support ticket to https://serverpress.com/contact/ with what you are describing and if possible, a database dump of both the Source and Target sites after the Push. That would help us to track this down.

Our goal is that, once the post is on the Target that it looks like like it would if you had created it on the Target. So if the Author ID is missing, that’s not right.

Hello jaroslawistok,

The usernames vs. email addresses shouldn’t make any difference when authenticating. You can use either one.

It’s possible that the host is blocking the API call, but I don’t think that’s the issue you’re seeing. If you can authenticate and send Content from one site you should be able to do it from another site. A host blocking the API call would more likely result in ALL Source sites being blocked, not just one.

If you like, we can investigate this further for you. Please contact us at our support page at https://serverpress.com/contact/ – we’ll need to know the URL that you’re using for your Target site and do a couple of tests to see if we can find the problem. And we may need some login credentials for a temporary account on the Target so we can check it out.

Hello jaroslawistok,

I can’t find your ticket in our issue tracking system. Can you please reply with the ticket number so we can track that down? Thanks!

Hi jaroslawistok,

I’m not finding a help ticket under that email address. And you don’t need premium support.

Please submit a new ticket at https://serverpress.com/contact/ with an explanation of the problem and the URL of your Target site. We’ll be happy to look into it.