Release Notes

When using a CMS_INPUT_DOMTABLE, references to used templates are now correctly recognized. This also applies to the standard templates table, tr, td, and CMS_LINK. Similar to CMS_INPUT_DOM, validation errors may now occur if referenced templates no longer exist.

The interface GidAgent has been extended with new methods.

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

From the latest release of FirstSpirit, the recommended Java version (reference) for use with the FirstSpirit Server is changing to OpenJDK 21 (in the current version) (previously: OpenJDK 17). OpenJDK 17 remains on the list of compatible JDKs.

Further information can be found in chapter “System: New Recommended Java Version (Reference)”.

In the configuration of the Image Assistant, the secret AWS access key is now stored encrypted in the file system.

In the Template development for the ContentCreator, there could be malfunctions in displaying the version history if there are invalid revisions in the project.

When using corporate content, there could be memory issues with packages containing many elements.

A problem with repeatedly closing unused project repositories after executing jobs has been fixed.

An error in the reference view for bundles in the release status was fixed. The release status is now also correctly taken into account in the display.

With GOM elements provided by external modules, errors such as a NoClassDefFoundError could occur when updating the module.

The Java classes available in fs-isolated-runtime.jar now include the parameter names from the original source code, which simplifies their use.

Update of internally used software

Further information can be found in chapter “Administration: Update of internally used software”.

The content of FirstSpirit JAR files is signed with a certificate. In the current FirstSpirit version, the content is signed with new certificates.

Further information can be found in chapter “General: Code signing certificate updated”.

Elements that were transferred to the target project per bundle through the bundling strategy can now also be transported back into the master project using back transport.

FirstSpirit Content Experience Tools: Latest module versions

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

The transfer of large generators with S3 deployment could lead to connection interruptions.

When using ContentCreator deep links to a GCA page, a Tomcat error page could appear. Instead, a white page is now displayed, similar to other unsupported elements. Other pages of the project can be accessed through the "Navigation" area.

Within the cropping dialog, incorrect image dimensions were displayed for manually uploaded resolutions.

Under certain circumstances, it could happen that the search result display in FS_REFERENCE/FS_DATASET was covered by other components.

When creating paragraphs with configured fallback values for a DOM editor, it could happen that value changes were also displayed during a subsequent creation operation.

With FirstSpirit 2025.12, the FragmentCreator will no longer be supported and will no longer be available.

Further information can be found in chapter “FragmentCreator: Discontinuation of the FragmentCreator”.

Under certain circumstances, no new connections could be established to MicroApps such as Site Developer or Multisite Management.

Under certain circumstances, no new connections could be established to MicroApps such as Template Development for ContentCreator or Multisite Management.

The DQMConnect module now supports multiple DQM website IDs per server. In the server manager, endpoints can be configured with website ID and API key, which can be selected project-specifically in the Project app.

Further information can be found in chapter “Modules: DQM Connect: Multiple websites for DQMConnect”.