Release Notes
1 Administration
1.1 ContentCreator active for new projects
In the project properties under “ContentCreator” menu item it is specified whether the project can be edited in the FirstSpirit ContentCreator (see FirstSpirit Manual for Administrators, “FirstSpirit ServerManager / Project properties / ContentCreator”).
From FirstSpirit version 2022.11 the ContentCreator is automatically activated when a new FirstSpirit project is created.

ContentCreator active for new projects
1.2 Installing/uninstalling project-local web applications only for server administrators
Web applications require resources on the web server, which must be scheduled accordingly. To avoid FirstSpirit web applications being installed on a web server without appropriate coordination, the permissions required to install/uninstall these web applications have been restricted.
From FirstSpirit version 2022.11 it is only possible for server administrators to install and uninstall web applications. This was already the case for global web applications and has now been extended to project-local web applications.
Downloading and updating project-local web applications is still possible for project administrators.
2 Administration / Modules
Drivers for the Berkeley DB V7 are now integrated into the FirstSpirit server
Since the support of Berkeley DB versions 3 and 5 was removed in FirstSpirit version 2018-11, only Berkeley DB V7 is used for the FirstSpirit backend (“FirstSpirit ServerManager / Project properties / Repository / Backend”).
The corresponding drivers for Berkeley DB V7 are now integrated into the FirstSpirit server so that the previously used standard module fs-berkeleydb7.fsm is no longer required and is automatically removed when the server is updated.
If your server was installed with version 2018-11 (or older), you may delete the unneeded modules fs-vberkeleydb3.fsm and fs-berkeleydb5.fsm in the directory ~firstspirit/data/modules.
3 FirstSpirit Content Experience Tools (CXT)
3.1 Latest module versions
FirstSpirit 2022.11 supports the following module versions for “FirstSpirit Content Experience Tools”.
| Module / file name | Version number |
FirstSpirit CXT Plattformplatform-[version].fsm | 2.5.7 |
FirstSpirit CXT DAP Bridgedataservice-[version].fsm | 1.44.8 |
FirstSpirit CXT FragmentCreatorfragment-creator-[version].fsm | 3.4.11 |
FirstSpirit Fragment DAPfragmentdap-[version].fsm | 1.40.12 |
FirstSpirit Media DAPmediadap-[version].fsm | 1.31.7* |
FirstSpirit PageRef DAPpagerefdap-[version].fsm | 1.9.7 |
FirstSpirit Markdown Editormarkdown-editor-[version].fsm | 1.29.6* |
FirstSpirit Tagging Editortagging-editor-[version].fsm | 1.29.6 |
FirstSpirit CXT FragmentCreator - CaaS Integrationcaas-integration-[version].fsm | 1.31.7 |
* These modules require FirstSpirit 2020-03 or higher from this version.
3.2 Extension and modification of the MicroApp JavaScript API
Attention! The following changes will be active with the next FirstSpirit release 2022.12 (November).
The MicroApps API will be changed: new methods will be added and one method will be renamed. This concerns the JavaScript objects
CxtMicroAppBridge
CxtMicroAppsQuerying possible MicroApps was previously done using the method
getButtonsThis method will be renamed to
requestMicroAppActionsWith this query a list of
contextTypes (optional) and
clientIds (Pflichtfeld) can be passed.
MicroApps define themselves which contextTypes and clientIds they support.
Possible clientIds are for example
content-creator or
fragment-creatorExample
previously
window.CxtMicroApps.getButtons(context).then(...)new
window.CxtMicroApps.requestMicroAppActions(clientId, contextTypes, context).then(...)4 Module Development, Scripts, API
Making API status visible via annotation
The artifacts provided for module developers, such as the fs-isolated-runtime.jar, now contain information about whether Java methods, fields or even entire classes are not part of the stable FirstSpirit API. The annotation @ApiStatus.Internal provided by Jetbrains is used for this purpose. In this way, problematic calls become apparent directly in the IDE.

