Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...HTML Editor in module settingsHTML Editor in module settings
Previous
 
Next
New Post
9/26/2012 1:46 PM
 

Can I add an HTML Editor to my custom module settings? I tried adding a TextEditor control, but I'm not sure that's the right control. 

If that is correct, how can I set the text value of the editor when the module loads? There's no "Text" property

 
New Post
9/26/2012 8:13 PM
 

Please see the following DotNetNuke Wiki entry:

http://www.dotnetnuke.com/Resources/W...


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
9/27/2012 1:10 PM
 

Thanks for the reply William. I actually started with that Wiki post. It turns out the problem was in my designer.cs file. For some reason the TextEditor control was set as 

System.Web.UI.UserControl, rather than 
DotNetNuke.UI.UserControls.TextEditor

I've seen this before, but don't understand why it happens. In any case, I'll have to remember to check the .designer.cs file from now on.

Thanks again

 
New Post
9/27/2012 9:15 PM
 

I thought that the issue might be in VS not assigning the correct class to the control in the designer file but had to make sure that you were properly referencing the TextEditor control in your markup.

I have had this same issue happen to me many times with the TextEditor control, the DnnLabel control, and some of the other "core" user controls. Most of my VS development of DNN modules is done "outside" of a DNN installation's DesktopModules folder as I like to avoid closely tying the development to a particular DNN installation's DesktopModules folder except during testing and debugging. I have tried all sorts of configuration of the project's Web references, IIS root application URL override, etc. without completely eliminating the problem. I too have had to manually edit the designer file.

Keep in mind, however, that any further changes you make to the markup may force the designer file to be re-generated - in which case you will have to again manually update the TextEditor controls class in the newly-generated designer file.

 


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
9/28/2012 6:03 PM
 

I just discovered this same thing, and returned to the forums to ask for a solution. Every time I touch my Settings.ascx file, it seems to re-set all my dnn controls (LabelControl, TextEditor so far) to some .NET version ie System.Web.UI.WebControls.

It's a total pain. Do you know if anyone is working on it? It seems like I should be able to register these DNN control somewhere to avoid this issue.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...HTML Editor in module settingsHTML Editor in module settings


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out