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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesUsing TextEditor in new moduleUsing TextEditor in new module
Previous
 
Next
New Post
7/27/2014 4:20 PM
 

I'm not sure if anyone else has run into this issue with using  TextEditor control in a custom module, but wanted to share my experience in case it helps someone.

I had need to create a few custom profile pages for different roles on a site.  My goal was to emulate the basic functionality of the default Activity-Fee/Profile edit page and really wanted the collapsible  tabs.

To this end, I created a new module using Chris Hammonds template (thanks again for this...PS.  I was NOT using the DAL2 template).

Everything was working well until the point of adding the TextEditor control for the Company Info/Bio section.

This was added at the top of my control file: <%@ Register TagPrefix="dnn" TagName="TextEditor" Src="~/controls/TextEditor.ascx"%>

 Instantiated down in the form like this: <dnn:TextEditor runat="server" id="txtClientData" height="400" width="100%" />

And it immediately broke the dnnTabs().dnnPanels(); that previously worked on the first 3 sections added to the form.  I borrowed the javascript from EditUser.ascx file as that page used the same control and obviously worked.

<script language="javascript" type="text/javascript">
    /*globals jQuery, window, Sys */
    (function ($, Sys) {
        function setUpDnnEditUser() {
            $('#divProfile').dnnTabs().dnnPanels();
        }

        $(document).ready(function () {
            setUpDnnEditUser();
            Sys.WebForms.PageRequestManager.getInstance().add_endRequest(function () {
                setUpDnnEditUser();
            });
        });
    } (jQuery, window.Sys));
</script>

 

As I said, the 3 tabs already in place for Name, Address, Contact Info were setup and worked.  This didn't break until adding the TextEditor.ascx control.

I tried multiple variations of Javascript and JQuery to enter a .noConflict(); resolution with no success.

In the end, I had to install the CKEditor HTML Editor as my default Editor control.  This got the tabs working again up to the point where AutoSave tried to save the content (25 seconds default).  I had to then go into the configuration of the editor and remove AutoSave from the extensions used by the CKEditor.

Success.

PostScript Note: Because my skin does use some JQuery plugins as well, I did try changing to the default Gravity skin prior to installation of the CKEditor Control.  This resulted in no difference.  There still seemed to be some sort of jQuery conflict, but yet, I didn't see any instance of jQuery being used by the text editor control.

In the end the point is to have the functionality you want, which I now have, but I sure wish I could have figured out why the original code didn't work instead of having to install and configure a separate HTMLEditor control to work around the issue.

 

 
New Post
7/28/2014 7:02 AM
 

Hi could this be to do with a naming issue, the texteditor of the jquery functions?

Regards,

Geoff


      
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesUsing TextEditor in new moduleUsing TextEditor in new module


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