Gentics CMP 8.0 Changelog Summary

When moving a Form between the nodes, that point to the different Mesh CRs, pointing to the same Mesh instance, the following publish process may fail with an item duplication error. This has been fixed.

Importing a content package left file handles open for too long, which could lead to problems like “too many open files”.
This has been fixed, file handles will be closed now immediately after they were used.

Administrator User Interface: Fix vanishing parts of constructs when saving with the save dialog modal.

When moving an object (Page, File etc) between the nodes, that point to the different Mesh CRs, pointing to the same Mesh instance, the following publish process may fail with an item duplication error. This has been fixed.

The publish process will now check for required features and fail, if one of the required features is not activated.

Administrator User Interface: The copying of templates is now performed directly without opening a modal first.

Administrator User Interface: Align behavior of activities and messages. The icons are only shown if new messages/activities exist.

Editor User Interface: Fixed non-visible elements of the select input type for forms.

Administrator User Interface: Corrected the displayed status of the Publisher.

The static resources of devtools packages, served over filesystem symlinks, are now accessible again.

An occasional `NoSuchElementException` crash in Content Staging has been fixed.

Some errors in sorting and filtering of result lists have been fixed in the REST API.
Sorting and filtering abilities of REST API endpoints have been clarified in the documentation.

Now all the permissions, excluding the legal READ_PUBLISHED, are forcefully removed from the objects upon Mesh publish.

The old `invoker queue` database entries, that are not anymore supported, were removed.

Editor User Interface: In some cases the tag editor for overviews showed the order direction to be “descending“ while it was
actually “ascending”. This has been fixed.

Editor User Inferface: When changing the order direction of an overview in the tag editor from “ascending“ to “descending”,
the preview of the tag showed the items in the wrong order, this has been fixed.

Editor User Interface: Add clear button to dropdown to remove already selected items (e.g.: Enable removal of input validation after selecting one)

Now every object disallows leading and trailing spaces in its name. Those will be removed on every object save.

The error message when uploading images exceeding the maximum allowed dimensions has been improved.

Editor User Interface: Fix the deletion of form reports with invalid data (i.e.: containing null values)

Editor User Inferface: When using the Link Checker and an invalid external link is changed to an internal link,
the marking of the link was not removed (the link was still shown as invalid). This has been fixed: since internal links
are not checked by the Link Checker, the any markings will be removed when an external link is changed to an internal one.

Moving a page into another node will no longer be possible, if the page has variants in languages,
which are not activated in the target node. The only exception is when moving a page with a single language
into a node, that does not have languages at all (in this case, the page will also have no language) or when
moving a page without a language into a node with languages (the page will get the first assigned language
of the target node).
If a page is copied into another node, only the language variants with languages, which are activated in the
target node, will be copied. If no language variant of the page is activated in the target node, the selected
language variant will be copied and will get the first assigned language of the target node.

If removing a “publish at“ or “offline at” time was denied due to insufficient permissions, the request still succeeded and no
appropriate message was shown to the user. This has been fixed.

Updating object property definitions over the REST API failed with an internal error, if not all attributes were sent.
This has been fixed.

Docker Image: The package mariadb-client has been added to the CMS docker images. This package e.g. includes mysqldump, which can be used to make a backup of the cms backend database.

Due to an incorrect permission check, removing a previously set “publish at“ or “offline at” time did not always work for
users with permissions restricted to certain channels/nodes. The permission check has been fixed.

Editor User Interface: When using the advanced search, the search was not restricted to the current folder but always searched the whole node.
This has been fixed so that the search will be restricted to the current folder and all subfolders.

The version of the Mesh REST Client has been updated to 2.0.14.

Editor User Interface: Autofocus of the searchbar has been fixed to only occur while not editing a object. Navigation in the list will properly reset the focus to the searchbar as well.

REST API: Getting the localization Information for an inexistent ID caused an Internal Server Error, which has been fixed.

On a file/image copy, its object property values were not copied onto the new instance. This has been fixed.

Overviews that contained objects, which were deleted caused NullPointerExceptions during publishing to a Mesh Content.Repository, which have been fixed.

Administration User Interface: Option list of Validator field is in alphabetical order in TagType editor. Incorrect regex options name and expression are updated.

