Don't miss out Virtual Happy Hour today (April 26).

Try our conversational search powered by Generative AI!

Episerver - update 233

New release of Episerver Commerce, Episerver Forms, Episerver Campaign, and the Episerver Visual Studio extention. Bug fixes for Episerver CMS Core, Episerver CMS UI, and Episerver TinyMCE.

The update applies to Episerver projects version 7.5 and higher, and contains finalized work items included in the latest iteration. Continuous release updates are cumulative to include previous updates. Episerver supports all platform updates and strongly recommends that you keep ongoing projects up-to-date. You can install the updates from the Episerver NuGet feed.

Main packages
This release information lists updated main package versions for the Episerver platform. When a release is built, other dependent packages also may be bumped to new versions, although they contain no publicly visible changes. This is done to avoid dependency errors. When you upgrade, NuGet alerts you to upgrade related packages to the required versions. For Commerce, it is important to ensure that you are running the same version of CMS and Commerce, both in the front-end and back-end applications.

Updated main packages

Click a package in the list to see work item details.

Episerver CMS Core

Episerver CMS UI

Episerver Commerce

New feature:

    • COM-6899: Catalog export for Episerver Campaign
      A mechanism is provided to periodically transfer the latest product data from Commerce to Campaign in a CSV format. To carry out this transfer, Episerver.Campaign.Commerce provides a scheduled job, Export Product Data To Campaign. At regular intervals, the job collects Commerce product data and exports it to a CSV file in a specified format. The file is automatically transferred to an Episerver server. From there, it is imported to the Campaign system.

Episerver Campaign

Episerver Forms

New feature:

    • AFORM-1636: Respect personalization policy to NOT collect data in FormElements
      Episerver Forms collects Data Subject username (of the current authenticated website visitor) and browser IP address to perform some features. If the personalization policy indicates that personalization should not happen, Episerver Forms stops collecting data.

Important notifications

Related topics

Last updated: Sep 24, 2018