[mirrorpress_documentation_nav]
SirSync Pro lets you synchronize Advanced Custom Fields configurations and values between connected WordPress websites. You can deploy Field Groups, ACF-created Post Types, Taxonomies, Options Pages, and the custom field values associated with your content.
SirSync works with both Advanced Custom Fields (ACF) and Secure Custom Fields (SCF). This documentation refers primarily to ACF, but the same synchronization features also apply when using Secure Custom Fields.
SirSync does not place separate synchronization limits on ACF Free, ACF Pro, or Secure Custom Fields. The available configuration screens and field types depend on the custom fields plugin installed on your website, but SirSync can synchronize the supported features available in that installation.
SirSync supports synchronizing the following ACF and SCF features:
ACF configurations and ACF field values are related, but they are synchronized as separate parts of a deployment.
Synchronizing a Field Group deploys the fields, settings, and location rules that determine how the editing interface is structured. It does not automatically synchronize every page, post, product, or other content item using that Field Group.
Custom field values are synchronized when the page, post, product, or custom post type containing those values is pushed or pulled through SirSync.
This separation keeps deployments predictable. Synchronizing a Field Group does not automatically trigger the synchronization of every piece of content that uses it.
When setting up ACF on a connected website for the first time, synchronize the supporting configurations before synchronizing the content that uses them.
SirSync can help resolve some missing Field Group locations during synchronization, but deploying the supporting configurations first gives you greater control over what is created on the receiving website.
SirSync adds synchronization controls to the ACF Field Group editor. You can push the current Field Group to the connected website or pull its linked version to the current website.
To synchronize a Field Group:
If the Field Group has not been synchronized before, SirSync creates it on the receiving website. After the first synchronization, SirSync stores a relationship between the two Field Groups so future deployments update the corresponding version.
Field Group synchronization includes the Field Group settings and its complete field structure. This includes nested fields used by supported field types such as:
SirSync preserves the field hierarchy and uses stable field identities to update existing fields without relying on WordPress database IDs from the source website.
Field Group location rules can reference a Post Type, Taxonomy, Options Page, or Block that is not available on the receiving website. SirSync checks for these missing location targets before synchronizing the Field Group.
If a location target is missing, SirSync gives you the following choices:
If SirSync cannot create a requested location, the unresolved location rule is excluded from the synchronized Field Group. Review the Field Group on the receiving website after synchronization to confirm that its location rules are complete.
Before updating an existing Field Group, SirSync compares the fields on both websites. If fields exist on the receiving website but are missing from the version being synchronized, SirSync asks how those fields should be handled.
Removing a field from a Field Group can affect how existing data is displayed or edited. Review the listed fields carefully before choosing to remove them.
SirSync checks for changes that may affect existing field data before applying an update. For example, a warning may appear when:
The warning shows the conflicting settings and asks you to confirm before continuing. Cancel the synchronization if you need to review the differences before changing the receiving Field Group.
ACF can be used to register Custom Post Types through the WordPress dashboard. SirSync can synchronize these Post Type definitions between connected websites.
To synchronize a Post Type:
Post Type synchronization includes the registration settings stored by ACF, such as labels, visibility, hierarchy, archive behavior, rewrite settings, supported features, menu settings, and other available Post Type options.
Synchronizing a Post Type creates or updates the Post Type definition. It does not automatically synchronize the posts or entries stored within that Post Type. Those items must be synchronized separately.
SirSync warns you when an incoming change may alter the identity, URLs, or behavior of an existing Post Type. This can include changes to:
Changes to these settings can affect existing URLs, templates, queries, and content. Review the warning before continuing.
SirSync can synchronize Custom Taxonomies registered through ACF.
To synchronize a Taxonomy:
Taxonomy synchronization includes the registration settings stored by ACF, including its labels, object type assignments, visibility, hierarchy, rewrite settings, administrative settings, and other available Taxonomy options.
Synchronizing a Taxonomy creates or updates the Taxonomy definition. It does not automatically synchronize all terms or content assigned to that Taxonomy. Terms used by synchronized content are handled as part of the content deployment.
SirSync can synchronize Options Pages created through the ACF interface. Options Page synchronization includes both the page configuration and the custom field values saved to that Options Page.
To synchronize an Options Page:
The Options Page configuration can include its page title, menu title, menu slug, parent page, capability, position, redirect behavior, menu icon, and other settings available through the installed custom fields plugin.
SirSync also synchronizes the values stored for fields assigned to the Options Page. This allows sitewide settings such as contact information, global calls to action, logos, reusable content, and theme settings to be deployed with the Options Page.
Synchronize the Field Group assigned to the Options Page so the receiving website also has the correct editing interface and field definitions.
Custom field values attached to content are synchronized when you push or pull the page, post, product, or supported custom post type containing them. You do not need to map each ACF field manually.
SirSync reads the ACF field definitions associated with the content and uses them to determine how stored values should be handled on the receiving website.
Text, textarea, number, select, checkbox, radio, date, color, and other standard values are copied with the content that contains them.
SirSync supports values stored in nested ACF structures, including:
SirSync uses ACF field keys to identify nested values, including values stored inside repeated rows or Flexible Content layouts.
Media referenced by Image, Gallery, File, and other supported media fields is transferred to the receiving website when required. SirSync then replaces the source attachment IDs and URLs with the corresponding attachments on the receiving website.
This prevents ACF fields from continuing to reference attachment IDs that belong only to the original website.
SirSync remaps supported content references stored by fields such as:
For the most reliable mapping, synchronize the referenced pages, posts, products, or custom post type entries before synchronizing the content containing the relationship field.
Synchronizing a relationship field does not automatically deploy every referenced content item. This keeps the deployment limited to the content you intentionally selected.
Taxonomy field values are matched to the corresponding Taxonomy and terms on the receiving website. Synchronize the Taxonomy definition before deploying content that relies on it.
User field values are matched to existing users on the receiving website using available account information, such as the email address or username. SirSync does not automatically create a new WordPress user when a matching account does not exist.
ACF WYSIWYG fields are processed similarly to WordPress editor content. SirSync updates supported internal links and media references so they point to the corresponding content and files on the receiving website.
Push to Remote sends the configuration or content from the current website to the connected website.
Pull from Remote retrieves the linked configuration or content from the connected website and applies it to the current website.
SirSync creates a relationship during the first successful synchronization. Later pushes and pulls use that relationship to update the corresponding item instead of creating a new copy each time.
Always save the current item before synchronizing it. Synchronization begins when you confirm the action.
When you activate or deactivate a linked ACF Field Group, Post Type, Taxonomy, or Options Page, SirSync can apply the same status change to its remote copy.
When prompted, choose whether to apply the change to both websites or only to the current website. This is also supported when using the bulk activation and deactivation actions on supported ACF list screens.
