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 |
|---|---|
| 250 | * 3. The plugin basename minus the file extension. |
| 251 | * |
| 252 | * Together, the three parts form the `$page_hook`. Citing the example above, |
| 253 | * the hook name used would be 'settings_page_pluginbasename'. |
| 254 | * |
| 255 | * @see get_plugin_page_hook() |
| 256 | * |
| 257 | * @since 1.5.0 |
| 258 | */ |
| 259 | do_action( $page_hook ); |
| 260 | } else { |
| 261 | if ( validate_file( $plugin_page ) ) { |
| 262 | wp_die( __( 'Invalid plugin page.' ) ); |
| 263 | } |
| 264 | |
| 265 | if ( ! ( file_exists( WP_PLUGIN_DIR . "/$plugin_page" ) && is_file( WP_PLUGIN_DIR . "/$plugin_page" ) ) |
| 266 | && ! ( file_exists( WPMU_PLUGIN_DIR . "/$plugin_page" ) && is_file( WPMU_PLUGIN_DIR . "/$plugin_page" ) ) |
| 267 | ) { |
| 268 | /* translators: %s: Admin page generated by a plugin. */ |