Last updated: Nov 14 2016

Episerver - update 137

Includes a new release of CMS containing a new Content approvals feature (in Beta), and the ability to extend the user interface with plug-in areas. It also includes bug fixes for Episerver Find and the Lionbridge connector. The following add-ons have been updated with CMS 10 support: Episerver Self-Optimizing Block, Episerver Spellchecker for Tiny MCE and Episerver Live Monitor.

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-3487: Support for International Resource Identifiers, IRI
      Adds support for enabling unicode characters in the URL segments to content. See Internationalized Resource Identifiers (IRIs) in the Episerver CMS Developer Guide for details.
    • CMS-2031: Content Approval: Implement Core API (Beta)
      Core API implemented for content approval (Beta). Technical documentation will be available later, API is only used by the UI so far.

Episerver CMS UI

New features:

    • CMS-2881: Content approvals (Beta)
      This is the first release of the Content Approvals feature, which enables administrators to set up approval sequences containing a number of steps that editors have to collaborate on and approve to be able to publish the content.
      This feature is currently in beta, meaning that users need to be in the EPiBetaUsers group in order to use the new feature.
      See the documentation in the the Episerver User Guide for details.
    • Plug-in areas
      As a part of the content approvals story, Episerver has also added plug-in areas at common extension points to make it easy for developers to extend the Episerver user interface. See Plug-in areas in the Episerver Developer Guide for details.
    • CMS-4708Extend Episerver ASP.Net Identity implementations

      It is now possible to replace parts of the ASP.NET OWIN pipeline used by Episerver. See Episerver CMS UI AspNetIdentity OWIN authentication in the Episerver CMS Developer Guide for details.

Episerver Find

Episerver add-ons

CMS 10 support

Commerce 10 support

Third-party add-ons

Important notifications

Related topics