2.2.6. Release 7.5.39

This chapter contains all changes made in Release 7.5.39 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.39 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.6. Tooling of CoreMedia DXP 8


CoreMedia Studio Changes and Improvements

  • For video documents, the new view type "Shoppable Videos" is now selectable. Once selected, the new property editor "Product Assignments" appears where time intervals can be added. Each interval has a start time and a linked target. So when the video is played and the start time of the corresponding interval is reached, the linked content is shown next to the video.

    If no interval is defined or the first interval does not start at 0 seconds, the content linked in the "Default Product" link list is shown.

    (CMS-5048)
  • It is now possible to create a dashboard widget from the Save Search Dialog in the Library.

    (CMS-4990)
  • Added copy and paste buttons for the taxonomy linklists.

    (CMS-4921)
  • The class fixedSearchWidgetState has been removed. A fixed search widget is configured by the widget type id, only, so that you can use a widgetState object instead.

    (CMS-4917)
  • The RichtextPropertyField's change event buffer can now be configured via property changeBuffer, defaulting to 1000.

    (CMS-4827)
  • The corresponding keys have been moved to BlueprintStudio.properties and blueprintDocumentTypes.properties.

    (CMS-4704)

CoreMedia Blueprint Changes and Improvements

  • Update node.js to latest LTS version 4.2.6, npm to 3.5.3 and frontend-maven-plugin to 0.0.27.

    (CMS-5101)
  • The blueprint now supports alternative media formats like videos or 360 degree views in the same fashion as simple images. So we weakened the content type of the CMTeasable#pictures link list from CMPicture to CMMedia. This allows to add other kinds of media where previously, only pictures were allowed. In order to avoid migration issues, we preserved the property name "pictures" even though it is not exactly appropriate any longer. CMTeasable#getPictures remains backward compatible, i.e. it returns only the CMPicture documents of the link list. There is a new method CMTeasable#getMedia which returns the complete list. (Apart from the type constraints, both methods are subject to validators like the validity period check.)

    While we separated getPictures and getMedia, we also simplified the type of getPictures from List<? extends CMPicture> to List<CMPicture>. Overriding methods must weaken their return type accordingly.

    (CMS-4842)
  • The cookbook dependency 'chef_handler' of the `coremedia` cookbook has been updated from a strict 1.1.4 to 1.2.0.

    (CMS-4481)
  • All Maven plugins have been updated to be compatible with Maven 3.3.3, which is now the recommended version for CoreMedia projects.

    (CMS-4282)

Miscellaneous Changes and Improvements

  • There is a new property editor for editing a list of non-empty strings. In the blueprint, the editor is used for showing and editing the list of product codes in an asset's meta data. The editor supports addition, modification, deletion and reordering the elements in the list. For further details, consult the asdoc of com.coremedia.cms.editor.sdk.config.stringListPropertyField

    (CMS-5055)
  • The maximum z-index for slideshows used in LiveContext sites is now 99 by default.

    (CMS-4745)

Fixed Issues

  • CMS-5158: ProductTeaser image does not work for SKUs/ProductVariants

    ProductTeaser images now work for SKUs/ProductVariants.

  • CMS-5156: CoreMedia specific JSPs in WCS throw Errors due to wrong include

    Fixed include-paths in CoreMedia specific JSPs in WCS workspace.

  • CMS-5141: 360 Spinners are sometimes not displayed correctly

    Increased search limit in Asset Service from 10 to 500 by default and making this value configurable via application property livecontext.assetService.resultLimit

  • CMS-5094: "Long Description" FormField for Categories and Products is too big

    "Long Description" FormField for Categories and Products is now reduced in height and made resizable.

  • CMS-5015: Layout for Product Teaser of Aurora Products is broken for responsive preview

    Product Teasers of Aurora Products without CoreMedia-managed product pictures are now working in responsive view/preview.

  • CMS-4553: Service init scripts are not Centos 7 compatible

    Tomcat init scripts are now compatible for Centos 7 compatibility layer for SystemV scripts. Still Centos 7 may remove that layer in future releases.

  • CMS-4381: Copy RPMs from shared folder to a folder owned solely by the box

    To prevent maven builds from interferring with chef resources, the rpm repodata needs to be created in a folder owned solely by the box. To achieve this all platforms now run a shell provision step in advance of the chef run to copy the artifacts from the shared folder to /var/tmp/rpm-repo.

  • CMS-4147: "Deleted concurrently" message after every tab close

    The message "A content item had to be closed because it was deleted concurrently" is not shown anymore, if the current user has closed the tab by reverting the initial version or deleting the content. The message is still shown if other users delete or destroy the content.

  • CMS-4120: Fix overriding of application properties using JNDI

    Every spring property of webapps based on the component framework of coremedia-spring can be overridden using JNDI entries below java:comp/env/coremedia/application. With this fix it is now possible to override properties as well as to add extra configuration files using the entry java:comp/env/coremedia/application/propertieslocations to set a comma separated list of file URIs.

  • CMS-3815: Use execution resource to execute tool commands

    All executions using backticks have been replaced with the execution resource using the sensitive=true option to suppress passwords from the command in the chef log.