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 |
---|---|
2028 | * @type string $user_nicename The user's nice name. Defaults to a URL-safe version of user's login |
2029 | * @type string $display_name The user's display name. |
2030 | * @type string $user_registered MySQL timestamp describing the moment when the user registered. Defaults to |
2031 | * the current UTC timestamp. |
2032 | * } |
2033 | * @param bool $update Whether the user is being updated rather than created. |
2034 | * @param int|null $id ID of the user to be updated, or NULL if the user is being created. |
2035 | * @param array $userdata The raw array of data passed to wp_insert_user(). |
2036 | */ |
2037 | $data = apply_filters( 'wp_pre_insert_user_data', $data, $update, ( $update ? (int) $ID : null ), $userdata ); |
2038 |
|
2039 | if ( empty( $data ) || ! is_array( $data ) ) { |
2040 | return new WP_Error( 'empty_data', __( 'Not enough data to create this user.' ) ); |
2041 | } |
2042 |
|
2043 | if ( $update ) { |
2044 | if ( $user_email !== $old_user_data->user_email || $user_pass !== $old_user_data->user_pass ) { |
2045 | $data['user_activation_key'] = ''; |
2046 | } |