Release Notes

Since FirstSpirit 2023.6, it is possible to create the configuration of the logging framework using the XML syntax of Log4j2. At the same time, the old configuration in the style of Log4j1 is still supported.

With FirstSpirit 2024.6, this support will be discontinued.

Crownpeak recommends migrating to the new syntax early. Further details can be found in the release notes of FirstSpirit 2023.6.

As of the release 2024.1, the following internally used software has been updated.

• Apache HttpClient
  Update to version 4.5.14 respectively 5.2.1
• Apache PDFBox
  Update to version 1.8.17

The FirstSpirit server now optionally outputs a message in the log when a scalable image exceeds a specific size.

The threshold in megapixels can be specified through the newly added parameters in the configuration file fs-server.conf. The settings apply to both info and warning logging.

• imageio.logging.largeImageInfo
  Default value: 75
• imageio.logging.largeImageWarn
  Default value: -1

When the value is -1, the corresponding log message is disabled.

For a client connection in HTTP mode, a web socket is used for data transfer if possible.

The websocket endpoint can be deactivated via the websocket.endpoint.enabled parameter in the configuration file fs-server.conf:

websocket.endpoint.enabled=false

Default value: true

To improve the discoverability of elements in distributed scenarios, the GIDs of store elements are also transported.

Import and update behaviour

The behavior surrounding GID import and updates is now aligned with the existing behavior observed during operations using external synchronization. Specifically, GIDs will be imported and updated under the following circumstances:

Here's the spell-checked and fixed version of the text:

• GID Availability: GIDs will be imported only if they have not already been assigned to another element (whether in the Current or Release state). In cases where a GID conflict is detected, a warning will be logged.
• Element Type: GIDs will be transported for elements that are not categorized as Datasets. This ensures that GIDs are appropriately managed for the relevant content.
• Explicit Import: Elements explicitly imported or imported as children of explicit nodes will have their GIDs transported. This ensures that GIDs remain consistent throughout the hierarchy.
• Implicit Import: GIDs will also be transported for elements that are implicitly imported and did not exist before the import operation. This facilitates the inclusion of GIDs in evolving content structures.
• Newly Imported Parent Chain: When a parent chain is newly imported, GIDs for parent elements within this chain will be automatically carried over. This maintains coherence within the content hierarchy.

FirstSpirit 2024.1 supports the following module versions for FirstSpirit Content Experience Tools.

The feature “Advanced Image Editing” uses a third-party component that is no longer actively developed. Therefore, this function will be discontinued with a future release of FirstSpirit.