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 |
|---|---|
| 173 | $ext_plugins = ''; |
| 174 | } else { |
| 175 | /* |
| 176 | The following filter takes an associative array of external plugins for TinyMCE in the form 'plugin_name' => 'url'. |
| 177 | It adds the plugin's name to TinyMCE's plugins init and the call to PluginManager to load the plugin. |
| 178 | The url should be absolute and should include the js file name to be loaded. Example: |
| 179 | array( 'myplugin' => 'http://my-site.com/wp-content/plugins/myfolder/mce_plugin.js' ) |
| 180 | If the plugin uses a button, it should be added with one of the "$mce_buttons" filters. |
| 181 | */ |
| 182 | $mce_external_plugins = apply_filters('mce_external_plugins', array()); |
| 183 | |
| 184 | $ext_plugins = ''; |
| 185 | if ( ! empty($mce_external_plugins) ) { |
| 186 | |
| 187 | /* |
| 188 | The following filter loads external language files for TinyMCE plugins. |
| 189 | It takes an associative array 'plugin_name' => 'path', where path is the |
| 190 | include path to the file. The language file should follow the same format as |
| 191 | /tinymce/langs/wp-langs.php and should define a variable $strings that |