I am pleased to announce that DotNetNuke 5.2.1 has been released.  DotNetNuke 5.2.1 is a monthly stabilization release and includes a number of fixes aimed at improving the overall stability and performance of the platform.  We continue to significantly enhance our testing effort with each release.  The 5.2.1 release benefited from an improved testing procedure that included several iterations of Load and Performance testing.  While we recognize that there is always room for improvement, we hope you’ll find that this release represents another significant step forward and further improves an already great product.   This release includes a number of fixes related to upgrade and installation scenarios.  Over the next couple of stabilization releases we will continue to focus on improving this critical part of the product.  As usual, the complete details for all of the changes can be found in the ChangeLog.

Major Highlights

• Fixed issue where banners were not properly rotated according to the specified views/clicks
• Fixed issue where upgrades could fail if the the user account did not have permission to update objects in some db schemas
• Fixed issue where list values were visible outside of the Portal where they were created.
• Fixed issue where caching providers were not rendering unicode characters properly.
• Fixed issue with missing Telerik assembly in the source package.
• Fixed issue where Ajax HostSetting was not properly set on upgrade from 4.x installations.
• Fixed issues where upgrades would fail with a unique index violation
• Fixed issue with the Starter Kit which was missing HTML module files
• Fixed issue where page templates were not working correctly
• Fixed default settings for the module and output caching providers
• Fixed issue which prevented Blog module from working after some upgrades to 5.x
• Fixed issue when creating a new module in the Module Definition Wizard if the .ascx extension was not specified.
• Fixed issue where localization was not working if the application virtual directory name was also part of the module name.
• Fixed issue where the FriendlyName for Schedule Items was not being saved.
• Fixed issue where GetUserCountByPortal was making excessive database calls instead of using cached values
• Added binding redirect setting in web.config to prevent versioning issues with Telerik assembly

Security Fixes

• none

Updated Modules/Providers

The following modules and providers have been updated in the 5.2.0 packages.  Please see the specific project pages for notes on what bugs or enhancements were corrected with each release.

Modules

• Form and List 05.01.01

Providers

• FileModuleCachingProvider 05.02.01
• MemoryModuleCachingProvider 05.02.01
• SchedulingProvider 05.02.01

As with any release, we recommend you do a complete file and database backup before performing any upgrade on a production website and that you first perform a trial upgrade on a staging version of the site.  Following these guidelines will ensure that you are able to recover should any unforseen problems arise during the upgrade process.

NOTE: System requirements have changed in DotNetNuke 5.2.0. DotNetNuke requires SQL Server 2005 or above and .NET 3.5 SP1. Please ensure you are running a supported version of SQL Server and .NET before installing or upgrading to DotNetNuke 5.2.1.