WPSiteSync Error Messages Explained

To help you work through any problems using WPSiteSync, we’ve compiled a list of error messages that are displayed by the tool. There are a lot of error messages. Don’t let this discourage you. Most of these will never be seen by users. It’s only in the case of something out of the ordinary that one of these will be displayed.

“The requested action is not recognized. Is plugin activated on Target?”

This error is returned from the Target site when the requested API action is not recognized. It happens mostly when an add-on plugin, such as WPSiteSync for Menus or WPSiteSync for Genesis Themes is activated on a Source site and makes a request to the Target- where the plugin is not activated.

To resolve: Make sure that all WPSiteSync plugins activated on the Source site are also activated on the Target site. Additionally, ensure that all license keys are entered and activated on the Target site.

“WPSiteSync for Content is not installed and activated on Target site.”

This is just want it sounds like. Most often caused by not activating WPSiteSync on the Target site.

To resolve: Make sure the plugin is activated on the Target site. Alternatively, there may be something interfering with the WPSiteSync API. This can be caused by a “Coming Soon” or “Maintenance Mode” type plugin, or some security plugins. Try disabling these types of plugins and try again.

“Unable to authenticate on Target site.”

The username or password that you’re trying to configure WPSiteSync do not match a valid username and password on the Target site. This is most often caused by entering credentials of the Source site, rather than credentials for a valid user of the Target site.

To resolve: Enter the proper credentials for a user that has at least Editor privileges.

This can also be caused by a “Coming Soon” or “Maintenance Mode” type of plugin. Or a similar feature built into your theme. Ensure that all such plugins or features are disabled.

Finally, another possible cause could be that the database tables that WPSiteSync stores authentication tokens in do not exist. This can happen if there’s an error during the plugin activation process. Try reinstalling the plugin on the Target site and/or use a tool such as phpMyAdmin to ensure that there are the following four tables: ‘wp_spectrom_sync’, ‘wp_spectrom_sync_log’, ‘wp_spectrom_sync_media’, and ‘wp_spectrom_sync_sources’. If these are not being created on activation, there might be some deeper cause. To track this down, enable logging and examine the contents of the wp-content/debug.log file to find the cause.

“User session has expired.”

This is caused when the user session on the Source site is no longer valid. This can occur when you’ve been logged in to the site, but your session then expires. After it expires, if you click on the “Push to Target” button, this error is returned.

To resolve: Log in to the Source site and try again.

“A user is currently editing this Content on the Target site.”

This is caused when you attempt to Push some Content from the Source site to the Target, but a user on the Target site is currently editing the page or post.

To resolve: Make sure that no one is editing the Content on the Target site. Someone editing the content causes entries to be written into the database on the Target. These can sometimes be left behind if the browser tab is suddenly closed. This means you may need to edit the page again, then go to some other page such as the Dashboard. This removes the database entries and “frees up” the page, allowing the Push operation to occur.

“Error while handling file upload.”

This occurs when an attachment, such as an image, is being Pushed to the Target along with the Content. This error message indicates that there was a problem with the file upload portion of the Push. This can be the result of the file being too large.

To resolve: First, we need to determine the cause of the problem. To do this, enable logging and check the contents of the wp-content/debug.log file. This might indicate an error that is interfering with the upload operation. If nothing is found in the debug.log file, you can send us the contents of the WPSiteSync log file and we can examine that for the cause.

“The WordPress versions are different on the Source and Target sites.”

This is caused when the version of WordPress on the Source site is different than the version of WordPress on the Target site. In order to be absolutely sure of the behavior of the Content after it has been Pushed to the Target. This is controlled by the optional “Strict Mode” configuration setting.

To resolve: You can configure WPSiteSync to ignore version differences by going to Settings -> WPSiteSync and look for the “Strict Mode” setting. Select the “Off – WordPress and WPSiteSync for Content versions do not need to match.”

“The SYNC versions are different on the Source and Target sites.”

Similar to the above WordPress version mismatch, WPSiteSync versions also need to be the same on the Source and Target. This is controlled by the same configuration setting as above.

