ContentConnect for Spryker Commerce OS

New features

Highlights

Components
This release contains the following components and Spryker modules.
Versions marked with an arrow (⬆) changed since the last release.

General information
For the full range of functions the ContentConnect for Spryker Commerce OS integration requires the following modules to be installed on the FirstSpirit server:

For this release the operation of the following versions is recommended:

Deprecations
The support for the following functions is deprecated:

Fixed issues

New features

Highlights

Components
This release contains the following components and Spryker modules.
Versions marked with an arrow (⬆) changed since the last release.

General information
For the full range of functions the ContentConnect for Spryker Commerce OS integration requires the following modules to be installed on the FirstSpirit server:

For this release the operation of the following versions is recommended:

Deprecations
The support for the following functions is deprecated:

New features

Highlights

Components
This release contains the following components and Spryker modules.
Versions marked with an arrow (⬆) changed since the last release.

General information
For the full range of functions the ContentConnect for Spryker Commerce OS integration requires the following modules to be installed on the FirstSpirit server:

For this release the operation of the following versions is recommended:

Deprecations
The support for the following functions is deprecated:

SPRY-175 - Content Management of Product Detail Pages
From this version on, it is possible to create and manage content on product detail pages. Turn your product information into a product presentation and enrich your product presentation with interactive videos, case studies and instructions. Increase your sales with product descriptions that inspire and capture your customer’s imagination. Almost all content modules from the reference project can be used on product pages, so that you can give your marketing strategy full scope.

Update Notice

SPRY-175 - Content Management of Product Detail Pages
The necessary steps to activate the feature product detail pages are documented in chapter 2.1. ff.

SPRY-97 - Banner Carousel component
In Spryker the module firstspirit-reference-components must be updated.
In the FirstSpirit project an update of the section templates banner_section and carousel_section is required. The section template carousel_item must be removed.
The following link displays all of these changes:
ecom-spryker-reference-project @ GitHub

Fixed issues

New features

Highlights

Components
This release contains the following components and Spryker modules.
Versions marked with an arrow (⬆) changed since the last release.

General information
For the full range of functions the ContentConnect for Spryker Commerce OS integration requires the following modules to be installed on the FirstSpirit server:

This release was tested with the following versions:

Deprecations
The support for the following functions is deprecated:

Update Notice

SPRY-513 - Navigation can’t be released
Explicit permissions in the global content area were missing. In order to determine the right to edit navigation_extensions, the script 'create_navigation_extension' now has a new dryRun parameter. Furthermore, both for the workflow transitions and the Navigation Extensions folder within the Global Content area rights must be defined.

Fixed issues

New features

Fixed issues

Highlights

SPRY-439 - Teaser Grid component
With this release the look and feel of the teaser grid component has been improved. Now, editors have much more control over the design of any teaser grid and get a completely new user experience.

Update Notice

Components
This release contains the following components and Spryker modules.
Versions marked with an arrow (⬆) changed since the last release.

General information
This release was tested with the following versions:

Deprecations

SPRY-511 - polymorphism issues in UserAwareProcessor
This fix requires an update of the firstspirit-data-rest-api module at the spryker side.

SPRY-506 - Console warnings for fs-spryker-content-editing via unpkg CDN
This fix requires an update on the Spryker side in the firstspirit-preview module. The changes in CSS and JavaScript are automatically loaded from unpg.

SPRY-439 - Teaser Grid component
In Spryker the modules firstspirit-reference-components and firstspirit-preview must be updated.
In the FirstSpirit project an update of the section templates teaser_grid and teaser_item is required. The section template teaser_grid_two_columns must be removed.
The following link displays all of these changes:
ecom-spryker-reference-project @ GitHub

Fixed issues

New features

Update Notice

SPRY-489 - Missing dependencies in firstspirit/firstspirit-data-inconsistency-check
We have added dependencies to all sprkyer modules to clearify their direct dependencies.

Module dependencies. 

"firstspirit/firstspirit-caas":
-  "spryker/log": "^3.0.0"

"firstspirit/firstspirit-cms-data-connector":
- "spryker/log": "^3.0.0"

