You define per entity type (like a Page, an Image or a Menu Item) how you want to push it. The following is available per type:
Besides pushing automatically or manually, the third option is to push referenced content, meaning that this content is only pushed if it’s used somewhere else. This is useful for paragraphs and bricks for example. Depending on your desired workflow, it can also be useful for taxonomy terms, menu items or media elements. You can even use it to push referenced nodes along with the main node.
Push to Pools
Select what Pools you want to push the given entity type to. You have the following options per Pool:
Forbid: Ignore this Pool; this Flow will never push content of this type to the given Pool.
Allow: Don’t push content into this Pool by default, but allow editors to choose whether they want to push a particular content item of this type into the given Pool.
Force: Always use this Pool when pushing content of this type.
By default, Content Sync will not only distribute creating or updating content items but also deletions of content meaning that if you delete content on the source site where you first created it, the content will also be deleted on all the subscribing sites that pulled it. This option allows you to disable this default behaviour.
Please note that you need to both enable Push deletions on the publishing site and Pull deletions on the subscribing sites for deletions to come through.
This is only relevant if one of your Pools is set to Allow for this type (see above). If so, editors can use the widget you select here to assign Pools. The following widgets allow editors to select exactly one of the Pools you Allowed:
The following widgets allow editors to select none, one or more of the Pools you Allowed:
This is only relevant if you are pulling content of this type on your other subscribing sites manually. See here for an explanation of previews: Pull Content Manually.
Push menu items
You can configure per entity type whether menu link items that link to the specific entity should be syndicated as well when the entity is pushed.
Type and Field: File
Files are syndicated along with their file contents, so they are an exact replica as on the source site. If you don’t want to syndicate the same file to save storage, we recommend you use a CDN or DAM tool to manage these assets.
Type: Menu items
By default, only menu items that are enabled will be pushed to Content Sync. You can use this option to also syndicate menu items that are disabled.
Restrict to menus
By default, Content Sync will distribute all menu items from all menus. You can use this option to only syndicate menu items from specific menus.
Type: Node (Content)
By default, unpublished content won’t be pushed to Content Sync. This is based on revisions in Drupal, so as long as a revision isn’t published, it won’t be syndicated. There’s one special use case however that we also support and that is to Explicitly unpublish content. So if you completely unpublish a content item, you usually want the Unpublished status to still be syndicated to your remote sites, so to unpublish it on all sites.
You can overwrite both of these settings per node type.
Field: Entity reference
By default, Content Sync will distribute not only the content you are pushing directly but also the content, media elements, tags etc that you assigned to the content through entity reference fields. You can disable this behaviour per field by unchecking the Push referenced entities option.
By default, links to other content will remain local meaning that when you link to another content on the publishing site, the link on the subscribing site will point to the same referenced content on the subscribing site. If the content doesn’t exist on the subscribing site, the field will be empty. You can use the Push as absolute URL option to change this- if set, links to content will go back to the source site of that content.
Field: User reference
As mentioned here we don’t syndicate user accounts. We do syndicate user references however. So if the same user exists on both the publishing and the subscribing sites that either has the same email address or the same user name, we will assign the user accordingly on the subscribing site as well. You can configure whether to use the user name or email address for matching.