Did last night's Windows Update kill your DNN sites?

(Updated )
Did last night's Windows Update kill your DNN sites?

There apparently were two .Net Security Patches made available last night in WIndows Update. They are causing some problems with DNN, not sure which versions specifically, but I've seen issues reported in 4.3.6 and  4.3.5 so far.

Sebastian posted this in a forum earlier today as fix for the Text/HTML module no longer working.

in /controls/TextEditor.ascx line 9 replace id = ”celTextEditor” Runat=”Server” with id = "celTextEditor" Runat="Server"

The issue being the CURLY quotes (I don't know the proper term and am too lazy busy to look it up). I had another client with the same problem, they had curly quotes in their skin file instead of normal "" quotes, with windows update last night the skin immediately broke.

So if you're having some issues with your DNN sites, start looking for funky quotes and replacing them with standard quotes!

Posted from weblogs.asp.net/christoc

Recent Comments

There are currently no comments. Be the first to make a comment.

Add Comment

Please add your comment by filling out the field(s) below. Your comment may need to be approved before it becomes visible.
Enter your first name for display with the comment
Enter your last name for display with the comment.
Enter your comment here.
If you can't type DNNRocks in, you can't post, plain and simple.
Submit Comment Cancel

Chris Hammond

Chris Hammond is a father, husband, leader, software developer, photographer and car guy. Chris focuses on the latest in technology including artificial intelligence (AI) and has spent decades becoming an expert in ASP.NET and DotNetNuke (DNN) development. You will find a variety of posts relating to those topics here on the website. For more information check out the about Chris Hammond page.

Find me on Twitter, GitHub and LinkedIn.