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 |
|---|---|
| 2126 | |
| 2127 | /** |
| 2128 | * Filters whether the provided username is valid. |
| 2129 | * |
| 2130 | * @since 2.0.1 |
| 2131 | * |
| 2132 | * @param bool $valid Whether given username is valid. |
| 2133 | * @param string $username Username to check. |
| 2134 | */ |
| 2135 | return apply_filters( 'validate_username', $valid, $username ); |
| 2136 | } |
| 2137 | |
| 2138 | /** |
| 2139 | * Inserts a user into the database. |
| 2140 | * |
| 2141 | * Most of the `$userdata` array fields have filters associated with the values. Exceptions are |
| 2142 | * 'ID', 'rich_editing', 'syntax_highlighting', 'comment_shortcuts', 'admin_color', 'use_ssl', |
| 2143 | * 'user_registered', 'user_activation_key', 'spam', and 'role'. The filters have the prefix |
| 2144 | * 'pre_user_' followed by the field name. An example using 'description' would have the filter |