2.2.12. Release 7.5.34

This chapter contains all changes made in Release 7.5.34 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.34 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.12. Tooling of CoreMedia DXP 8


CoreMedia CMS Changes and Improvements

  • If a richtext contains an internal link pointing to a CMDownload object, the link lead to another site containing only the link to the blob. Now the link contained in the richtext points directly to the blob.

    (CMS-4466)

CoreMedia Studio Changes and Improvements

  • The packages com.coremedia.rest.intercept, com.coremedia.rest.cap.intercept, com.coremedia.rest.validation and com.coremedia.rest.cap.validation and all respective subpackages have been moved from the module cap-rest-service to the modules coremedia-rest-plugins and cap-rest-plugins. No classes have changed their package, but it might be necessary to update dependencies of modules containing custom interceptors and validators.

    (CMS-4549)
  • Control Room: Content sets as logical containers for contents are replaced by fully-fledged projects. A project encompasses not only content items but also members, to-dos and due dates. For details, we refer to the Studio User Manual. There is no migration tool/path for transferring former content sets to projects.

    (CMS-4542)

CoreMedia Blueprint Changes and Improvements

  • Update frontend-maven-plugin to latest version 0.0.26, node.js to 4.1.1 and npm to 3.3.4 in all blueprint themes.

    (CMS-4472)

Miscellaneous Changes and Improvements

  • In order to improve performance and unnecessary executions, bean customizers destroy themselves when done.

    (CMS-4527)
  • The cms catalog document types CMProduct and CMCategory featured the property metaDescription. Since it has the same meaning as htmlDescription, inherited from CMLinkable, we dropped metaDescription and use only htmlDescription. The ecommerce API remains unchanged. I.e. the getMetaDescription() methods are still supported, but they are backed by the htmlDescription property now.

    (CMS-4519)

Fixed Issues

  • CMS-4532: Collapsible Group with issue should be uncollapsed

    Fixed auto expand of empty titles in collapsibles

  • CMS-4463: changed tomcat cache directory

    The default directory for temporary files with tomcat has changed from /var/tm/coremedia/ to /var/cache/coremedia to prevent accidential removing cache files needed by CoreMedia applications.

  • CMS-4458: Solr schema.xml changed to use autoGeneratePhraseQueries

    The attribute autoGeneratePhraseQueries="true" was added to the field type text_general in the Solr schema.xml. This fixes a bug where searching for a word with a dash (e.g. tv-show) returned documents that matched only parts of the query (e.g. just contained tv).

    There's no need to reindex because this setting does not affect indexing but only query processing.

  • CMS-3637: Naming constraint for cache keys

    The CacheKey name, defined by com.coremedia.cache.CacheKey#cacheClass(Cache, T):String, must not contain the reserved colon character ':'.