Release Notes FirstSpirit™ 2022.13

Release Notes

FirstSpirit™ 2022.13

1 Administration / Modules

Launcher: Preferred debug port

Previously, developers were able to configure the launcher with the option -DclientDebugging=true via {FS-Launcher installation path}/FSLauncher.vmoptions file so that a random debug port would be opened.

The current release allows for specifying a preferred port with -DpreferredClientDebugPort=5005. If the port is already in use, a random port is used instead.

Example configuration:

-DclientDebugging=true
-DpreferredClientDebugPort=5005

Note: The configuration is imported only once, when the FirstSpirit Launcher application is starting up. Therefore any changes to the configuration are not taken into account until after FirstSpirit Launcher restarts.

2 FirstSpirit Content Experience Tools (CXT)

2.1 Latest module versions

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

Module / file nameVersion number
FirstSpirit CXT Plattform
platform-[version].fsm
3.0.1
FirstSpirit CXT DAP Bridge
dataservice-[version].fsm
1.44.9
FirstSpirit CXT FragmentCreator
fragment-creator-[version].fsm
4.0.1
FirstSpirit Fragment DAP
fragmentdap-[version].fsm
1.40.14
FirstSpirit Media DAP
mediadap-[version].fsm
1.31.8*
FirstSpirit PageRef DAP
pagerefdap-[version].fsm
1.9.8
FirstSpirit Markdown Editor
markdown-editor-[version].fsm
1.29.7*
FirstSpirit Tagging Editor
tagging-editor-[version].fsm
1.29.7
FirstSpirit CXT FragmentCreator - CaaS Integration
caas-integration-[version].fsm
1.31.8

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

2.2 Management page for MicroApps

Under

/management

(appended to the URL of the platform), a management page can be reached that can be used to configure the availability of the MicroApps, for example:

http://myServer:8080/cxt-platform/management

In addition, MicroApps can also define actions that are available to users. These actions can also be configured on the management page.

To save the configuration settings, the optional parameter cxt.platform.management.persistence.persistenceFile with the desired path to the persistence file is to be specified in the configuration file cxt-platform.properties.

The status page can only be accessed by administrators.

3 Template development

Standard syntax for executing a source code from another output channel

In complex templates it can be usefull to outsource identical calculations for several output channels to a technical output channel so that these can be managed centrally. Until now, a template type specific $CMS_VALUE()$ call had to be used for this.

This syntax has been simplified to

$CMS_RENDER(#this,templateSet:"<Reference name of the output channel>")$

The complete source code of the specified output channel is then generated at the corresponding point, whereby variables existing in the current context can be used and there newly generated variables are available afterwards in the current output channel.

If another template is called within the switched output channel, this is also evaluated in the specified output channel.

This behaviour can be influenced via the parameter pinTemplateSet. With the default value true, the template remains in the specified output channel, with false, the called template is used in the original output channel.

Example:

$CMS_RENDER(#this,templateSet:"logicChannel",pinTemplateSet:true)$

Overview

ID Description Categories
CORE-12667

With the current FirstSpirit version it is possible to execute a source code from another output channel using a standard syntax.

Further information can be found in chapter “Template development: Standard syntax for executing a source code from another output channel”.

Template Development
CORE-13813

When a dataset was released via a workflow, two release events have been generated. One for the actual release and one for the removal of the workflow from the element. This second event is now no longer generated.

Workflow
CORE-14721

Support for working in projects with very many languages has been improved within the SiteArchitect.

SiteArchitect
CORE-14738

When using the “SAP Login” Module (“SAP Business Package for FirstSpirit”), a NoClassDefFoundError could occur despite correct configuration. The corresponding class loading problems have been solved.

Modules
CORE-14760

The “FirstSpirit SearchFilter” module is now permanently integrated in the FirstSpirit server. After upgrading to the current version, the old module is automatically deleted.

FirstSpirit Administrator, Modules
CORE-14775

Syncing files between a local generation directory and a S3 bucket using the AWS S3 Deployment module was improved. if a local file cannot be opened for reading, the file is excluded from the sync.

AWS S3 Deployment
CORE-14817

When calling the method getExclusionNodeList() (FirstSpirit Access-API, Package de.espirit.firstspirit.access.packagepool, Interface Subscription) an error could occur. This has been fixed.

FirstSpirit API
CORE-14830

A preferred debug port can be configured via the parameter -DpreferredClientDebugPort.

Further information can be found in chapter “Administration / Modules: Launcher: Preferred debug port”.

Developer, Launcher
CORE-14836

The maintaining of groups in the ServerManager has been improved.

FirstSpirit Administrator
CORE-14842

If Executables from a module are used in a workflow, custom exception types from the module can now also be used there to signal an error state in the workflow.

Developer, Workflow
CORE-14847

An error has been fixed that caused ttf files to be incorrectly marked with the file type emf by FirstSpirit. Newly uploaded TrueType fonts are now correctly marked with the file type ttf again.

Media
CORE-14859

An error with the display of web applications (NullPointerException) in ServerManager was fixed.

FirstSpirit Administrator
CORE-14863

An error has been fixed that could lead to filehandles opened by FirstSpirit not being closed correctly.

FirstSpirit Administrator
CORE-14867

Fixed a bug that could lead to slow loading of pages in very rare cases (deadlock in DefaultStoreElement#_refreshElements).

Developer
CORE-14878

The search in the FirstSpirit SiteArchitect was adjusted, so that the search results now better meet the expectations from a technical perspective in cases where the search string contains special characters (except umlauts). This partially results in that more and better results containing special characters are found without having to use quotation marks.

Please note that corresponding special characters are not taken into account for the search, which means they do not influence the search result.

ContentCreator, Editor, Search
CORE-14939

FirstSpirit Content Experience Tools: Latest module versions

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

FirstSpirit Content Experience Tools (CXT)
CORE-14941

When redeploying WebApps assembled with FirstSpirit, a classloading problem could occur in rare cases.

FirstSpirit Administrator
CXT-2049

The welcome tour was not shown properly, if the documented features were disabled using the TailoredUI configuration.

ContentCreator
CXT-2719

Management page for MicroApps

Further information can be found in chapter “FirstSpirit Content Experience Tools (CXT): Management page for MicroApps”.

FirstSpirit Content Experience Tools (CXT)

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