Skip to content

@ohine ohine released this Oct 1, 2018

Release Notes for v9.2.2

We'd like to first thank everyone from the community and ESW who has submitted pull requests or reported issues. This is our second community driven release, and our first time generating the actual installation packages. If you notice anything (good or bad) please let us know. We are looking to automate and improve this process as much as possible to increase the quality and frequency of platform releases.

A total of 29 pull requests were processed for the 9.2.2 release in the platform repository, plus 24 additional pull requests were processed in the personabar repository. Below you can find a short list of the noteworthy changes in this release, below that you can find all the changes in 9.2.0 as well. For a full list, please check the GitHub milestone pages on each of the repositories.

Changes in v9.2.2

  • This release contains fixes for 2 security issues. Please see the Security Center for additional details.
  • Improvements in string management to increase overall performance. Thanks @mitchelsellers #2217
  • Registration when using email address failed. Thanks @Mohtshum #2212
  • Improve feedback in the cleanup process during module installation and upgrades. Thanks @donker #2207
  • Reduce the scope of cache keys cleared after a user registers for an account. Thanks @zyhfish #2175
  • Improve MVC support with RedirectToAction. Thanks @ahoefling #2171
  • Reviewed and updated build scripts throughout the platform to enable VSTS CI. Thanks @ohine @bdukes and @ahoefling for their work on these tasks. We will continue to refine and improve this process in each release this year.
  • Combined the multiple Admin Experience repositories into one shared repo. Since this was done mid-9.2.2 development, we have issues split between the older archived repositories and the new combined location. We are linking to all 4 repos for access to full commit history below, in the next release this will be much easier to manage with the new combined repository. Thanks to @bdukes, @ohine and @ashishpd for their work on this task.
  • Various improvements and stabilization fixes in the control panel and administration modules.

List of Contributors for v9.2.2

Release Notes from v9.2.0.

New Features in v9.2.0+

  • Prompt - New command line Administrative Interface
  • Pages - New Page Management
  • Connectors - New Connector Management via Persona Bar
  • Azure Storage Connector - Migrated from Evoq to Platform

Framework Updates in v9.2.0+

  • Libraries updated to - jQuery 3.2.1, Newtonsoft 10.0.3, Sharpzlib
  • Upgraded ClientDependency.Core to 1.9.3
  • Replaced 51 Degrees with local provider
  • Removed ~500 APIs deprecated prior to 7.0
  • New Integration Testing framework

Known Potential Breaking Changes in v9.2.0+

For clarity, we are restating the breaking changes from the 9.2.0 here, as if you have not yet upgraded to 9.2.0 or later, they still apply.

  • Removed ~500 deprecated APIs
    • Upgrade any 3rd party extensions before upgrading DNN
    • Recompile custom extensions against DNN 9, and review deprecation warnings
  • jQuery upgraded from 1.9.1 to 3.2.1 (with jQuery Migrate 3)
  • jQuery UI upgraded from 1.11.3 to 1.12.1
  • SharpZipLib upgraded
    • DNN has been using a very old version of the SharpZipLib library for zipping and unzipping archive files, because the newer versions had a major breaking change, with the library being renamed in a way where both versions cannot be supported at the same time. This new version is now being used, so modules which referenced the older version will break upon upgrading DNN. The recommendation is to either use the APIs that DNN exposes (e.g. DotNetNuke.Services.FileSystem.FileManager.UnzipFile), or to use the APIs available in .NET 4.5, under the (System.IO.Compression namespace)[]
  • Newtonsoft.Json upgraded from version 7 to 10
    • A binding redirect has been put in place, so components compiled against older (or newer) versions of Newtonsoft.Json should still operate. However, the details of the JSON serialization and deserialization may be different, which could cause components to break if they have assumptions on those details of the JSON format
    • There is a chance on upgrades you will run into issue #2121. You may need to manually copy the assembly from the install package to continue with the upgrade procedure. This will be fully resolved in the next release.
Assets 7
You can’t perform that action at this time.