DotNetNuke 5.0.1 represents the latest release for the 5.x codebase.  While we have made significant strides in dealing with the most significant issues discovered in the 5.0.0 release, it is still not at a level where we recommend this release for production use.  DotNetNuke 4.9.2 still represents our most stable and mature release and is recommended for most users.

As always you can see a complete list with all the details of each fix/change in the ChangeLog.

Major Highlights

• Added the ability to automatically update user roles without requiring the user to logout and log back in.
• Changed the user deletion code to use a soft-delete rather than removing the user record.  This ensures that modules like the Forums behave correctly for a previously "deleted" user.
• Added IP logging to the User's table to capture the last IP address from which a user logged in.
• Fixed breaking change with case sensitivity in the name of skin panes.  This fix restores the case-insensitivity of previous DotNetNuke releases.
• Fixed breaking change with ModuleId in DotNetNuke 5.0 which changed ModuleId to a readonly value.
• Fixed breaking change in CBO.FillDictionary to restore previous behavior.
• Fixed breaking change which prevented legacy skins from being installed when using the auto-install option.
• Fixed breaking change which prevented updated DLLs from being replaced when repairing a module installation.
• Fixed breaking change in HumanFriendlyUrls which prevented querystrings from being properly read when using HumanFriendlyUrls
• Fixed breaking change in legacy modules which would not store a zip file which was not designated as a resource file.
• Fixed breaking change in legacy modules which ignored zip directories.  DNN 5 changed this behavior.
• Fixed breaking change in default.css which resulted in changes to existing skin layouts.
• Fixed issue with roles module which prevented users from delegating role administration to a non-admin user.
• Fixed issue which prevented some users from logging out due to the inability of the system to detect their country.
• Fixed issue with Module Action Menu which prevented it from opening links in new windows.
• Fixed issue that results in an error when the Cache logs an error under the new CACHE_ERROR event type
• Fixed a packaging issue with FCKEditor which caused the LinkEditor to cause an unhandled exception.
• Fixed an issue which resulted in the system not being able to display the portalaliases screen

Security Fixes

• Fixed version information leakage issue in the install wizard

Updated Modules/Providers

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

Modules

• Forms and List 05.00.00

Providers

• FckHtmlEditorProvider 2.0.3
• AD Provider 05.00.01

DotNetNuke 4.9.2 represents the final planned release for the 4.x codebase.  The DotNetNuke 4.x platform has been in production since the launch of Visual Studio 2005 and it is finally time to shift our focus to the new DotNetNuke 5.x platform.  We have a lot of great features planned for development and release in 2009, many of which have been high on the list of requested features for some time.

As always you can see a complete list with all the details of each fix/change in the ChangeLog.

Major Highlights

• Added the ability to perform permanent redirect from an existing page using the page settings screen.
• Fixed issue with the permanent forms authentication cookie which cause problems in SSO environments.
• Fixed issue which required a workaround to import page templates into a portal
• Fixed a caching issue which prevented modules from being properly cached if they used a specific caching method overload
• Fixed issue which resulted in an error installing the Broadcast Polling Provider
• Fixed tab redirect issue which allowed a user to directly navigate to a tab which was supposed to redirect to another URL
• Fixed a continuous redirect issue which occurred when trying to upgrade from early 4.x releases to 4.9.1

Security Fixes

• None

Updated Modules/Providers

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

Modules

• None

Providers

• FckEditor Provider 2.0.3

Now that the holidays are through and we have had a chance to assess and fix a number of issues reported in DotNetNuke 4.9.1 and 5.0.0, we are just about ready to release DNN 4.9.2 and 5.0.1.  To avoid some of the confusion with a dual release we are going to stagger the two releases.

DotNetNuke 4.9.2 will be released on Monday, February 16th.  DotNetNuke 5.0.1 will be released the following Monday, February 23rd.  Barring any major hidden show-stopping issues, DotNetNuke 4.9.2 will be the final 4.x release and all future development will focus on the 5.0 platform.

As usual we will post release notes when we make the final releases.

As part of our annual planning we have completed our roadmap for our 2009 development which we’ll be updating shortly on the DotNetNuke.com website.

Today starts the Fit in February Develop Challenge and I have decided to go ahead and participate.  2 years ago after seeing my 3 older brothers for the first time in many years I noticed that we had all put on excessive weight.  I was embarrassed to sit there realizing how much weight I had gained since leaving the Navy in 1995 and determined to take it all back off.  I knew how important it is to stay fit as I lost my Step-father to heart attack a little over 12 years ago.  He was only 55 at the time.  Over the next 6 months I lost almost 60 lbs and was back down below my final weight when I left the navy.  I was pretty happy with my accomplishment and feeling much better.

More...