"firstspirit/firstspirit-cms-data-storage":
- "spryker/locale": "^3.0.0"
- "spryker/log": "^3.0.0"

"firstspirit/firstspirit-data-cleanup":
- "propel/propel": "^2"
- "spryker/cms-page-search": "^2"
- "spryker/config": "^3.0.0"
- "spryker/event": "^2.1.0"
- "spryker/log": "^3.0.0"
- "spryker/navigation": "^2"

"firstspirit/firstspirit-data-import":
- "firstspirit/firstspirit-preview": "^1.0.0"
- "spryker/category": "^4.0.0"
- "spryker/cms": "^7.5.0"
- "spryker/cms-block-category-connector": "^2"
- "spryker/cms-block-product-connector": "^1.1.0"
- "spryker/cms-block-storage": "^1.2.0"
- "spryker/cms-page-data-import": "^1.0.0"
- "spryker/locale": "^3.0.0"
- "spryker/url": "^3.0.0"

"firstspirit/firstspirit-data-inconsistency-check":
- "spryker/category": "^4.0.0"
- "spryker/product": "^6"
- "spryker/product-storage": "^1.2.0"

"firstspirit/firstspirit-data-rest-api"
- "spryker/log": "^3.0.0"
- "spryker/glue-application": "^1.21.0"
- "spryker/glue-application-extension": "^1.2"

"firstspirit/firstspirit-data-state-writer"
- "propel/propel": "^2"
- "spryker/cms-block": "^2.1.1"
- "spryker/log": "^3.0.0"
- "spryker/navigation": "^2"

"firstspirit/firstspirit-preview"
- "spryker/container": "^1.4.0"
- "spryker/log": "^3.0.0",
- "spryker/navigation": "^2"
- "spryker/navigation-storage": "^1.0.0"
- "spryker/product": "^6.0.0"
- "spryker/product-storage": "^1.0.0"
- "spryker/silex": "*"
- "spryker/util-text": "^1.2.0"
- "spryker-shop/cms-block-widget": "^1.1.0"
- "spryker-shop/shop-application": "^1.6.0"

Fixed issues

New features

Update Notice

SPRY-400 - Category Teaser for N-Up Teaser Component
This feature extends the N-Up Teaser component by creating a category teaser. For the new component the section template n_teaser_item_categroy_teaser must be added to the FirstSpirit project. This must also be permitted in the existing section template n_teaser. In addition, an update of the FirstSpiritReferenceComponents and the FirstSpiritPreview module is necessary.

New features

Highlights

SPRY-445 - Publish reference project to GitHub
Beginning with this release, the reference project will be made available at GitHub. In future, this will allow an easy update of the reference project templates.

SPRY-432 - New front end for the Shoppable Video YouTube player
With this release an updated default design for the content component "Shoppable Video" is delivered.

It is now possible to display products and Content Cards at any time in a YouTube video. Visitors to the website can switch between the individual cards, and the video jumps in parallel to the respective points linked to the content.

In addition, it is now possible to limit the search for videos to your own YouTube channels in order to present the editor with a more targeted selection of videos.

SPRY-413 - Identifie and delete orphaned category/product pages
It is now possible to identify content in FirstSpirit for which no equivalent exists in Spryker. This applies to category pages and product detail pages, where the corresponding categories and products have been deleted in Spryker. To use this function a report is provided, which can be activated from the right toolbar. This lists the "orphaned" pages in FirstSpirit and offers the option of deleting them. This eliminates the need to use the SiteArchitect for this action.

Update Notice

SPRY-432 - New front end for the Shoppable Video YouTube player
This ticket affects the section templates shoppable_video and shoppable_video_item as well as the Spryker molecule fs-shoppable-video.
The changes to the section templates must be copied from the current version of the reference project. The molecule requires an update of the Spryker module firstspirit-reference-components.

Furthermore, the extension of the compilerOptions and the installation of the YouTube Iframe is no longer necessary. They can be removed with the following command:

removal of the compilerOptions extension and the YouTube Iframe. 

npm uninstall youtube-iframe @types/youtube

