Release Notes

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

• Apache FOP (Formatting Objects Processor)
  Via the module fs-fop.fsm (for the output of FirstSpirit content in PDF format).
  Updated from version 2.5 to version 2.8.
  Furthermore, Apache Batik was updated to version 1.16 in the module.
  Note: Besides closing several security holes, this also results in a better display of SVG graphics in the generated PDF files.
• Commons FileUpload
  Updated from version 1.3.1 to version 1.5

In the JSON output configuration, the json.outputLengthLimit parameter can be used to set a size limit in bytes for the JSON file to be generated. If the set value is exceeded, the generation of the JSON file is aborted with an error message, the non-valid file is not deleted. Without setting the value, the file size will be limited to 2GB.

Example (size limit at 15MB):

$CMS_SET(#global.json.outputLengthLimit, 15728640)$

FirstSpirit 2023.5 supports the following module versions for “FirstSpirit Content Experience Tools”.

* These modules require FirstSpirit 2020-03 or higher from this version.

The CXT MicroApp API URL configuration was moved from the “FirstSpirit FragmentDAP” module (Web component “Fragment DAP for ContentCreator”) to the “FirstSpirit CXT Platform” module (“CXT Platform | Configuration Service”) starting with version 3.0.6.

CXT-Platform Configuration Service

The “CXT-Platform | Configuration Service” provides a configuration interface that can be opened by clicking on “Configure” or by double-clicking on the service. Here, the URL to the MicroApp is configured. In this case, the URL is used to integrate the CXT MicroApp API into a website.

This is the value of the cxt.platform.external-url parameter configured for the CXT platform (see Installation / Modules / Installing modules / Platform (→Documentation “Content Experience Tools”)):

https://external/cxt-platform/microapps/api.js

The interface RenderingAgent (package de.espirit.firstspirit.agency, FirstSpirit Developer API) allows to manage the generating process for certain dynamic FirstSpirit content directly via the API.

With the new method getResult(@NotNull Writer contentWriter, @Nullable Writer logWriter), the rendering results are written directly into the transferred writers.