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 |
|---|---|
| 281 | |
| 282 | // Load the functions for the active theme, for both parent and child theme if applicable. |
| 283 | if ( ! defined( 'WP_INSTALLING' ) || 'wp-activate.php' === $pagenow ) { |
| 284 | if ( TEMPLATEPATH !== STYLESHEETPATH && file_exists( STYLESHEETPATH . '/functions.php' ) ) |
| 285 | include( STYLESHEETPATH . '/functions.php' ); |
| 286 | if ( file_exists( TEMPLATEPATH . '/functions.php' ) ) |
| 287 | include( TEMPLATEPATH . '/functions.php' ); |
| 288 | } |
| 289 | |
| 290 | do_action( 'after_setup_theme' ); |
| 291 | |
| 292 | // Set up current user. |
| 293 | $wp->init(); |
| 294 | |
| 295 | /** |
| 296 | * Most of WP is loaded at this stage, and the user is authenticated. WP continues |
| 297 | * to load on the init hook that follows (e.g. widgets), and many plugins instantiate |
| 298 | * themselves on it for all sorts of reasons (e.g. they need a user, a taxonomy, etc.). |
| 299 | * |