Administration User Interface: Confirmation dialog is shown on TagPart editing, if devtool automatic synchronization is enabled and TagPart has changes in the file system during editing.

Overviews that contained objects, which were deleted caused NullPointerExceptions during content staging, which have been fixed.

Random actions on a construct with a part with missing PartType were throwing NullPointerException with no meaningful description. This has been fixed.

Deleting a page and its language in the same transaction caused an error, which has been fixed.

Administration User Interface: The error message, which is shown when a construct cannot be deleted, because it is still in use, has been improved.

Editor User Interface: The translated pages are displayed properly in the page language indicator after changing page properties. clear

Administrator User Interface: The permission lookup for the (DevTool) Package Module and the Templates Module have been corrected.

Administration UI: The performance of fetching all templates, which are assigned to a node, and the assignment operation has been improved.
REST API: New endpoints have been added:

• GET /node/{nodeId}/template/{templateId}
• GET /template/{id}/nodes

Editor User Interface: When opened by a user without permission to see a single node, the button for opening the Administration Interface will now correcly open the Admin UI.

Publishing into a Mesh Content.Repository has been optimized to use fewer requests to read roles from Mesh or set permissions on roles.

The logging for publish runs has been improved to include the durations for writing
objects into a Mesh Content.Repository and also the waiting time for putting items into
the internal queue.

Editor User Interface: The preselection of templates while creating language variants of pages has been fixed.

Makes sure information about whether a page is online is accurate during instant publishing. This issue caused overviews to skip pages which where itself instant published during a long running publish process.

The paths for publishing into the filesystem were not correct when using non-empty node publish directories.
For published nice URLs, the node publish directory was not used at all.
If the publish path should contain the language code, the language code was inserted into the path before the node
publish directory, instead of after it.

The uniquess check for URLs did not consider the page publish directory of nodes/channels when
checking nice URLs. This could result in duplicate URLs, which would cause subsequent errors.
The check has been fixed. Possibly existing duplicate URLs have to be fixed manually in the CMS.

Administration User Interface: Several modules failed to refresh entity lists when entities were created, modified or deleted and have been fixed.

Publishing into a Mesh Content.Repository with “project per node” disabled might fail with a NullPointerException, if e.g.
pages were taken offline and re-published between two publish runs.
This has been fixed.

Adds check if the publish dir is empty for a folder create or save request when publish dir segments is active. An empty publish dir segment is only valid for the root folder of a node.

If a schedule was set up to follow after another schedule, and the followed scheduled failed with
an exit code bigger than 127, further scheduling failed with an internal error.
This has been fixed.

Scheduling tasks with intervals behaved differently than the old scheduler:
While the old scheduler always calculated the intervals from the start time, the new scheduler
calculated from the last execution. This is unexpected, because when for example a task should be executed (automatically) once a day at 3 AM,
a manual execution of the task would break the start time (next automatic execution would be one day after the last manual exection, not necessarily at 3 AM the following day).
The behaviour of the scheduler has now been changed to the behaviour of the old scheduler.

Editor User Interface: Changing list settings with a checkbox had inconsistent behaviour which sometimes didn‘t save the setting correctly.

Editor User Interface: The repository browser for forms always showed the forms from the selected
folder including all subfolders, even if no search phrase was entered. This has been fixed to be consistent
with the repository browser for other types: When no search phrase is entered, only the forms of the selected
folder will be shown.

Execution of external tasks in the scheduler has been improved: stdout and stderr of the executed command (script)
will now not be buffered, but will be redirected to log files. This fixes problems with commands that create lots of output (e.g. curl, if the request runs for a long time),
which could cause some executions to hang forever.
Additionally, the display of scheduler executions has been improved:

• Running scheduler tasks will now be shown as “Running“ (instead of “Failed”)
• Running scheduler tasks will now show the current duration instead of 0

Editor User Interface: Selection of content- and template-tags has been fixed.

The conflict resolving behaviour when publishing into a Mesh Content.Repository has been improved.

Editor User Interface: Opening Embedded Tools now properly display the tool instead of being overlayed on the Editor.

Administrator User Interface: An issue with editing Tag-Parts, causing corruption of these has been resolved.

Moving folders in the CMS in a multichannelling environment might cause publishing errors when publishing to a Mesh Content.Repository,
which have been fixed.

