Some content types form tree hierarchies through parent-child relationships. The most prominent example is the navigation structure: CMChannel content items reference child channels, forming the sites page tree.

When translating a content item that belongs to such a tree, the parent content items may not yet exist in the target site. Without the parents, the translated content item ends up as an orphan structurally disconnected from the rest of the tree.

Automatic Referrer Transfer Augmentation

CoreMedia Multi-Site may consider referencing parent content items when computing the translation set based on the provided configuration. If configured and enabled for navigations channels, when localizing a navigation channel, all ancestor channels up to the root channel are considered automatically at any depth.

Include Updated Dependent Content

By default, only parents are considered that do not exist yet in the target site.

For parents that already exist in the derived site, editors should activate the option to include updated dependent content when starting the localization workflow. This ensures that structural link-list changes are propagated to derived sites even when the parent content item already exists.

Built-In Relations

Several referrer relations are pre-configured and enabled by default:

Custom Referrer Relations

If your content type model includes custom content types with structural parent-child relationships, you can register additional referrer relations. For example, given a custom content type AcmeCategory with a subcategories link-list descriptor:

multisite.transfer.relations.referrer.acme-category.content-type=AcmeCategory
multisite.transfer.relations.referrer.acme-category.source-property=subcategories

If your custom content type replaces one of the built-in types (for example, a custom taxonomy type that replaces CMTaxonomy), you can override just the content type the other properties are preserved from the defaults:

multisite.transfer.relations.referrer.taxonomy.content-type=AcmeTaxonomy

Configuration

All properties are prefixed with multisite.transfer.relations. The full reference is available in Section 3.6.2, “Shared Multi-Site Configuration” in Deployment Manual as well as in Section 3.4.3, “Shared Multi-Site Configuration” in Deployment Manual.

To disable a specific relation:

multisite.transfer.relations.referrer.navigation.enabled=false

To disable referrer relation augmentation entirely:

multisite.transfer.relations.enabled=false

Keep Studio Server and Workflow Server in Sync

Referrer relation augmentation runs on two applications: CoreMedia Studio (Start Localization Workflow window) and the Workflow Server (actual augmentation during the workflow). Both must use the same configuration. If the configuration diverges, editors may see a set of additional content items that does not match the content items actually added by the workflow.