Ben  McKernan
Sep 18, 2017
  12498
(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!

Please login to comment.
Latest blogs
Integrating Optimizely DAM with Your Website

This article is the second in a series about integrating Optimizely DAM with websites. It discusses how to install the necessary package and code t...

Andrew Markham | Sep 28, 2024 | Syndicated blog

Opticon 2024 - highlights

I went to Opticon in Stockholm and here are my brief highlights based on the demos, presentations and roadmaps  Optimizely CMS SaaS will start to...

Daniel Ovaska | Sep 27, 2024

Required fields support in Optimizely Graph

It's been possible to have "required" properties (value must be entered) in the CMS for a long time. The required metadata haven't been reflected i...

Jonas Bergqvist | Sep 25, 2024

How to write a bespoke notification management system

Websites can be the perfect vehicle for notifying customers of important information quickly, whether it’s the latest offer, an operational message...

Nicole Drath | Sep 25, 2024

Optimizely DAM – An Introduction

I presented a talk about the Optimizely DAM at the OMVP summit during Opticon 2024 in Sweden. I have now converted that talk into two blog posts....

Andrew Markham | Sep 25, 2024 | Syndicated blog

Simple and Effective Personalization with Optimizely Data Platform (ODP)

As we dive into the amazing capabilities of Optimizely One, let’s shine a spotlight on the Optimizely Data Platform (ODP). This simple tool unifies...

Alex Harris - Perficient | Sep 24, 2024 | Syndicated blog