Welcome, visitor! Log in
 

Source View: after_setup_theme

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: 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.

Source View

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