• Login
  • Register

DNN Platform

Stay Up To Date With The Latest Releases

Following is a direct feed from the open and free source code repository for DNN Platform on GitHub. For those less savvy with GitHub, the below list serves as a less techy rendition of the most recent, versioned Release Notes for DNN Platform. These come complete with links to the GitHub repository for those wishing to dig deeper.

v9.8.0

Thursday, November 19, 2020

Release Notes

We'd like to first thank everyone from the community who has submitted pull requests or reported issues. A grand total of 84 pull requests by 14 contributors were processed for this release.

Noteworthy Changes in v9.8.0

Optional Telerik Removal

The major highlight for this release is that we removed all our dependencies on the Telerik library. In oder to not make this a breaking change, we do leave Telerik removal as a manual option until v10. The main component that still relied on Telerik where Site Assets and Global assets which used Digital Assets Manager. We ship with v9.8.0 a new file manager that has no dependencies on Telerik but it is not installed by default to not break existing sites upon upgrades. Please note that it will be automatically replaced in v10, so please test and plan accordingly.

To identify any third-party extension(s) that depend on Telerik, our very own @mitchelsellers has published the DNN Telerik Identifier module which you can download and install to to find assemblies that reference Telerik. Carefully review the results from this module to determine if your website is ready for full removal of Telerik. For any third-party modules that depend on Telerik, you should contact the module vendor/developer before following the steps below.

If you would like to remove Telerik in DNN 9.8.0 following are the steps to do so. Again, proceed with caution based on your findings using the DNN Telerik Identifier module above, as performing these steps may also break third-party extensions that depend on Telerik. We recommend you contact the developer/vendor in these cases for further guidance.

  1. Create a full backup of the site and database.
  2. Install the new Resource Manager module via Extensions > Available Extensions (Modules).
  3. Navigate to Manage > Site Assets via the Persona Bar and remove the Digital Assets Management module from the page.
  4. Add an instance of the Resource Manager module to the Site Assets page.
  5. Navigate to Manage > Global Assets via the Persona Bar and repeat Steps 3 & 4 for that page.
  6. Navigate to Manage > SQL Console via the Persona Bar and run the following script:
UPDATE {databaseOwner}{objectQualifier}Packages
SET IsSystemPackage = 0
WHERE Name IN ('DigitalAssetsManagement', 'DotNetNuke.Telerik.Web', 'DotNetNuke.Web.Deprecated', 'DotNetNuke.Website.Deprecated')
GO

DELETE FROM {databaseOwner}{objectQualifier}PackageDependencies
WHERE (PackageName = 'DotNetNuke.Web.Deprecated')
GO

UPDATE {databaseOwner}[{objectQualifier}Lists] SET Text = 'DotNetNuke.Web.UI.WebControls.Internal.PropertyEditorControls.DateEditControl, DotNetNuke.Web'
WHERE ListName = 'DataType' AND Value = 'Date'
GO

UPDATE {databaseOwner}[{objectQualifier}Lists] SET Text = 'DotNetNuke.Web.UI.WebControls.Internal.PropertyEditorControls.DateTimeEditControl, DotNetNuke.Web'
WHERE ListName = 'DataType' AND Value = 'DateTime'
GO
  1. Navigate to Settings > Servers in the Persona Bar and click the Clear Cache button in the top-right corner.
  2. Navigate to Settings > Extensions (Modules) in the Persona Bar and uninstall the Digital Assets Management extension. Be sure to check the Delete Files checkbox.
  3. Navigate to Settings > Extensions (Libraries) in the Persona Bar and uninstall the DotNetNuke Telerik Web Components extension. Be sure to check the Delete Files checkbox.
  4. Navigate to Settings > Extensions (Libraries) in the Persona Bar and uninstall the DNN Deprecated Web Controls Library extension. Be sure to check the Delete Files checkbox.
  5. Navigate to Settings > Extensions (Libraries) in the Persona Bar and uninstall the DotNetNuke Deprecated Website Codebehind files extension. Be sure to check the Delete Files checkbox.
  6. Open the web.config file within the site root and search for "Telerik". Delete any lines that reference it.
  7. Test all third-party modules to make sure they still work without Telerik. If any do not work properly, please contact the developer/vendor for further guidance.

