Release Notes

When restricting the maintenance mode to individual projects, allowing further connections for users who were granted access through group names did not work correctly.

In rare cases, the status of web applications or components was not correctly recognised in the ServerManager, so that the “Update” button was incorrectly active. This error has been fixed.

Consolidation of the FirstSpirit API

Further information can be found in chapter “Module Development, Scripts, API: Consolidation of the FirstSpirit API”.

Improved display of elements' workflow status in the reference selection dialog of the input component FS_REFERENCE.

Fixed a problem when installing ContentTransport features that contain many data sets.

Changes to SEO or short URLs made by another user now appear correctly in SiteArchitect after refreshing the corresponding element.

Optimized performance when editing forms with FS_CATALOG components in projects with many languages.

The “FirstSpirit Launcher JRE” module allows the configuration of different JRE files for launching Java-based applications such as the SiteArchitect. If a Java version is selected that does not meet the minimum requirements for the current FirstSpirit server, it will now be automatically reset, allowing the application to start smoothly.

When uploading images, the preProcess(...) method of the ExifUploadHook interface (FirstSpirit Access API, package de.espirit.firstspirit.service.mediamanagement) was incorrectly executed twice.

FirstSpirit also generates error reports even when reporting is inactive, but these reports are never sent and therefore unnecessarily occupy disk space. With the current version, all reports older than one month are now being deleted.

The file size and file type of an image section are now displayed in SiteArchitect, if the image file for the section has already been calculated on the server.

Note: The image file of a section is only calculated upon the first request, and no longer upon the definition of the section in any of the clients.

When starting an application from the FirstSpirit Launcher panel, an error could occur under Linux-based operating systems.

The problem that led to an erroneous termination of long-running feature scheduler tasks has been resolved.

During the processing of XML content, there could have been a misbehavior due to a missing Java export parameter. This has been fixed in version 3.0.8 of the wrapper.

FirstSpirit Content Experience Tools: Latest module versions

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

An incompatibility between the FirstSpirit launcher and installations that are still operated with Java 11 has been resolved.

Within the project-specific SEO URL configuration for the ContentCreator, the “Move Down” button was not functional.

A text alignment potentially configured in section style sheets is now visualised again in the DOM editor.

The icon display of some StoreElement types has been improved.

The rich text editor (CMS_INPUT_DOM) and rich text editor for tables (CMS_INPUT_DOMTABLE) have now been switched to the new TinyMCE API (3.9.3 => 6.7.0).

The availability of MicroApps can be configured on the MicroApp management page. The restriction of the use of MicroApps for members of external groups has been improved. Debug logging has also been added, which can be used to analyse unexpected results of the restriction.

The status pages of MicroApps can now be reached via the MicroApp Management page of the CXT-Platform.

Data sets could be copied in the data source management, even if copying was deactivated in the table template.

The display of pop-up dialogues with more than 3 buttons, which can be created using the RequestOperation interface (FirstSpirit API, package de.espirit.firstspirit.ui.operations), has been optimised.