SPRY-413 - Identifie and delete orphaned category/product pages
This feature requires that the new module "FirstSpiritDataInconsistyCheck" is added and the module "FirstSpiritDataRestApi" is updated. In addition the "FirstSpiritDataInconsistyCheck" module must be registered in the "GlueApplicationDependencyProvider" file. In addition, a new workflow has been added to the reference project. This new workflow "Direct delete" with the reference name "delete_bypass" is used to delete the orphaned pages and must therefore be added to the FirstSpirit project.

Extension of the GlueApplicationDependencyProvider file. 

[...]
              new FirstSpiritCmsPagesResourceRoutePlugin(),
              new FirstSpiritDataStateWriterResourceRoutePlugin(),
              new FirstSpiritDataInconsistencyCheckResourceRoutePlugin()
         ];
[...]

Fixed issues

New features

Highlights

SPRY-433 - Added YouTube integration for the Shoppable video
You can now add YouTube videos for your shoppable video directly from a search panel in FirstSpirit by dragging them from the search result list onto the video component. Videos can be searched across all of YouTube or individual channels.

SPRY-427 - Category Report - Remove duplicate Category Label
A change was made to the category search: In addition to the category name we are now displaying its hierarchy in order to better distinguish between categories of the same name and provide a better orientation.

SPRY-418 - Bubble up Importer Issues to the FirstSpirit log
With this release, warnings which occur when importing the content data to Spryker are also written to the FirstSpirit log. This enables the FirstSpirit team to identify and remove redundant content in FirstSpirit.

This is primarily related to warnings that occur when category and product pages are missing in Spryker.

The following warnings are logged:

Failed to create category connector for CMS block "%s" due to missing category with id "%s".

Failed to create product connector for CMS block "%s" due to missing product abstract with sku "%s".

SPRY-399 - Product Teaser for N-Up Teaser Component
A new content module has been added to the reference project, allowing an easy representation of products in the "N-Up Teaser". An editor can now add a product to the teaser list by simply dragging it from the product search onto the reference component in the product teaser section. The content will be filled automatically with information pulled from Spryker.

Update Notice

SPRY-442 - Easy-Up Demo: Images should be deployed
An schedule for the media generation must be added to the project. In addition, the publication schedule must receive the following script as the first action. Note that the value of the variable 'SCHEDULER_NAME' is to be defined as the name of the media generation job.

Script action in the Spryker Deployment task. 

import de.espirit.firstspirit.access.AdminService;
String SCHEDULER_NAME = "Media Deployment";
connection = context.getConnection();
adminService = connection.getService(AdminService.class);
scheduleStorage = adminService.getScheduleStorage();
scheduleEntry = scheduleStorage.getScheduleEntry(context.getProject(), SCHEDULER_NAME);

if(scheduleEntry != null) {
	control = scheduleEntry.execute();
	control.awaitTermination();
	isSuccessful = control.state.state.equals(en.espirit.firstspirit.access.schedule.RunState.SUCCESS);
	if(!isSuccessful){
		context.logWarning(SCHEDULER_NAME + " Completed with errors!");
	}
    context.logInfo("Schedule Entry executed...");

} else {
    context.logError("Could not find schedule entry with name" + SCHEDULER_NAME);
}

SPRY-433 - Added YouTube integration for the Shoppable video
The YouTube integration affects the section template shoppable_video. We recommend to copy the updated version provided with the reference project.

SPRY-431 - Shoppable Video - Remove Validators for Entries
This change can be applied by removing the rules from the "shoppable_video" template.

SPRY-418 - Bubble up Importer Issues to the FirstSpirit log
To use the changes, the following modules must be updated:

In addition, the FirstSpiritDataStateWriter module must be installed using the following command:

Installation command. 

composer require firstspirit/firstspirit-data-state-writer

A new table using the following Propel scheme has been added for data storage:

Schema of table fs_data_state_writer_storage. 

