Gentics CMP 8.2.0 Changelog

Some dependencies have been updated:

• json-path: 2.9.0
• logback: 1.2.13

Page Expire Date: After taking a page in the CMS offline, the information of when it went offline is now available to the user.
Two new endpoints have been introduced to obtain this information

• GET /publish/state/{type}/{objId}
• GET /publish/state/

Additionally, a publish protocol of pages and forms has been added to the Editor User Interface.

Administrator User Interface: Content Packages can now be checked in the background. Any errors during the report can then be viewed with full context to the error and suggestions for resolution.

Editor User Interface: Forms can now enable a “rich content” mode for individual STRING properties. This allows the text content to add, modifiy, and delete links to internal and external ressources.

Editor User Interface: Files and Images now also have the option to set a custom create and edit date.

Content Staging: The import of a node, which was assigned to restricted object property definitions will only restrict
the object property definition on the target system to the node, if the object property definition has the “restricted” flag set.
If the object property definition is not restricted on the target system, it will remain globally available.

Automatic Translation: Introducing the new automatic translation feature to translate pages and text between multiple languages.
The new endpoints to use the translation feature are:

• @POST /translation/text
• @POST /translation/page/{id}

The new “Handlebars” Part Type brings the Handlebars templating language to the CMS.
See the Guides for details.

The Elasticsearch feature now requires Elasticsearch 8.x. Adds configuration options for HTTPS connections and Basic Auth. For detailed information, please look at the documentation.

Content Staging: The notifications about the package import errors have been improved.

When publishing into a Mesh Content.Repository with “Project per Node” activated, it is now possible to
define the Mesh Project and Branch names in the Node/Channel properties instead of having them derived from the name of the Node/Channel.