API status via annotation
5 Modules: AWS S3-Deployment
5.1 S3 Deployment in the case of a missing generation directory
If the generation directory is not created during a generation (e.g. during a delta generation without changes), a subsequent S3 deployment is no longer marked as failed.
Instead, the missing generation directory is logged there with an INFO message and the S3 deployment is not performed. The task is marked as successful.
INFO ... (com.espirit.ps.aws.services.s3.execution.S3Executable): Staging Folder ... does not exist. Nothing to deploy. Stopping S3 Deployment.
5.2 Partial generation: Evaluation of the fullMatching List
When using the AWS S3 deployment module, it is possible to force a matching of the data for partial deployments by using the fullMatching List.
Previously, this required at least one file to be created in the corresponding subtree within the local generation. Deleting complete subtrees was therefore not possible.
Furthermore, the S3 folder configured in the deployment itself could not be included in the fullMatching list. Matching was only possible from the second level.
Both restrictions are no longer applicable with the new version of the AWS S3 Deployment Module.
Overview
| ID | Description | Categories |
|---|---|---|
| CLOUDPROV-15 | The evaluation of the fullMatching List during part generation has been optimised. |
AWS S3 Deployment, FirstSpirit Administrator |
| CORE-13876 | After a project export/import it could happen that a feature selected in a “Content Transport” action was not found in a job and had to be selected again. |
Project export / import |
| CORE-14238 | Fixed a bug that in rare cases could cause connection errors for listeners registered by the module after updating it. |
FirstSpirit Administrator, Modules |
| CORE-14309 | The synchronisation of the SearchManager has been improved to prevent very rare problems with parallel indexing of nodes in different projects. |
FirstSpirit Administrator, Performance, Tasks |
| CORE-14536 | An error in the reference calculation has been corrected, which potentially led to missing outgoing references. |
FirstSpirit Administrator |
| CORE-14608 | An error has been fixed which in very rare cases could lead to the FirstSpirit ServerManager being unusable for some time when trying to edit the project settings. |
ServerManager |
| CORE-14642 | Fixed an error that could cause an incorrect error message to be generated in SiteArchitect for reference targets to which the user does not have access. |
SiteArchitect |
| CORE-14651 | During module development the API status of the FirstSpirit APIs used is now visible. |
Module development |
| CORE-14664 | The drivers for Berkeley DB V7 are now integrated into the standard, so that the previously used standard module |
Server Administrator |
| CORE-14689 | When using special characters in display names, display errors could occur in SiteArchitect in rare cases. This behaviour has been corrected. |
SiteArchitect |
| CORE-14697 | Due to a change of the “FirstSpirit Portal” Module (“SAP Business Package for FirstSpirit”, |
FirstSpirit Administrator, Modules |
| CORE-14701 | From the FirstSpirit version 2022.11 on, the ContentCreator is automatically activated when a new FirstSpirit project is created. |
FirstSpirit Administrator |
| CORE-14702 | Installing/uninstalling project-local web applications is only possible for server administrators. |
FirstSpirit Administrator, Server Administrator |
| CORE-14708 | In very rare cases, a This problem has been fixed. In this case, a corresponding error is now output in the |
Modules |
| CORE-14720 | For languages containing an underscore, selecting a language-dependent data source column did not work properly for the text of the sitemap in a content projection. |
SiteArchitect |
| CORE-14723 | Using the |
ContentCreator, Support for JSON |
| CORE-14737 | If the generation directory is not created during a generation, a subsequent S3 deployment will not be executed. |
AWS S3 Deployment |
| CORE-14748 | With FirstSpirit version 2022.10, a security function was introduced that restricted unauthorized access to preview files. In very rare cases, this function could lead to an increased load on the FirstSpirit server and, in the worst case, prevent the calculation of preview pages. This problem has been fixed. |
FirstSpirit Administrator |
| CORE-14751 | The storage of information about the users' external groups has been optimized so that significantly less memory is required for them. Especially on servers with lots of parallel users who are in many external groups, this results in a noticeable improvement of memory consumption. |
FirstSpirit Administrator |
| CORE-14757 | FirstSpirit Content Experience Tools: Latest module versions |
Developer, FirstSpirit Administrator, FirstSpirit Content Experience Tools (CXT), FragmentCreator, Modules |
| CORE-14797 | With FirstSpirit 2022.10 the integrated browser could not be updated in the server installation directory. This could result in the integrated preview not working properly. |
FirstSpirit Administrator, Preview |
| CXT-2029 | When using the NewSectionOperation, an error message could occur when canceling the creation while the page had validation errors. |
ContentCreator |
| CXT-2108 | Error messages related to network problems have been improved. |
ContentCreator |
| CXT-2360 | The MicroApps API will be changed: new methods will be added and one method will be renamed. |
Developer, FirstSpirit Content Experience Tools (CXT), Module development |
| CXT-2691 | Display names are often based on element snippets. In some cases formattings like "bold" were not properly removed before visualizing the evaluated display name. |
ContentCreator, Snippets |
| CXT-2704 | The input components CMS_INPUT_TEXT and CMS_INPUT_NUMBER were displayed to small, if the form definition was configured using the attribute |
ContentCreator, Input Components |
| DEVEX-554 | With the current release 4.0.1, “fc-cli” (FSDevTools) has been adjusted to improve compatibility with Java 17. |
FSDevTools |
Deprecations
| Functionality | Deprecated as of | Will be removed / Was removed as of |
|---|---|---|
| Input component CMS_INPUT_CONTENTAREALIST | 5.2R3 | |
| Input component CMS_INPUT_CONTENTLIST | 5.2R3 | |
| Input component CMS_INPUT_FILE | 5.2R3 | |
| Input component CMS_INPUT_LINKLIST | 5.2R3 | |
| Input component CMS_INPUT_OBJECTCHOOSER | 5.2R3 | |
| Input component CMS_INPUT_PAGEREF | 5.2R3 | |
| Input component CMS_INPUT_PICTURE | 5.2R3 | |
| Input component CMS_INPUT_TABLIST | 5.2R3 | |
| FirstSpirit Access API: de.espirit.firstspirit.agency.GroupsAgent | 5.2R15 | |
| FirstSpirit Access API: delete (de.espirit.firstspirit.access.AccessUtil) | 5.2R18 | |
| FirstSpirit Access API: release (de.espirit.firstspirit.access.AccessUtil) | 2018-06 | |
| FirstSpirit Access API: getLastLoginAsDate (de.espirit.firstspirit.agency.UserStatisticsAgent) | 2018-07 | |
| FirstSpirit Access API: remainingDurationOfCurrentStageInMillis (de.espirit.firstspirit.server.MaintenanceModeInfo) | 2018-07 | 2025-13 |
| FirstSpirit Access API: getStartingTimeOfStageAsDate (de.espirit.firstspirit.server.MaintenanceModeInfo) | 2018-07 | 2025-13 |
| FirstSpirit Access API: getSelectedWebserverConfiguration (de.espirit.firstspirit.access.serverConfiguration) | 2018-10 | 2025-13 |
| FirstSpirit Access API: setSelectedWebserverConfiguration (de.espirit.firstspirit.access.serverConfiguration) | 2018-10 | 2025-13 |
| FirstSpirit Access API: getSelectedWebServer (de.espirit.firstspirit.access.project.Project) | 2018-10 | 2025-13 |
| FirstSpirit Access API: setSelectedWebServer (de.espirit.firstspirit.access.project.Project) | 2018-10 | 2025-13 |
| FirstSpirit Access API: getLostAndFoundStoreNodes(); (de.espirit.firstspirit.feature.FeatureInstallResult) | 2018-10 | |
| FirstSpirit Access API: getDeletedStoreNodes(); (de.espirit.firstspirit.feature.FeatureInstallResult) | 2018-10 | |
| FirstSpirit Access API: de.espirit.firstspirit.access.store.Previewable | 2019-01 | |
| WebSphere Application Server support for FirstSpirit | 2019-05 | |
| Database layer for Oracle Database 11g/12c | 2020-12 | 2025-05 |
| FirstSpirit Access API: redirectTemplateLogToDefaultLog() (Interface RenderingAgent.Renderer) | 2021-05 | |
| Support for Log4j 1 | 2022-05 | 2024-06 |