WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 240 | } |
| 241 | |
| 242 | /** |
| 243 | * Filter the HTML markup output that displays the editor. |
| 244 | * |
| 245 | * @since 2.1.0 |
| 246 | * |
| 247 | * @param string $output Editor's HTML markup. |
| 248 | */ |
| 249 | $the_editor = apply_filters( 'the_editor', '<div id="wp-' . $editor_id_attr . '-editor-container" class="wp-editor-container">' . |
| 250 | $quicktags_toolbar . |
| 251 | '<textarea' . $editor_class . $height . $tabindex . $autocomplete . ' cols="40" name="' . esc_attr( $set['textarea_name'] ) . '" ' . |
| 252 | 'id="' . $editor_id_attr . '">%s</textarea></div>' ); |
| 253 | |
| 254 | // Prepare the content for the Visual or Text editor, only when TinyMCE is used (back-compat). |
| 255 | if ( self::$this_tinymce ) { |
| 256 | add_filter( 'the_editor_content', 'format_for_editor', 10, 2 ); |
| 257 | } |
| 258 | |