Troubleshooting

Most SirSync synchronization issues can be traced to a connection problem, a disabled deployment setting, a missing dependency on the receiving website, or a referenced item that has not yet been synchronized.

Use the steps below to identify common issues before attempting the deployment again.

Start With These Checks

1. Confirm that both websites are available and connected.
2. Confirm that SirSync is active and up to date on both websites.
3. Verify that synchronization is enabled for the applicable content type.
4. Review the deployment history for an error or warning.
5. Confirm that the required theme, plugins, page builder, and custom modules exist on the receiving website.
6. Review the content on the receiving website after clearing any page, object, or CDN caches.

The Connected Website Is Unavailable

If SirSync cannot communicate with the connected website, verify that:

• The connected URL is correct.
• The remote website is publicly accessible.
• SirSync is active on both websites.
• The websites are still paired.
• A maintenance mode, security plugin, firewall, or hosting rule is not blocking the request.
• The receiving website is not returning a server error.

If the website was migrated or its domain changed, reconnect the websites using the current URLs before attempting another deployment.

Content Did Not Update

If the deployment completes but part of the content remains unchanged, review the deployment settings for that content type.

Depending on your configuration, SirSync can separately control whether it updates:

• Post status
• Post slug
• Visibility
• Published or scheduled date
• SEO metadata
• Custom fields and post metadata

A disabled option preserves the corresponding value already stored on the receiving website. Enable the required setting and synchronize the content again.

Images or Files Are Missing

If an image or file is missing or still points to the source website, confirm that it is stored in the WordPress Media Library and used in a supported field.

Also check that:

• The source media file still exists and can be opened.
• The receiving website allows the file type.
• The receiving server has sufficient upload and storage capacity.
• The file is not blocked by a security or file-size restriction.
• A custom module is not storing the media reference in an unsupported field.

For custom shortcodes, Elementor widgets, WPBakery modules, or SiteOrigin widgets, you may need to configure a custom media mapping rule. Custom mapping rules currently support media references only.

The Wrong Image Appears

SirSync uses its synchronization mappings to associate source attachments with their corresponding Media Library items on the receiving website. If content was manually imported, copied, restored from a backup, or moved during a migration, those relationships may need to be rebuilt.

Use Scan Keys on This Site for the affected content type to rebuild SirSync’s locally stored mapping information. After the scan finishes, synchronize the content again and review the result.

Scanning keys does not inspect custom fields to create new synchronization rules. It rebuilds SirSync relationships for content that already contains its synchronization data.

Internal Links Point to the Source Website

SirSync can update supported internal links when the linked content has a known corresponding item on the receiving website.

If a link still points to the source website:

• Confirm that the linked page, post, product, or other content item has been synchronized.
• Synchronize the referenced content before synchronizing the page that links to it.
• Confirm that the URL is stored in a supported editor or field.
• Check whether the link was entered as an external or custom URL.

SirSync does not automatically deploy every content item referenced by a page. Referenced content should be synchronized separately so you remain in control of the deployment.

A Page Builder Layout Is Incorrect

If the content transfers but its layout or functionality differs, confirm that both websites use compatible versions of the required:

• Page builder
• Theme
• Builder add-ons
• Custom widgets, blocks, or modules
• CSS and JavaScript

SirSync transfers supported content and builder data, but it does not install plugins, themes, extensions, or custom code. A module may transfer successfully but fail to render if the code that registers it is unavailable on the receiving website.

Custom Fields Did Not Synchronize

Confirm that Sync custom fields (post meta) is enabled for the applicable content type. The field definitions and the plugin or theme that uses them must also exist on the receiving website.

SirSync includes built-in support for Advanced Custom Fields. Other custom metadata may require configuration depending on how its values are stored and what they reference.

SEO Metadata Did Not Synchronize

Confirm that:

• Sync SEO meta is enabled.
• The same supported SEO plugin is installed and active on both websites.
• Both websites use compatible versions of Yoast SEO or All in One SEO.

SirSync synchronizes supported content-level SEO metadata between matching plugins. It does not convert Yoast SEO data into All in One SEO data or synchronize the plugin’s complete sitewide configuration.

WooCommerce Product Data Is Incomplete

WooCommerce products can contain relationships between parent products, variations, attributes, categories, media, grouped products, upsells, cross-sells, and downloadable files.

If part of a product is missing, confirm that:

• WooCommerce is active on both websites.
• The product type is supported on the receiving website.
• Related products are included in the deployment or have already been synchronized.
• Required global attributes and taxonomies are available.
• Referenced images and downloadable files are valid Media Library items.
• The receiving website supports the file type being transferred.

For products with relationships, synchronizing the related products first can help SirSync establish the mappings needed by the parent product.

A Scheduled Deployment Did Not Run

If a scheduled deployment has not started, confirm that:

• The scheduled date, time, and website timezone are correct.
• The deployment is still listed in the queue.
• WordPress scheduled tasks are running normally.
• The source and receiving websites were available at the scheduled time.
• The connection remained active.

Review the deployment history to determine whether the job is waiting, completed, or encountered an error.

Email Notifications Were Not Received

Confirm that the notification email address is correct and that email notifications are enabled. Check the recipient’s spam or junk folder and verify that the WordPress website can send other administrative emails.

Email delivery depends on the website’s mail configuration. If WordPress email is unreliable, configure an authenticated SMTP or transactional email service.

A Deployment Completed but Changes Are Not Visible

The receiving website may be displaying a cached version of the content. Clear any applicable:

• WordPress page cache
• Object cache
• Hosting cache
• CDN cache
• Browser cache
• Page-builder generated CSS cache

Then open the content directly in the WordPress editor to confirm whether the synchronized data is present.

Review Deployment History

Use the deployment history to confirm whether a synchronization completed successfully and to review available error details. Note the affected content item, the direction of the deployment, and any displayed message.

If only one item is affected, test it separately before repeating a larger deployment. This makes it easier to determine whether the issue belongs to the content itself or to the connection and configuration.

Before Requesting Support

If the issue continues, gather the following information:

• The source and receiving website URLs
• The type and title of the affected content
• Whether the action was a push or pull
• The approximate deployment date and time
• The deployment history message
• The specific field, image, link, or setting that did not synchronize correctly
• The editor, page builder, or plugin responsible for that field
• Screenshots of the source and receiving content

A focused example using a single affected content item is usually more helpful than repeating a large bulk deployment.