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 |
|---|---|
| 268 | * The load-* hook fires in a number of contexts. This hook is for plugin screens |
| 269 | * where the file to load is directly included, rather than the use of a function. |
| 270 | * |
| 271 | * The dynamic portion of the hook name, `$plugin_page`, refers to the plugin basename. |
| 272 | * |
| 273 | * @see plugin_basename() |
| 274 | * |
| 275 | * @since 1.5.0 |
| 276 | */ |
| 277 | do_action( "load-{$plugin_page}" ); // phpcs:ignore WordPress.NamingConventions.ValidHookName.UseUnderscores |
| 278 | |
| 279 | if ( ! isset( $_GET['noheader'] ) ) { |
| 280 | require_once ABSPATH . 'wp-admin/admin-header.php'; |
| 281 | } |
| 282 | |
| 283 | if ( file_exists( WPMU_PLUGIN_DIR . "/$plugin_page" ) ) { |
| 284 | include WPMU_PLUGIN_DIR . "/$plugin_page"; |
| 285 | } else { |
| 286 | include WP_PLUGIN_DIR . "/$plugin_page"; |