Release Notes

For FirstSpirit, e-Spirit supports:

• OpenJDK: the current Java version as well as the latest LTS (Long-Term-Support) variant.
• Oracle Java: only the latest LTS (Long-Term-Support) variant.

This applies to both the FirstSpirit Server and the FirstSpirit desktop applications.

These are for the current FirstSpirit version:

• Oracle Java 11 (in the current version)
• OpenJDK 15 (in the current version)
• OpenJDK 11 (in the current version)

In February 2021 e-Spirit started the test phase for the use of OpenJDK 16 (non-LTS; Release Date 2021/03) with FirstSpirit. During this phase, the FirstSpirit desktop applications (SiteArchitect, ServerManager) and the FirstSpirit server will be subject to intensive internal testing. We currently expect to release FirstSpirit version 2021/04 with support for OpenJDK 16.

With the support for OpenJDK 16, the support for OpenJDK 15 (non-LTS; Release Date 2020/09) expires. (FirstSpirit is expected to remain functional with OpenJDK 15. However, e-Spirit AG will neither carry out tests with OpenJDK 15 nor implement any measures designed to eliminate errors or problems that are exclusively associated with the use of OpenJDK 15.

Further documentation see FirstSpirit: Technical requirements and recommendations.

There have been issues with inserting formatted text in rich-text editors in ContentCreator (CMS_INPUT_DOM and CMS_INPUT_DOMTABLE) as well as when using the “Undo” function by icon.
These have been resolved.

Rich-text editors provide editors with a variety of formatting options. However, this can result in invalid HTML being output, depending on the project configuration.
The new functions referred to below are designed to help the editor identify invalid formatting.

In general, project-specific sign formatting is now enclosed in square arrows so that it can be identified more easily in the editor:

Additionally, text with invalid formatting is now highlighted in color in the rich-text editor, providing a visual indication of a rule violation:

• orange: This indicates a format template that is in the project but is not permitted for the rich-text editor in question.
  It can be saved, but the formatting concerned should be removed before release (“prevents release”).
• red: This indicates a format template that has subsequently been deleted or is unrecognized for another reason.
  The formatting concerned must be removed before the template can be saved (“prevents saving”).

DIV elements (<div>) are block elements in HTML. If a format template was declared as character formatting (“inline”) in the project for DIV elements, this may have led to problems with saving section formatting. As of the current release, such invalid DIV formatting is automatically removed.

In addition, the behavior for lists and inline tables (attributes list and table) has been improved if the setting was subsequently changed on the template side: Existing content remains editable in any case.

FirstSpirit 2021-02 supports the following module versions for “FirstSpirit Content Experience Tools”:

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

The following modules and extensions are compatible with FirstSpirit 2021-02:

The Java versions included in the “FirstSpirit Launcher JRE” module were updated in the latest FirstSpirit release:

In addition to the version supplied with the FirstSpirit Launcher, AdoptOpenJDK 11.0.10+9 (default), the following Java variant is currently available:

• AdoptOpenJDK 15.0.2+7 (new)

For documentation on the “FirstSpirit Launcher JRE” module, see the corresponding manual.

New behavior (default setting: start via the FirstSpirit Launcher):

As of the current FirstSpirit version, the FirstSpirit desktop apps (SiteArchitect, ServerManager) are started automatically for all users via the FirstSpirit Launcher. The “Use FirstSpirit Launcher” option on the start screen is no longer shown as of the current FirstSpirit version. This means that the user can no longer activate or deactivate the use of the FirstSpirit Launcher.

The option of starting the FirstSpirit desktop applications via Java Web Start is no longer available. The FirstSpirit JNLP files required for Java Web Start are no longer available either.

The FirstSpirit Launcher provides a continuously updated, extensively tested, and license-free Java Runtime Environment which is rolled out when the Launcher is installed. This allows SiteArchitect and ServerManager to be operated in a preconfigured environment which is independent of the Java version on the client computer – even if there is no Java version installed at all (see The Benefits of FirstSpirit Launcher).

Previous behavior (default setting: start via Java Web Start):

Previously, FirstSpirit desktop apps were only started via the FirstSpirit Launcher if the “Use FirstSpirit Launcher” option was activated.

It was possible to make this setting:

• for each user separately in the connection settings on the start page (see Configuring connection settings) or
• for a group of client computers within the configuration file fs-server.conf using the parameter externalLauncherGroup (see fs-server.conf configuration). With this option, the use of the Launcher was stipulated for all members of the group in question and it was not possible for individual users to deactivate it.

Do any changes need to be made in line with the new behavior?

Installing the FirstSpirit Launcher on all workstations:

The Launcher must be installed on the user’s workstation first (see Installing the FirstSpirit Launcher).

When using the externalLauncherGroup parameter:

If you use the externalLauncherGroup setting, the following message appears in the log when the FirstSpirit Server is started:

WARN(...): External launcher groups are configured. 
This is deprecated since the launcher is always active for all users (...)

Aside from this warning, however, the configuration does not have any negative consequences. The fs-server.conf should be amended promptly anyway and the parameter removed from the configuration.

Overview: Process of ramp-down phase for Java Web Start in FirstSpirit

• Release Notes 2019-10: Discontinuation of the use of Java Web Start for starting and rolling out FirstSpirit desktop applications.
• Release Notes 2020-06: Discontinuation of support for the use of Java Web Start for starting and rolling out FirstSpirit desktop applications. However, the applications can still be started via Java Web Start.
• Release Notes 2021-02: As of FirstSpirit 2021-02, it is no longer possible for editors to select Java Web Start for starting and rolling out FirstSpirit desktop applications.

As of the current release, the following internally used software has been updated:

• Java The following new Java version is available:
  • Integrated in FirstSpirit (default): 11.0.10+9 64bit AdoptOpenJDK
  • In the FirstSpirit Launcher JRE module: 15.0.2+7 64bit AdoptOpenJDK

As planned, the current FirstSpirit release does not include the control files fs5 and fs5.cmd (see “Discontinuations”). The control files have been replaced by the new, improved control files fs-server for Linux and fs-server.bat for Windows operating systems, which were released as of FirstSpirit 2020-08 and are recommended for production environments.

e-Spirit recommends upgrading existing installations that still use the old control files to the new control files as soon as possible.

Provision and requirements for the use of the new control files: Java and the Java Service Wrapper are required to operate a FirstSpirit Server. The Java Service Wrapper and corresponding control files are provided by e-Spirit via:

• The installation archive (for new installations) or
• The update archive (for existing installations)

Both archives are available for download (please contact Technical Support for login details).

To use the new control files, the Tanuki Java Service Wrapper must be updated to version 3.5.42 or higher. The latest Wrapper version is included in the installation and update archive.

To perform a new installation, follow the instructions in Installing via install archive.

To update an existing installation. follow the instructions in Updating the FirstSpirit backend.

The FirstSpirit Server can then be started via the new control files fs-server (for Linux) or fs-server.bat (for Windows).

For more information about the scope of functions and control, see:

• Controlling the FirstSpirit Server (Unix)
• Controlling the FirstSpirit Server (Windows)

The current release has extended the output options for snippets relating to the #now object.

#now provides the current date at the point when the request is made.
This means it is possible to check whether the date in the CMS_INPUT_DATE input component is in the future, for example, so that a label indicating this can be added to the snippet.