Release Notes

When logging out of the ContentCreator and then logging in with a different user account in the same browser window, the previous session was mistakenly used for MicroApp actions.

When importing via Feature-Transport or ExternalSync, previously deleted sections and bodies are now correctly mapped to their original IDs, preventing duplicate GIDs for newly created sections with the same name.

JSpecify annotations for nullability in the Access API

Further information can be found in chapter “Module Development, Scripts, API: JSpecify annotations for nullability in the Access API”.

Multisite Management now supports custom bundling strategies via API.

Further information can be found in chapter “Module: Multisite Management: New API for Bundling Strategies in MSM”.

FirstSpirit now supports the import and export of remote schema properties via ExternalSync or ContentTransport, ensuring that the linkage to remote data is maintained during transport operations.

Further information can be found in chapter “Remote Data: Import/export of remote schema properties”.

When assembling the bundle content, explicitly added elements are now correctly processed, even if they were previously already indirectly captured through outgoing references of other bundle elements.

A problem with time-limited archiving has been fixed: If archiving makes no progress due to a time limit, it will now continue archiving until the next savable continuation point.

The method IDProvider#moveChild now correctly sets the start node of the target folder even if it is locked during the move operation.

The behavior of the URL registry with deleted elements has been improved. Reserved paths (preview URLs) and stored URLs of deleted elements are no longer considered in URL conflict resolution within the URL registry, so new elements do not receive unnecessary numbered suffixes when an element is deleted and a new one with the same name is created.

When using the FOP module on an Apache Tomcat server, error messages such as "factory already defined" occurred.

The JRE supplied with the FirstSpirit Launcher has been updated to version 21.

The project export no longer fails when symlink targets are unreachable or other filesystem access errors occur in the FirstSpirit server directory.

Editing permissions can now be restricted per user group based on project languages.

Further information can be found in chapter “Language-dependent user persmissions: Language-dependent user permissions”.

The new method Connection#matchesTicket(String) in the FS Access API provides the ability to verify whether the passed login ticket belongs to the current connection.

Resource conflicts between modules on the server scope are now detected and displayed both as a warning in the server log and in the ServerManager under "Resource Issues".

A display issue with outdated remote schema information in the SiteArchitect has been fixed.

FirstSpirit Content Experience Tools: Latest module versions

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

The return value of the API method IDProvider#getReleaseStatus(Language) has been adjusted. If none of the provided languages have a release revision, the method now returns NEVER_RELEASED as the return value.

A problem with the language-dependent release of datasets using BasicWorkflows has been resolved.

The current version of the FirstSpirit Launcher (1.3.0) now offers native support for Apple Silicon processors.

Open beta phase for the new feature "FirstSpirit REST API"

Further information can be found in chapter “FirstSpirit REST API: FirstSpirit REST API - Open beta phase”.

The ContentCreator now supports Local Network Access (LNA) in preview. Access to internal network addresses can be configured for selected hostnames.

Further information can be found in chapter “Administration: Support for Local Network Access (LNA) in ContentCreator”.

In ContentCreator, the element status area and menus have been adapted to the new look.

Updating the NPM dependencies to the latest versions, specifically TypeScript 5.7.2 → 6.0.3.

General validation notices of the INFO type were mistakenly displayed as "recommended correction." The display of these notices is now limited, similarly to SiteArchitect and the documentation, to the corresponding input component.

When using MicroApps, a state could be reached in which connections to FirstSpirit could no longer be terminated.

When maintaining SEO URLs, outdated URLs were displayed when repeatedly editing individual entries.

In OCM 3.0, there was an issue with detecting the drop zones after a change in the visibility or size of the navigation area.