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 |
|---|---|
| 205 | * 3. The plugin basename minus the file extension. |
| 206 | * |
| 207 | * Together, the three parts form the `$page_hook`. Citing the example above, |
| 208 | * the hook name used would be 'load-settings_page_pluginbasename'. |
| 209 | * |
| 210 | * @see get_plugin_page_hook() |
| 211 | * |
| 212 | * @since 2.1.0 |
| 213 | */ |
| 214 | do_action( "load-{$page_hook}" ); |
| 215 | if (! isset($_GET['noheader'])) |
| 216 | require_once(ABSPATH . 'wp-admin/admin-header.php'); |
| 217 | |
| 218 | /** |
| 219 | * Used to call the registered callback for a plugin screen. |
| 220 | * |
| 221 | * @ignore |
| 222 | * @since 1.5.0 |
| 223 | */ |