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 |
|---|---|
| 838 | * to be valid as they come directly from a client-provided cookie value. |
| 839 | * |
| 840 | * @type string $username User's username. |
| 841 | * @type string $expiration The time the cookie expires as a UNIX timestamp. |
| 842 | * @type string $token User's session token used. |
| 843 | * @type string $hmac The security hash for the cookie. |
| 844 | * @type string $scheme The cookie scheme to use. |
| 845 | * } |
| 846 | */ |
| 847 | do_action( 'auth_cookie_bad_username', $cookie_elements ); |
| 848 | return false; |
| 849 | } |
| 850 | |
| 851 | if ( str_starts_with( $user->user_pass, '$P$' ) || str_starts_with( $user->user_pass, '$2y$' ) ) { |
| 852 | // Retain previous behaviour of phpass or vanilla bcrypt hashed passwords. |
| 853 | $pass_frag = substr( $user->user_pass, 8, 4 ); |
| 854 | } else { |
| 855 | // Otherwise, use a substring from the end of the hash to avoid dealing with potentially long hash prefixes. |
| 856 | $pass_frag = substr( $user->user_pass, -4 ); |