XLIFF Import: Markup in Structs Support Enhanced

XLIFF Import of Markup in Structs may have failed, reporting an invalid property value. This got caused by Markup nodes in Struct, where only the Markup value holds grammar information.

This got fixed in that way, that if no other information is available, a fallback to CoreMedia Rich Text 1.0 grammar is applied to the imported Markup node.

(CMS-22528)

RichtextInStructTranslatablePredicate: NullPointerException Fixed

RichtextInStructTranslatablePredicate , used to mark all Struct nodes with CoreMedia RichText 1.0 Grammar as translatable failed with NullPointerException if Markup nodes exist without grammar set at Struct node.

The robustness has been increased: Struct Markup nodes without grammar set at node are now ignored, not being marked as translatable .

Note, that having this, nodes without grammar declared at Struct, but with Markup values having a grammar set, are ignored, too. A corresponding issue exists, to address this, but this requires more fundamental changes, as TranslatablePredicate instances do not have access to the value of a property, yet.

Thus, for best support by CoreMedia Multi-Site feature, it is recommended to set the grammar at Struct Markup nodes always.

(CMS-22527)

Fixed Bug in "cm content-uuid-import'

Fixed a bug in the command-line tool to import content UUIDs ( cm content-uuid-import ) that could cause failures like IndexOutOfBoundsException .

(CMS-22464)

Third-Party Update: Woodstox

FasterXML Woodstox has been updated to version 6.4.0 to avoid security vulnerabilities of previous versions.

(CMS-22314)

Fixed Studio Search Information Disclosure

Original exception messages from Solr, which contain sensitive information in some cases, are no longer passed to clients through Studio Server REST Endpoints.

(CMS-22212)

Improved BELOW Content Query Execution

The Content Server executes content queries with "BELOW" folder clause(s) more efficiently now. This is especially true, if the server is not maintaining a folder index. For details, see the description of the 'cm dbindex' tool in the Content Server Manual.

The server now uses more efficient SQL queries (recursive common table expressions) to query the database, if no folder index was created. The query performance for BELOW queries with enabled folder index will still be slightly better, but the performance difference got a lot smaller, and query performance without folder index can be acceptable for many use cases. In case of problems, the old less efficient implementation can still be enabled by setting Content Server configuration property sql.store.use-ctes-for-below-queries=false .

Some improvements have also been made for query execution with enabled folder index. In rare cases a content query never returned if PostgreSQL was used as database. This has been fixed.

If the folder index is enabled, queries have to wait for the index to be up-to-date, which may take some time after large folders have been moved. In rare cases, this can take quite a long time and block querying applications. A timeout has been added now, so that waiting queries will be executed without the folder index, if the folder index isn't available for some time. The timeout can be set with the Content Server configuration property sql.store.folder-index-timeout and defaults to 1 minute.

(CMS-21264)

Fixed CAE Feeder Possible Deadlock

Fixed a bug that could lead to a dead lock of the CAE Feeder in case of cyclic navigation structures.

(CMS-19571)