Fixed Content Feeder Bug that Causes Reindexing after Restart

Fixed a bug in the Content Feeder, that after restart, old content events are handled once again and cause up-to-date content to be re-indexed, which may take some time. Furthermore, the bug caused the PendingEvents metric to stay at a high value until restart. The reason of this bug was that the Content Feeder has not always correctly stored the last processed timestamp in Solr.

(CMS-23910)

Fixed Bug in Workflow Converter

Fixed a bug in the Workflow Converter's check to detect incompatible code changes for existing workflow definitions. The bug caused workflow definitions to be treated as incompatible, even if nothing had changed. This could lead to unnecessary conversion of workflow definitions, and also delay Workflow Server startup if it's configured with workflow.server.enable-workflow-converter=true .

(CMS-23678)

Updated JSON-Java

Updated JSON-Java from 20230227 to 20231013

(CMS-23648)

Updated Netty

Updated Netty to 4.1.100

(CMS-23625)

Third-Party Update: Jetty

Jetty has been updated to version 10.0.17 (9.4.53.v20231009 for Site Manager) to avoid reported security vulnerabilities of previous versions.

(CMS-23614)

Fixed Solr Deadlock

Solr 9 contains a bug that may cause a deadlock in rare cases, if a JMX request is received for an index that is still being created: https://issues.apache.org/jira/browse/SOLR-17060 . Such requests may happen automatically at any time with the Prometheus JMX Exporter.

As workaround, we have disabled the problematic JMX MBean attribute solr.<core>.INDEX.segments in the solr.xml configuration file.

(CMS-23602)

Ambiguous published navigation tree will be detected

If an already published navigation node (a page) has been moved under another node, then it was a common error that the old parent node was not also updated/published. If only the new parent node was published then suddenly there were 2 parent nodes on the live side, both of which linking to the moved child page. No validator has drawn attention to this yet.

A new Studio validator "PublishedNavigationTreeValidator" is introduced to address this issue. A warning is displayed both on the moved page and on the new parent page. It says that there is still a published parent page that should also be updated/published.

(CMS-23597)

Studio Search and Special Characters in Prefix Queries

Fixed a bug in the Studio search functionality, that some content items were not returned for a prefix query, if the query contained special characters like dashes or slashes. This fix also affects the suggested content items for link list fields, and the suggested folders in the folder chooser.

A prefix query is a query that ends with an asterisk like "2023-04*". Such queries can be used in the library's search view to find content items containing words that start with a given string. Suggestions for link list fields and the folder chooser use such prefix queries internally.

Previously, these queries did not return all expected results, if the query prefix contained certain special characters. This has been fixed by replacing special characters internally before sending queries to the Solr Server.

In case of unexpected problems, the old behavior can be restored by configuring the Studio Server with studio.rest.search-service.replace-special-characters-in-prefix-or-wildcard-query=false .

(CMS-12532)