Now it's turned off/on via url filter. It's not flexible solution.

It would be great if TinyMCE will turn on/off per specific textarea like HTMLarea in its settings (ex. "comment/edit.comment" is on or "node/add/blog.body").

Comments

JohnG-1’s picture

Title: Dynamically turn off/on TinyMCE per textarea field » Remove TinyMCE toggle per textarea field
Component: Code » User interface

apologies if the bump & subject shift are inappropriate, but:

Is the 'enable rich-text' / 'disable rich-text' toggle necessary? in what circumstances is the local toggle required?

From a UI point of view, the 'Edit HTML Source' button gives users all they need for HTML editing. The button is currently only in advanced profile - which makes sense! - but I understand that an admin-button-selection interface is in the drupal pipeline.

By enabling a wysiwyg interface to a textarea, the admin is saying : "the content of this field is going to be html". If you're expecting input other than HTML in this field, you wouldn't enable the wysiwig interface! So why would you want to give all and sundry a way round it?

Are there browser compatibility or other issues I'm not aware of?

What else would you want to put in there?

m3avrck’s picture

Status: Active » Fixed

You can turn off or on TinyMCE per textarea by overriding the theme() in the next version of TinyMCE. See the documentation for this, it is quite easy.

Additionally, there are new visibility rules so you can be much more picky about what pages TinyMCE appears on.

The enable/disable button is useful, becuase TinyMCE can be on or off by default. Many times I prefer it off by default to add certain content, but sometimes it is nice for me (or other users) to be on by default because it makes it easier. Makes it more flexible this way instead of always on or always off. Sometimes you want it mixed, so it's easy with the toggle button.

Anonymous’s picture

Status: Fixed » Closed (fixed)