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 |
---|---|
1479 | $valid = ( $sanitized == $username ); |
1480 | /** |
1481 | * Filter whether the provided username is valid or not. |
1482 | * |
1483 | * @since 2.0.1 |
1484 | * |
1485 | * @param bool $valid Whether given username is valid. |
1486 | * @param string $username Username to check. |
1487 | */ |
1488 | return apply_filters( 'validate_username', $valid, $username ); |
1489 | } |
1490 |
|
1491 | /** |
1492 | * Insert an user into the database. |
1493 | * |
1494 | * Most of the $userdata array fields have filters associated with the values. |
1495 | * The exceptions are 'rich_editing', 'role', 'jabber', 'aim', 'yim', |
1496 | * 'user_registered', and 'ID'. The filters have the prefix 'pre_user_' followed |
1497 | * by the field name. An example using 'description' would have the filter |