DotNetNuke 6.1.x Release and Warning! 

As I'm sure that you have seen in the last day or so DotNetNuke 6.1.0 was released.  Overall, this release is a major improvement for DotNetNuke with enhancements to performance, support for mobile devices and other general upgrades.  However, I've already been alerted to a major, slightly hidden change that I wanted to be sure to put out here as a warning.

If you look at the release notes there are references to updates to the Text/HTML Module and the Telerik Editor.  However, my attention was brought to this posting Telerik Editor on 6.1.0 this morning.  On the surface this doesn't seem to be a big deal, but for some of my regular content editors there are a lot of issues with this.

To spare you from reading the thread I'll summarize the issue, with 6.1.0 all javascript that is included in the Text/HTML module (Rich Text Editor) regardless of the mode used for the editor will be removed.  What this means is that people managing content such as Google Analytics, Google Adsense, Custom jQuery implementations, or any other number of custom implementions that require <script> tags to be included in their HTML content will no-longer be able to manage that content.

Now, this isn't an issue for everyone, but it is a change in behavior that could cause issues for some.  Other highlights though in this release include a lot better handling of mobile and other devices as well as streamlined support/minification of CSS other resources!

UPDATE:

I have found out that this also affects 5.6.4 as well.

 

Posted by Mitchel on Wednesday, November 02, 2011
Tags: DotNetNuke, DotNetNuke Administration
 

Comments

This is not a "major hidden change" it's a screw up of major proportions. Clients use scripts in their code all the time. This "change" is worse than the description implies. They changed something at the DATABASE level that purges scripts. This means that even if you move to fck or ck editor or something other than telerik or rad there is no way to get the content back with the script into the system. We've already rolled two sites back from 6.1 because of this. The system is unusable and unacceptable as is, and to make this change without plastering a million warnings in large red letters all over everything that says something like "applying this will disable your ability to embed scripts in html permanently" is simply unacceptable. They obviously knew the consequences based on the response in the forum.

By Lee Drake on Wednesday, November 02, 2011 at 4:21 PM

Thanks Mitch, for this heads up - this would have hosed all my sites.

By Bill on Thursday, November 03, 2011 at 11:43 AM

Easiest way around this is to use the module footer field in the settings.

By Lance on Friday, November 04, 2011 at 2:00 PM

Lance,

Yes that works in a lot of cases, but not for everything, or if you need to do stuff inline.

By mitchel.sellers@gmail.com on Friday, November 04, 2011 at 2:04 PM

This has got to be one of the bigger stuff ups from DNN for some time ... and it would appear its also effecting not just

Friend of RedGate

www.datasprings.com - DotNetNuke Modules ICG Hosting

Click here for advertising information.

Content in this blog is copyright protected.  Re-publishing on other websites is allowed as long as proper credit and backlink to the article is provided.  Any other re-publishing or distribution of this content is prohibited without written permission from Mitchel Sellers.