Per Bjurström
Aug 25, 2016
(9 votes)

Planned breaking changes 2016

An update to let you know what breaking changes are coming in CMS this year.

The main breaking changes are:

  1. A new state AwaitingApproval for content. We are also adding new events to IContentEvents and new save actions. Supports features around content approval.
  2. IContentRepository.Save and the events around that (IContentEvents) have a few quirks and odd behaviours that we have fixed to make the API more consistent and work better with approvals.
  3. Migration to UTC dates in the database will be a required step when upgrading, be ready by doing the migration today.
  4. Reviewed all APIs to make sure we do not expose implementation classes as part of our public versioned API. We will make a separate post about this with more details.

Some of the smaller breaking changes:

  • Links to unpublished content will return 404 (instead of login screen).
  • Localized texts will fallback to a fallback culture in the language files before falling back to values specified in code.
  • LanguageBranch class now implements IReadOnly to support read-only caching.
  • No longer possible to create sites without at least one host defined.
  • Properties PageData.StartPublish/StopPublish are changed to Nullable.
  • StartPublish will be null until published or set explicitly (today it defaults to the created date which is misleading).
  • Fixed confusing handling of empty properties (for example assigning an empty link item collection to a typed model resulted in a null value)
  • IContentVersionRepository List methods have been consolidated into one
  • The UI Framework EPiServer.Shell.dll will be moved from NuGet package EPiServer.Framework to EPiServer.CMS.UI.Core.

A lot more details will be provided as part of the release, including a list of all breaking changes and which APIs are being changed. Pre-release packages of the breaking change release will be made available as part of the continous release process in the coming weeks.

Aug 25, 2016


valdis Aug 27, 2016 10:51 PM

Changes for better :) Good work. Are you planning to jump to 10.x?

Aug 29, 2016 08:23 AM

Thanks, yes there will be a new major.

Johan Kronberg
Johan Kronberg Sep 4, 2016 04:55 PM

StartPublish changes sound great!

Please login to comment.
Latest blogs
Optimizely finally releases new and improved list properties!

For years, the Generic PropertyList has been widely used, despite it being unsupported. Today a better option is released!

Tomas Hensrud Gulla | Mar 28, 2023 | Syndicated blog

Official List property support

Introduction Until now users were able to store list properties in three ways: Store simple types (int, string, DateTime, double) as native...

Bartosz Sekula | Mar 28, 2023

New dashboard implemented in CMS UI 12.18.0

As part of the CMS UI 12.18.0 release , a new dashboard has been added as a ‘one stop shop’ to enable editors to access all of their content items,...

Matthew Slim | Mar 28, 2023

How to Merge Anonymous Carts When a Customer Logs In with Optimizely Commerce 14

In e-commerce, it is common for users to browse a site anonymously, adding items to their cart without creating an account. Later, when the user...

Francisco Quintanilla | Mar 27, 2023

How to Write an xUnit Test to Verify Unique Content Type Guids in Content Management

When developing an Optimizely CMS solution, it is important to ensure that each content type has a unique GUID. If two or more content types share...

Minesh Shah (Netcel) | Mar 27, 2023

Extend TinyMCE in Optimizely CMS 12

Since technologies are upgraded to newer versions the ways to extend or override the out-of-the-box functionality are also changed a little bit so...

Ravindra S. Rathore | Mar 27, 2023 | Syndicated blog