Pass post type as a class to TinyMCE init

[markjaquith]

If we pass the post type as a class to TinyMCE, editor-styles.css can target rules to specific post types which may be displayed differently.

<?php wp_editor($post->post_content, 'content', array('dfw' => true, 'tabindex' => 1, 'tinymce' => array( 'body_class' => 'post-type-' . $post_type ) ) ); ?>

[nacin]

+100. Ran into this earlier today.

[azaozz]

Been looking into something similar recently too. However to set anything into TinyMCE's iframe it has to go through JS (as it's 100% JS generated). So we need a JS "helper" function to modify classes (and IDs?) in the iframe document.

Seems the best way to do this would be to handle it from one of our custom TinyMCE plugins: we can pass extra classes as MCE init setting and then apply them from the plugin.

Also it seems we need to make editor-style.css more structured/predictable. There are styles/selectors that shouldn't go in there and all selectors should be exactly the same as in the theme's style.css.

[johnjamesjacoby]

Just dropping a note while it's on my mind, this will become increasingly more important as plugins (like bbPress/BuddyPress) start including wp_editor() in places outside of the traditional post editor; within the theme, for example.

[gluten]

It would also be useful to have a class added with the wp_editor() $editor_id to allow for unique styling of TinyMCE editors.

[azaozz]

3.4 as part of the editor enhancements.

[azaozz]

In [19912]:

Add the editor ID and the post type (when available) as classes to the TinyMCE's body, fixes #19437

[jamescollins]

For security, do we need to esc_attr() the $body_class variable?

That's what we do at the end of the get_body_class() function (​http://core.trac.wordpress.org/browser/trunk/wp-includes/post-template.php#L545).

[ocean90]

See #20009

[azaozz]

Replying to jamescollins:

For security, do we need to esc_attr() the $body_class variable?

Don't see a point in escaping the editor ID or the post_type strings.

That's what we do at the end of the get_body_class() function (​http://core.trac.wordpress.org/browser/trunk/wp-includes/post-template.php#L545).

Right, seems that's not needed there either, the HTML class attribute allows all UTF-8 chars with very few exceptions.

[azaozz]

In [20054]:

Improve adding more css classes to the editor body, add "rtl", "ie7", "ie8", "ie9" so they can be targeted in editor-style.css, see #19437

[azaozz]

In [20059]:

Don't pass non-existing rtl stylesheet to TinyMCE, update phpdoc for add_editor_style(), see #19437

[SergeyBiryukov]

[20059] brings back #18457. 19437.child-editor-style.patch​ is an attempt to fix that.

[azaozz]

Replying to SergeyBiryukov:

Wouldn't that add the child theme's stylesheet before the parent theme's? At first look in the patch the parent theme loop is after the child theme loop:

Edit: nevermind, that's otherwise round. It's the differences between get_stylesheet_directory() and get_template_directory().

[azaozz]

In [20342]:

Fix adding of parent theme's editor-style before child theme's, props SergeyBiryukov, see #19437

[azaozz]

Seems to work properly