Archive
Monthly
Go
|
|
DNN Blog
Jul
11
Posted by:
Chris Hammond
7/11/2007 9:00 AM
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. (found in 4.3.6, not sure about 4.4 or later releases)
in /controls/TextEditor.ascx line 9 replace id = ”celTextEditor” Runat=”Server” with id = "celTextEditor" Runat="Server"
The issue being the CURLY quotes. 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!
17 comment(s) so far...
Re: Did last night's Windows Update kill your DNN sites?
The quotes have been corrected in DotNetNuke 4.4.0
By leupold on
7/11/2007 9:48 AM
|
Re: Did last night's Windows Update kill your DNN sites?
take a look on :
http://www.dotnetnuke.com/Community/Forums/tabid/795/mid/2108/threadid/151719/scope/posts/Default.aspx#151749
By mic on
7/12/2007 12:39 PM
|
Re: Did last night's Windows Update kill your DNN sites?
Just ran into this problem on my 4.3.7 site. Corrected the quotes, and all is well. Thanks for the info!
By jnuw on
7/12/2007 1:47 PM
|
Re: Did last night's Windows Update kill your DNN sites?
I have confirmed this to be an issue with 4.3.7 sites as well. Thanks for pointing this out.
If you're having this problem, the error message will look like:
DotNetNuke.Services.Exceptions.ModuleLoadException: The Runat attribute must have the value Server. ---> System.Exception: The Runat attribute must have the value Server. ---> System.Web.HttpParseException: The Runat attribute must have the value Server.
By davido on
7/12/2007 1:48 PM
|
Re: Did last night's Windows Update kill your DNN sites?
I had an issue with Blog module. Thankfully someone found the problem. See http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/92/threadid/125139/postid/151755/threadpage/4/scope/posts/Default.aspx
By jhildebrant on
7/12/2007 10:28 PM
|
Re: Did last night's Windows Update kill your DNN sites?
I spent 1/2 of yesterday trying to find a solution to this. Thx for the heads-up.
By prigbye on
7/12/2007 10:29 PM
|
Re: Did last night's Windows Update kill your DNN sites?
I had 4.5.1 installed and spent 1/2 a day yesterday looking for why sites would not work. Looks like there are other issues that need correcting in later versions
By prigbye on
7/12/2007 10:29 PM
|
Re: Did last night's Windows Update kill your DNN sites?
We also had a problem with some online forms that sent out confirmation emails (No relation to DotNetNuke operability, but I wanted to give a heads-up that the problem in this post may not be all that the Windows update affected). Apparently, the same update must have affected the method that we were using to send emails. Our code did not return any errors, but the emails just never arrived. The timing corresponded exactly with this issue. I am not sure, but the problem may have been that I had imported the "System.net.Mail" namespace into my form using a lower-case "n" in "net. Other forms that used "System.Net.Mail" continued working just fine.
By KurtMer on
7/13/2007 12:59 PM
|
Re: Did last night's Windows Update kill your DNN sites?
I have the same error on 4.5.3, and fixing the quotes did nothing for me. Does anyone have a nother idea
By NamoGuy on
7/14/2007 12:08 AM
|
Re: Did last night's Windows Update kill your DNN sites?
I dont have the funny quotes but the ability to see or therefore select the HTML/Text module is missing any thoughts appreciated
By Arbatel on
7/16/2007 7:43 AM
|
Re: Did last night's Windows Update kill your DNN sites?
We are using 4.3.5 for our intranet. After I installed the update I noticed that when trying to edit an announcement it failed with an error.
I opened up 'EditAnnouncements.ascx' in Visual Studio and I noticed 17 warnings and errors, mostly related to HTML syntax (ie.
should be
and attributes should all be lower case, etc.)
I didn't have time to change the source so I just uninstalled the patch for now :(
By SCCdev2 on
7/18/2007 12:43 PM
|
Re: Did last night's Windows Update kill your DNN sites?
We are using 4.3.5 for our intranet. After I installed the update I noticed that when trying to edit an announcement it failed with an error.
I opened up 'EditAnnouncements.ascx' in Visual Studio and I noticed 17 warnings and errors, mostly related to HTML syntax (ie.
should be
and attributes should all be lower case, etc.)
I didn't have time to change the source so I just uninstalled the patch for now :(
By SCCdev2 on
7/19/2007 10:49 PM
|
Re: Did last night's Windows Update kill your DNN sites?
blog module, add entry blew up sometime around the 16th or 17th of july. I looked for incorrect quotes but do not see them. more info here: http://www.dotnetnuke.com/Community/Forums/tabid/795/mid/2108/threadid/153854/scope/posts/Default.aspx#153854
By morgan@morgancase.com on
7/19/2007 10:49 PM
|
Re: Did last night's Windows Update kill your DNN sites?
Thanks it works
By osousa26 on
8/3/2007 10:36 AM
|
Re: Did last night's Windows Update kill your DNN sites?
I'm having this issue with almost every module. I'm on version 4.3.5. I've done no coding to the site myself. Anyway to fix this, GoDaddy just washes their hands from any wrong doing as well as any support for DNN.
By packman73 on
8/16/2007 1:10 PM
|
Re: Did last night's Windows Update kill your DNN sites?
Packman, you best bet will probably be to upgrade your DNN instance on Godaddy if you have the option to do so. I'd recommend upgrading to 4.5.5
By christoc on
8/16/2007 1:10 PM
|
Re: Did last night's Windows Update kill your DNN sites?
I have been trying to find the problem with my DNN sites on godaddy for months now. The quotes were curly exactly as Chris stated. Changing them to regular fixed the text/html module not being available problem!
By kkginc on
12/31/2007 1:14 AM
|
|