Release Notes

If a medium is created language-dependently, the image files and files of other media formats must be provided for every existing language. Categorically, the medium will otherwise not be output and/or the medium is linked to an URL that does not exist.

With the latest release, it is now possible to define that for the language, for which a file has not been stored, the file of the master language will be used.
For this, select the option “Use master language” (FirstSpirit ServerManager/Project Properties/Substitutions, “Language substitution (media”)):

If the option “Ignore” is selected (this is the default setting), nothing is displayed for the language of the medium for which no file is stored.

Note: a medium will also not be displayed in the following cases:

• No file is stored in the master language for a language-dependent medium.
• No file is stored for a language-independent medium.
• No file is stored for a language that is not equal to the master language for a language-dependent medium and for “Language substitution (media)”, the option “Use master language” is not activated.

One of the following FirstSpirit releases will provide a corresponding solution for these cases.

In the context of this new functionality, the FirstSpirit Access API was also expanded to be able to respond to this project setting: Package de.espirit.firstspirit.access.project, Interface Project.

In the “Health Center” (FirstSpirit ServerMonitoring), the current state of health of the FirstSpirit server can be read out. For example, the degraded state (symbol: exclamation mark on red background) can indicate that there are problems concerning the available memory or an excessive load on the server.
However, web applications that are included with FirstSpirit as standard that were not correctly rolled out at the FirstSpirit start (“deployed”) will also cause the degraded state.
More detailed information is provided in the server-incidents.log file (downloadable in FirstSpirit ServerMonitoring under “FirstSpirit / Monitoring / Codes” via the envelope icon; “Server status is degraded!” message). Here, causes that lead to or have led to the problematic state can be read out.
If the server is in the degraded state, suitable measures must be taken to remedy the problems.

A FirstSpirit Server is now also viewed as degraded when an aggregating web server is used and a web application cannot be rolled out successfully on all web servers of the aggregating web server.
Message in the server-incidents.log file:

Web server errors detected: #

whereby # is the number of the corresponding warnings.

The message

Some core web applications are not running: ...

indicates that at least one web application could not be rolled out and which one.

In rare cases, no explicit error message was displayed when a web application or a web component could not be rolled out on a web server. This error has also been rectified now.

The MBean HealthManager was enhanced with two additional pieces of information:

• LastWebServerError
• WebServerErrorsPerDay

Messages pertaining to the Health state are now also included in the fs-server.log file. They are output via the de.espirit.firstspirit.server.HealthStatus class. Corresponding messages can thereby also be found later on. Example:

INFO  19.01.2022 14:14:47.570 (de.espirit.firstspirit.server.HealthStatus): 
   RUN_LEVEL (de.espirit.firstspirit.server.RunLevelHolder) Reached run level:
   STARTED(100)

Note: in some cases, messages will be output twice now.

In the context of the Health state, a few threshold values from which a FirstSpirit Server under a high load is considered to be degraded have also been raised, based on experience gained so far.

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

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

The ModuleAdminAgent.getProjectAppConfig() method (FirstSpirit Developer API, package de.espirit.firstspirit.agency) – as described in the API documentation – returns an IllegalArgumentException already since FirstSpirit 2022.1, if the project component is not added / installed in the project concerned.

Note: This only applies to servers running in “Isolated mode”. For servers still running in the deprecated “Legacy mode”, it was always the IllegalArgumentException that was returned.

FirstSpirit input components can be adapted by project developers extremely flexibly and fine-tuned to the requirements of the respective project and editors.
For example, the FS_CATALOG input component allows the convenient creation of lists that can consist of sections or links.
The central function is thereby the creation of new entries.
This function can be managed using a specific rule definition, namely via the NEW property.
In the past, this property was also the basis for the “Duplicate” function, which can be executed in the FirstSpirit ContentCreator in the form via icon:

in the FirstSpirit SiteArchitect via context menu:

Until now, the functions “New”and “Duplicate” could only be activated or deactivated together.
With the latest release the functions “New” and “Duplicate” can now be controlled separately using the new property COPY:

PROPERTY name="COPY"

For reasons of compatibility, COPY takes the status of NEW into account unless there is an explicit definition for COPY.
To make “Duplicate” possible, but not “New”, COPY must be activated explicitly, NEW must be deactivated, e.g.:

<RULES>
    <RULE>
        <WITH>
            <TRUE/>
        </WITH>
        <DO>
            <PROPERTY name="COPY" source="catalog"/>
            <NOT>
                <PROPERTY name="NEW" source="catalog"/>
            </NOT>
        </DO>
    </RULE>
</RULES>

Note: the icons in the preview (EasyEdit icons) cannot be influenced with rules. The Tailored UI functionality can be used to categorically prohibit the duplication in the preview.

For more information, see:

• FS_CATALOG: https://docs.e-spirit.com/odfs/template-develo/forms/input-component/catalog/index.html
• COPY property: https://docs.e-spirit.com/odfs/template-develo/rules/form-properties/property-cop/index.html
• Tailored UI: https://docs.e-spirit.com/odfs/template-develo/contentcreator/customization/standard-functi/index.html

Unresolvable references during the JSON generation now lead to WARN level log messages.

For example, this is the case when a linked medium cannot be accessed in the release state because it was never released or the parent chain of the medium contains a folder that was never released.

Example:

WARN  24.01.2022 14:26:24.248{g-node=850537} (de.espirit.firstspirit.generate.
   SiteProduction): Reference 'xyz' [type=MEDIASTORE_LEAF] is set but not accessible! 
   It may have been deleted or is not correctly released.