[mirrorpress_documentation_nav]
SirSync supports content created with Elementor, SiteOrigin Page Builder, the WordPress Block Editor (Gutenberg), and the Classic Editor. When content is synchronized, SirSync preserves the editor or builder data and updates supported media, links, templates, and other references for the receiving website.
Each supported editor stores content differently. SirSync recognizes these formats and processes the information based on the editor or page builder used to create the content.
SirSync supports pages and posts created with Elementor. It transfers the Elementor layout data and processes supported references stored within its widgets and settings.
Supported Elementor content can include:
When an Elementor setting references a WordPress attachment, template, or synchronized content item, SirSync replaces the source website’s ID or URL with the corresponding value on the receiving website.
Elementor Pro widgets can be synchronized when Elementor Pro is installed on both websites. Synchronizing a page that uses Elementor Pro does not install or activate Elementor Pro on the receiving website.
SirSync supports layouts created with SiteOrigin Page Builder. It transfers the layout structure and processes supported references stored within rows, columns, widgets, and builder settings.
Supported SiteOrigin content can include:
Widgets provided by custom development or third-party SiteOrigin extensions may store their data differently from standard SiteOrigin widgets. These widgets may require additional configuration before SirSync can process all their stored references.
SirSync supports pages and posts created with the WordPress Block Editor. It transfers the block markup, attributes, and supported references stored within the content.
Supported Gutenberg content can include:
When a supported block contains an attachment ID, media URL, or link to synchronized content, SirSync replaces it with the corresponding value on the receiving website.
Custom and third-party blocks can use their own attribute structures. Additional configuration may be required when a block stores references in attributes that SirSync does not recognize automatically.
SirSync supports pages and posts created with the WordPress Classic Editor. The HTML content is transferred to the receiving website and processed for supported links and media references.
Supported Classic Editor content can include:
When an image or linked content item has already been synchronized, SirSync updates its attachment reference or URL so it points to the corresponding item on the receiving website.
Shortcodes are transferred as part of the editor content. The theme or plugin that registers a shortcode must also be installed on the receiving website for it to render correctly.
Page builders and editors can store WordPress attachment IDs, post IDs, template IDs, and URLs within their content and settings. Because these values may be different on each website, SirSync processes supported references during synchronization.
For example, SirSync can:
SirSync does not automatically synchronize every page, post, template, or other content item referenced by the builder. Referenced content should be synchronized separately so you remain in control of what is included in each deployment.
SirSync includes built-in handling for common blocks, widgets, modules, and fields used by its supported editors. Standard builder content usually does not require additional configuration.
Custom modules and some third-party extensions can store media, links, and content selections in their own data structures. If SirSync does not recognize those fields automatically, the module can be configured under the SirSync settings so its references are processed during synchronization.
Configuring a module does not install, recreate, or change the module itself. The block, widget, or module and the code that supports it must already be available on the receiving website.
Synchronizing builder content does not automatically synchronize:
For consistent results, connected websites should use compatible themes, plugins, builder versions, and custom code.
