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 |
|---|---|
| 1395 | /** |
| 1396 | * Filter a username after it has been sanitized. |
| 1397 | * |
| 1398 | * This filter is called before the user is created or updated. |
| 1399 | * |
| 1400 | * @since 2.0.3 |
| 1401 | * |
| 1402 | * @param string $sanitized_user_login Username after it has been sanitized. |
| 1403 | */ |
| 1404 | $pre_user_login = apply_filters( 'pre_user_login', $sanitized_user_login ); |
| 1405 | |
| 1406 | //Remove any non-printable chars from the login string to see if we have ended up with an empty username |
| 1407 | $user_login = trim( $pre_user_login ); |
| 1408 | |
| 1409 | // user_login must be between 0 and 60 characters. |
| 1410 | if ( empty( $user_login ) ) { |
| 1411 | return new WP_Error('empty_user_login', __('Cannot create a user with an empty login name.') ); |
| 1412 | } elseif ( mb_strlen( $user_login ) > 60 ) { |
| 1413 | return new WP_Error( 'user_login_too_long', __( 'Username may not be longer than 60 characters.' ) ); |