[wp-trac] [WordPress Trac] #37166: Correct way of rendering an wp_editor outside of the basic browser request cycle

[WordPress Trac]

#37166: Correct way of rendering an wp_editor outside of the basic browser request
cycle
-----------------------------+-----------------------------
 Reporter:  andreiglingeanu  |       Owner:
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Future Release
Component:  Editor           |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+-----------------------------
Changes (by azaozz):

 * focuses:  administration, template =>
 * milestone:  Awaiting Review => Future Release


Comment:

 `wp_editor()` is meant to make it (very) easy to output the exact same
 editor like on the Edit Post screens, including TinyMCE initialization,
 Quicktags/Text editor, etc.

 You can also use it to output multiple editor instances with different
 configuration on the same screen, as long as you need them to be pretty
 similar to the Edit Post editor.

 If you need to use TinyMCE in a different way like inline instance(s),
 dynamically added instance(s), in a modal, etc. you would generally need
 to initialize it yourself. In its current state `wp_editor()` is not meant
 to handle all the different ways TinyMCE can be used.

 On the other hand it's time to look again at `wp_editor()` and see how we
 can improve it so plugins can make better use of it. Ideas and example
 patches welcome :)

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37166#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform