Release Notes

In the ServerManager, derby layers are now hidden in the project properties under the “Databases” option if they have not been selected.

Using the new checkbox “Show databases for all projects”, all database layers can be shown.

Show database for all projects

The migration to Jakarta Servlet 6.0 is an essential step to ensure the security of web applications.

With the current FirstSpirit version 2023.9, the changeover to Jakarta Servlet 6.0 with support for automatic migration took place.

Support for automatic migration will be removed with FirstSpirit 2024.9.

In contrast to the phased rollout for cloud customers, on-premises customers are able to test and migrate their FirstSpirit servers once version 2023.9 has been released.

Important:

• If FirstSpirit is run in an on-premises scenario, the Tomcat version must be updated when migrating to the FirstSpirit JakartaEE edition. Since the servlet version will be updated to 6.0, a 10.1.x version of Tomcat is required.
• The use of FirstSpirit version 2023.9 requires that Java version 17 is used.

The FirstSpirit installation may be affected if any of the following conditions apply:

• The FirstSpirit installation is not maintained in the Crownpeak Cloud and deploys web-applications to an application server like Apache Tomcat.
• A custom module is used that contains a WebApp component with code that uses the legacy Java Servlet API.
• A custom module is used that contains a WebApp component with dependencies that use the old JavaEE API, e.g., Spring Boot 2.x.

More information and updates can be found in the Crownpeak Community and the detailed Jakarta FAQ.

Contact Customer Support Team if you have questions or feedback regarding the migration.

SEO URLs could so far only be managed in SiteArchitect (see Global settings / URL Settings / “SEO URLs” tab (→Documentation FirstSpirit SiteArchitect))

The SEO URL functionality now is also available in ContentCreator.

Configuration

With the new project component “CXT ContentCreator: URL Configuration ProjectApp” a list of “UrlCreators” can be configured.

Action

There is a new action Show URLs with which the new functionality can be called up. The action is available in the navigation for the menu structure.

For media and media folders, the functionality can be accessd via the icon in the action menu.

Both actions can be deactivated via TailoredUI and are active by default.

For more information, see FirstSpirit Manual for Editors (ContentCreator), “Menu functions / Navigation / SEO URLs”.

FirstSpirit 2023.9 supports the following module versions for FirstSpirit Content Experience Tools.

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

To reach the management page without having to know the URL, a start button can be configured on the FirstSpirit start page.

For this, the “ApplicationPlugin: MicroApp Management” has to be added to the web application “Start page””.

The web component must also be deployed there (“Install” / “Update” button).

The ApplicationPlugin for “MicroApp Management” then has to be added in the “Home page” area (“FirstSpirit ServerManager / Server / Properties / Home page”):

Once the plugin has been selected, the icon for launching “MicroApp Management” is available on the start page.

With the current FirstSpirit version it is possible to apply changes to the definition of the content areas of a page template to all pages based on it via the FirstSpirit API.

The new SynchronizeTemplateBodiesOperation (FirstSpirit Access API, Package de.espirit.firstspirit.store.operations) allows the content areas of a template to be synchronised in all pages based on it.

With the current FirstSpirit version 2023.9, “FirstSpirit Embedded Tomcat Web Server” is introduced as an additional web server alongside the “Jetty Web Server”.

Both “FirstSpirit Embedded Tomcat Web Server” and “Jetty Web Server” are to be used for testing purposes only and are not intended for productive use.

For further information please refer to FirstSpirit Manual for Administrators, Chapter “FirstSpirit ServerManager / Server properties / Web server”, “FirstSpirit Embedded Tomcat Web Server” paragraph.

With the current FirstSpirit version, the unique GID (“Global ID”) of a store element is displayed in the technical properties of this element (context menu “Extras / Display properties”).

Store element GID

The following internally used software was updated with the current FirstSpirit release:

• Eclipse Jetty
  Modul fs-jetty.fsm: update to 12.0.0

As before, use of Eclipse Jetty for production purposes is not recommended!

If the configuration for calculating resolutions is changed via the ImageWriteParams (the user-defined project property), the corresponding resolutions are recalculated once the next time they are accessed.

Note: During the first generation with the current FirstSpirit version, provided ImageWriteParams has been set, the resolutions are recalculated once. This does not applies to manually defined resolutions.