Release Notes

As of the current release, the following internally used software for FirstSpirit Content Experience Tools (CXT) has been updated:

• Spring Boot
  Update to version 2.5.12

Information concerning some statistics that could be downloaded individually as CVS files in the FirstSpirit ServerMonitoring can now be downloaded conveniently at the same time in a ZIP file that contains the CSV files.

FirstSpirit ServerMonitoring:

• Overview/Activities
• FirstSpirit/Monitoring/Codes

If there are crops for an image and if the original image is replaced later, the details have remained unchanged in the past. The completed crops could potentially no longer match the new image and should therefore be checked and adjusted as needed.

With the most recent release, the editor can now choose in the “Edit” dialog in the FirstSpirit ContentCreator how to proceed in this case with existing crops.

• Reset crop selections
  Existing image crops are removed and must be created new. This option is initially selected.
• Do not change cropped resolutions
  Existing image crops are kept. They may potentially no longer match the original image. This is the current standard behavior.
• Renew crop selections, if possible
  Image crops are recalculated and applied. For example, this is practical when the motive and size of the original image remained unchanged.

In the crop dialog of the FirstSpirit ContentCreator, a corresponding note is now displayed when crops exist and the original image was replaced:

Some resolutions have a deprecated crop selection!

In the FS_CATALOG input component (“Catalog List”), lists of sections or links can be created and maintained.

If such component in turn contains an FS_CATALOG, the order of the internal elements could previously only be changed in the form itself with drag-and-drop.

With the most recent release, the order can now also be changed directly in the preview with drag-and-drop:

The most recent release includes some minor optimizations concerning the design and user guidance (UI and UX) in the FirstSpirit ContentCreator:

• After creating a new medium or dataset, it will now be selected accordingly and can therefore be found better.
• When saving changes for media elements, an indicator now shows the loading process.
• The standard size of forms has been marginally increased.
• The scaling of the font size now also affects the Rich-Text Editor.
• The display of thumbnails in the reports has been improved with an additional space.
• A security questions is now displayed when deleting entries of an FS_CATALOG component in the preview (“Do you really want to delete the element ...?”).
• The display of tasks now also shows the comments since the last non-automatic transition.
• Element Status entries are now visualized with the ! Icon (instead of the previous Edit icon) in case of validation problems:

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

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

The registration of MicroApps can take some time, especially in the case of the restart of a FirstSpirit-Server or the Tomcat web server.
In the past, an error message was displayed while starting the FragmentCreator after a timeout of 5 minutes.

x MicroApps could not be registered in a reasonable amount of time.

when the existing MicroApps could not be registered during this time and the FragmentCreator was not started.

With the most recent release, the default value for the timeout was increased to 10 minutes.
If necessary, you can now also adjust it individually for the requirements of your installation by using the new parameter

cxt.fragmentcreator.microAppRegistration.timeoutInMinutes

in the properties file cxt-fragment-creator.properties.

Excerpt from the properties file:

<context-param>
   		<param-name>cxt.fragmentcreator.microAppRegistration.timeoutInMinutes</param-name>
   		<param-value>10</param-value>
	</context-param>

For more information about cxt-fragment-creator.properties, see https://docs.e-spirit.com/odfs/edocs/cxt/installation-mo/installing-modu/fragmentcreator/index.html#web_xml.

During an upload to FirstSpirit, images are initially stored in the project without changes concerning the format and resolution (resolution “Original”). However, for certain actions (based on the original image data), new image files are automatically generated by FirstSpirit, for example:

• when generating a preview image
• when generating new resolutions
• when using an automatically generated resolution
• in case of an image crop (in the FirstSpirit ContentCreator or SiteArchitect)

ImageWriteParams

(FirstSpirit Access API, package de.espirit.firstspirit.access.project, interface Project, Method setCustomProperties). For example, you can configure the compression rate of images to generate a better image quality or smaller file size.

With the most recent release, it is now also possible to specify the image format of automatically generated images (targetType).

Example script, which was used to generate all automatically generated image files in the WebP format:

project = context.getProject();
project.lock();
properties = new java.util.LinkedHashMap();
properties.put("default.targetType", "webp");
project.setCustomProperties("ImageWriteParam", properties);
project.save();
project.unlock(); 

This script must be executed once with Administrator permissions in the project.

The change applies to all images that are automatically generated after executing the script.
For instructions on how you can remove already calculated resolutions from the project, please contact e-Spirit Technical Support.

Important: ImageWriteParams, that are already configured for the respective project must also be included in the script because they will otherwise be overwritten.
Find out if and what parameters are already configured via

context.project.getCustomProperties("ImageWriteParam");

In addition, you can define definitions for individual image formats and/or resolutions.
The setting for the currently specified image type will thereby be used. If it does not exist, the global setting will be used for the resolution as a fallback.

Example script, that maintains the type for PNG images, for the “Icon” resolution uses the JPG type and applies the WebP type for all other scalable images:

project = context.getProject();
project.lock();
properties = new java.util.LinkedHashMap();
properties.put("default.targetType", "webp");
properties.put("default.png.targetType", "png");
properties.put("resolution.Icon.targetType", "jpg");
project.setCustomProperties("ImageWriteParam", properties);
project.save();
project.unlock(); 

If images that are generated by the font(...) function must be output in the WebP format, the filetyp to be transferred must be webp.

For more information, see:

• ImageWriteParam: https://docs.e-spirit.com/odfs/template-develo/template-syntax/functions/instructions/ref/index.html#hinweis_zu_automatisch_erzeugten_bilddateien
• font(...) function: https://docs.e-spirit.com/odfs/template-develo/template-syntax/functions/instructions/font/index.html#filetype