Source View: validate_username

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: 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.

Source View

Line Code
1454      /**
1455       * Filters whether the provided username is valid or not.
1456       *
1457       * @since 2.0.1
1458       *
1459       * @param bool   $valid    Whether given username is valid.
1460       * @param string $username Username to check.
1461       */
1462      return apply_filters( 'validate_username', $valid, $username );
1463 }
1465 /**
1466  * Insert a user into the database.
1467  *
1468  * Most of the `$userdata` array fields have filters associated with the values. Exceptions are
1469  * 'ID', 'rich_editing', 'syntax_highlighting', 'comment_shortcuts', 'admin_color', 'use_ssl',
1470  * 'user_registered', and 'role'. The filters have the prefix 'pre_user_' followed by the field
1471  * name. An example using 'description' would have the filter called, 'pre_user_description' that