Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

DataObjectManager Module

Discuss the DataObjectManager module, and the related ImageGallery module.

Moderators: martimiz, UncleCheese, Sean, biapar, Willr, Ingo, swaiba, simon_w

[solved] Using SimpleHtmlEditorField or SimpleWysiwygField in CMS?


5 Posts   1778 Views


19 July 2009 at 10:52pm (Last edited: 19 July 2009 11:33pm), Community Member, 901 Posts

Hello all

I wanted to use the SimpleWysiwygField in the CMS content editor tabs (not in a Popup) and it doesn't seem to work. No joy with the SimpleHtmlEditorField either...
Did anybody figure out to do this? I'd rather use the SimpleWysiwygField instead of TinyMCE since the Site Administrator should only have a very limited set of text-formatting capabilities.

Any pointers are welcome. Thanks.


19 July 2009 at 11:07pm (Last edited: 19 July 2009 11:33pm), Community Member, 901 Posts

I managed to make the SimpleHtmlEditorField to work.

Edit: Removed the patch. Doesn't work as expected... still looking for a solution.

Update: Used HtmlEditorConfig to configure good ol' TinyMCE to suit my needs. Problem solved.


20 July 2009 at 3:57am 4085 Posts

What exactly didn't work? I have several clients using it right now. If you could provide an exact error, I can put in a patch. Thanks.


20 July 2009 at 4:58am Community Member, 901 Posts

Hey UncleCheese

They both didn't work because of JavaScript library clashes. The SimpleWysiwygField throws some JavaScript errors, and the SimpleHtmlEditorField worked, after I changed your "Requirements::customScript" to a jQuery.noConflict variant. This only worked on Page load, but sadly not when page-content is being loaded via AJAX.

Are you sure your clients use the Editor in the CMS as TinyMCE replacement? It works fine in pop-ups, that's for sure. I'd be surprised if it works in the CMS Content-Tabs as it is now.


20 July 2009 at 5:41am 4085 Posts

Oh, okay, I misunderstood. Yeah, those two fields are meant for DOM popup windows only. That's why they come with the DOM package. I should make that clearer in the docs.