Bug Fixes

  • Fixed an issue where newly created sub-folder was not shown if the parent folder name starts with 0 #3976 Thanks @kmuralidaran
  • Fixed an issue where the module friendly name was not updated as part of module extension update #4082 Thanks @tauqeer-haider
  • Fixed an issue where is was not possible to set page permissions for "unauthentication users" role #4094 Thanks @zyhfish @bdukes @mitchelsellers
  • Fixed a styling issue for checked Accept License checkbox in Extension installer #4103 Thanks @david-poindexter
  • Fixed an issue where the React common components would interfere with container css class #4109 Thanks @valadas
  • Fixed an issue where module dialog added new module to wrong pane #4113 Thanks @bdukes
  • Fixed an issue where the incorrect icon would show for errors in the Pages module #4124 Thanks @tauqeer-haider
  • Fixed an issue where Dnn would not install due to a missing config file #4136 Thanks @valadas
  • Fixed an issue where some Visual Basic modules would fail due to members that differed only by case #4139 Thanks @bdukes
  • Removed beacon setting on upgrade #4141 Thanks @bdukes
  • Fixed an issue with module pane placement after export/import #4144 Thanks @tauqeer-haider
  • Fixed an issue where 09.07.03.config was not included in the project #4151 Thanks @valadas
  • Fixed an issue that would cause an infinite redirect loop on mobile #4158 Thanks @valadas
  • Fixed an issue where some dates where not parsed with invariant culture which caused issues for non-Gregorian calendars #4164 Thanks @tauqeer-haider
  • Fixed an issue where the Event Log would fail silently during application startup #4178 Thanks @ahoefling
  • Fixed an issue where page title and description would get saved with site values unintentionnally #4184 Thanks @mitchelsellers
  • Fixed an issue with profile image visibility #4185 Thanks @tauqeer-haider
  • Fixed an issue where line breaks and year tokens would not be properly formatted in Social Messaging #4186 Thanks @hismightiness
  • Ensure new Localization HTTP module is running soon enough #4251 Thanks @bdukes
  • Remove Localization HTTP module from config #4264 Thanks @bdukes
  • Fix Localization Issues in WebAPI #4265 @donker
  • Fix the web.config errors for the new Localization module #4267 @donker

New features

  • Implemented a new optional file manager called Resource Manager #4152
  • Adds host setting option and ability to use settings outside module context #4153 Thanks @donker
  • Adds support for editing the robots.txt on a website #4165 #4172 Thanks @hismightiness
  • Fixed an issue where all emails where missing the body. #4285 Thanks @valadas
  • Fixed an issue where new users would have no preferred locale. #4284 Thanks @valadas

Enhancements

Developer Experience / Documentation

List of Contributors

Additional Resources.

Is this your first time installing or upgrading DNN? If so, you can find some help with the installation and upgrade wiki articles. If this is your 100th time upgrading DNN, maybe review the guides and submit a few changes!

MD5 Checksums

File Checksum
Dnn_Platform_9.8.0_Deploy.zip d342140db880e11e982d254c57f790c4
Dnn_Platform_9.8.0_Install.zip f66ac15e2c2e0faa75d3074e69adce2a
Dnn_Platform_9.8.0_Upgrade.zip abe0b66c882ddaa2ec0c266f0773fc5b
Dnn_Platform_9.8.0_Symbols.zip 7e39e094687435c041ec4cad323fd35e

v9.8.0-rc2

Thursday, November 5, 2020

Release Candidate

This is a release candidate, please do not install in production environments. RC (Release Canadidate) versions are meant for testing the next release. Please test in non-production environments.

Release Notes

We'd like to first thank everyone from the community who has submitted pull requests or reported issues. A grand total of 84 pull requests by 14 contributors were processed for this release.

