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 |
|---|---|
| 1665 | |
| 1666 | /** |
| 1667 | * Filters whether the provided username is valid. |
| 1668 | * |
| 1669 | * @since 2.0.1 |
| 1670 | * |
| 1671 | * @param bool $valid Whether given username is valid. |
| 1672 | * @param string $username Username to check. |
| 1673 | */ |
| 1674 | return apply_filters( 'validate_username', $valid, $username ); |
| 1675 | } |
| 1676 | |
| 1677 | /** |
| 1678 | * Insert a user into the database. |
| 1679 | * |
| 1680 | * Most of the `$userdata` array fields have filters associated with the values. Exceptions are |
| 1681 | * 'ID', 'rich_editing', 'syntax_highlighting', 'comment_shortcuts', 'admin_color', 'use_ssl', |
| 1682 | * 'user_registered', 'user_activation_key', 'spam', and 'role'. The filters have the prefix |
| 1683 | * 'pre_user_' followed by the field name. An example using 'description' would have the filter |