Release Notes

In FirstSpirit, you can use elements repeatedly, e.g., images, sections, pages, datasets, etc. This means that these contents can appear in multiple places of the site. This is also referred to as “Usages” or “References”.
When an element is changed in one place, these changes can also affect other pages. For example, if you cut an image in the Media Store or directly on a page, the image will also appear on other pages in the modified format.
There are now additional functions to better be able to evaluate and check if, where and how the changes you made to elements have an impact:

Report “References”

The “References” report lists dependent elements.
By default (when the report is opened via the icon in the Report bar), the list refers to the actual preview element, which means generally to the current preview page.

A distinction is made for references between

• Incoming references:
  Here, all elements that reference the current element are shown.
  Example: pages that contain a link to the current page.
• Outgoing references:
  Here, all elements that are used by the selected element are shown.
  Example: media or datasets that are included on the current page (e.g. per FS_REFERENCE or FS_DATASET).

The entry below the report heading shows the element to which the report refers.

If you are in the preview, the report always refers to the current page.
If you change to another page via Preview or Navigation bar, the references of the selected page are shown.
You can fix the current element by clicking on the icon

Click on the text with the blue background to return to this fixed element at any time.

Clicking on the icon

Will release the fixation and the references are displayed again in the preview.

Note: The display of references can also contain elements from other projects, or elements for which there is no display option in the current ContentCreator session. Such references are shown in the report; however, further interaction is not possible.

For elements such as sections, media and datasets, the respective references can be displayed via the icon

• EasyEdit bar
  
  
  

• Navigation bar
  
  
  

• Media management and Data sources
  
  
  

• Editing dialogs
  
  
  

For more information, see also https://docs.e-spirit.com/contentcreator/report-area/references/index.html.

Report “Related objects”
The “References” report replaces the previous “Related objects” report and takes on its functions:

• “Inbound links”:
  pages that contain a reference to the current page.
  Now located on the “Inbound” tab.
• “Outbound links”:
  elements that are used by the current element.
  Now located on the “Outbound” tab.
• “Neighborhood”:
  these are pages that are below the same menu item, such as the current page, but that do not have their own menu item.
  They are no longer displayed in the report but are shown in the Navigation view:

The user guidance when uploading media via the input element “Reference selection” (FS_REFERENCE) and “Reference sensitive graphic” (CMS_INPUT_IMAGEMAP) has been improved (Parameter upload):
If the upload was not limited to a specific folder with the uploadFolder parameter, only those folders are now offered from which a selection is actually permitted, including their subfolders.

Example

<FS_REFERENCE name="st_picture" hFill="yes" imagePreview="yes" upload="yes" 
           useLanguages="yes">
  <FILTER>
    <ALLOW type="picture"/>
    <HIDE type="file"/>
  </FILTER>
  <LANGINFOS>
    <LANGINFO lang="*" label="Picture" description="Choose the desired picture."/>
    <LANGINFO lang="DE" label="Bild" description="Wählen Sie das gewünschte Bild aus."/>
  </LANGINFOS>
  <PROJECTS>
    <LOCAL name=".">
      <SOURCES>
        <FOLDER name="aboutus" store="mediastore"/>
      </SOURCES>
    </LOCAL>
    <REMOTE name="remote">
      <SOURCES>
        <FOLDER name="homepage" store="mediastore"/>
      </SOURCES>
    </REMOTE>
  </PROJECTS>
</FS_REFERENCE>

This input component enables an upload to the aboutus folder of the local project, the homepage folder of the remote project and subfolder:

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

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

With the latest release, e-mails can now also be sent via API to visible and invisible copy recipients (cc / “Carbon copy” and bcc / “Blind carbon copy” / “Blind copy”).

The class MailHeader.Builder (package de.espirit.firstspirit.access, FirstSpirit Access API) has been expanded with the methods

ccRecipient
bccRecipient

Example:

import de.espirit.firstspirit.access.MailHeader;
import de.espirit.firstspirit.access.MailService;
  
mailHeaderBuilder = MailHeader.getBuilder();
mailHeaderBuilder.bccRecipient("<mailadress1>;<mailadress2>");
mailHeaderBuilder.ccRecipient("<mailadress1>;<mailadress2>");
mailHeaderBuilder.recipient("<mailadress1>;<mailadress2>");
mailHeaderBuilder.sender("<senderMailadressFromServer>");
mailHeader = mailHeaderBuilder.create();
attachment = null;
service = context.getConnection().getService(MailService.class);
service.sendMail(mailHeader, "<Subject>", "<Mailbody>", attachment);

A security gap was closed that allowed users to adjust the workflow permissions via FirstSpirit API in spite of insufficient permissions.

This affects the StoreElement interface, de.espirit.firstspirit.access.store package (FirstSpirit Access API):

When using the Setter methods and some modifying Getter methods, e.g.

• setWorkflowPermission
• setWorkflowPermissions
• setInheritWorkflowPermission
• getCreateWorkflowPermission

a check now determines if the executing user has the permission to change workflow permissions (CAN_CHANGE_PERMISSION, permission 128).

If the user does not have the respective permission, the method is not executed and a corresponding exception is logged, e.g.

...
Target exception: de.espirit.firstspirit.access.AccessSecurityException: Access 
   denied to StoreElement 'xyz' with permission 128! 
   (de.espirit.firstspirit.store.access.sitestore.PageRefFolderImpl, id=1600310)
...

Previously, the methods were also executed without sufficient permissions.
Existing customer solutions that use these methods must be checked for functionality and, if necessary, the required permissions must be assigned to the executing user.