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 |
|---|---|
| 1850 | * |
| 1851 | * @return string Either 'tinymce', or 'html', or 'test' |
| 1852 | */ |
| 1853 | function wp_default_editor() { |
| 1854 | $r = user_can_richedit() ? 'tinymce' : 'html'; // defaults |
| 1855 | if ( $user = wp_get_current_user() ) { // look for cookie |
| 1856 | $ed = get_user_setting('editor', 'tinymce'); |
| 1857 | $r = ( in_array($ed, array('tinymce', 'html', 'test') ) ) ? $ed : $r; |
| 1858 | } |
| 1859 | return apply_filters( 'wp_default_editor', $r ); // filter |
| 1860 | } |
| 1861 | |
| 1862 | /** |
| 1863 | * Renders an editor. |
| 1864 | * |
| 1865 | * Using this function is the proper way to output all needed components for both TinyMCE and Quicktags. |
| 1866 | * _WP_Editors should not be used directly. See http://core.trac.wordpress.org/ticket/17144. |
| 1867 | * |
| 1868 | * NOTE: Once initialized the TinyMCE editor cannot be safely moved in the DOM. For that reason |