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 |
|---|---|
| 452 | * where 'path' is the include path to the file. |
| 453 | * |
| 454 | * The language file should follow the same format as wp_mce_translation(), |
| 455 | * and should define a variable ($strings) that holds all translated strings. |
| 456 | * |
| 457 | * @since 2.5.0 |
| 458 | * |
| 459 | * @param array $translations Translations for external TinyMCE plugins. |
| 460 | */ |
| 461 | $mce_external_languages = apply_filters( 'mce_external_languages', array() ); |
| 462 | |
| 463 | $loaded_langs = array(); |
| 464 | $strings = ''; |
| 465 | |
| 466 | if ( ! empty( $mce_external_languages ) ) { |
| 467 | foreach ( $mce_external_languages as $name => $path ) { |
| 468 | if ( @is_file( $path ) && @is_readable( $path ) ) { |
| 469 | include_once( $path ); |
| 470 | $ext_plugins .= $strings . "\n"; |