Release Notes

As of the release 2023.2, the following internally used software has been updated.

• Apache Commons IO (library with operations for file inputs and outputs)
  Update from version 1.3.2 to version 2.11.0
• Apache Commons Lang
  Update to version 3.12.0
• Java (JRE, with which the desktop clients SiteArchitect and ServerManager are operated)
  Integrated in FirstSpirit (standard): 17.0.5+8 64bit AdoptOpenJDK

As of the release 2023.3, the following internally used software will be updated.

• Gson (2.8.0 --> 2.10)
• metadata-extractor (2.11.0 --> 2.18.0)
• Apache POI (3.7 --> 5.2.2)
• commons-codec (1.11 --> 1.15)
• commons-collections (4.1 --> 4.4)
• commons-math (3.6.1, new)
• xmlbeans (2.5.0 --> 5.0.3)
• dom4j (1.6.1 --> no longer used)

If the FirstSpirit ContentCreator was run with an application server on Java 17 or newer, this could lead to problems with creating new sections or editing existing ones.

To resolve this, it is necessary to use the following parameter:

--add-opens=java.base/java.lang=ALL-UNNAMED

The parameter has been added to the fs-wrapper-vendor.conf file. After a FirstSpirit server update, it is available automatically.

The start parameters of external application servers (e.g. Tomcat) need to be complemented with the --add-opens parameters found in the fs-wrapper-vendor.conf file.

Java 17 is now used by default to start the FirstSpirit desktop applications (ServerManager, SiteArchitect).

If the operating system ran out of free file handles for the user for which the FirstSpirit server was operated, this led to severe follow-up problems.

The server settings for Linux-based operating systems have now been edited in the fs-server.conf file to prevent such problems:

• The Open Files are being checked every 60 seconds.
• As soon as the warning limit is surpassed (pre-setting: 90%), the server receives the “Degraded” status.
• As soon as the shutdown limit is surpassed (pre-setting: 95%), the server is being shut down.
• The server administrator is notified via e-mail about a surpassed limit.

Default values of the fs-server.conf file:

# open files warning limit
files.limit.percent=90
files.limit.active=true
# open files shutdown limit
files.shutdown.percent=95
files.shutdown.active=true

You can check the Open Files in the “HealthManager MBeans” using the entries maxFileHandles and openFileHandles.

So far, JSON generation has been cancelled if implementation errors in the Data Access Plugin occurred.

JSON generation is now continued even if DAP errors occur. The error is output as a JSON error object.

Manual croppings can be reset for the complete group. Resolutions that have been uploaded manually are highlighted with an exclamation mark and can also be reset as a group.

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

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

From FirstSpirit Relase 2022.13 it is possible to configure the availability of MicroApps via the management page.

This management page is accessible under

/management

(appended to the URL of the platform), e.g.

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

Previously, the management page was only accessible to server administrators.

With the current release, the page is also accessible for project administrators.

Installation / Modules / Installing modules / Platform (→Documentation “Content Experience Tools”)

Threshold values for free disk space can be defined in the global server settings (FirstSpirit ServerManager) or using the parameters hdd.limit and hdd.shutdown (fs-server.conf). When these values are surpassed, an e-mail is sent to the server administrator. If the shutdown limit is surpassed, the FirstSpirit server is shut down.

So far, the threshold value could only be set as a disk space percentage.

With the current release, the free disk space can be set as an absolute value instead of the percentage.

Note:

Values under 100 are interpreted as a percentage setting:

• hdd.shutdown=1073741824: shutdown limit at 1 GiB remaining disk space
• hdd.shutdown=97: shutdown limit at 97% of the total disk space

For absolute values' settings, you can also use m (MiB), g (GiB) and t (TiB):

• hdd.shutdown=2g: shutdown limit at 2 GiB remaining disk space

Note:

• Technically smallest possible shutdown limit setting for remaining disk drive: 512 MiB
• Recommended shutdown limit setting for remaining disk drive: 95%, minimum 2 GiB

The threshold values can also be defined via API (FirstSpirit access API, package de.espirit.firstspirit.server.configuration). The previous methods have been deprecated and replaced by new ones. Now, the threshold values are transferred as String.

So far, when creating or editing a table in a database schema, it was possible to use spaces in the table name. With spaces in table names, it was possible that no results were found when searching the corresponding table's data source.

With the current release, you cannot use spaces in table names any longer when creating new tables or editing existing ones in the GUI.

Note: The names of existing tables have not been adjusted and still are considered correct even if spaces in the table name do exist. When changing the table name, you will need to delete such spaces.