|Number of votes:||11|
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.
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.
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.
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.
The jQuery library that is bundled with the CMS UI is being deprecated and should no longer be used.
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.
And of course, included with all this are a lot of bug fixes :)