Release Notes / Version 12.2506.0
Table Of Contents
As part of the correction of a configuration known as
translateXliffTranslatableExpressions that has not
worked (with default Blueprint configuration) for CoreMedia Studio
since version CMCC v11.2307.1, the configuration itself has been
significantly simplified and the configuration eventually fixed.
Instead of previous customizations of the bean
translateXliffTranslatableExpressions like this:
@Bean
@Customize("translateXliffTranslatableExpressions")
List<String> translatableExpressions() {
return List.of(
"CMLinkable.localSettings.callToActionCustomText",
"CMTeaser.targets.links.callToActionCustomText"
);
}
You can now use a property-based configuration instead:
translatable.predicate.property-path[CMLinkable.localSettings.callToActionCustomText]=true translatable.predicate.property-path[CMTeaser.targets.links.callToActionCustomText]=true
As these settings are typically required at least for CoreMedia Studio
and for Workflow Server (if you generate XLIFF directly within a
translation workflow action), a new Blueprint module
com.coremedia.blueprint:multi-site has been
introduced for this shared configuration and subsequently added as
dependency to both, the Studio Server and Workflow Server application.
Via AutoConfiguration it is ensured that these
properties are available in the corresponding applications.
See Also
Find more information in the CoreMedia Blueprint Developer and Deployment Manual.
Workaround for Versions prior to CMCC v12.2506.0.0
As a quick fix for previous releases, you may adapt the
StudioInMemoryAutoConfiguration and remove the
ConditionalOnProperty annotation (for property
elastic.core.persistence), so that the
customization of
translateXliffTranslatableExpressions is also
active for default Studio deployments.
Upgrade Notes
Deprecation: While it still works,
the customization of bean
translateXliffTranslatableExpressions is considered
deprecated starting from CMCC v12.2506.0.0.
No immediate action required: For
now, both configurations, the property-based configuration via
translatable.predicate.property-path and the
property-paths mentioned in
translateXliffTranslatableExpressions are merged,
so that, if any of these configurations mark a property as
translatable, it will be considered as translatable (as by default
these translatable decisions are ORed; see Blueprint Developer Manual
for details).
Recommended steps:
Accept updates for
StudioInMemoryAutoConfigurationandBlueprintWorkflowServerAutoConfigurationwhich remove the customization oftranslateXliffTranslatableExpressions.Accept updates for modules
studio-blueprint-componentandworkflow-blueprint-componentthat add this dependency as runtime dependency:<dependency> <groupId>com.coremedia.blueprint</groupId> <artifactId>multi-site</artifactId> <scope>runtime</scope> </dependency>
Transform previous adaptations of
translateXliffTranslatableExpressionsto the corresponding configuration fortranslatable.predicate.property-path.
Side Note Blueprint Module: If you
upgrade from versions prior to CMCC v11.2307.1, you will observe, that
the module com.coremedia.blueprint:multi-site
existed before (since CMCC v10.2004.1).
(CMS-27624)
