Ability to Supply Different TinyMCE Configurations

Favorite-off Notification-off
21 Thumb-up Thumb-down
Idea by tim.reilly about 1 year ago Favorite-off - Open

This is a continuation of the feature request located here.

Would like the ability to have control over:

    * buttons
    * content validation (allowed/disallowed content)
    * plugins

Buttons

Allow control over which buttons can be used in the WYSIWYG editor.

Content Validation

TinyMCE has a right language for disallowing/allowing certain types of contents that could be used, for example, to enforce XHTML strict content in the WYSIWYG if the user so desired or even a smaller subset of a just a few tags/attributes.
Plugins

Allow arbitrary plugins to be included.

This one is a really tough call, because there are tons and tons of plugins out there. The support implications are the main concern.
Solutions

The easiest mechanism for doing this would be to allow CMS administrators to supply their own JSON object containing the configuration of TinyMCE that is passed when TinyMCE is initialized. However, Hannon Hill would need to figure out its support policy with respect to various configurations as there is a high risk of crippling the WYSIWYG or causing significant behavior changes

No comments

No attachments


* Note - To input code samples, click the pencil icon (this will remove the WYSIWYG) then be sure to start and end code sections with @@@ (three '@' signs).  For more information on textile markup, click here.  

Sign in

Follow us on Twitter