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 |
|---|---|
| 752 | * to be valid as they come directly from a client-provided cookie value. |
| 753 | * |
| 754 | * @type string $username User's username. |
| 755 | * @type string $expiration The time the cookie expires as a UNIX timestamp. |
| 756 | * @type string $token User's session token used. |
| 757 | * @type string $hmac The security hash for the cookie. |
| 758 | * @type string $scheme The cookie scheme to use. |
| 759 | * } |
| 760 | */ |
| 761 | do_action( 'auth_cookie_bad_username', $cookie_elements ); |
| 762 | return false; |
| 763 | } |
| 764 | |
| 765 | $pass_frag = substr( $user->user_pass, 8, 4 ); |
| 766 | |
| 767 | $key = wp_hash( $username . '|' . $pass_frag . '|' . $expiration . '|' . $token, $scheme ); |
| 768 | |
| 769 | // If ext/hash is not present, compat.php's hash_hmac() does not support sha256. |
| 770 | $algo = function_exists( 'hash' ) ? 'sha256' : 'sha1'; |