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 |
|---|---|
| 377 | * The load-* hook fires in a number of contexts. This hook is for core screens. |
| 378 | * |
| 379 | * The dynamic portion of the hook name, `$pagenow`, is a global variable |
| 380 | * referring to the filename of the current screen, such as 'admin.php', |
| 381 | * 'post-new.php' etc. A complete hook for the latter would be |
| 382 | * 'load-post-new.php'. |
| 383 | * |
| 384 | * @since 2.1.0 |
| 385 | */ |
| 386 | do_action( "load-{$pagenow}" ); // phpcs:ignore WordPress.NamingConventions.ValidHookName.UseUnderscores |
| 387 | |
| 388 | /* |
| 389 | * The following hooks are fired to ensure backward compatibility. |
| 390 | * In all other cases, 'load-' . $pagenow should be used instead. |
| 391 | */ |
| 392 | if ( 'page' === $typenow ) { |
| 393 | if ( 'post-new.php' === $pagenow ) { |
| 394 | do_action( 'load-page-new.php' ); // phpcs:ignore WordPress.NamingConventions.ValidHookName.UseUnderscores |
| 395 | } elseif ( 'post.php' === $pagenow ) { |