Opened 6 years ago
Closed 5 years ago
#4708 closed defect (bug) (fixed)
Change "mode" Option for TinyMCE
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | low | Milestone: | 2.5 |
| Component: | TinyMCE | Version: | 2.3 |
| Severity: | trivial | Keywords: | has-patch |
| Cc: | cpoteet |
Description
The option "mode" has deprecated the usage of "specific_textareas". Suggest we change it to:
tiny_mce_config.php
mode : "exact", editor_selector : "mceEditor", elements: "content"
Maybe make that "elements" pluggable to allow theme developers to add other textareas in admin section.
Attachments (1)
Change History (9)
comment:2
Otto42
— 6 years ago
Considering that WordPress is already using the editor_selector, wouldn't mode: "textareas" work just as well? Having to specify the specific ID of the textarea when you can simply add mceEditor to it as a class seems silly.
http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/editor_selector
comment:3
cpoteet
— 6 years ago
That is as long as were comfortable turning every textarea in the admin section to a visual editor.
comment:4
Otto42
— 6 years ago
Ummm.. Then what, exactly, is the point of "editor_selector"? Because from what that page says, that will let you only turn areas marked with the mceEditor class into visual editors.
comment:5
Otto42
— 6 years ago
As a matter of fact, I'm right. "specific_textareas" is exactly the same as "textareas". Look at tiny_mce.js, line 1638.
Changing it to "textareas" will work and it won't turn all textareas into visual editors, because we're using an editor_selector.
Otto42
— 6 years ago
Trunk patch: Eliminate use of deprecated "specific_textareas" option in TinyMCE configuration.
Oh and here is the URL explaining the deprecation
http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/mode