Release/9.8.0 #4291
Merged
Release/9.8.0 #4291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature/resource manager
Ensure yarn runs when module is built
Fix resource manager to use the revised upload file handler in the core
* Standardization of File Headers * Standardized license file * Improved generic enum description value * Code standardization & cleanup * Updated to remove [AllowAnonymous] from API calls to fall back to Module Permissions
* First try at merging the build * Trying to fix lerna build * Should fix eslint errors * Fixes some dependency versions * Fix store and downgrade react-dropzone as it required react 16.8 * Fixing references * Fixes missing references and updates some * Fixes whitespace eslint warnings * Fixes css issue with visibility of upload button Co-authored-by: Peter Donker <peter@bring2mind.net>
Bump version to 1.1.0
Co-authored-by: Daniel Valadas <info@danielvaladas.com>
Further fixes to RM
That prevented the buid from running
Fixes 2 wrong merged conflicts resolutions
Add better wildcard file search support
… name starts with "0"
Meged latest changes from development into the resource manager feature branch
#4007) * First code push * Adds own implementation of PB DnnSf * Some more fixes Co-authored-by: Peter Donker <peter@bring2mind.net>
The frontend build of the new resource-manager had many warnings which this PR resolves. (whitespace and unused vars and method parameters).
Introduce MailAttachment class
* Updated Release Schedule Documentation * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> * Update .github/RELEASE_SCHEDULE.md Co-authored-by: Brian Dukes <bdukes@engagesoftware.com> * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> * Updated release verbiage * Updated Notes * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> * Update .github/RELEASE_SCHEDULE.md * Update .github/RELEASE_SCHEDULE.md * Update .github/RELEASE_SCHEDULE.md Co-authored-by: David Poindexter <dpoindexter@nvisionative.com> Co-authored-by: Brian Dukes <bdukes@engagesoftware.com> Co-authored-by: Daniel Valadas <info@danielvaladas.com>
Updates versions as per release candidate creation
It needs to be right after URL Rewrite (which determines the culture from the URL), and then all modules after it can make use of that culture info
Ensure new Localization HTTP module is running soon enough
It'll get added by 09.08.00.config, having it already in there will create a duplicate
Remove Localization HTTP module from config
(cherry picked from commit da5d855)
Fix Localization Issues
* Install JWT by default * Resolves multiple stylecop warnings in JWT project.
…ed so they get upgraded during DNN's upgrade process
Upgrade optional packages when they've already been installed
With the recent change to make optional packages (.resources) upgrade if the package was previously installed, while upgrading the JWT authentication provider, it cause the existing web.config configuration to be reset to the default and that would happen on each upgrade. This PR makes it ignore the node if it is already present from a previous installation.
Prevents JWT upgrade to change existing config
The user preferred locale is a required field in user profiles. Some change made it that in 9.8.0 this property is null. This PR reverts the behavior so the preferred locale is set on new users.
Fixed an issue where new users would have no preferred locale.
While working on the Feedback module the messages where missing their body, then I tried creating new users and those emails where also missing the body. Looks like the CoreMailProvider was missing setting the body to the emails. This PR solves that.
Fixed an issue where all emails where missing the body
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merging into master to release v9.8.0
This is a release management task, as per our policy, we are are self approving it.