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 |
|---|---|
| 523 | * |
| 524 | * @since 2.8.0 |
| 525 | * @since 4.5.0 `$username` now accepts an email address. |
| 526 | * |
| 527 | * @param null|WP_User|WP_Error $user WP_User if the user is authenticated. |
| 528 | * WP_Error or null otherwise. |
| 529 | * @param string $username Username or email address. |
| 530 | * @param string $password User password |
| 531 | */ |
| 532 | $user = apply_filters( 'authenticate', null, $username, $password ); |
| 533 | |
| 534 | if ( $user == null ) { |
| 535 | // TODO what should the error message be? (Or would these even happen?) |
| 536 | // Only needed if all authentication handlers fail to return anything. |
| 537 | $user = new WP_Error( 'authentication_failed', __( '<strong>ERROR</strong>: Invalid username, email address or incorrect password.' ) ); |
| 538 | } |
| 539 | |
| 540 | $ignore_codes = array('empty_username', 'empty_password'); |
| 541 | |