Noteworthy Changes in v9.8.0

Optional Telerik Removal

The major highlight for this release is that we removed all our dependencies on the Telerik library. In oder to not make this a breaking change, we do leave Telerik removal as a manual option until v10. The main component that still relied on Telerik where Site Assets and Global assets which used Digital Assets Manager. We ship with v9.8.0 a new file manager that has no dependencies on Telerik but it is not installed by default to not break existing sites upon upgrades. Please note that it will be automatically replaced in v10, so please test and plan accordingly.

To help you try to identify if you have any other 3rd party extension that depends on Telerik, our very own @mitchelsellers has published the Dnn Telerik Identitier module which you can download and install to try and list all assemblies that reference Telerik.

If you want in v9.8.0 to remove the Telerik library, here are the steps to do so (please note this may also break any other 3rd party module that depends on Telerik):

  1. Take a full backup of the site and database.
  2. In Extensions > Available Extensions > Modules : Install the Resource Manager module.
  3. Navigate to Site Assets, remove the Digital Assets manager module from the page, insert an instance of the Resource Manager.
  4. Repeat step 3 but for the Global Assets page.
  5. In SQL Console Run the following command:
UPDATE {databaseOwner}{objectQualifier}Packages
SET IsSystemPackage = 0
WHERE Name IN ('DigitalAssetsManagement', 'DotNetNuke.Telerik.Web', 'DotNetNuke.Web.Deprecated', 'DotNetNuke.Website.Deprecated')
  1. Go to Servers and Clear cache.
  2. In Extensions > Modules , uninstall Digital Assets Manager (Tick delete files).
  3. In Extensions > Libraries, uninstall DotNetNuke Telerik Web Components (Tick delete files).
  4. In Extensions > Libraries, uninstall DNN Deprecated Web Controls Library (Tick delete files).
  5. In Extensions > Libraries, uninstall DotNetNuke Deprecated Website Codebehind files (Tick delete files).
  6. Open the web.config file and search for Telerik, delete any lines that reference it.
  7. Verify in bin folder, there is no dlls including the word Telerik.
  8. Test your 3rd party modules to make sure they still work without Telerik.

Bug Fixes

  • Fixed an issue where newly created sub-folder was not shown if the parent folder name starts with 0 #3976 Thanks @kmuralidaran
  • Fixed an issue where the module friendly name was not updated as part of module extension update #4082 Thanks @tauqeer-haider
  • Fixed an issue where is was not possible to set page permissions for "unauthentication users" role #4094 Thanks @zyhfish @bdukes @mitchelsellers
  • Fixed a styling issue for checked Accept License checkbox in Extension installer #4103 Thanks @david-poindexter
  • Fixed an issue where the React common components would interfere with container css class #4109 Thanks @valadas
  • Fixed an issue where module dialog added new module to wrong pane #4113 Thanks @bdukes
  • Fixed an issue where the incorrect icon would show for errors in the Pages module #4124 Thanks @tauqeer-haider
  • Fixed an issue where Dnn would not install due to a missing config file #4136 Thanks @valadas
  • Fixed an issue where some Visual Basic modules would fail due to members that differed only by case #4139 Thanks @bdukes
  • Removed beacon setting on upgrade #4141 Thanks @bdukes
  • Fixed an issue with module pane placement after export/import #4144 Thanks @tauqeer-haider
  • Fixed an issue where 09.07.03.config was not included in the project #4151 Thanks @valadas
  • Fixed an issue that would cause an infinite redirect loop on mobile #4158 Thanks @valadas
  • Fixed an issue where some dates where not parsed with invariant culture which caused issues for non-Gregorian calendars #4164 Thanks @tauqeer-haider
  • Fixed an issue where the Event Log would fail silently during application startup #4178 Thanks @ahoefling
  • Fixed an issue where page title and description would get saved with site values unintentionnally #4184 Thanks @mitchelsellers
  • Fixed an issue with profile image visibility #4185 Thanks @tauqeer-haider
  • Fixed an issue where line breaks and year tokens would not be properly formatted in Social Messaging #4186 Thanks @hismightiness
  • Ensure new Localization HTTP module is running soon enough #4251 Thanks @bdukes
  • Remove Localization HTTP module from config #4264 Thanks @bdukes
  • Fix Localization Issues in WebAPI #4265 @donker
  • Fix the web.config errors for the new Localization module #4267 @donker

