Episerver - update 167

New releases of Episerver CMS Core and Episerver CMS UI, including group support for content approvals and changes to the APIs. Bug fixes for Episerver CMS Core (including a critical bug fix), Episerver CMS UI, Episerver Commerce (including critical bug fixes), Episerver Recommendations, and Episerver Find. A new release of the third-party add-on SiteAttention.

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

New features:

- CMS-4675: Review and release of Beta APIs
  A number of APIs have been updated, see the release notes for the work item CMS-4675 for details.
- CMS-7015: API: Roles in Content Approvals API
  The content approvals API has been updated with group support.

Episerver CMS UI

New features:

- CMS-6927: UI Support for groups in Approval Sequences
  It is now possible to add a group to a content approval sequence. Groups have a special group icon in the list of suggestions and you can also see how many users are included in the user group. Hover over the group to see a list of included users.
  A new appSetting, episerver:ui:ApprovalStepRoleUserLimit, has also been introduced in the web.config file, which triggers a warning when an administrator adds a group larger than the defined value in the appSetting. It also limits the amount of notifications sent to the users in the group. See John-Philip Johansson's blog post and Configuring CMS user interface.

- CMS-1506: Support Razor views in Shell Modules
  Shell modules has traditionally only supported WebForms views per default. As Razor views now are the default choice, we have made it easier to use Razor views by allowing Module developers to select which View Engine that should be used for their module.
  View engine selection is done by changing the viewEngine attribute in the module.config to Razor. Standard Razor configuration in web.config is still required.
  In addition, it is possible to opt out of any view engine registration by setting the module configuration to None.

Episerver Commerce

EPiServer.Commerce 10.7.2
EPiServer.Recommendations 1.3.5 (Beta. There are no public work items in this release.)
EPiServer.Recommendations Commerce 10.7.2 (Beta. There are no public work items in this release.)

Episerver Find

EPiServer.Find 12.5.1

Third-party add-ons

SiteAttentionModule 3.0.0 (There are no public work items for this release.)

Important notifications

Update 150 included breaking changes for Episerver Service API 3.
Update 141 included breaking changes for Episerver Languages 3.
Update 134 included breaking changes for Episerver CMS 10, Episerver Commerce 10 and Episerver Forms 4.
Update 118 included breaking changes for Episerver Forms 3 and Episerver Languages 2.
Update 114 included breaking changes for Episerver Find 12.
Update 108 included breaking changes for Episerver Forms 2.
Update 94 included breaking changes for Episerver Mail 8.
Update 89 included breaking changes for Episerver Find 11.
Update 83 included breaking changes for Episerver Commerce 9.
For previous notifications, see update 83.

Try our conversational search powered by Generative AI!