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 |
|---|---|
| 1773 | * |
| 1774 | * @return string Either 'tinymce', or 'html', or 'test' |
| 1775 | */ |
| 1776 | function wp_default_editor() { |
| 1777 | $r = user_can_richedit() ? 'tinymce' : 'html'; // defaults |
| 1778 | if ( $user = wp_get_current_user() ) { // look for cookie |
| 1779 | $ed = get_user_setting('editor', 'tinymce'); |
| 1780 | $r = ( in_array($ed, array('tinymce', 'html', 'test') ) ) ? $ed : $r; |
| 1781 | } |
| 1782 | return apply_filters( 'wp_default_editor', $r ); // filter |
| 1783 | } |
| 1784 | |
| 1785 | /** |
| 1786 | * Renders an editor. |
| 1787 | * |
| 1788 | * Using this function is the proper way to output all needed components for both TinyMCE and Quicktags. |
| 1789 | * _WP_Editors should not be used directly. See http://core.trac.wordpress.org/ticket/17144. |
| 1790 | * |
| 1791 | * NOTE: Once initialized the TinyMCE editor cannot be safely moved in the DOM. For that reason |