New features

  • Implemented a new optional file manager called Resource Manager #4152
  • Adds host setting option and ability to use settings outside module context #4153 Thanks @donker
  • Adds support for editing the robots.txt on a website #4165 #4172 Thanks @hismightiness

Enhancements

Developer Experience / Documentation

List of Contributors

Additional Resources.

Is this your first time installing or upgrading DNN? If so, you can find some help with the installation and upgrade wiki articles. If this is your 100th time upgrading DNN, maybe review the guides and submit a few changes!

v9.8.0-rc1

Tuesday, October 20, 2020

Release Candidate

This is a release candidate, please do not install in production environments. RC (Release Canadidate) versions are meant for testing the next release. Please test in non-production environments.

Release Notes

We'd like to first thank everyone from the community who has submitted pull requests or reported issues. A grand total of 84 pull requests by 14 contributors were processed for this release.

Noteworthy Changes in v9.8.0

Optional Telerik Removal

The major highlight for this release is that we removed all our dependencies on the Telerik library. In oder to not make this a breaking change, we do leave Telerik removal as a manual option until v10. The main component that still relied on Telerik where Site Assets and Global assets which used Digital Assets Manager. We ship with v9.8.0 a new file manager that has no dependencies on Telerik but it is not installed by default to not break existing sites upon upgrades. Please note that it will be automatically replaced in v10, so please test and plan accordingly.

To help you try to identify if you have any other 3rd party extension that depends on Telerik, our very own @mitchelsellers has published the Dnn Telerik Identitier module which you can download and install to try and list all assemblies that reference Telerik.

If you want in v9.8.0 to remove the Telerik library, here are the steps to do so (please note this may also break any other 3rd party module that depends on Telerik):

  1. Take a full backup of the site and database.
  2. In Extensions > Available Extensions > Modules : Install the Resource Manager module.
  3. Navigate to Site Assets, remove the Digital Assets manager module from the page, insert an instance of the Resource Manager.
  4. Repeat step 3 but for the Global Assets page.
  5. In SQL Console Run the following command:
UPDATE {databaseOwner}{objectQualifier}Packages
SET IsSystemPackage = 0
WHERE Name IN ('DigitalAssetsManagement', 'DotNetNuke.Telerik.Web', 'DotNetNuke.Web.Deprecated', 'DotNetNuke.Website.Deprecated')
  1. Go to Servers and Clear cache.
  2. In Extensions > Modules , uninstall Digital Assets Manager (Tick delete files).
  3. In Extensions > Libraries, uninstall DotNetNuke Telerik Web Components (Tick delete files).
  4. In Extensions > Libraries, uninstall DNN Deprecated Web Controls Library (Tick delete files).
  5. In Extensions > Libraries, uninstall DotNetNuke Deprecated Website Codebehind files (Tick delete files).
  6. Open the web.config file and search for Telerik, delete any lines that reference it.
  7. Verify in bin folder, there is no dlls including the word Telerik.
  8. Test your 3rd party modules to make sure they still work without Telerik.