<database xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          name="zed" xsi:noNamespaceSchemaLocation="http://static.spryker.com/schema-01.xsd"
          namespace="Orm\Zed\FirstSpiritDataStateWriterStorage\Persistence"
          package="src.Orm.Zed.FirstSpiritDataStateWriterStorage.Persistence">

    <table name="fs_data_state_writer_storage" identifierQuoting="true">
        <column name="id_fs_data_state_writer_storage" type="BIGINT" autoIncrement="true" primaryKey="true"/>
        <column name="fs_schedule_id" type="VARCHAR" required="true"/>
        <column name="message" type="VARCHAR" required="true"/>
        <column name="severityLevel" type="INTEGER" required="true"/>
        <behavior name="timestampable"/>
        <id-method-parameter value="fs_data_state_writer_storage_pk_seq"/>
    </table>
</database>

Following the installation, the FirstSpiritDataStateWriterResourceRoutePlugin must be added to the GlueApplicationDependencyProvider:

Extension in the GlueApplicationDependencyProvider. 

[...]
           new FirstSpiritDataCleanupsResourceRoutePlugin(),
           new FirstSpiritCmsPagesResourceRoutePlugin(),
           new FirstSpiritDataStateWriterResourceRoutePlugin(),
         ];
     }
[...]

Furthermore, the following script action must be added within the schedules in the FirstSpirit project after the CleanUp action:

Trigger Fetch Spryker Logs. 

#!executable-class
com.espirit.ecom.contentconnect.spryker.module.trigger.triggerfetchlogs.TriggerFetchLogsExecutable

SPRY-399 - Product Teaser for N-Up Teaser Component
For the new component the section template n_teaser_item_product_teaser must be newly created in the FirstSpirit project. This must also be permitted in the existing section template n_teaser. In addition, an update of the 'FirstSpiritReferenceComponents' and the FirstSpiritPreview module is necessary.

SPRY-294 - Edit page added to drop-down menu
If a page has already been created in the Content Creator, it is possible to edit it. Therefore, the drop-down menu Actions at the top of the toolbar has a menu option Edit Page.

This allows you to edit either the url or the metadata.

Fixed issues

New features

Highlights

SPRY-408 - Spruce up FirstSpirit Publication and Deletion Mails
For the execution of publication workflows FirstSpirit will now send out information mails. These contain relevant information about the outcome of the publication with consolidated information from the logfiles. Editors are thus enabled to take appropriate steps if necessary.

The following cases are covered:

The cases marked with (*) will be removed in a future release, which means it will not be possible anymore to approve or delete a page in FirstSpirit only without publishing the change.

With this ticket we have removed the partial publication feature. It is now no longer possible to publish just a single page. Every publication will publish all approved content.

Update Notice

SPRY-408 - Spruce up FirstSpirit Publication and Deletion Mails
To be able to use the function of sending an e-mail when using workflows, the following steps must be performed:

The page template 'html_mail_template' from the reference project must be added to the customers FirstSpirit project in the template store under 'technical'.
The scripts "trigger_deployment" and "trigger_full_deployment" from the reference project were simplified.
These are to be filled as follows:

Content of the script "trigger_deployment. 

#!executable-class
com.espirit.ecom.contentconnect.spryker.module.workflow.ReleaseWorkflowExecutable

Content of the script "trigger_full_deployment. 

#!executable-class
com.espirit.ecom.contentconnect.spryker.module.workflow.DeleteWorkflowExecutable

SPRY-242 - Select text color for title and subtitle of the carousel element
In the section template of the list element 'Carousel element', it is possible to select a text color for the title and subtitle.

Therefore the form, the output channel and the fs-carousel.twig have to be adapted:

Modification in the form: 

