After upgrading DNN from version 4.4 to 4.5.3, we started having a problem with the FCK editor when it is embedded inside of a module's settings control and the user is using Firefox.  When the settings view first loads, you can not edit anything in the editor.  No matter how much you click on the content area, it will not place a cursor there to allow typing.  You can highlight the existing text, but you can not edit, delete, or add to it.  If you click on the button to change to the source view and then change back again, the editor wil then work normally from there on.  However, if you reload the page, the problem comes back again until you once again perform the work around of switching to source view and back.  The problem does not seem to be occurring with IE 6 at all (haven't checked 7), but it consistently occurs with Firefox.  The problem also seems to be isolated to when the editor is embedded inside of a module's settings control.  It works fine when it is embedded inside a regular module control such as in the standard Text/Html module.

Has anyone else seen this behavior?  Any ideas on how to fix it?

Thanks

Unfortunately, I don't have a test URL I can give you.  Since the problem is only occurring when the editor appears within a module's settings view, I'd have to provide an admin login to one of our public facing sites to demonstrate it.  I'm guessing some people might be a bit upset with me if I provided their admin login on a public message board. :)

However, I ran across this wiki entry this morning that I think may help explain the problem:

http://wiki.fckeditor.net/Troubleshooting#head-b3157703eeeef9d287b4c922f9b43eab9d551417

The problem described there sounds awfully similar to what we are seeing.  Since the custom settings part of the page is initially hidden when the module's settings view is loaded, I'm guessing that is what is causing the problem.  Since the logic to show/hide that part of the page is in the core settings control and we would prefer not to alter any core code if at all possible, that might make fixing it somewhat tricky.  Any ideas on that?

I found a solution to this.  Including the following javascript code in the custom settings control that contains the editor seems to fix it without causing any other adverse effects.

    function FCKeditor_OnComplete(editorInstance)
    {
        editorInstance.Events.AttachEvent('OnFocus', fckEditorOnFocus);
    }

    function fckEditorOnFocus(editorInstance)
    {
        if(editorInstance.MakeEditable)
        {
            editorInstance.MakeEditable();
        }
    }