3.0.0
Release Notes
We deeply appreciate the contributions from our community. A grand total of 71 pull requests by 2 contributors were integrated into this release bring the total to 2449 commits all time.
Noteworthy Changes in v3.0.0
#1782 Upgrade to 5.1.3 Bootstrap and Bootswatch Cyborg @leigh-pointer
#1781 fix UX in module/theme creators @sbwalker
#1776 [RootFolder] was missing from Release.cmd @leigh-pointer
#1772 Updated module and theme templates to .NET 6 @sbwalker
#1764 Add support for TrustServerCertificate connection string option for SQL Server @sbwalker
#1762 Remove unnecessary cascading parameter to improve efficiency @sbwalker
#1761 Fix error on WebAssembly when logging out @sbwalker
#1760 Allow for direct navigation to pages in Page Management @leigh-pointer
#1759 SQL Server installation needs to allow configuration of encryption setting on .NET 6 @sbwalker
#1757 Fix issue when creating site with new tenant @sbwalker
#1754 Make date format configurable for the Audit component @leigh-pointer
#1750 Fix Blazor theme not rendering correctly on Bootstrap 5 @leigh-pointer
#1735 Fix link to home path displays login page @sbwalker
#1725 Upgrade to .NET 6 and increment version to 3.0.0 @sbwalker
#1720 Add proper help text to aliases field in default resource file for Site Settings @sbwalker
#1720 Set default value for new ShowLogin parameter in Login theme component @sbwalker
#1709 Fixed validation issue in Role Managment - Users @sbwalker
#1709 Modified FileManager component to allow Folder parameter to contain a folder path which is translated to a FolderId internally and refactored Packages folder logic @sbwalker
#1708 Added ability for Runtime and RenderMode to be set per Site - enabling the framework to support multiple hosting models concurrently in the same installation @sbwalker
#1708 Fixed WebAssembly Prerendering issue (this also resolved the issue where the component taghelper was not passing parameters correctly to the app when running on WebAssembly) @sbwalker
#1708 Remove web.config from upgrade package @sbwalker
#1704 Fix logic which sometimes results in System.InvalidOperationException: The value of IsFixed cannot be changed dynamically @sbwalker
#1703 Allow site root page paths (rather than specifying a magic "home" string) @sbwalker
#1701 Fix User Management Tab needs clicking to render UI when language is not default @leigh-pointer
#1699 UX improvements to FileManager and Pager components @sbwalker
List of Contributors in v3.0.0
Upgrade Instructions
In .NET 6 Microsoft introduced a breaking change in regards to SQL Server connection strings. Previously, database connections were not expected to be encrypted; however, in .NET 6 they are now expected to be encrypted by default. You can override this behavior by appending an Encrypt=False attribute to your connection string. In Oqtane, this needs to be done in both the appsettings.json file as well as the DBConnectionString column in the Tenants table in the master database. New installations of Oqtane from 3.0+ include this attribute by default. Please note that not all installations will experience this upgrade issue. It typically occurs in local development environments where you are using LocalDB or have installed SQL Server locally without using a trusted certificate.
Additional Resources
The Oqtane Framework is built on Blazor, an open source and cross-platform web UI framework for building single-page apps using .NET and C# instead of JavaScript.
This release of Oqtane is targeted at .NET 6.0. This release is upgradeable from previous Oqtane releases. Simply install the Upgrade package and your database will be upgraded automatically.