[...]
<CMS_INPUT_TEXT name="st_title" hFill="..." [additional Options]>
[...]
</CMS_INPUT_TEXT>

 <CMS_INPUT_COMBOBOX name="st_titleColor" [additional Options]>
    <ENTRIES>
      <ENTRY value="#FFFFFF">
        <LANGINFOS>
          <LANGINFO lang="*" label="White"/>
          <LANGINFO lang="DE" label="Weiß"/>
        </LANGINFOS>
      </ENTRY>
      <ENTRY value="#D3D3D3">
        <LANGINFOS>
          <LANGINFO lang="*" label="Light Grey"/>
          <LANGINFO lang="DE" label="Hellgrau"/>
        </LANGINFOS>
      </ENTRY>
      <ENTRY value="#808080">
        <LANGINFOS>
          <LANGINFO lang="*" label="Dark Grey"/>
          <LANGINFO lang="DE" label="Dunkelgrau"/>
        </LANGINFOS>
      </ENTRY>
      <ENTRY value="#000000">
        <LANGINFOS>
          <LANGINFO lang="*" label="Black"/>
          <LANGINFO lang="DE" label="Schwarz"/>
        </LANGINFOS>
      </ENTRY>
    </ENTRIES>
    <LANGINFOS>
      <LANGINFO lang="*" label="Title color"/>
      <LANGINFO lang="DE" label="Farbe des Titels"/>
    </LANGINFOS>
  </CMS_INPUT_COMBOBOX>

<CMS_INPUT_TEXT name="st_subtitle" [additional Options]>
     [...]
  </CMS_INPUT_TEXT>

  <CMS_INPUT_COMBOBOX name="st_subtitleColor" [additional Options]>
    <ENTRIES>
      <ENTRY value="#FFFFFF">
        <LANGINFOS>
          <LANGINFO lang="*" label="White"/>
          <LANGINFO lang="DE" label="Weiß"/>
        </LANGINFOS>
      </ENTRY>
      <ENTRY value="#D3D3D3">
        <LANGINFOS>
          <LANGINFO lang="*" label="Light Grey"/>
          <LANGINFO lang="DE" label="Hellgrau"/>
        </LANGINFOS>
      </ENTRY>
      <ENTRY value="#808080">
        <LANGINFOS>
          <LANGINFO lang="*" label="Dark Grey"/>
          <LANGINFO lang="DE" label="Dunkelgrau"/>
        </LANGINFOS>
      </ENTRY>
      <ENTRY value="#000000">
        <LANGINFOS>
          <LANGINFO lang="*" label="Black"/>
          <LANGINFO lang="DE" label="Schwarz"/>
        </LANGINFOS>
      </ENTRY>
    </ENTRIES>
    <LANGINFOS>
      <LANGINFO lang="*" label="Subtitle color"/>
      <LANGINFO lang="DE" label="Farbe des Untertitels"/>
    </LANGINFOS>
  </CMS_INPUT_COMBOBOX>

Modification in the output channel: 