To resolve: You can configure WPSiteSync to ignore version differences by going to Settings -> WPSiteSync and look for the “Strict Mode” setting. Select the “Off – WordPress and WPSiteSync for Content versions do not need to match.”

“The required SYNC extension is not active on the Target site.”

This occurs when an extension, such as the WPSiteSync for Menus add-on is installed on the Source site but is not present on the Target site.

To resolve: Check to make sure that all add-on plugins that are in use on the Source site are also installed, activated and licensed on the Target site.

“The post type is not allowed.”

This occurs when you Push non-standard Content from the Source (that is, something other than a Page or a Post) to the Target. To do this, you have to use one of the add-ons such as WPSiteSync for Custom Post Types or something that recognizes a Custom Post Type, such as WPSiteSync for WooCommerce.

To resolve: Make sure that the add-on plugin you are using to enable Pushing of the Custom Post Type on the Source site is also installed, activated and licensed on the Target site.

“Unable to make API request to Target system.”

This happens when the API request to the Target system fails.

To resolve: Start by enabling logging on both the Source and the Target sites. Then, examine the wp-content/debug.log files on both sites and look for anyreports of PHP runtime errors. If this do not yield any answers, you can send us the WPSiteSync log files and we can track down the cause of the problem.

“Target system did not respond with success code.”

This occurs when the API request to Push Content to the Target encounters a runtime error. The Target site responded with something besides am HTTP “200 OK” result code. This can be caused by a number of things: most often a PHP runtime error caused by the theme, a plugin conflict or something else misconfigured on the Target site.

To resolve: To track down the problem, enable logging on the Target site. Then, examine the wp-content/debug.log file and reports of PHP runtime errors. If this do not yield any answers, you can send us the WPSiteSync log file and we can track down the cause of the problem.

“Site Key for Target system has not been obtained.”

WPSiteSync uses what we call a “site key” to uniquely identify each site when making API calls. This message is displayed when the Target site’s site key isn’t found. This can occur when the data in WPSiteSync’s database tables is corrupt. It can also be caused by migrating the contents of the Target site’s database to the Source site.

To resolve: Try resetting the configuration of WPSiteSync on the Source site by re-entering the authentication credentials of your Target site.

“Unable to determine post content.”

This error message appears when WPSiteSync cannot find the post Content while processing a Push request. In most cases, you won’t see this but it can occur if something is causing a problem internally that causes the Content that you’re editing to not be found.

To resolve: This is an internal error so there’s likely not much you can do. Your best course of action would be to submit a Support Request to let our development team know about the problem and we can take steps to fix it.

“Unable to validate AJAX request.”

After clicking on the “Push to Target” button, WPSiteSync verifies the request with some data found on the Source page. This data is not what is expected. This can be caused by not using the web page for an extended period of time and your login session expiring.

To resolve: Reload the page containing the “Push to Target” button and try clicking on it again.

“Content has a Parent Page that has not been Sync’d.”

This occurs when you Push a page which has a Parent. But you have not yet Push the Contents of the Parent page to the Target.

To resolve: Find the Page’s Parent and Push this to the Target site. Then, return to the original child page that you wish to Push and Push that to the Target.

“Unable to authenticate with Target site. Please re-enter credentials for this site.”

The authentication token that WPSiteSync uses for it’s API request is missing or invalid. This can be caused by Migrating the Target site’s database to the Source site, which replaces the contents of the database table containing these authentication tokens.

To resolve: Go the the Settings -> WPSiteSync and re-enter the credentials for the Target site. This will re-create and/or update the authentication used for API requests.

“User does not have permission to perform Sync. Check configured user on Target.”

The username that WPSiteSync uses on the Target site does not have the permissions to create or update the Content on the Target site. This can happen if the username’s Role on the Target site changed after WPSiteSync was configured. This can also happen if you’re Pushing Content that the user does not have access to on the Target, such as a Post that was not created by an Author.

To resolve: Adjust the user’s Role on the Target site. We recommend using an Editor role as this role allows the user to create and edit content and the user does not need any additional capabilities.