Some possible NullPointerExceptions during the publish process have been fixed.
Error logging in cases of lock wait timeouts during the publish process has been improved.

Performance of checking template permissions has been improved.
This especially reduces load time for the REST API call to /rest/node/[node_id]/templates.

The detection of changes in constructs has been refined when synchronizing devtool packages from the filesystem into the CMS.

Editor User Interface: Restored the functionality of the full-screen editor.

When publishing into a Mesh CR with instant publishing enabled, it could happen that objects, which were published and then deleted into the wastebin
between two regular publish runs where not removed from Mesh. This could lead to conflicts during subsequent publish runs, if objects with the same publish
path should be published afterwards.
This has been fixed.

The migration of old scheduler tasks to the new scheduler has been made more robust.

Forms were not always dirted, when referenced eMail template pages were changed and republished.
This has been fixed. It is important to note, that forms need to be republished manually once after
the CMS has been updated to trigger the fixed dependency calculation.

The detection of failed publish processes has been improved.

Removes a misleading error message when publishing into a Mesh-SQL ContentRepository.

Editor User Interface: The permission check for creating Folders has been fixed, and will now properly hide the create button if the user isn‘t permitted to create new Folders.

The purge logs and purge messages jobs have been improved to purge the records in batches.

Adds a fix to prevent duplicate filenames when multiple files are uploaded, moved or copied in parallel.

Content Staging has been made more tolerant with regards to the implementation hash checks.

Some problems with inheritance have been fixed:

• Opening the inheritance dialog for pages in folders, where were not fully inherited failed with an error.
• The option “Disinherit by default“ was missing from the inheritance dialog.
• The option “General inheritance” did not show the correct status and changing it behaved inconcistently.
• The inheritance dialog allowed inheriting objects into channels, even if the folder was not inherited in that channel.

Add flag to objects of GET /msg/list response to indicate if message is an instant message.
Editor User Interface, Admin User Interface: Fix instant messaging.

Some REST API requests could fail with an Internal Error (due to incorrect permission checks).
This has been fixed.

A flawed content staging management of Overview tags have been fixed, including self-reference.

The path to the link-checker custom tool was fixed to make it available with the
configuration mentioned in the Guides

Administrator User Interface: Fixed table cell values to be vertically aligned properly.

Administrator User Interface: Fixed missing permission icons for scheduler management.

Deleting an object property definition using the REST API (or the Admin UI) failed with an internal error, which has been fixed.

Editor User Interface: Sorting select options in a form will now re-order them correctly.

The SSO Login is now compatible with Keycloak 22.

Some dependencies have been updated:

• imageio: 3.9.4
• tika: 1.28.5
• commons-fileupload: 1.5
• commons-beanutils: 1.9.4
• nekohtml: 1.9.22
• xml-apis: 1.4.01
• org.json: 20230227
• xalan: 2.7.3
• xerces: 2.12.2
• spring-security: 5.7.10

Editor User Interface: The styling/sizing of the columns and cells of the form reports table has been updated to make it possible to view all content.

If a content resource (file / page / etc), attached to the content staging package, has been moved around, the package keeps its copy under its old placement, which produces a mess during the restore of this package. This has now been fixed.

The JSON output of Devtools items has been normalized to use LF line endings only on all systems. It is now exporting all non-null (e.g. including empty) fields.

Administrator User Interface: Fixed inconsistency error with translatable texts (Name, Description) which didn‘t apply changes correctly.
This prevented Roles and other Entities to be created and/or to be properly edited.

Fixes rendering of #gtx_channel directive after editing when creating a link to a local object in another channel.

Fixing the issue where new object tags are created when merely changing properties of a template.
This triggers the generation of new global ids (UID‘s) for the same object tags, hence causing issues, especially with package synchronization.

Editor User Interface: Constructs are properly grouped by their categories again when inserting them in a Page.

Editor User Inferface: Form Reports are now properly sized, paginated, and can be scrolled through.

Editor User Interface: Fixed the validation and indication of required fields when creating a new form.

Editor User Interface: The Headline for language-specific settings in the form properties is now getting hidden when only one Language is set for the Node.

Administrator User Interface: Added back option to restrict groups of a user to a specific Node.