close

Filter

loading table of contents...

Release Notes / Version 10.2107

Table Of Contents

CoreMedia Core

cm dumpusers: Pretty Print Option

For convenience, a pretty-print option has been introduced: \-P or --pretty .

(CMS-17782)

Rights for Property Service

Using the Content Server configuration option cap.server.persistentPropertyWriters it is possible to specify a group or a list of groups that are granted the right to write and delete system properties through the UAPI PropertyService . By default, the properties are still writable to every logged-in user.

(CMS-17654)

Third-Party Update: Apache Tika and Transitive Dependencies

Apache Tika has been updated to version 1.24.1 to avoid a security issue of the previous version (CVE-2020-9489). As part of this change, the following transitive dependencies of Apache Tika have been updated to match versions used by Tika.

Updated dependencies:

  • com.github.openjson:openjson : 1.0.12

  • org.apache.commons:commons-lang3 : 3.10

  • org.apache.tika:tika-core : 1.24.1

  • org.apache.tika:tika-parsers : 1.24.1

  • org.bouncycastle:bcmail-jdk15on : 1.65

  • org.bouncycastle:bcpkix-jdk15on : 1.65

  • org.bouncycastle:bcprov-jdk15on : 1.65

  • org.ow2.asm:asm : 8.0.1

Replaced dependencies:

  • com.googlecode.mp4parser:isoparser is no longer a transitive dependency of Tika. org.tallison:isoparser version 1.9.41.2 is used instead.

If you use the libraries in project code, please check their respective release notes for changes and upgrade information. No changes were necessary in the CoreMedia Blueprint for these updates.

(CMS-17435)

Option to Exclude Unchanged Property Values from Translation

Added a new option to exclude property values from translation, if they haven't changed since previous translation. If the property " translate.item.include-unchanged-properties " is set to " false ", then unchanged properties will not be included in TranslateItem -s, which are used to create XLIFF for translation purposes. Set this property at the Studio Server for the exported XLIFF that can be requested in Studio for a translation workflow. The same property can be set at the Workflow Server , if XLIFF is exported from a custom workflow step.

The default value for the property is " true ", which keeps the existing behavior.

As part of this change, the two-argument constructor of the public API class com.coremedia.translate.item.DefaultContentToTranslateItemTransformer has been deprecated. Usages should be replaced with the new constructor, as described in the API documentation.

(CMS-17231)

Introducing SitesService to JShell

You may now access the SitesService within JShell CoreMedia namespace via cm.sites . In addition to that, you can access the Spring context via cm.context for additional beans.

The standard imports for the COREMEDIA startup script have been extended by an import of com.coremedia.cap.multisite.* , so that you can easily access multi-site features.

(CMS-15597)

Derive Site Workflow Will Apply Missing Rights

The workflow derive-site.xml has been extended by a new action EnsureSiteWideRightsAction (FQN: com.coremedia.translate.workflow.EnsureSiteWideRightsAction ). It is added as final action as successor of DeriveSiteAction .

This action validates, if the given site-manager-groups for the newly derived site, have sufficient rights (Read, Modify, Delete, Approve, Publish) on Document- and Folder-type. If rights are missing, a rule will be added to the new site-root-folder. Thus, the action grants that the new site-managers have privileges on the new site.

Using this action requires the group translation-workflow-robots having supervise rights on the root-folder of all sites (typically /Sites ).

Upgrade: To benefit of the new workflow, you have to re-upload it. Prior to that, you should change the permissions of translation-workflow-robots extending it by the required supervise permissions.

Note: This change expects, that some preconditions are met:

  • Site-Manager-Group already exists.

  • Site-Manager-Group has already been assigned to required workflow roles, like for example: translation-manager-role , approver-role , ...

  • Site-Manager-Group is already configured for required rights outside the site-root-folder (like Themes or global Settings for example).

Documentation:

Studio User Manual (Section: Preparing Translation: Deriving A Translated Site) and Blueprint Developer Manual (Sections: Deriving Sites and Groups and Rights Administration for Localized Content Management) have been adapted accordingly.

(CMS-9422)

Search Results

Table Of Contents