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
1378      /**
1379       * Filters whether the provided username is valid or not.
1380       *
1381       * @since 2.0.1
1382       *
1383       * @param bool   $valid    Whether given username is valid.
1384       * @param string $username Username to check.
1385       */
1386      return apply_filters( 'validate_username', $valid, $username );
1387 }
1389 /**
1390  * Insert a user into the database.
1391  *
1392  * Most of the `$userdata` array fields have filters associated with the values. Exceptions are
1393  * 'ID', 'rich_editing', 'syntax_highlighting', 'comment_shortcuts', 'admin_color', 'use_ssl',
1394  * 'user_registered', and 'role'. The filters have the prefix 'pre_user_' followed by the field
1395  * name. An example using 'description' would have the filter called, 'pre_user_description' that