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 |
|---|---|
| 295 | $wp->init(); |
| 296 | |
| 297 | /** |
| 298 | * Most of WP is loaded at this stage, and the user is authenticated. WP continues |
| 299 | * to load on the init hook that follows (e.g. widgets), and many plugins instantiate |
| 300 | * themselves on it for all sorts of reasons (e.g. they need a user, a taxonomy, etc.). |
| 301 | * |
| 302 | * If you wish to plug an action once WP is loaded, use the wp_loaded hook below. |
| 303 | */ |
| 304 | do_action( 'init' ); |
| 305 | |
| 306 | // Check site status |
| 307 | if ( is_multisite() ) { |
| 308 | if ( true !== ( $file = ms_site_check() ) ) { |
| 309 | require( $file ); |
| 310 | die(); |
| 311 | } |
| 312 | unset($file); |
| 313 | } |