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 |
|---|---|
| 668 | $scheme = 'secure_auth'; |
| 669 | } else { |
| 670 | $auth_cookie_name = AUTH_COOKIE; |
| 671 | $scheme = 'auth'; |
| 672 | } |
| 673 | |
| 674 | $auth_cookie = wp_generate_auth_cookie($user_id, $expiration, $scheme); |
| 675 | $logged_in_cookie = wp_generate_auth_cookie($user_id, $expiration, 'logged_in'); |
| 676 | |
| 677 | do_action('set_auth_cookie', $auth_cookie, $expire, $expiration, $user_id, $scheme); |
| 678 | do_action('set_logged_in_cookie', $logged_in_cookie, $expire, $expiration, $user_id, 'logged_in'); |
| 679 | |
| 680 | setcookie($auth_cookie_name, $auth_cookie, $expire, PLUGINS_COOKIE_PATH, COOKIE_DOMAIN, $secure, true); |
| 681 | setcookie($auth_cookie_name, $auth_cookie, $expire, ADMIN_COOKIE_PATH, COOKIE_DOMAIN, $secure, true); |
| 682 | setcookie(LOGGED_IN_COOKIE, $logged_in_cookie, $expire, COOKIEPATH, COOKIE_DOMAIN, $secure_logged_in_cookie, true); |
| 683 | if ( COOKIEPATH != SITECOOKIEPATH ) |
| 684 | setcookie(LOGGED_IN_COOKIE, $logged_in_cookie, $expire, SITECOOKIEPATH, COOKIE_DOMAIN, $secure_logged_in_cookie, true); |
| 685 | } |
| 686 | endif; |