Bug Fixes

  • Fixed an issue where newly created sub-folder was not shown if the parent folder name starts with 0 #3976 Thanks @kmuralidaran
  • Fixed an issue where the module friendly name was not updated as part of module extension update #4082 Thanks @tauqeer-haider
  • Fixed an issue where is was not possible to set page permissions for "unauthentication users" role #4094 Thanks @zyhfish @bdukes @mitchelsellers
  • Fixed a styling issue for checked Accept License checkbox in Extension installer #4103 Thanks @david-poindexter
  • Fixed an issue where the React common components would interfere with container css class #4109 Thanks @valadas
  • Fixed an issue where module dialog added new module to wrong pane #4113 Thanks @bdukes
  • Fixed an issue where the incorrect icon would show for errors in the Pages module #4124 Thanks @tauqeer-haider
  • Fixed an issue where Dnn would not install due to a missing config file #4136 Thanks @valadas
  • Fixed an issue where some Visual Basic modules would fail due to members that differed only by case #4139 Thanks @bdukes
  • Removed beacon setting on upgrade #4141 Thanks @bdukes
  • Fixed an issue with module pane placement after export/import #4144 Thanks @tauqeer-haider
  • Fixed an issue where 09.07.03.config was not included in the project #4151 Thanks @valadas
  • Fixed an issue that would cause an infinite redirect loop on mobile #4158 Thanks @valadas
  • Fixed an issue where some dates where not parsed with invariant culture which caused issues for non-Gregorian calendars #4164 Thanks @tauqeer-haider
  • Fixed an issue where the Event Log would fail silently during application startup #4178 Thanks @ahoefling
  • Fixed an issue where page title and description would get saved with site values unintentionnally #4184 Thanks @mitchelsellers
  • Fixed an issue with profile image visibility #4185 Thanks @tauqeer-haider
  • Fixed an issue where line breaks and year tokens would not be properly formatted in Social Messaging #4186 Thanks @hismightiness

New features

  • Implemented a new optional file manager called Resource Manager #4152
  • Adds host setting option and ability to use settings outside module context #4153 Thanks @donker
  • Adds support for editing the robots.txt on a website #4165 #4172 Thanks @hismightiness

Enhancements

Developer Experience / Documentation

List of Contributors

Additional Resources.

Is this your first time installing or upgrading DNN? If so, you can find some help with the installation and upgrade wiki articles. If this is your 100th time upgrading DNN, maybe review the guides and submit a few changes!

v9.7.2

Tuesday, September 22, 2020

Release Notes

We'd like to first thank everyone from the community who has submitted pull requests or reported issues.
A grand total of 18 pull requests by 11 contributors were processed for this release.

Noteworthy Changes in v9.7.2

Bug Fixes

  • Fixed an issue where page went into wrong workflow state after import. #4036 Thanks @berkarslan-xo
  • Fixed an issue with user management in portal groups. #4041 Thanks @valadas
  • Fixed bug with hierarchical vocabularies. #4048 Thanks @daguiler
  • Fixed an issue where a new page was created by "Add page", the "Advanced/More/Secure Connection" property was always stored as "Off", regardless of the setting in the UI. #4059 Thanks @berkarslan-xo
  • Fixed an issue in creating multiple pages validation passed with same page name on same hierarchy. #4067 Thanks @berkarslan-xo
  • Fixed an issue that prevents 9.7.0 to 9.7.1 upgrades. #4076 Thanks @valadas

Enhancements

  • Created IPortalAliasService for Dependency Injection #4021 Thanks @ahoefling
  • Moved pencil icon to the right ... menu in pages module #4022 Thanks @tauqeer-haider
  • Implemented sorting in column headers on the users table #4032 Thanks @donker
  • Use request scope in PortalModuleBase. #4053 Thanks @GerardSmit
  • Changed 'DNN Error' to 'Application Error'. #4055 Thanks @thabaum
  • Ability to set mobile view cookie name in root web.config #4064 Thanks @thabaum
  • Warns admins about running search indexer on wrong server #4068 Thanks @daguiler

Developer Experience / Documentation

List of Contributors

Additional Resources.

Is this your first time installing or upgrading DNN? If so, you can find some help with the installation and upgrade wiki articles. If this is your 100th time upgrading DNN, maybe review the guides and submit a few changes!

Checksums