“The image uploaded is not a valid image type.”

This occurs when you’re attempting to Push an attachment that is not allowed or not recognized on the Target site. WPSiteSync allows you to Push any image type and the PDF file type. Additional attachment or image can be included by WPSiteSync add-on plugins as needed. Seeing this error message could indicate that the add-on plugin used to add the image type has not been activated.

To resolve: Make sure that all add-on plugins are installed, activated and licensed on the Target site. Also ensure that any attachments to the Content you are Pushing are allowed. These should be limited to images (.png, .gif, .jpg, etc.) and PDF files. Anything else needs to have a WPSiteSync plugin that recognizes them and allows them.

“Requested post cannot be found.”

This error is displayed when Content from the Source site has already been Pushed to the Target site, but the post ID on the Target site cannot now be found. This happens if the post on the Target was deleted. This can also happen if the contents of the Source site’s database is migrated to the Target site which can cause the post ID values on to change.

“Content update on Target failed.”

This occurs when the update of Content on the Target site fails for some reason. The reasons are usually due to an error detected within the Content. This could be due to the post content being empty, an invalid date provided, or some other internal condition detected by WordPress itself.

“Cannot write authentication token.”

During the authentication process, WPSiteSync saves the authentication token that it creates in a database table. This write to the database table has failed. Causes of this could be that the tables do not exist or some other error occurred during the save process.

To resolve: Check to make sure that the database tables have been created. There should be four tables: ‘wp_spectrom_sync’, ‘wp_spectrom_sync_log’, ‘wp_spectrom_sync_media’, and ‘wp_spectrom_sync_sources’. If not, try re-installing WPSiteSync. Failing that, enabling logging. Check the contents of the wp-content/debug.log file and resolve any PHP runtime errors that are shown. If there is still a problem, you can send the WPSiteSync log file to us and we can research that and solve it from there.

“Attachment upload failed. No content found; is there a broken link?”

This message can be seen when Pushing Content that includes some attachments. One or more of the attachment files are empty. This can occur if the Image within the Image library exists, but the physical image file (the .jpg, .gif, .png, etc.) does not exist or is empty. The cause of this can be many, including a corrupt file or inadvertently deleting the file via an FTP program.

To resolve: Check the attachment files referenced from the post. This would include any featured image, gallery or other images associated. Ensure that all the files exist and are not empty. If this does not explain the problem, enable logging on the Source and Target sites and we can examine these for find the problem.

“A PHP error occurred on Target while processing your request. Examine log files for more information.”

This one is pretty clear, right? WPSiteSync detected an error in the response to it’s API call to the Target.

To resolve: Start by enabling logging on the Target site and try Pushing the Content again. Examine the contents of the wp-content/debug.log file and look for any PHP runtime errors. These can be caused by your theme, plugins, etc. Resolve these errors and try Pushing the Content again.

“Unknown SSL protocol error on Target. Check DNS settings on Target domain.”

There is a problem in making an SSL connection to the Target site. This can be caused by your Source site not being able to connect to the Target using the SSL protocol that the Target requires. For example, if the Target is requiring TLS 1.1 or TLS 1.2 and the Source is using an older version of Open SSL, it will not be able to provide that protocol. This can also be caused by the SSL Certificate on the Target site not being set up correctly, or by misconfigured DNS settings.

To resolve: You should start by determining what the real issue is. You can use either the mxtoolbox.com tool and/or the builtwith.com tool to get information on the Target domain. These tools will show any DNS issues or what the expected SSL Protocol is on the Target.

Older versions of OpenSSL will not be able to connect using new SSL Protocols such as TLS 1.1 and TLS 1.2. If this is how the Target domain is configured, you can either upgrade the version of Open SSL on the Source site – to allow it to use the newer protocols, or configure the allowed protocols on the Target site to allow TLS 1.0.

Being the Product Architect at ServerPress, LLC, Dave brings 35+ years of experience bridging traditional architecture with innovative Workflow solutions. Creator of WPSiteSync, among many other products, he loves pushing technology to the limit. His motto: No coffee. No code.