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 |
---|---|
1770 | /** |
1771 | * Filters a username after it has been sanitized. |
1772 | * |
1773 | * This filter is called before the user is created or updated. |
1774 | * |
1775 | * @since 2.0.3 |
1776 | * |
1777 | * @param string $sanitized_user_login Username after it has been sanitized. |
1778 | */ |
1779 | $pre_user_login = apply_filters( 'pre_user_login', $sanitized_user_login ); |
1780 |
|
1781 | // Remove any non-printable chars from the login string to see if we have ended up with an empty username. |
1782 | $user_login = trim( $pre_user_login ); |
1783 |
|
1784 | // user_login must be between 0 and 60 characters. |
1785 | if ( empty( $user_login ) ) { |
1786 | return new WP_Error( 'empty_user_login', __( 'Cannot create a user with an empty login name.' ) ); |
1787 | } elseif ( mb_strlen( $user_login ) > 60 ) { |
1788 | return new WP_Error( 'user_login_too_long', __( 'Username may not be longer than 60 characters.' ) ); |