"DotNetNuke 6.1.1 and 5.6.5 are officially released. These maintenance releases contain a couple of updates that emphasize our commitment to backwards compatibility. DotNetNuke 6.1 inadvertently changed the default load order for CSS files. In addition, the behavior of the HTML module changed slightly due to new content filtering capabilities.

While our intent was to release DotNetNuke 6.1.1 in early January along with many other fixes, we felt that since these issues were related to backwards compatibility it would be best to address these items as soon as possible. Below is a summary of the major changes for this release. For more information about a specific issue please refer to the official change log.

Major Highlights

6.1.1 - Fixed problem with the core skin object rendering CSS above the other framework inserted files, which caused problems when using core style skin objects
6.1.1/5.6.5 - Fixed issue with iFrames getting removed when content is saved
6.1.1/5.6.5 - Fixed issue with the HTML module removing styling and scripts from the content
6.1.1 - Fixed issue with inserting the link to jQuery after the header of the page"


--------------------
Several people have noted the impact of these issues ... so I recommend that you take a look at the new releases.

Excellent!

I was holding off on updating to 6.1 due to using the HTML module for many javascript and adsense and google map implementations, as well as having html fields that contain said content in my article modules!

Great news, chalk up a win for the users of DotNetNuke!