New releases of Episerver CMS with notifications for content approvals (Beta) and improved scheduled jobs telemetry, Episerver Commerce with improved cart performance, and Episerver Find with improved stemming for Swedish. Also includes fixes for the Episerver Forms Marketing Automation connector.
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.
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.
Click a package in the list to see work item details.
Users who have started a content approval sequence by setting an item to Ready for Review, or are set as approvers, now receive notifications in the user interface.
The bell icon in the toolbar displays the number of new notifications a user has; click the icon to display a list of notifications. From the notification list, you can go to the item that needs to be reviewed.
If the notifications should be displayed instantaneously, you need to enable WebSocket support on your web server; otherwise the user interface must be refreshed to display the notifications.
You can also configure your system to send out email notifications. See Configuring your email server.
Note: Unfortunately a breaking change was introduced with 10.2.0. In previous versions, DefaultShippingCalculator.GetShippingCost will try to create an instance of IShippingGateway for a configured shipping gateway. In 10.2.0 it will try to create an instance of IShippingPlugin instead. If you are using the new abstraction APIs, you might get an error. See this blog post for a workaround.
Last updated: Dec 27, 2016