Menu Adam R Brown

WP hooks navigation: Home/browseActions indexFilters index

Source View: wp_pre_insert_user_data

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.

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
2001       *     @type string $user_url        The user's url.
2002       *     @type string $user_nicename   The user's nice name. Defaults to a URL-safe version of user's login
2003       *     @type string $display_name    The user's display name.
2004       *     @type string $user_registered MySQL timestamp describing the moment when the user registered. Defaults to
2005       *                                   the current UTC timestamp.
2006       * }
2007       * @param bool     $update Whether the user is being updated rather than created.
2008       * @param int|null $id     ID of the user to be updated, or NULL if the user is being created.
2009       */
2010      $data = apply_filters( 'wp_pre_insert_user_data', $data, $update, $update ? (int) $ID : null );
2011
2012      if ( empty( $data ) || ! is_array( $data ) ) {
2013           return new WP_Error( 'empty_data', __( 'Not enough data to create this user.' ) );
2014      }
2015
2016      if ( $update ) {
2017           if ( $user_email !== $old_user_data->user_email || $user_pass !== $old_user_data->user_pass ) {
2018                $data['user_activation_key'] = '';
2019           }