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 |
|---|---|
| 392 | * where 'path' is the include path to the file. |
| 393 | * |
| 394 | * The language file should follow the same format as wp_mce_translation(), |
| 395 | * and should define a variable ($strings) that holds all translated strings. |
| 396 | * |
| 397 | * @since 2.5.0 |
| 398 | * |
| 399 | * @param array $translations Translations for external TinyMCE plugins. |
| 400 | */ |
| 401 | $mce_external_languages = apply_filters( 'mce_external_languages', array() ); |
| 402 | |
| 403 | $loaded_langs = array(); |
| 404 | $strings = ''; |
| 405 | |
| 406 | if ( ! empty( $mce_external_languages ) ) { |
| 407 | foreach ( $mce_external_languages as $name => $path ) { |
| 408 | if ( @is_file( $path ) && @is_readable( $path ) ) { |
| 409 | include_once( $path ); |
| 410 | $ext_plugins .= $strings . "\n"; |