Episerver (Optimizely) Release Notes - July 2020

August 11, 2020
David Korff, David Fewless

Episerver’s (now Optimizely) July 2020 release notes cover CMS changes to on-page editing, CSR enhancements in Commerce, and Content Delivery API changes to enable more consistent experiences for global audiences.


Episerver’s (now Optimizely) continuous release cycle provides new features and bug fixes on a bi-weekly cadence. Each month, C2 will aggregate and highlight some of the bigger updates to Optimizely software. To learn more, or if you have specific questions, you can contact The C2 Group, an Optimizely Gold Partner, here.

Support on-page edit of content areas

Fixed in: EPiServer.CMS.UI 11.27.0 [ID: CMS-16043]

Previously, you could not edit blocks directly from the on-page edit screen. With this update, developers can now render blocks inside content areas using guid based identifiers instead of the traditional integer-based identifiers. This minimizes steps for a content editor to edit individual blocks when using the on-page edit feature.

Remove option for CSR to enter credit card info

Fixed in: EPiServer.Commerce 13.21.0 [ID: COM-11324]

Previously released in June 2020, Episerver has revoked the ability for customer service representatives to enter credit card information for the built-in payment methods. All payments are now done externally to the Order Management screen.

Necessary shipping information displayed to CSRs

Fixed in: EPiServer.Commerce13.21.0 [ID: COM-11388]

Customer service representatives now get a better overview of recipient shipping information in the Forms Details tab under Shipments. This will allow for less manual effort for looking for prevalent customer information.

When handling content areas, maintain requested language

Fixed in: EPiServer.ContentDeliveryApi2.14.0 [ID: HAPI-654]

When a specific piece of content or page is requested through the REST API with a specific requested language.

Language of the response (content language) is resolved based on requested language, available translations as well as fallback and replacement rules for the page. All properties try to match the content language, to return a single consistent translation. All links should try to match the requested language.

Media URLs should use management host – important for headless scenarios

Fixed in: EPiServer.ContentDeliveryApi2.13.0 [ID: HAPI-635]

REST API had exposed absolute URLs with the incorrect host. Media URLs now use the management host. Use fetchable URL for images in XHTML properties, link item, collections, URL properties. This will be especially helpful for Epi customers taking advantage of its headless CMS features.

Mechanism for setting the parent domain

Fixed in: EPiServer.CMS.UI 11.26.0 [ID: CMS-15892]

For content editors to on page edit (OPE) when a site is split up between a delivery application and a management, the applications need to share the same parent domain. This latest feature enables support for setting the document-domain to the same domain on both the delivery site and the management site. It returns a full URL from the Content Delivery API where normally they would have to call for each element and built it in code.

Return absolute canonical URLs from Content Delivery API

Fixed in: EPiServer.ContentDeliveryApi 2.13.0 [ID: HAPI-634]

All internal content links are returned as absolute URLs using the canonical schema, host, and path configured for the site and branch of the linked content. Any content that is located outside of any site uses the default CMS logic to determine the current site. Making any changes to the canonical URL are language aware.