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 |
|---|---|
| 634 | * |
| 635 | * Most of WP is loaded at this stage, and the user is authenticated. WP continues |
| 636 | * to load on the {@see 'init'} hook that follows (e.g. widgets), and many plugins instantiate |
| 637 | * themselves on it for all sorts of reasons (e.g. they need a user, a taxonomy, etc.). |
| 638 | * |
| 639 | * If you wish to plug an action once WP is loaded, use the {@see 'wp_loaded'} hook below. |
| 640 | * |
| 641 | * @since 1.5.0 |
| 642 | */ |
| 643 | do_action( 'init' ); |
| 644 | |
| 645 | // Check site status. |
| 646 | if ( is_multisite() ) { |
| 647 | $file = ms_site_check(); |
| 648 | if ( true !== $file ) { |
| 649 | require $file; |
| 650 | die(); |
| 651 | } |
| 652 | unset( $file ); |