close

Filter

loading table of contents...

Release Notes / Version 10.2104

Table Of Contents

CoreMedia Core

Universally Unique Identifiers (UUIDs) for Content and Version

The Content Management Server maintains stable and universally unique identifiers (UUIDs) as specified in RFC 4122 for content items and versions. Existing and newly created contents and versions get a random UUID in addition to existing numeric content IDs and version numbers. UUIDs are not meant to replace existing IDs, and IDs can be used for all purposes as before. Note, that UUIDs are currently only available on the Content Management Server, and not on live servers.

Follow Section, “Universally Unique Identifiers (UUIDs) for Content and Version” for upgrade information.

(CMS-16509)

Maturing Translation API: TranslatablePredicate and TranslatablePredicateConfiguration

In order to mature our experimental translation API, we had to refactor com.coremedia.translate.TranslatablePredicate . Instead of implementing isTranslatable(CapPropertyDescriptor):boolean you now need to implement isTranslatable(List<CapPropertyDescriptor>):boolean .

Follow Section, “Maturing Translation API: TranslatablePredicate and TranslatablePredicateConfiguration” for upgrade information.

(CMS-16402)

Elastic-Social and MongoDB properties have changed.

The following Elastic-Social properties have changed. Previous versions are still working but have been deprecated and should be migrated:

Follow Section, “Elastic-Social and MongoDB properties have changed.” for upgrade information.

(CMS-13113)

Known Issue: Release cannot be used with DB2 database

The release contains a known issue which makes it impossible to use DB2 as database for the Content Server. Do not try to upgrade to this release, if you are using DB2. A fix will be delivered in one of the next releases.

(CMS-17785)

CMResourceBundle localizations in Translation Workflows

The property "localizations" of document type "CMResourceBundle" is no longer marked with attribute extensions:automerge="true" in the Blueprint document type definition in modules/server/doctypes/src/main/resources/framework/doctypes/blueprint/blueprint-doctypes.xml . It was removed to avoid that translation workflows always run into merge conflicts when CMResourceBundle value changes are propagated to an existing and already translated derived content.

Follow Section, “CMResourceBundle localizations in Translation Workflows” for upgrade information.

(CMS-16568)

MongoDB: New TTL index for events_ collection

A new TTL (Time To Live) Index of 5 min is introduced for property "creationDate" in collection events_ (database: blueprint_internal_models). The index is required to reduce network traffic between MongoDB and ModelService (e.g. in Studio) due to event handling. The index can be configured via Configuration Property elastic.core.event-collection-ttl-sec. Set to 0 to disable the index. Note that the existing index on field "creationDate" must be dropped manually for existing MongoDB deployments, before the new index is created. Otherwise the new index cannot be created.

(CMS-16561)

Unified API in Workflow Server

The Workflow Server defines the Unified API bean connection and all associated repository and service beans in the same way as other applications now. That means that the beans are available for synchronous injection into custom beans. It is no longer necessary to use an ObjectProvider for this purpose. You can share bean definitions across the Workflow Server and other applications now.

Follow Section, “Unified API in Workflow Server” for upgrade information.

(CMS-10928)

Translation Workflow Excludes Translatable Nested Properties From Auto-Merge

The "Auto-Merge" feature used in translation workflows to copy non-translatable property values from master to derived contents has been improved to exclude translatable properties nested in struct properties. In previous releases, nested properties that were marked as translatable were both passed to translation, and copied ("auto-merged") from master to derived, which could have led to warnings about merge conflicts in the workflow. One example of such a nested property is the translatable "call to action button text" of the teaser options for a Blueprint's CMArticle content, which is now correctly ignored by the "auto-merge" logic.

Follow Section, “Translation Workflow Excludes Translatable Nested Properties From Auto-Merge” for upgrade information.

(CMS-10850)

Search Results

Table Of Contents