File MD5
DNN_Platform_9.7.2_Install.zip 7a918c12bdfacfc2a40933bd239f50a9
DNN_Platform_9.7.2_Upgrade.zip 62b19226e6886480e20a86ca2a638b91
DNN_Platform_9.7.2_Deploy.zip 911f0d85924e70af1568e4c064a55a65
DNN_Platform_9.7.2_Symbols.zip eda27375807449e2978bd7e660eb75e6

v9.7.2-rc1: Merge pull request #4077 from dnnsoftware/update-versions/patch-74facac

Wednesday, September 9, 2020

Updates versions as per release candidate creation

v9.7.1

Wednesday, September 9, 2020

Release Notes

We'd like to first thank everyone from the community who has submitted pull requests or reported issues. A grand total of 17 pull requests by 9 contributors were processed for this release.

Known issue

There is currently a known issue with Dnn 9.7.1 that affects token replace providers.

If you are doing a clean 9.7.1 install

No workaround needed, the normal install works fine.

If you are upgrading from 9.7.0 to 9.7.1

Nothing special is needed, this upgrade path will work.

If you are upgrading from any version before 9.7.0

  • Unzip the upgrade zip and add an empty text file named 09.07.00.SqlDataProvider in the Providers\DataProviders\SqlDataProvider folder.
  • Continue the upgrade as usual

If you have already upgraded to 9.7.1 before encountering this issue

  • Find the web.config file that is located in the root folder of the installation.
  • Create a copy of this file as a backup just in case.
  • Open the original web.config file that is in the root files of the installation in any text editor.
  • In the <sectionGroup name="dotnetnuke"> section add the following line:
<section name="tokens" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
  • In the <dotnetnuke> section, add the following lines :
<tokens defaultProvider="CoreTokenProvider">
      <providers>
        <clear />
        <add name="CoreTokenProvider" type="DotNetNuke.Services.Tokens.CoreTokenProvider, DotNetNuke" />
      </providers>
    </tokens>

Additional information

Token replace providers are a recent feature (Dnn 9.7.0) and is probably not yet used by many 3rd party modules. But if you do see other configured providers for tokens, you may want to consult with the 3rd party module vendor for instructions on how to best merge this config with theirs.

Noteworthy Changes in v9.7.1

Bug Fixes

  • Prevents Role Groups dropdown from expanding on delete. #3950 Thanks @daguiler
  • Fixed an issue where the efault site alias came as pre-selected on SEO URL edit page #3954 Thanks @berkarslan-xo
  • Fixed an issue where adding a page URL would default to 'Page and Child pages' site alias option. #3957 Thanks @berkarslan-xo
  • Added retry to CompressionUtil.OpenCreate to prevent failures during site export #3965 Thanks @daguiler
  • Fixed an issue where URLs added to pages unexpectedly redirected to the original URL #3983 Thanks @berkarslan-xo
  • Added administrators role id to the test url page #3996 Thanks @donker
  • Fixed an issue where TokenReplace would get the wrong moduleId #4018 Thanks @iJungleboy

Enhancements

Developer Experience / Documentation

  • Merged fixes from release/9.7.0 to develop #3958 Thanks @bdukes
  • Created IApplicationInfo and IApplicationStatusInfo for Dependency Injection #3988 Thanks @ahoefling
  • Created IHostSettingsService for Dependency Injection #3990 Thanks @ahoefling
  • Standardized CR/LF line endings in source code #3998 Thanks @bdukes
  • Update mergeable to check for Status: On Hold label #4000 Thanks @david-poindexter
  • Add documentation to new .NET Standard projects #4001 Thanks @bdukes
  • Improves GitVersion speed by limiting the lookup date #4016 Thanks @valadas

List of Contributors

Additional Resources.

Is this your first time installing or upgrading DNN? If so, you can find some help with the installation and upgrade wiki articles. If this is your 100th time upgrading DNN, maybe review the guides and submit a few changes!

Checksums

