Release Notes / Version 10.2107
Table Of ContentsPrevent duplicate URLs for preview allow list and connect sources
Previously the automatically generated connect sources and allowed preview urls may have contained many duplicates, if they were identical in all provider setting documents. This lead to a problem while loading the studio, because the corresponding http header became to large. This fix filters the list for duplicate entries.
(CMS-18345)
'SiteService' in Documentation is wrong
Replaced siteService with sitesService .
(CMS-18150)
Snakeyaml has been updated to version 1.26
The dependency org.yaml:snakeyaml has been updated from 1.13 to 1.26 for the headless-server and from 1.25 to 1.26 for studio (editorial comments). This fixes a security vulnerability which was present in former versions of this library.
(CMS-18138)
Updated Upload Settings Documentation and Mime Type Mapping
The documentation of the Upload Settings has been updated according to the implementation. Additionally, the usage of the settings mimeTypeToMarkupPropertyMappings and mimeTypeToBlobPropertyMappings has been updated so that the primary type of a mime-type is sufficient to configure these mappings.
(CMS-17809)
Studio may leave database lock when interrupted during startup
Should the startup of a Studio-Server instance be interruped, it is possible that a lock is left on the database schema cm_editorial_comments. In this case it is necessary to remove the lock manually, either by performing the following SQL Statement:
UPDATE DATABASECHANGELOGLOCK SET LOCKED=0, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
or
use liquibase to do so: "liquibase releaseLocks"
(see: https://docs.liquibase.com/concepts/basic/databasechangeloglock-table.html )
It is also possible to disable Liquibase with the configuration
editorial.comments.liquibase.enabled=false
. However this means that it is necessary to apply the database changesets manually after an upgrade. This is possible by activating liquibase for at least one startup of a Studio-Server, or to run liquibase manually (
https://docs.liquibase.com/tools-integrations/cli/home.html
).
Example of liquibase.properties file for command line tool (Mysql-Setup):
changeLogFile=db/changelog/db.changelog-editorial-comments.xml username=cm_editorial_comments password=cm_editorial_comments driver=com.mysql.cj.jdbc.Driver url=jdbc:mysql://localhost:3306/cm_editorial_comments?useUnicode=yes&characterEncoding=UTF-8 classpath=>pathToMySqlDriver>/mysql-connector-java-8.0.20.jar:<pathTo_editorial-comments-data-jar>editorial-comments-data-1-SNAPSHOT.jar
(CMS-17784)
Configuration property studio.security.autoLogout.delay renamed to studio.autoLogout.delay
Due to conflicts with StudioSecurityConfigurationProperties the property studio.security.autoLogout.delay in StudioConfigurationProperties was renamed to studio.autoLogout.delay.
(CMS-17731)
Improve Taxonomy Change Plugin
The mechanism to detect changes of taxonomy properties within in the taxonomy manager has been improved. The TaxonomyChangePlugin provides the additional String property properties which supports a comma separated value with the names of the taxonomy properties which should be observed. The property is optional and should only be used when property editors of Taxonomy forms are working on Structs.
Additionally, the class TaxonomyNode.as has the new boolean field _AUTO_COMMIT_ now. This allows to disable the "auto-commit" of the taxonomy manager completely. In this case, we recommend to use the Control Room for detecting and publishing changed content.
(CMS-17707)
Fixed MIME-type Detection for Calendar Files
MIME-type detection for Outlook calendar files (*.ics) has been fixed to return "text/calendar" instead of "text/html".
(CMS-17529)