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 |
|---|---|
| 188 | * match the format used by API methods internally (that is, the `status` |
| 189 | * data should be used). A callback can return `true` to indicate that |
| 190 | * the authentication method was used, and it succeeded. |
| 191 | * |
| 192 | * @since 4.4.0 |
| 193 | * |
| 194 | * @param WP_Error|null|true $errors WP_Error if authentication error occurred, null if authentication |
| 195 | * method wasn't used, true if authentication succeeded. |
| 196 | */ |
| 197 | return apply_filters( 'rest_authentication_errors', null ); |
| 198 | } |
| 199 | |
| 200 | /** |
| 201 | * Converts an error to a response object. |
| 202 | * |
| 203 | * This iterates over all error codes and messages to change it into a flat |
| 204 | * array. This enables simpler client behavior, as it is represented as a |
| 205 | * list in JSON rather than an object/map. |
| 206 | * |