close

Filter

loading table of contents...

Deployment Manual / Version 2506.0

Table Of Contents

3.4.3 Shared Multi-Site Configuration

The following list contains configuration properties for the multi-site feature, that are typically shared between different applications (or they must be kept in sync).

translatable.predicate.property-path
Type Map<String,Boolean>
Description

Marks properties or nested (Struct) properties as translatable. Typically applied to nested properties in Structs, which cannot be individually marked as translatable in the content type model.

The map entry's key represents the property path starting from the content type that declares the property.

A map entry's value of true marks the property selected by the property path as translatable.

Example Configuration:

 translatable.predicate.property-path[CMLinkable.localSettings.callToActionCustomText]=true 

For Struct properties containing dots in their names, you may use bracket syntax instead:

 translatable.predicate.property-path[CMLinkable.localSettings['with.dots.in.name']]=true 

Note, that a value of false cannot veto a translatable decision by another predicate. The parsed configuration will just ignore those property paths marked with false from this configuration.

translate.item.include-unchanged-properties
Type Boolean
Default true
Description

Whether properties that have not changed since last translation are also included in items for translation.

translate.item.transform.failure.mode
Type String
Default fail
Description

Controls behavior when no matching transformers are available to eventually represent a property in XLIFF. Available values: fail, warn, and none.

translate.xliff.export.excludeContentName
Type Boolean
Default true
Description

Only if set to false, content names are included in the XLIFF export.

Table 3.21. Shared Multi-Site Properties


Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.