When a navigation channel is translated to a derived site, the parent channel must exist in the derived site before the child can be placed correctly. If the parent does not yet exist, the translated channel becomes a structural orphan — disconnected from the rest of the page tree in the derived site. The same applies to taxonomy hierarchies.

With this feature, localization workflows automatically consider referencing parent content items when computing the translation set. When you start a localization workflow for a navigation channel, all ancestor channels up to the root channel are considered automatically — at any depth. If any of those ancestor channels do not yet exist in the derived site, they are automatically added to the translation set.

This feature applies both to the Start Localization Workflow window in CoreMedia Studio (where editors see which content items will be included) and during the actual workflow execution on the Workflow Server.

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

For parent content items that already exist in the derived site, editors can 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.

Custom content types with parent-child relationships can be registered via additional configuration properties.

Upgrade Note

This feature is enabled by default. To disable it entirely, set the following property in both Studio Server and Workflow Server:

multisite.transfer.relations.enabled=false

Individual relations can be disabled selectively, for example:

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

Studio Server and Workflow Server must use the same configuration.

Documentation Reference

Multi-Site Manual, section Referrer Relations in Localization — feature overview, built-in relations, custom types, and configuration.

(CMS-29119)