[wp-trac] [WordPress Trac] #17144: Editor API enhancement

[WordPress Trac]

#17144: Editor API enhancement
----------------------------+---------------------
 Reporter:  azaozz          |       Owner:
     Type:  task (blessed)  |      Status:  closed
 Priority:  normal          |   Milestone:  3.3
Component:  Editor          |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  needs-patch     |
----------------------------+---------------------

Comment (by sushkov):

 Regarding the hooks:
 https://github.com/scholarpress/buddypress-
 courseware/blob/master/courses/courses.class.php#L397 (To load enqueues)
 https://github.com/scholarpress/buddypress-
 courseware/blob/master/groups/templates/edit_course.php#L13 (To render the
 editor, mind that now, `wp_tiny_mce()` gives a fatal error because it
 looks like `deprecated.php` is not loaded to properly inside the files
 that were containing it before)

 What about DFW, the plugin uses hard-coded stuff like:
 https://github.com/WordPress/WordPress/blob/master/wp-
 includes/js/tinymce/plugins/wpfullscreen/editor_plugin.dev.js#L37

 Where you can use something like:
 `ed = (tinyMCE.editors.length > 0) ? tinyMCE.editors[0] :
 tinymce.get('content');`

 Another problem is even DFW is passed as `true` the proper CSS is not
 loaded.

 So back to my initial argument, I can't see the real benefit of
 `wp_editor()` changes, because as an older developer of `wp-editor` API I
 still have to hack around to get things done!
 Another question is why would you decide to change code that was already
 working?!

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17144#comment:108>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software