$CMS_SET(set_carouselItem,{:})$
set_carouselItem.put("title")$
$CMS_SET(void, set_carouselItem.put("titleColor", st_titleColor))$
$CMS_SET(void, set_carouselItem.put("subtitle")$
$CMS_SET(void, set_carouselItem.put("subtitleColor", st_subtitleColor))$
[...]

Modification in fs-carousel.twig. 

[...]
<div class="titles">
   <h2 class="title"{% if carousel_item.titleColor is defined and carousel_item.titleColor is not null %} style="color:{{ carousel_item.titleColor}}"{% endif %}>{{ carousel_item.title }}
   </h2>
   <h4 class="subtitle"{% if carousel_item.subtitleColor is defined and carousel_item.subtitleColor is not null %} style="color:{{ carousel_item.subtitleColor}}"{% endif %}>
                                            {{ carousel_item.subtitle }}
   </h4>
[...]
[...]

Fixed issues

New features

Highlights

SPRY-405 - Publication Error Handling
The mail notification in case of errors has been redesigned: In the event of a failed publication, a mail is now sent to a definable recipient. This mail contains the essential information from the publication schedule. So measures can either be taken directly or the Technical Support of the e-Spirit AG can be provided with the relevant information immediately.

SPRY-329 - Replacing content areas on the homepage
The Spryker Demo Content has been removed from the reference project and replaced with empty content slots.

SPRY-315 - Editing the Content Navigation
This release introduces a new feature for Spryker integration. It is now possible to integrate content structures created with FirstSpirit as navigation in the storefront.
To use this feature, the editor defines a start node from which the content hierarchy should be displayed. The underlying hierarchy is displayed in the navigation - changes made by creating, moving or deleting pages are directly visible in the navigation. This feature is implemented as an example for the main navigation in the reference project.

SPRY-209 - Multi slot container
With this release we are introducing a new Content Component for the reference project. The "Mult-Slot Container" enables the marketing division to create rows of image-based teasers. Images will scale automatically depending on the number of "slots" created by the editor. Each row can hold up to four slots.

Update Notice

SPRY-411 - Improvement of the data import
From this version on, the deletion of Spryker categories or products that are still referenced in the FirstSpirit project no longer influences the importer. It ignores the corresponding elements while it transfers the remaining data.
This improvement requires an update of the firstspirit-data-import module.

SPRY-405 - Publication Error Handling
In order to use the function of sending an e-mail in the case of an error in the schedule, the following steps must be carried out:

The page template html_mail_template from the reference project must be added to the FirstSpirit project in the template store under technical.
Afterwards, a script action with the following content must be added to the schedules Spryker Deployment and Spryker Partial Deployment:

#! executable-class
com.espirit.ecom.contentconnect.spryker.module.schedule.ReviewScheduleResultExecutable

In order to send the e-mail, it is also necessary to specify a technical user in the e-mail distribution list field in the properties of both schedules.

SPRY-397 - Authentication Persistence Loop (Chrome Cookie Problem)
To use the fix for the authentication problem, an update of the fs-preview-user-authentication.js file and the FirstSpiritPreview module is necessary.

SPRY-358 - Remove workaround for navigation release workflow button issue
This ticket requires an update of the ocm-content-editing folder and the FirstSpiritPreview module. In addition, the generate_page_preview_url script within the reference project must be adapted as follows:

Adaptation of the script generate_page_preview_url. 

[...]
if(pageRef == zero) {
    return zero;
}

if ("technical".equals(pageRef.parentFolder.uid) {
    // since OCM-388 / TPP 1.2.21 - Deep-Link support, a start page in FirstSpirit is mandatory
    // using the "technical"-folder as default
    return "";
}

page = pageRef.getPage();
[...]

SPRY-329 - Replacing content areas on the homepage
The existing content areas banner and content_top of the homepage template were replaced by five new content areas: The new content area stage replaces the former content area banner. The content area content_top was exchanged by the areas homepage_one to homepage_four.

These are also to be added in the project code of the Twig template home.twig:

Adjustment within the twig template home.twig. 

{% block container %}
    {{ fsSpyCmsBlock({ name: 'stage' }) }}

    <div class="container container--home-page">
        <main>
            {% block content %}
                {{ fsSpyCmsBlock({ name: 'homepage_one' }) }}

                {{ fsSpyCmsBlock({ name: 'homepage_two' }) }}

                {{ fsSpyCmsBlock({ name: 'homepage_three' }) }}

                {{ fsSpyCmsBlock({ name: 'homepage_four' }) }}
            {% endblock %}
        </main>
    </div>
{% endblock %}

SPRY-315 - Editing the Content Navigation
Up from this release, the integration provides the option of maintaining the navigations of the Spryker shop with FirstSpirit and adding further menu items. In order to use the feature, various requirements must be met and some manual changes are needed. These are explained below.

Technical requirements
The feature requires the installation of the following Spryker modules in at least the specified version:

Furthermore, the following templates of the reference project were either added or extended:

Installation and configuration
Besides the installation of the above mentioned Spryker modules the contents of the folder b2c-demo-shop/src/Pyz/Yves/NavigationWidget/ from the zip file b2c-demo-shop-extensions-<VERSION>.zip contained in the delivery must be transferred to the Spryker project.

Among other things, the zip file contains the ExtendedNavigationWidget, which must be registered within the ShopApplicationDependencyProvider. The chapter Widgets in the documentation contains the necessary information to do this.

In addition, the configuration of the parameters FIRSTSPIRIT_PREVIEW_CAAS_TECHNICAL_PAGE_COLLECTION and FIRSTSPIRIT_PREVIEW_CAAS_NAVIGATION_DOCUMENT is required. The parameters and their configuration are described in the chapter Extension of the configuration in the documentation.

Adaptations of Twig templates
In general, the new feature enables the maintenance of all navigations of a Spryker shop in FirstSpirit. Within the reference project this possibility was implemented as an example for the main navigation of the Spryker B2C Demo Shop - both in the desktop and mobile version. However, it requires the adaptation of the following Twig templates in the Spryker project:

The steps to be performed are described in the chapter Navigation in the documentation.

SPRY-209 - Multi slot container
This feature creates the possibility to display several elements in a row.
To do this the section templates n_teaser and n_teaser_item_content_teaser must be added to the FirstSpirit project and be permitted in the desired content areas.
The reference components fs-n-teaser and fs-n-teaser-item are part of the FirstSpiritReferenceComponents. Therefore an update of the module firstspirit-reference-components is also required.

Fixed issues

New features

Highlights

SPRY-240 Reference project: The input components for the magazine teaser have been rearranged to match the way in which they are rendered on the storefront: Image - Title - Subtitle

SPRY-193 - Fallback for the magazine overview page
If the teaser of a magazine article is empty, the image and title of the magazine article are used for the display on the magazine overview page. If the teaser has an image or title, the contents of the teaser are displayed on the overview page.

Update Notice

SPRY-193 - Fallback for the magazine overview page
The teaser output of a magazine article is defined within the template magazine_teaser_render. In order to add the described fallback functionality to the reference project, the second if query within the style sheet must be extended as follows:

CaaS output channel of the magazine_teaser_render template. 

$CMS_SET(picture,{:})$
$CMS_IF(!rt_entity.teaser_picture.isEmpty())$
	$CMS_SET(imageUrl)$$CMS_REF(rt_entity.teaser_picture,resolution:"CONTENT_IMAGE",abs:1)$$CMS_END_SET$
	$CMS_SET(void, picture.put("imageUrl", imageUrl.toString()))$
	$CMS_IF(!#global.isRelease())$
		$CMS_SET(previewId)$$CMS_VALUE(previewId(element:rt_entity.teaser_picture))$$CMS_END_SET$
		$CMS_SET(void, picture.put("previewId", previewId.toString()))$
	$CMS_END_IF$
$CMS_ELSIF(rt_entity.teaser_picture.isEmpty() && !rt_entity.banner.isEmpty())$
	$CMS_SET(imageUrl)$$CMS_REF(rt_entity.banner,resolution:"CONTENT_IMAGE",abs:1)$$CMS_END_SET$
	$CMS_SET(void, picture.put("imageUrl", imageUrl.toString()))$
	$CMS_IF(!#global.isRelease())$
		$CMS_SET(previewId)$$CMS_VALUE(previewId(element:rt_entity.banner))$$CMS_END_SET$
		$CMS_SET(void, picture.put("previewId", previewId.toString()))$
	$CMS_END_IF$
$CMS_END_IF$
$CMS_SET(void, rt_teaser.put("picture", picture))$

Fixed issues

New features

Fixed issues

New features

New features

Fixed issues

Update Notice

This update includes an improved error handling of errors occuring during CMS block rendering. The error handling can be configured with the parameter FirstSpiritPreviewConstants::FIRSTSPIRIT_PREVIEW_DISPLAY_BLOCK_RENDER_ERRORS. This parameter defines whether errors should be displayed on the page. As it shows internal information and is useful for debugging purposes, it should only be enabled in development or staging environments.

Extension of the configuration. 

use FirstSpirit\Shared\FirstSpiritPreview\FirstSpiritPreviewConstants;

[...]

$config[FirstSpiritPreviewConstants::FIRSTSPIRIT_PREVIEW_DISPLAY_BLOCK_RENDER_ERRORS] = true;

The class FirstSpiritMagazineLinkWidget was removed from the FirstSpiritPreview module in this release. When updating this module it is necessary to remove the corresponding widget registration from the ShopApplicationDependencyProvider in src → Pyz → Yves → ShopApplication.

Additionally with this release the Publish and Synchronize process for the content pages managed by FirstSpirit has been added. The activation of this process requires the additional registration of two queues and a message processor.

Extension of the SprykerRabbitMqConfig (\Pyz\Client\RabbitMq\RabbitMqConfig). 

use FirstSpirit\Shared\FirstSpiritCmsDataStorage\FirstSpiritCmsDataStorageConstants;

[...]

class RabbitMqConfig extends SprykerRabbitMqConfig
{
   protected function getQueueOptions()
   {
      $queueOptionCollection = new ArrayObject();

      [...]

      $queueOptionCollection->append($this->createQueueOption(
         FirstSpiritCmsDataStorageConstants::FS_CMS_PAGE_DATA_SYNC_STORAGE_QUEUE,
         FirstSpiritCmsDataStorageConstants::FS_CMS_PAGE_DATA_SYNC_STORAGE_ERROR_QUEUE));

      [...]

      return $queueOptionCollection;
   }
}

Extension of the QueueDependencyProviders (\Pyz\Zed\Queue\QueueDependencyProvider). 

use FirstSpirit\Shared\FirstSpiritCmsDataStorage\FirstSpiritCmsDataStorageConstants;

[...]

protected function getProcessorMessagePlugins(Container $container)
{
   return [
      [...]
      FirstSpiritCmsDataStorageConstants::FS_CMS_PAGE_DATA_SYNC_STORAGE_QUEUE =>
         new SynchronizationStorageQueueMessageProcessorPlugin(),
      [...]
   ];
}

Furthermore the CmsBlockRenderControllerProvider was renamed to FirstSpiritPreviewControllerProvider. This change also has to be applied to the registration of this ControllerProvider in the YvesBootstrap (\Pyz\Yves\ShopApplication\YvesBootstrap).

Extension of the getControllerProviderStack method. 

use FirstSpirit\Yves\FirstSpiritPreview\Plugin\Provider\FirstSpiritPreviewControllerProvider;

[...]
protected function getControllerProviderStack($isSsl)
{
   return [
      [...]
      new FirstSpiritPreviewControllerProvider($isSsl)
   ];
}

Fixed issues

New features

Fixed issues

New features

Update Notice

With this release, the deletion of obsolete content pages has been added to the data cleanup process. This requires a project extension where the following files of the files.zip artifact must be created in the Spryker project:

Additionally, the OCM web asset files/b2c-demo-shop/public/Yves/assets/DE/default/js/fs-preview-ocm-impl.js has been extended with this release. An update of this file is necessary to use a deletion workflow in ContentCreator.

New features

Fixed issues

New features

Fixed issues

New features

Highlights

With this release the links were reworked: The existing use of widgets is now only used in the text-image section. Within the Shoppable Video, the Teaser Grid and the Carousel, the new dynamic links are used instead, which are represented on the Spryker side by Twig functions. These can be called either directly or via the integration of the Twig template "link.twig" within a molecule.

New features

Fixed issues

Fixed issues

Update Notice

Fixed issues

New features

Fixed issues

New features

Fixed issues

New features

Fixed issues

New features

Fixed issues

New features

Fixed issues

New features

Update Notice

This update includes a name change of the Spryker module FirstSpiritCmsBlockDataConnector. It was renamed to FirstSpiritCmsDataConnector. Make sure to remove the old module first before installing the new one.

Fixed issues

New features

Fixed issues

New features

Fixed issues

Update Notice

This version includes a minor fix in the schema of the table spy_fs_cms_block_data_connector that stores structured data for CMS blocks. This is part of the FirstSpiritCmsBlockDataConnector module. The name of the PK sequence for the mentioned table was changed from spy_firstspirit_content_pk_seq to spy_fs_cms_block_data_connector_pk_seq. After updating the module make sure to run the Spryker console command console propel:install in order for Propel to automatically make the necessary change and migrate the database. If Propel fails to perform the migration automatically the necessary change has be be applied manually by altering and updating the name of the sequence to the new name described above. This can be achieved by executing the SQL statement ALTER SEQUENCE spy_firstspirit_content_pk_seq RENAME TO spy_fs_cms_block_data_connector_pk_seq;.

Fixed issues

New features

New features

Fixed issues

New features

The Technical Support of the e-Spirit AG provides expert technical support to customers and partners covering any topic related to the FirstSpirit™ product. You can get and find more help concerning relevant topics in our community.