ServerPress

Hello scottdc24,

Thank you for your interest in WPSiteSync. Unfortunately we do not currently support the Redirection plugin. Our promise with the free version of WPSiteSync in the WordPress repository is to support core WordPress. Any third party plugin such as Redirection would require code to specifically handle how they store their data.

We’ve added this request to our roadmap and when the feature becomes available we will let you know. But we can’t give a date as to when this might be available.

All the best,
The ServerPress Team

You can do one of two things:

1. If you can whitelist IP addresses in CleanTalk, you can whitelist the Source site’s IP and that should allow the API calls.

2. If you can whitelist an endpoint, all WPSiteSync API calls go to domain.com?pagename=wpsitesync_api – so whitelisting that should work.

All the best,
The ServerPress Team

Hello @splaquet,

Thank you for your interest in our Database Collation Fix tool.

The reason this tool was created was to change a database’s collation algorithm AWAY from utf8mb4_unicode_520_ci. This is because at the time, the utf8mb4_unicode_520_ci algorithm required MySQL v5.6 or later and many hosts did not yet support that. Also, many hosts were using MariaDB instead of MySQL and MariaDB also did not support the utf8mb4_unicode_520_ci algorithm.

This meant that if you exported your utf8mb4_unicode_520_ci collated database and tried to import it into these non compatible version, the import would fail. You would then need to tediously edit the .sql file and change the collation algorithm references.

So we created this tool to help move you away from the less compatible utf8mb4_unicode_520_ci collation to utf8mb4_unicode_ci, for example. And if you set the collation in wp-config to use the 520 algorithm, we specifically ignore this in favor of the more compatible algorithm. This was done on purpose, not as an oversight.

All of the utf8mb4 collation algorithms support Emoji characters. So even when using utf8mb4_unicode_ci, you’re fine.

If you would like to enable the use of the utf8mb4_unicode_520_ci algorithm, you could always modify the code and remove that from the $_change_collation list, allowing the wp-config setting to be used.

All the best,
The ServerPress Team

Hello @kath_g,

Okay, thanks for that information. This is something that has been reported to us already and we’re working on a fix for this. We should have something to address this shortly. If you need a fix immediately, you can contact us at https://serverpress.com/contact/ and we can get an update to you right away.

All the best,
The ServerPress Team

Hello, @kath_g

Thanks for contacting us about this.

When you say WPSiteSync stopped working, can you be more specific? Do you mean that when you click on the “Push to Target” button, that it doesn’t perform the synchronization? Or that it syncs the Content, but doesn’t do it correctly? Or that you’re unable to click on the “Push to Target” button? Is there an error message displayed?

We’ll check out the latest release of Classic Editor, but having more information on what the behavior is that you’re seeing would be helpful in making sure we’re addressing the issue that you are reporting.

All the best,
The ServerPress Team

Hi @parthsanghvi,

Thank you for your interest in WPSiteSync. We’re glad you are finding it helpful.

A 500 error is generally caused by a server configuration issue, not a programming. In this case it is on the Source site and is happening when you’re sending the Push to Target request from your browser to the Source site. This can be caused by several things such as rules in your .htaccess file or a plugin conflict.

To find the problem you can enable debugging https://www.ads-software.com/support/article/debugging-in-wordpress/ then reproduce the error and look at the log file in wp-content/debug.log. You can also view your web server log files. This may point you to the problem. If you still need help, you can submit a support ticket at https://serverpress.com/contact/ and send us your log files.

All the best,
The ServerPress Team

Hello @vikasgunjeti,

You are correct, Page Builders such as WPBakery store a lot of unique data and require additional processing via an add-on. Currently, we do not support the WPBakery Page Builder but it is on our roadmap.

All the best,
The ServerPress Team

Hello @vikasgunjeti, and thanks for contacting us.

There are no additional settings you need to use to enable Media syncing. It should work automatically. This usually indicates a conflict of some kind. You mention that the assets are “broken” — how are they broken? Are the Media files missing (you don’t see them in the Media Library section of the WordPress admin on the Target), or do they have the wrong domain name? This can sometimes happen when using a plugin to hide the WordPress login, or with some themes like Bedrock that change the URL where images are located.

We’d like to ask that you submit a support ticket here: https://serverpress.com/contact/ and include some log files so that we can determine what the cause of this is. To generate log files, you can follow the instructions here: https://wpsitesync.com/knowledgebase/enabling-debugginglogging-wpsitesync/

Once we have logs we can determine what the problem is. We do have an upcoming release that improves the synchronization of Media files and this may help you.

Thank you for your interest in WPSiteSync.

All the best,
The ServerPress Team

Hello, @eastviewgeospatial and thank you for your interest in WPSiteSync.

This sounds like a Javascript error. Can you use the Inspector tool in your browser to see if there are any errors reported?

The Inspector tool can also show why the image isn’t being displayed. Is it showing a 404 error for the image or something else?

It’s possible this is caused by the .htaccess file in the plugin folder. What version of Apache are your sites using? You might try temporarily renaming the .htaccess file and see if it resolves the issues.

We’d like to move this to our support system so we can get some additional information from you and work through this better. Please submit a support ticket here: https://serverpress.com/contact/ and let us know that you are eastviewgeospatial from the WP support forums.

All the best,
The ServerPress Team

Hello @seanpaulfx,

Thank you for your interest in WPSiteSync.

WPSiteSync copies all of your Content from the Source site to the Target site, including metadata, images, taxonomies, etc. If it’s a new post on the Source site, it will look just the same on the Target site.

We’re not sure what you mean by “look like a new post”. Is there something else that your site uses to determine if a post is “new”? Is there some metadata or other Content that needs to be different between the Source and Target sites?

The year and month directories used when Pushing images are the year and month values of the original image when it was uploaded. This should be the same year/month values used on the Target site when uploading the image there.

If something different is happening on your site, we would ask that you submit a support request at https://serverpress.com/contact/ and we can get some more information from you and help you better.

All the best,
The ServerPress Team

Since we’ve moved this and your other issue to our support system, I’m going to close this issue.

All the best,
The ServerPress Team

Hello Dave,

For sites using Basic Authentication, we have a free add-on in the repository. You can find that here: https://www.ads-software.com/plugins/wpsitesync-for-http-authentication/

Once installed, you can enter the Target site’s username and password for Basic Authentication in the WPSiteSync Configuration Settings.

All the best,
The ServerPress Team

Hello Dave,

Thank you for your interest in WPSiteSync.

Yes, the core WPSiteSync plugin from the WordPress repository synchronizes media files. In fact, the core plugin syncs everything that you can create in core WordPress: media (including featured images), taxonomies, tags as well as Gutenberg content. Our add-ons are needed for third party content such as Beaver Builder, WooCommerce, EDD, etc.

Please let us know if you have any further questions.

All the best,
The ServerPress Team

Hi @rolfjeger,

Thank you for your interest in WPSiteSync.

Yes, you can set things up the way you describe. You can “chain” sites by having your first site configured to Push to the second site, then the second site configured to Push to the third site.

To automatically synchronize Content, you can your our “WPSiteSync for Auto Sync” add-on https://wpsitesync.com/downloads/wpsitesync-for-auto-sync/ to automatically Push any changes as they are made. When the new Content arrives at the second site, it will be seen as a change, and automatically Pushed again to the third site.

If you have any questions about this setup, you can contact our Support at https://serverpress.com/contact/ and we can help you.

All the best,
The ServerPress Team

Since we’re helping you through our support system, we’ll close this ticket.

The ServerPress Team