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 |
---|---|
1246 | * @since 2.0.1 |
1247 | * @uses apply_filters() Calls 'validate_username' hook on $valid check and $username as parameters |
1248 | * |
1249 | * @param string $username Username. |
1250 | * @return bool Whether username given is valid |
1251 | */ |
1252 | function validate_username( $username ) { |
1253 | $sanitized = sanitize_user( $username, true ); |
1254 | $valid = ( $sanitized == $username ); |
1255 | return apply_filters( 'validate_username', $valid, $username ); |
1256 | } |
1257 |
|
1258 | /** |
1259 | * Insert an user into the database. |
1260 | * |
1261 | * Most of the $userdata array fields have filters associated with the values. |
1262 | * The exceptions are 'rich_editing', 'role', 'jabber', 'aim', 'yim', |
1263 | * 'user_registered', and 'ID'. The filters have the prefix 'pre_user_' followed |
1264 | * by the field name. An example using 'description' would have the filter |