Release Notes

The processing of special symbols, such as emojis, now works correctly in the input component CMS_INPUT_DOM.

The dialog for editing project groups in the ServerManager indicated an incorrect state when converting internal to external groups if the dialog was reopened before saving the project settings.

When importing a project, the setting "Content Creator / Standard page template" was not retained.

The use of wildcard characters "%" and "_" in table names resulted in columns not being created in the database when editing.

With the current release, it is now possible to manage prompts for the Content Assistant and the Analyze Assistant directly in the ContentCreator.

Further information can be found in chapter “AI-powered tools: FirstSpirit AI: Web-basierte Prompt-Konfiguration”.

When using the module "FirstSpirit Online Documentation," which provides a local copy of the FirstSpirit documentation, the search function is no longer available. Furthermore, it is no longer possible to search within the documentation provided by the ContentCreator.

A problem with WebSocket connections when the root web app was running on only one or two CPU cores has been resolved.

New FirstSpirit server installations now use the internal webserver “Embedded Tomcat” by default.

Further information can be found in chapter “Administration: Embedded Tomcat is now the default webserver for new installations”.

All exceptions declared in the FirstSpirit API are now also part of the API.

An error handling feature has been added to the Analyze Assistant for failed AI requests.

FirstSpirit Content Experience Tools: Latest module versions

Further information can be found in chapter “FirstSpirit Content Experience Tools (CXT): Latest module versions”.

A bug in the Git-based template development for FirstSpirit has been fixed, which occurred when a FirstSpirit project branch was created with the same name as a previously deleted branch.

In global warnings, such as those regarding an upcoming maintenance window, an incorrect time zone could be displayed (e.g., CET instead of CEST).

The removal of the configuration for the web directory in the Tomcat web server resulted in an incorrect directory being used for the staging content.

MSM: Beta status for the Back Transport functionality

Further information can be found in chapter “Module: Multisite Management: Multi-Site Management: Beta status for Back Transport functionality”.

The representation of timestamps in the ContentCreator interface now also takes into account the user's time zone. In the data source view, CMS_INPUT_DATE columns are displayed as when editing in the form. Further information is available under CMS_INPUT_DATE configuration.

A error handling has been added in the Content Assistant for failed AI requests.

For the DOM editor, changes were incorrectly detected during saving in certain cases.

Starting from Chrome version 128+, there was an issue in the DOM editor with link creation via drag and drop.