World is now on Opti ID! Learn more

Per Bjurström
Jul 2, 2015
  3441
(0 votes)

Planned breaking changes 2015

An update to let you know what breaking changes we are doing in CMS later this year. For many sites the changes will go unnoticed, just another major version number, the latest version of the Alloy templates for example requires no code changes - just recompile and you are done.

Breaking Changes

  • Remove hard dependency on Log4Net. This will make it possible to run on the latest version of Log4Net or use another provider. Link to SDK.
  • As previously announced we will remove our implementation of WWF (Windows Workflow Foundation), where WWF 3 that we are using is now obsoleted and (officially) not supported on Azure. We are instead investing in "Projects 2.0" and you can follow the release feed to see this beta feature light up and support rich collaboration on not just pages but block, media and catalog content.
  • Remove remains of the VPP system that was obsoleted in CMS 7.5. Link to SDK.
  • Remove Content Channel and the other ASP.NET 2 Web Services that was last shipped in 7.5 and officially obsoleted in 8.
  • Remove assemblies EPiServer.BaseLibrary.dll and EPiServer.Implementation.dll. These assemblies was the framework of CMS 5 and contained internal features such as the ObjectStore. There are a few classes in there still used that are being moved to EPiServer.dll.
  • Remove Page Objects. A feature that pre-dated blocks. Obsoleted in 7.5.
  • Disable Dynamic Properties by default. As officially annonced in 7.5 this feature does not support the new user interface. We know there will be a lot of sites upgrading that are using dynamic properties so it will be left intact and there will be a setting to enable/disable this feature.

Release later this year with more details. See this post by Magnus for updates on planned breaking changes in Commerce.

Jul 02, 2015

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |