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 |
|---|---|
| 730 | * to be valid as they come directly from a client-provided cookie value. |
| 731 | * |
| 732 | * @type string $username User's username. |
| 733 | * @type string $expiration The time the cookie expires as a UNIX timestamp. |
| 734 | * @type string $token User's session token used. |
| 735 | * @type string $hmac The security hash for the cookie. |
| 736 | * @type string $scheme The cookie scheme to use. |
| 737 | * } |
| 738 | */ |
| 739 | do_action( 'auth_cookie_expired', $cookie_elements ); |
| 740 | return false; |
| 741 | } |
| 742 | |
| 743 | $user = get_user_by( 'login', $username ); |
| 744 | if ( ! $user ) { |
| 745 | /** |
| 746 | * Fires if a bad username is entered in the user authentication process. |
| 747 | * |
| 748 | * @since 2.7.0 |