Release Notes

Project administrators are permitted to create, edit, and delete (internal) groups by default (e.g., via “FirstSpirit ServerManager” / “Project Properties” / “Groups”).

With the latest release, this permission can be deactivated by setting the

localGroupManagementDisabled

parameter in the fs-server.conf file accordingly.

To withdraw permission to create, edit, and delete groups from project administrators, the parameter must be set to true:

localGroupManagementDisabled=true

With this setting, only server administrators are permitted to modify groups.
The corresponding context menu under “Groups” is grayed out for project administrators and a java.lang.SecurityException is recorded in the log.

External groups are not affected by this restriction and can continue to be modified by project administrators even if the parameter is set to true.

Some input components support the InEdit functionality. This function enables modifications to content without having to open a form beforehand. A pencil symbol on the mouse pointer shows the editor whether the corresponding value can be edited via InEdit. The editor can start InEdit mode simply by clicking at the desired spot in the preview (using Ctrl + CLICK ).

In the latest release, clicking on the “Edit” icon again opens the entire form.

This provides a convenient way of updating content from adjacent input components as well as content in other languages.
Previously, only the individual input components were displayed in the dialog that opened.

Specifically in projects with lots of different languages, editors can now set the priority languages for displaying content.
The configuration setting is made using the “Visible languages” menu item in the “three-point” menu:

Selecting content language(s)

By default, content is displayed in all available project languages.
Languages that are less relevant for the user can be deactivated via the menu: Content in the activated language(s) can be selected directly via the menu and deactivated language(s) can be accessed via the “More languages” dropdown submenu.

The selection of visible project languages is applied in various places:

Forms

Language selection in forms

Navigation bar

Language selection in the navigation bar

Creating, editing, and downloading (language-dependent) media

In the case of media, the language selection menu is displayed for the following functions if the “Language-dependent” box is checked:

• Upload new medium (menu bar):

Language selection when uploading language-dependent media

• Edit medium

The language selection menu is displayed for the following functions if the medium is language-dependent. Only those languages for which a language variant is available are listed for selection:

• Edit image section

• Download medium

For more detailed information, see https://docs.e-spirit.com/contentcreator/menu-functions/further-functio/index.html.

The settings made via the “Visible languages” menu item are saved to the corresponding server for all projects associated with the relevant user.

The available configuration settings are determined by the “Languages can be hidden” setting in FirstSpirit ServerManager in the properties of the corresponding project (under “Options”):

Activating the configuration

To display the “Language” menu item in ContentCreator and thus use the new functionality, this box must be checked.
Notice: The setting made here is also applied in FirstSpirit SiteArchitect.

In forms with multiple tabs (CMS_GROUP), only the selected tabs are synchronized when the language is changed:

Changing languages in forms with multiple tabs

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

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

In the FS_INDEX component, media can be referenced using the media data access plug-in (“Media DAP”) and page references can be referenced using the PageRef access plug-in (“PageRef DAP”).

With the latest release, the JSON information for the media or page references referenced in the FS_INDEX component can be included in the output. This can be activated via the new

jsonSupporting

attribute in the SOURCE tag of the FS_INDEX component by setting the value to yes.
Example:

...
<SOURCE name="FirstSpiritMediaAccess/Connector" jsonSupporting="yes">
    <PROJECT remote="remote"/>
</SOURCE>
...

This attribute is only available when using the “FirstSpiritMediaAccess/Connector” and “FirstSpiritPageRefAccess/PageRefConnector” DataAccessPlugin components.

By default, the JSON information for the referenced media or page references is not included in the output (corresponds to jsonSupporting="no").

For more information about JSON output of media, see also https://docs.e-spirit.com/odfs/enhanced-json-s/json-ausgabe-me/index.html.

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

The FirstSpirit Access API has been extended to include the following classes for responding to various events in the case of changes:

de.espirit.firstspirit.agency.IDProviderEventAgent;
de.espirit.firstspirit.event.RevisionEvent;
de.espirit.firstspirit.event.EventInfo;
de.espirit.firstspirit.event.EntityInfo;
de.espirit.firstspirit.event.DatasetChange;
de.espirit.firstspirit.event.IDProviderChange;

The

redirectTemplateLogToDefaultLog()

method in the RenderingAgent.Renderer interface (de.espirit.firstspirit.agency package, FirstSpirit Developer API) is now activated by default, so corresponding log data are output automatically in the standard log. This makes it easier to analyze problems.

In this context, the actual method has been marked as deprecated and may be omitted from a future release of FirstSpirit.
Therefore, it should be removed from scripts in which it is used.

The standard protocol when using an encrypted connection to the SMTP server has been changed to TLS 1.2.

If a different protocol is required, this can continue to be defined using the javamail.mail.smtp.ssl.protocols parameter in fs-server.conf.

In the event of problems with the recommended encryption, the following entry would be necessary to revert to the previous default value:

javamail.mail.smtp.ssl.protocols=TLSv1.0

Notice: The TLS protocols V1.0 and V1.1 are outdated and not secure. They should undergo a thorough assessment from the point of view of security prior to an activation.

With the new release, it is possible to call up the “Copy GID” function via the context menu of a dataset. This function writes the GID of the current dataset to the buffer.

This function can only be called up for a dataset which has a GID. If the dataset is new and has not previously been saved, for example, this menu option will be deactivated.

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

• Java (JRE with which the FirstSpirit Launcher is operated)
  The following new Java version is available:
  • New: Integrated in FirstSpirit (default): 11.0.11+9 64bit AdoptOpenJDK
  • New: In the FirstSpirit Launcher JRE module: 16.0.1+9 64bit AdoptOpenJDK
• Java Mail Library (for mail delivery)
  Update from Java Mail 1.4.4 to Jakarta Mail 1.6.6
• Eclipse Jetty (contained in the module fs-jetty.fsm / “FirstSpirit Jetty Service”)
  Update from version 9.4.33 to version 9.4.39