Ben  McKernan
Optimizely
Sep 18, 2017
visibility 13993
star star star star star star
(11 votes)

Planned Breaking Changes 2017 (CMS UI)

Notable Changes

TinyMCE Package

The TinyMCE editor and related plugin configuration features will be moved into a separate NuGet package as an add-on with its own versioning number and breaking changes. This is to allow us to have a release cycle for TinyMCE which is decoupled from the CMS UI release cycle.

 

ASP.NET Identity

It was previously not possible to reset a user's password programmatically when using the ASP.NET Identity provider. Due to a bug, the method for resetting the password simply generated a reset token but never changed the password.

ApplicationUIUserManager<TUser>.ResetPassword(IUIUser user) will now throw a not supported exception. This is because ASP.NET Identity does not support generating new passwords for security reasons, i.e. it is bad practice to send a new password to the user in plain text. The new method ResetPassword(IUIUser user, string newPassword) should be used instead.

Both methods will still work when using the API with older membership providers.

 

Dynamic Content and XForms Packages

The legacy features Dynamic Content and XForms will be removed from the platform and moved into separate NuGet packages as add-ons with their own versioning number and breaking changes. As the platform progresses, these features will become more limited over time. We recommend migrating to Forms or Blocks wherever possible.

 

Target .NET 4.6.1 Framework

The CMS Core team is now targeting .NET 4.6.1 in order to be compliant with NetStandard 2.0, and as such, all CMS UI projects will also target this framework.

 

Deprecations

jQuery

The jQuery library that is bundled with the CMS UI is being deprecated and should no longer be used.

 

Gadget Framework

As we have mentioned previously here, the gadget framework has been deprecated but will remain in the product for CMS 11. We recommend, however, that you begin to convert your gadgets to components now.

 

Other Changes

  • IContentChangeManager.Move(IContent source, IContent destination, bool createAsLocalAsset) will now return the ContentReference of the moved content instead of void.
  • The key for content repository descriptors is no longer case sensitive.
  • DateTime properties on the visitor group criterion model will now be serialized to ISO 8601 when being sent to the client.
  • The UIHint.BlockFolder and UIHint.MediaFolder have been obsoleted and should be replaced with UIHint.AssetsFolder.
  • The UIHint.LongString has been obsoleted and should be replaced with UIHint.Textarea.
  • Removed many previously obsoleted constructors from classes where another a public constructor is available for use instead.

And of course, included with all this are a lot of bug fixes :)

Sep 18, 2017

Comments

Aria Zanganeh
Aria Zanganeh Oct 31, 2017 12:29 AM

Really good move. Now I can say Episerver is lightweight and Enterprise CMS!

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026