File MD5
DNN_Platform_9.7.1_Install.zip d6a70b8c82d6e2ca3a5fb56de47fcb25
DNN_Platform_9.7.1_Upgrade.zip b2e63bf389234bdfeb2ec8a3984b6178
DNN_Platform_9.7.1_Deploy.zip 5adfbfffb172f7def01f1f514f83aa30
DNN_Platform_9.7.1_Symbols.zip 2cc344ec63f6c9f270f7c6cf294cd903

v9.7.1-rc1: Merge pull request #4019 from dnnsoftware/update-versions/patch-b7e7b16

Friday, August 28, 2020

Updates versions as per release candidate creation

v9.7.0

Tuesday, August 25, 2020

Release Notes

We'd like to first thank everyone from the community who has submitted pull requests or reported issues. A grand total of 26 pull requests by 12 contributors were processed for this release.

Noteworthy Changes in v9.7.0

Potential breaking changes

There is a small potential breaking change if you use custom email templates, please read carefully the comments on #3808 if that is the case for your sites it is just a matter of adjusting those templates.

New issue management, milestones and roadmap

In our roadmap, Dnn 9.7.0 was to be our next release and include a new file manager. While we are still working on this new file manager we have also received a good mix of bugfixes and new features as pull requests. Because we were aiming at 9.7.0 we did not separate the bug fixes from the new features and the new file manager is not yet fully complete. This brought us to a decision point of holding bugfixes for longer or simply releasing and pushing the file manager to 9.8.0. After some discussions we realized that it is hard to work with specifically versioned milestones when we cannot know in advance which contributions will come in.

We have reworked our process to manage issues. Up until now we were trying to assign issues to a specific version number where it could go in providing someone would contribute a pull request to resolve it. This process was inefficient and on each new release we had to reassign every single unresolved issue to a new specific version. We will now use milestones for specific version numbers on pull requests only. For issues, we created new milesones as follows:

  • Future: Major - Issues that represent a breaking change that will go into a major release (e.g., major.minor.patch).

  • Future: Minor - Issues that represent a non-breaking feature that will go into a minor release (e.g., major.minor.patch).

  • Future: Patch - Issues that represent a bug fix, or non-breaking enhancement, that will go into a patch release (e.g., major.minor.patch).

We hope this process will bring better flexibility, we can decide on the version number just before release. We will in the future always assume that we will do a bugfix (patch) release and only switch to a minor release if we do have a new feature ready and merged.

Bug Fixes

  • #3808 Fixed a random replacement of http with https in resources. Thanks @donker
  • #3890 fixed an issue where captcha images would not show in IE 11. Thanks @dsjak-shie
  • #3897 Fixed an issue where tabs that should not be indexed would appear in the SiteMap. Thanks @ajwaka
  • #3917 Fixed an issue where modules were not able to change settings in shared pages. Thanks @berkarslan-xo
  • #3919 Fixes a bug where page start date and end date could be saved for the wrong time. Thanks @daguiler
  • #3927 Improved Dnn install logic by retrying Globals.Status if it fails at first. Thanks @bdukes
  • #3936 Fixes a regressing issue where persona bar menu controllers would log a lot of exceptions. Thanks @valadas

New features

Enhancements

  • #3795 Moved prompt APIs to the core library. Thanks @donker
  • #3845 Moved after login/logout/registration redirection to site settings to better support portal groups. Thanks @donker
  • #3923 Prevents unecessary call to getCultureList method on website change. Thanks @tauqeer-haider
  • #3930 Ensures DI services are disposed in WebForms modules. Thanks @bdukes

Developer Experience / Documentation

List of Contributors

Additional Resources.

Is this your first time installing or upgrading DNN? If so, you can find some help with the installation and upgrade wiki articles. If this is your 100th time upgrading DNN, maybe review the guides and submit a few changes!

v9.7.0-rc2: Merge pull request #3952 from mikebigun/bugfix/DNN-42078

Tuesday, August 4, 2020

Reset invalidation link on email change

v9.7.0-rc1: Fixes a wrong merge conflict resolution that broke the pages module.

Wednesday, July 29, 2020

The returned object was not scope on a page object which caused the frontend to no read the proper object in GetPageDetails return.