Noteworthy Changes in v9. Bug Fixes Fixed a serialization issue with authentication config Thanks bdukes Fixed an issue that prevented inserting links using the default HTML Editor Provider Thanks valadas Add back alternate views for core mail provider Thanks bdukes Fixed an issue where custom Analyzer types generate System. MissingMethodException Thanks berkarslan-xo Fixed an issue where it was impossible to edit html on child portals Thanks valadas Fixed an issue where the wrong RedirectAfter tabs were showing for localized sites.
Web on Microsoft. Compiled from 6. Recipe from 1. CakeUtils from 2. Json references Thanks valadas Bumped Fare from 2. FileSystemGlobbing Thanks valadas Bumped redux-devtools-dock-monitor from 1.
Contributors bdukes, valadas, and 7 other contributors. Security This release includes fixes for known security issues, please consult the DNN Security Center for more details.
Bug Fixes Fixed an issue where deleting the parent page while the child page was open didn't redirect Thanks berkarslan-xo Fixed an issue where dnn. Contributors bdukes, berkarslan-xo, and 2 other contributors. UserName was wrong with "Use email as username" setting turned on Thanks donker Fixed an issue where SQL Console raised an error for variable declarations with " " character Thanks berkarslan-xo Fixed an issue where the profile picture was not shown to anonymous users.
Json from 6. Core from 5. WebData from 3. Client from 5. WebHost from 5. Contributors meetmandeep, david-poindexter, and 14 other contributors. Special Attention New features Added support for Page Stylesheets stored in AzureFolderProvider msant7 Added capability to add existing modules from other sites in site group Thanks dpoindexter valadas and jncraig Enhancements Bug Fixes Fixed an issue where AzureFolderProvider was uploading the same file with different case Thanks msant7 Fixed an issue where the PersonaBar would not load if in an iframe Thanks jmbockhorst Removed extra hardcoded spaces from UserAndLogin Theme Object Thanks Timo-Breumelhof Ensures the content is decoded before being passed to tokenization providers.
MsBuild Thanks bdukes Upgraded Yarn to latest 1. To get started, just start typing your question below and either select one of the suggested questions or ask a new question of your own.
Return to previous page. Download DNN Platform. Evoq Customers. DNN Modules. DNN Themes. Store Blog. Evoq Preferred. Update, I went ahead and started over, all good now.
Problem resolved, and I learned something new. Thank you Joe. For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:. Simply post in the forums using the link below and we'll get you started. Joe Craig. And is should be marked as Beta. Did you download from GitHub? Check the file name of the package that you downloaded. When it comes to major version increments ie.
From a business perspective this makes sense because we know the early adopter members of our community will be anxious to utilize our product with the latest Microsoft technology. In the fall of this year Microsoft is poised to release a whole new wave of products. On the server side is Windows Server and IIS8, enterprise platforms for running highly scalable websites.
NET 4. Nearly all of these products have already reached a Release Candidate stage which means Microsoft is on track for delivery this year. So in order to align ourselves with the next generation of Microsoft technology, we have decided that the next major version of DotNetNuke will be 7. This release is expected to occur in Q4 of and will include some changes to our baseline platform support requirements…. Based on information we have gathered from a variety of sources; including industry market trends, Hosting providers, and our own Update Service, we plan to move our baseline platform support requirements in DNN7 to the following:.
And although IIS7 supports both Classic mode and Integrated Pipeline mode, the DotNetNuke platform has supported Integrated Pipeline mode since and we feel there are few, if any, business reasons to continue to support Classic mode in the future.
From an ASP. NET 3. This will allow us and our developer community to be able to take advantage of the new features introduced in ASP.
0コメント