2.2.13. Release 7.5.33

This chapter contains all changes made in Release 7.5.33 of CoreMedia Digital Experience Platform 8.

Follow the CoreMedia DXP 8 Help Center section to receive release and product announcements automatically.

Modules and Tooling

Release 7.5.33 contains the following CoreMedia modules:

  • CoreMedia Blueprint

  • CoreMedia CMS

  • CoreMedia Studio

  • CoreMedia Elastic Social

In addition, CoreMedia DXP 8 uses the following tooling:

ProductKeyVersion
CoreMedia Application Maven Plug-inAPPPLUGIN2.7.9
CoreMedia Project Maven ExtensionPROJEXT1.0.5

Table 2.13. Tooling of CoreMedia DXP 8


CoreMedia CMS Changes and Improvements

  • Spring XML files for custom blob stores no longer support the #\{...\} syntax for dynamically reloaded properties. Instead, this syntax is reserved for Spring EL expressions now. Note that the Spring EL syntax is still not available in other Content Server and Workflow Server configuration files.

    (CMS-4054)

CoreMedia Studio Changes and Improvements

  • In order to ease translation of documents nested in folder hierarchies, folders can now be added to a translation workflow. They will be automatically expanded to their contained documents.

    As this operation might possibly cause high load in CoreMedia Studio the number of expanded documents is limited to 100 by default. This limit can be configured through the ContentUtilConfigurationPlugin:

        
    <editor:contentUtilConfigurationPlugin
        expandFolderLimit="100"/>
    
    
      
    (CMS-4376)
  • The class com.coremedia.cms.editor.sdk.desktop.InvalidateAllAction has been removed from the product. Because invalidations are automatically pushed to the client, it is not longer necessary to invalidate the client-side beans manually.

    (CMS-3742)
  • Introduced configuration option for new CSP level 2 directive frame-ancestors in Studio. The directive is used to avoid clickjacking attacks in supporting browsers. It is enabled by default with the value none, i. e. you cannot load it into any frame. For details see Studio Developer Manual, section Security/Content Security Policy.

    (CMS-789)

CoreMedia Blueprint Changes and Improvements

  • The string property productCode has been added to the document type definition of CMProduct. This document type is used by the Corporate Blueprint and its catalog extension. It is a required property for products of the CMS catalog. If you're already using the document type CMProduct, then you need to perform the following steps as part of the update:

    • Set sql.schema.alterTable=true once when starting a Content Server to let it automatically adapt the database schema for the new property.

    • Edit all existing documents of CMProduct and enter a non-empty product code. The product code has to be unique within a site's catalog and must not contain slashes, colons or whitespace characters. Studio displays a warning for products that don't have a valid product code

    The product code is also indexed in the newly added productCode field in Solr. The new field was added to the default search fields so that it is possible to find products in Studio and on the website by their product code. It's not necessary to reindex from scratch to get the product codes into Solr. Existing products are automatically reindexed with their product code when they are edited in Studio.

    (CMS-4375)
  • Moved QuickCreate and related components to "blueprint-base-components":

    • moved quick create to blueprint-base components

    • moved FolderCombo to blueprint-base components

    • added AddDefaultFolderComboEntry configuration plugin to support calculated path information for the FolderCombo

    • provided function support for the folder property of the quickcreate editors: the folder combo for a new content creation can be left empty. A separate function can be passed instead to calculate the target folder for the newly created content

    • added "AddDefaultFolderComboEntry" plugin to support the calculation of the default entry of the folder combo with a function

    In order to move the quick create module to blueprint base, the following changes have been made previously:

    • removed blueprint ContentUtils: new class "IdHelper" should be used for parsing the numeric content id instead

    • removed unused NewContentDialog: this was the default dialog used for the create content menu on the favourites toolbar. Quick-Create dialogs are used now instead. The old dialog has been deleted.

    • moved new content defaults to blueprint-forms: the properties file that contains the initialialization of default paths has been moved to the blueprint-forms module

    • provided QuickCreate Hook: extended customization of the quick create plugin, see class "QuickCreate" for details

    • removed StyledButton: unused component

    • moved PreserveCursorPlugin to core

    • removed Toaser: the toaster wasn't used in the blueprint. Use the new studio notifications instead.

    • moved XMLUtil to Struct Editor plugin: The utility was mostly used by the old struct editor, so it has been removed from the blueprint.

    • moved FolderChooser to bpbase-studio-components

    • moved ContentCreationUtil to bpbase-studio-components

    • removed blueprint Studio Logger: use the "Logger" class from the Studio core instead.

    • removed ClearableTextField: unused component

    • refactored several utility methods of the "studio-plugin-utils"

    • moved quick create to blueprint-base components

    • moved FolderCombo to blueprint-base components

    • added AddDefaultFolderComboEntry configuration plugin to support calculated path information for the FolderCombo

    • provided function support for the folder property of the quickcreate editors: the folder combo for a new content creation can be left empty. A separate function can be passed instead to calculate the target folder for the newly created content

    • added "AddDefaultFolderComboEntry" plugin to support the calculation of the default entry of the folder combo with a function

    (CMS-4261)

CoreMedia Elastic Social Changes and Improvements

  • Updated the MongoDb Java client version to 2.13.0.

    (CMS-4347)
  • The option to define a TTL collection with index options in the ModelCollectionConfigurationBuilder has been removed. It is now possible to configure a model index and a TTL collection with the same property. A merged configuration will be used for the actual index creation.

    (CMS-3952)

Miscellaneous Changes and Improvements

    • JUnit updated from 4.11 to 4.12.

    • PowerMock updated from 1.5.2 to 1.6.2.

    • Mockito updated from 1.9.5 to 1.10.19.

    • Objenesis updated from 1.4 to 2.2.

    (CMS-4377)

Fixed Issues

  • CMS-4459: DymnamicPricing typo

    Fixed a typo in String Constant AbstractStoreContextProvider#CONFIG_KEY_DYNAMIC_PRICING_ENABLED

  • CMS-3734: Added order attribute to @Link annotation

    Although link handlers should typically be selected by bean- and view-type, it is now possible to override predefined link handlers using the new 'order' attribute. The order attribute of the @Link annotation follows the semantics of org.springframework.core.Ordered#getOrder.

  • CMS-3004: Contradictory publication result after global publication error

    Fixes an issue where when publication / withdrawal fails with a "global" publication error - such as a Master Live server being down - the publication result window showed contradictory results

  • CMS-484: cm destroyversions

    cm destroyversions is now bundled only with the command line tools for the content management server as it is not advisable to execute this command on any other content server (master/replication).