Thought I'd share some initial thoughts on this much needed release. Why much needed? As most people know version x.x.0 (in this case 5.6.0) there are almost always some large changes included. Waiting for the point (.1) release is usually a pretty smart move.

One of those issues in 5.6.0 was the new "automatic portal alias creation for single portal installs". This caused some installations to have numerous "rogue" entries in the database, this in turn caused some strange browser redirecting. That said, 5.6.1 addressed that issue and several more. Also addressed where 5 security issues (listed below).

 I found that version 5.6.1 installed flawlessly on 18 installs this morning. Not a single issue! Most of the sites I upgraded where version 5.5.1. I opted not to upgrade to v5.6.0 for the reasons stated above. The only issue I came across was a minor module compatibility problem, that was the DNN Rad Tag Cloud. I have since recompiled it against v 5.6.1 (download here ).

Here are the list of highlights in this release:

• Fixed issue to remove preCondition checks when upgrading to .Net 4.0
• Fixed issue where some valid domains were failing email validation checks.
• Fixed issue where editing Host menu page settings assigns the page to a Portal.
• Fixed issue which caused XHTML validation problems in 5.6.0
• Fixed issue where an aspx page in any subfolder was inaccessible.
• Fixed issue where Config.Touch method signature had an unintentional breaking change in 5.6.0
• Fixed issue which caused error on adding new super user account
• Fixed issue where Google Analytics was broken during upgrade to 5.6.0
• Re-Added Checkbox to Profile Property Types 

• Edit Level Users have Admin rights to modules 
• Unauthenticated user can install/uninstall modules 
• Failure to filter viewstate exception details can lead to reflective xss issue
• Remove OS identification code 
• Add additional checks to core input filter
• Change localized text to stop user enumeration 
• Ensure that profile properties are correctly filtered