close

Filter

loading table of contents...

Release Notes / Version 13.2512.1

Table Of Contents

Miscellaneous

Breaking change when using translations for ckeditor5 plugins

Before it was possible to use addTranslations from "@coremedia/ckeditor5-core-common". Now it is necessary to add translations via EditorConfig of ckeditor5 Editor.

Follow Section, “Breaking change when using translations for ckeditor5 plugins” for upgrade information.

(CMS-31193)

Migrated JUnit 4 Tests to JUnit Jupiter

JUnit 4 tests have been migrated to JUnit Jupiter. This may be breaking if you have adjusted unit tests provided by the Blueprint.

(CMS-31161)

XML Repository: Extended Support for Getting Referrers

The XML Repository, a mocking implementation for unit-testing Unified API based features, now supports getReferrer* calls also for Structs and Markup properties and thus enriches testing possibilities, where before other mocking strategies had to be found.

Follow Section, “XML Repository: Extended Support for Getting Referrers” for upgrade information.

(CMS-30229)

Variant Model Configuration moved to CMS Core

The variant model configuration has been moved from the Blueprint layer to the CMS core. This makes the variant feature available to applications that do not depend on the Blueprint.

Follow Section, “Variant Model Configuration moved to CMS Core” for upgrade information.

(CMS-29967)

Bugfix: XML Repository Behaved Differently for ContentType#getDirectInstances()

When setting up tests with the XML repository, the implementations of ContentType#getDirectInstances() and QueryService#poseContentQuery(...) could deliver different results as in a real Content Server connection. While the real connection always delivers all contents regardless of user's rights on them, the XML repository would filter them for readability by the current UAPI user. This deviation is now fixed and the XML repository behaves just like the real connection.

Follow Section, “Bugfix: XML Repository Behaved Differently for ContentType#getDirectInstances()” for upgrade information.

(CMS-29959)

Upgraded to Spring Boot 4.1

The Spring dependencies were upgraded to the Spring Boot 4.1. With these upgrades, some further dependencies had to be upgraded as well.

Follow Section, “Upgraded to Spring Boot 4.1” for upgrade information.

(CMS-29855)

Referrer Relation Augmentation for Localization Workflows

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:

  • navigation — includes parent navigation channels (CMNavigation / children)

  • navigation-root — includes the site document that roots the navigation tree (CMSite / root)

  • taxonomy — includes parent taxonomy nodes (CMTaxonomy / children)

  • taxonomy-root — includes root-indicator documents that reference top-level taxonomies (CMSettings / settings)

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.

Follow Section, “Referrer Relation Augmentation for Localization Workflows” for upgrade information.

(CMS-29119)

Refactored Tests to Replace Deprecated Spring Test Classes

Spring's junit 4 integration is deprecated. This affects all classes in the org.springframework.test.context.junit4 package, in particular SpringJUnit4ClassRunner and SpringRunner. Hence, all tests using these classes have been converted to junit 5 tests, most of them using org.springframework.test.context.junit.jupiter.SpringJUnitConfig. This ticket is labelled as breaking because blueprint test code is affected.

(CMS-29052)

Migration to Jackson 3

The CMS applications have been migrated from using Jackson 2 to Jackson 3. The migration required some breaking changes. Some minor parts of the applications still require Jackson 2.

Follow Section, “Migration to Jackson 3” for upgrade information.

(CMS-28694)

Optimization of Cache Class Configuration

CoreMedia Cache Keys that are not specified for a dedicated cache class are stored in default cache class java.lang.Object. This could

  • lead to unwanted eviction of cache keys as the individual key types cannot be weighted against each other, and could also

  • make it difficult to size Java heap memory correctly as the real memory consumption of keys may differ widely.

Follow Section, “Optimization of Cache Class Configuration” for upgrade information.

(CMS-27132)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

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