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 |
|---|---|
| 540 | * |
| 541 | * @since 2.8.0 |
| 542 | * @since 4.5.0 `$username` now accepts an email address. |
| 543 | * |
| 544 | * @param null|WP_User|WP_Error $user WP_User if the user is authenticated. |
| 545 | * WP_Error or null otherwise. |
| 546 | * @param string $username Username or email address. |
| 547 | * @param string $password User password |
| 548 | */ |
| 549 | $user = apply_filters( 'authenticate', null, $username, $password ); |
| 550 | |
| 551 | if ( null == $user ) { |
| 552 | // TODO: What should the error message be? (Or would these even happen?) |
| 553 | // Only needed if all authentication handlers fail to return anything. |
| 554 | $user = new WP_Error( 'authentication_failed', __( '<strong>Error</strong>: Invalid username, email address or incorrect password.' ) ); |
| 555 | } |
| 556 | |
| 557 | $ignore_codes = array( 'empty_username', 'empty_password' ); |
| 558 | |