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.
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!
Updates versions as per release candidate creation
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.
There is currently a known issue with Dnn 9.7.1 that affects token replace providers.
No workaround needed, the normal install works fine.
Nothing special is needed, this upgrade path will work.
<section name="tokens" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
<add name="CoreTokenProvider" type="DotNetNuke.Services.Tokens.CoreTokenProvider, DotNetNuke" />
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.
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.
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.
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.
Reset invalidation link on email change
The returned object was not scope on a page object which caused the frontend to no read the proper object in GetPageDetails return.
We'd like to first thank everyone from the community who has submitted pull requests or reported issues. A grand total of 52 pull requests by 15 contributors were processed for this release.
Additionally we would like to thank our wonderful testers for this release.
Fix to membership module due to cast error when using JWT auth
Fixes error in image handler cached response (#3873)