DotNetNuke Issues

FCK Editor Wraps ALL Text Entries with (P) tags

Rick Stam — 2007-12-14T06:54:30Z

This causes Firefox to always display some blank space before the first line of text, while IE does not. For the long story, and fix options read the DotNetNuke Forum post at: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/127/threadid/153307/scope/posts/Default.aspx Suggested fixes: 1) In the fckconfig.js file replace (in \Providers\HtmlEditorProviders\Fck\FCKeditor) FCKConfig.EnterMode = 'p' ; with FCKConfig.EnterMode = 'br' ; /* or 'div' */ 2) Use CSS to set the properties to: p {margin-top: 0px; margin-bottom: 3px;} Both solutions have favorable arguments: The first avoids FCK from modifying the HTML, while the second provides more standardized HTML and a uniform way of controlling the tag formating. Also, check for updates to the DNN FCK Editor Provider, since these issues are currently being addressed. OK, I've had better results with the CSS solution. Setting the margin-top to 0 solves the problem with Firefox, but I'd rather not set the margin-bottom (use the default, which follows the font size). So you can set p { margin-top: 0px; } either in the \Portals\_default\default.css or in the appropriate skin.css, if you don't want to change the default for all portals.

Pinned Threads Don't Show in Agreggated Forum

Rick Stam — 2007-12-09T21:12:42Z

Pinned Threads Don't Show in Agreggated Forum. This is a result of the (way too complex!) dbo.Forum_Thread_GetAll() stored procedure. Quick Fix (Hack): Remove (or comment out) the T.IsPinned = 0 condition from the SQL WHERE clauses (3 places) in the dbo.Forum_Thread_GetAll() stored procedure. Note: I can't guarantee that this will not cause undesired side effects for other functionalities of the site. So far I haven't seen any...

HTML Text Disappears from Blog Entry Text when edited

Rick Stam — 2007-12-09T00:05:42Z

There is an issue when editing blog entries that contain textual HTML code in the text. The blog's EditEntry.ascx.cb does a call to HtmlDecode() in the Page_Load Event that eliminates any HTML code in the entry's text. Quick Fix (Hack): Change to the following code in /DesktopModules/Blog/EditEntry.ascx.vb: Change: teBlogEntry.Text = Server.HtmlDecode(m_oEntry.Entry) to: teBlogEntry.Text = m_oEntry.Entry Recompile and copy the Blog.dll to the dnn\bin directory of the production server.

Careful Deleting DotNetNuke Site Users

Rick Stam — 2007-12-08T09:07:06Z

Be carful when deleting users from a DotNetNuke site. You should delete all the user's 'owned' content (such as the users Blog) before deleting the user, or you might end up with 'orphaned' records in the database. You may then get the infimous 'Object Reference not set to an Instance of the Object' errors :( A safer approach could be to 'Unauthorize' the user instead of deleting it. This will also prevent the user from re-regestering again with the same credentials. Note: To be fair to the DotNetNuke developers, I'm not claiming that this 'orphaned records' problem is very common, but I have had it happen to me (when deleteing a user that owned a blog). A good recomendation, as always, is to make backups before doing anything that could cause problems.