Release Notes

When importing projects, the default setting was so far to keep the export file on the server. Deleting it needed to be done either manually or actively set for an automatic deletion.

Now, the option to automatically delete the export file after the import completion is active by default. This results in the disk space to be available immediately after the import is completed.

The web compatibility module (fs-web-compatibility.fsm) ensures the operation of existing web applications requiring the presence of external classes in fs-webrt.jar in the process of moving to an isolated server. Additionally, the module contains dependencies which are no longer available in fs-isolated-webrt.jar.

Currently, the module is used only extremely rarely and has been updated only in exceptional cases lately, as announced.

The module will no longer be distributed starting with the current FirstSpirit version.

More information: Modules: Ensuring compatibility (→Isolated Mode Guide), “Modules with WebApp Components” chapter.

Structure variables can now be edited inside ContentCreator.

Editing structure variables

From within the context menu of SiteStore folder navigation, it is now possible to edit structure variables:

The pop-up dialog lists all variables that have been defined for the current folder:

• New variables are marked with a “+” icon
• Inherited variables are displayed in gray
• Inherited but changed variables are marked with a “pencil” icon
• The “Defined for” column indicates name of the folder for which the displayed value of the variable is defined
• If the variable does not have the same value for all languages, it is marked with a respective icon

Actions

The entered values can be changed for new variables. Click the “trash bin” icon to delete the variable.

The original values can be changed for inherited variables.

Note: Inherited values are not checked for their validity.

The values received from inherited variables that have already been changed, can also be changed. Click the “X” icon to reset any changes to inherited values: The variable will be restored in its original state.

Editing a variable

When editing a variable, a pop-up dialog is displayed:

To change a structure variable's value (a page reference or a media reference), enter the exact value of the variable into the “Value” field. Alternatively, you can search and select a value in the search field. The variable's name will be filled-in automatically.

“Accept for all languages”: The variable's value will be applied to all languages. The option is active by default if the variable's value is already identical in all languages.

Creating a variable

When creating a variable, a pop-up dialog is displayed:

To create a structure variable you need to specify its name and value.

“Accept for all languages”: The variable's value will be applied to all languages.

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

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

Compatibility: The new version of fs-cli is still compatible with older versions of FirstSpirit (up to 2023.3).

The change recently announced with FirstSpirit version 2023.3 to improve the processing of incorrectly configured SVG image files (CORE-15042) will not be available in the next FirstSpirit version 2023.4. In a later FirstSpirit version this change will be restored.

Unfortunately, we have identified that the implementation of this change may lead to some unexpected problems. Therefore, we have temporarily deactivated this change and point out that uploading and using SVG files with unsupported configurations in version 2023.4 could again lead to a misbehaviour.

With the current FirstSpirit version, enhancements were made to the identification of recursions in JSON output via the inline JSON function which lead to a change in behavior.

The JSON function can be called up multiple times recursively during the rendering process. When paragraphs and data records were called up recursively, this could lead either to missing output or to a FirstSpirit server's OutOfMemoryException – depending on the FirstSpirit server's configuration.

The identification of recursions during a JSON function's call up has been improved. If a reference is detected, the reference to the paragraph or data record is output as a placeholder and the recursion is cancelled for that place.

• So far, the data record was output despite the dataRenderDepth=0 parameter.
• Now, only the reference to the data record is output for the place.

If dataRenderDepth=1 (default value) is specified, the behavior remains unchanged. The data record is output, connected data records are output as references.

For more information, see Enhanced JSON support / Configuration (→FirstSpirit Online Documentation), chapter “Configuration”.

If no page template was defined in a project for the project settings page, then no output was generated when outputting the project settings via the json function.

With the current FirstSpirit release a JSON object is always generated when the project settings page is output. If no page template has been defined, the attribute "template" has the value "null".