Last updated: Jul 05 2016

Episerver - update 118

Includes new releases of Episerver CMS Core, Episerver Commerce, Episerver Service API, Episerver Forms, and Episerver Languages. The Episerver Forms and Episerver Languages include breaking changes. The release also includes bug fixes for Episerver Find and Episerver Service API.

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

NuGet dependencies
In some upgrade scenarios, you might experience issues with the dependency chains due to issues with NuGet. This mostly affects Commerce and Find, but also might occur when updating CMS. The workaround usually is to update the packages one-by-one. The issue was fixed in NuGet but requires Visual Studio 2015. See Issues with NuGet package updates.

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-3682Support for .NET Diagnostics Tracing in Azure Web Apps
    Adds a built-in logger for writing log messages from the Episerver Log API to .NET Diagnostics Trace, that you can use in Azure Web Apps without making any changes to the application. See Redirect Episerver log messages into .Net Diagnostics Trace in the CMS Developer Guide for details about how to enable this trace logger via an app setting.
  • CMS-2029: Improve content API in preparation for approvals (Beta)
    See Validation in the CMS Developer Guide.
  • CMS-3767: Add explicit (null) fallback behavior to LocalizationService

    Add an additional fallback behavior for LocalizationService that makes the service return null rather than an empty string when a missing resource is requested. This behavior replaces the current method of passing in null as the fallback string in a future major release.

Episerver Commerce

New features:

  • COM-1794: Campaigns and Promotions: General Availability Release

    This marks the campaigns and discounts system ready-for-production use, including previously released discount types. Prerelease tags on related APIs are removed, delcaring them as stable (subject to semantic versioning).

  • COM-1361: Campaigns: Preview images for discount types

    Adds preview images for the built in promotion types.

  • COM-111: Quicksilver updated to Commerce 9
  • COM-94: Campaigns: Spend [currency amount] and receive a [discount] on selected items

    This discount type lets you get a discount off selected items when the total order value exceeds a set threshold.

  • COM-100: Campaigns: Spend [currency amount] and receive selected gift items

    This discount type lets you add one or more gift items to the customer's cart when the order value exceeds a set threshold.

Episerver Service API

Episerver Forms

New features:

    • AFORM-700: Forms 3.0 is released in zipped format

      Forms 3.0 is released in zipped format.

      Note: The .cshtml view was removed because the CMS does not support Razor view for block inside a zip file.

    • AFORM-742: Submit a form asynchronously in Ajax mode

      To make Episerver Forms use $.ajax() to submit a form asynchronously, do one of the following:

      • set JavaScript object epi.EPiServer.Forms.AsyncSubmit to true 

      • decorate the tag with the data-epiforms-async-submit="true" atttribute.

      Otherwise, a form submits SubmissionData to server side synchronously (to prevent a visitor from continuously clicking Submit).

    • AFORM-709: Updated built-in jQuery in Forms to the latest version (1.12.4 or newer)

      The built-in jQuery in Forms was updated to 1.12.4.

    • AFORM-627: Breaking change: built-in WebHook changed format of JSON data

      Changed the built-in Webhook JSON format to be compatible with Breaking changes include:

      • Changed CallWebHookAfterSubmissionActor

      • Changed format of JSON data send by webhook from JSON array to single JSON object.

      • Changed format from [ {"Key":"keyname","Value":"objectvalue"} ,{"Key"...] to {"keyname":"objectvalue","keyname2"...}

    • AFORM-571: Don't install a bunch of modules-files into non-web projects


    • AFORM-676: An abstraction was added to EPiServerFormsSection.Instance

      Introduced IEPiServerFormsConfig in Forms.Core. Forms implement its EPiServerFormsConfig, registers it in the DI container, and looks into modules/_protected/EPiServer.Forms/Forms.config for values. You can override IEPiServerFormsConfig using DI.

    • AFORM-246: Breaking change: Use new abstract DI of StructureMap, in Core 9.5

      Changed NuGet depends on Core 9.5.0 Use Abstract usage of StructureMap​ that exposes new dependency injection.

Episerver Languages

Important notifications

Related topics