Gentics CMP 8.1.25 Changelog

Administrator User Interface: Now the `Add languages to a node` modal window scrolls its table content correctly.

Administrator User Interface: Now the list pagination is reset when a new search term is entered.

Administrator User Interface: Fixed an the creation of new nodes, to also save the configured publishing settings.

Editor User Interface: Fixed a potential race-condition which prevented the edit-button to be displayed when previewing a page.

Fixes compatibility issues with Oracle MySQL databases.

Administration User Interface: The `Object Type` values of the Content Repository Tagmap entries list are back.

Editor User Interface: Now edit mode allows the editor hyperlinks being clicked only with CTRL key, preventing accidental page leaves or reloads.

Editor User Interface: Links to the Administrator User Interface will now contain the ‘skip-sso‘ parameter,
if the Editor User Interface was accessed with this parameter.

A column in the table dependencymap2 has been increase to avoid SQL errors during the publish process.
The update to this CMS version might therefore take longer than usual.

Administrator User Interface: Now the display/segment/URL field pickers from the schema editor function correctly, being filled with the field values to pick from.

Administrator User Interface: The behaviour of cancelling the publish process has been improved.
The UI will now wait for up to 10 seconds for the publish process to stop. If the publish process is
still running after 10 seconds, a warning will be shown and stack traces of all publisher related threads will
be logged to the server log.

Administrator User Interface: It is now possible to change the keyword of a construct and the keyword of a part in a construct.

The default log level for the logger ‘org.eclipse.jetty‘ has been changed to ‘warn‘ to log errors
that occur in servlet filters (e.g. used for single-sign-on).
This change will only take effect, if no custom nodelog.yml file is present. If a custom nodelog.yml file
is used, it is recommended to set the log level of ‘org.eclipse.jetty‘ to at least ‘warn‘ there.

The keycloak integration filter, which is used for handling SSO via Keycloak will now log
a more specific error message, if SSO fails because the JWT does not contain the required “preferred_username“ claim.
Also the Guides:“https://www.gentics.com/Content.Node/cmp8/guides/rest_auth.html#sso-with-keycloak” for SSO Keycloak now
mention the required and optional JWT claims.

SSO: The javascript adapter for SSO using keycloak has been updated for compatibility with Keycloak up to version 26.