Make WordPress Core


Ignore:
Timestamp:
08/30/2008 09:23:43 PM (15 years ago)
Author:
westi
Message:

phpDoc corrections for wp-includes. See #7550 props jacobsantos.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/wp-includes/registration.php

    r8701 r8782  
    77
    88/**
    9  * username_exists() - Checks whether the given username exists.
     9 * Checks whether the given username exists.
    1010 *
    1111 * @since 2.0.0
     
    2323
    2424/**
    25  * email_exists() - Checks whether the given email exists.
     25 * Checks whether the given email exists.
    2626 *
    2727 * @since 2.1.0
     
    3939
    4040/**
    41  * validate_username() - Checks whether an username is valid.
     41 * Checks whether an username is valid.
    4242 *
    4343 * @since 2.0.1
     
    5454
    5555/**
    56  * wp_insert_user() - Insert an user into the database.
    57  *
    58  * Can update a current user or insert a new user based on whether
    59  * the user's ID is present.
    60  *
    61  * Can be used to update the user's info (see below), set the user's
    62  * role, and set the user's preference on whether they want the rich
    63  * editor on.
    64  *
    65  * Most of the $userdata array fields have filters associated with
    66  * the values. The exceptions are 'rich_editing', 'role', 'jabber',
    67  * 'aim', 'yim', 'user_registered', and 'ID'. The filters have the
    68  * prefix 'pre_user_' followed by the field name. An example using
    69  * 'description' would have the filter called, 'pre_user_description'
    70  * that can be hooked into.
     56 * Insert an user into the database.
     57 *
     58 * Can update a current user or insert a new user based on whether the user's ID
     59 * is present.
     60 *
     61 * Can be used to update the user's info (see below), set the user's role, and
     62 * set the user's preference on whether they want the rich editor on.
     63 *
     64 * Most of the $userdata array fields have filters associated with the values.
     65 * The exceptions are 'rich_editing', 'role', 'jabber', 'aim', 'yim',
     66 * 'user_registered', and 'ID'. The filters have the prefix 'pre_user_' followed
     67 * by the field name. An example using 'description' would have the filter
     68 * called, 'pre_user_description' that can be hooked into.
    7169 *
    7270 * The $userdata array can contain the following fields:
     
    7876 * 'user_url' - A string containing the user's URL for the user's web site.
    7977 * 'user_email' - A string containing the user's email address.
    80  * 'display_name' - A string that will be shown on the site. Defaults to user's username.
    81  *      It is likely that you will want to change this, for both appearance and security
    82  *      through obscurity (that is if you don't use and delete the default 'admin' user).
     78 * 'display_name' - A string that will be shown on the site. Defaults to user's
     79 *      username. It is likely that you will want to change this, for both
     80 *      appearance and security through obscurity (that is if you don't use and
     81 *      delete the default 'admin' user).
    8382 * 'nickname' - The user's nickname, defaults to the user's username.
    8483 * 'first_name' - The user's first name.
    8584 * 'last_name' - The user's last name.
    8685 * 'description' - A string containing content about the user.
    87  * 'rich_editing' - A string for whether to enable the rich editor or not. False if not
    88  *      empty.
     86 * 'rich_editing' - A string for whether to enable the rich editor or not. False
     87 *      if not empty.
    8988 * 'user_registered' - The date the user registered. Format is 'Y-m-d H:i:s'.
    9089 * 'role' - A string used to set the user's role.
     
    209208
    210209/**
    211  * wp_update_user() - Update an user in the database
    212  *
    213  * It is possible to update a user's password by specifying the
    214  * 'user_pass' value in the $userdata parameter array.
    215  *
    216  * If $userdata does not contain an 'ID' key, then a new user
    217  * will be created and the new user's ID will be returned.
    218  *
    219  * If current user's password is being updated, then the cookies
    220  * will be cleared.
     210 * Update an user in the database.
     211 *
     212 * It is possible to update a user's password by specifying the 'user_pass'
     213 * value in the $userdata parameter array.
     214 *
     215 * If $userdata does not contain an 'ID' key, then a new user will be created
     216 * and the new user's ID will be returned.
     217 *
     218 * If current user's password is being updated, then the cookies will be
     219 * cleared.
    221220 *
    222221 * @since 2.0.0
     
    259258
    260259/**
    261  * wp_create_user() - A simpler way of inserting an user into the database.
     260 * A simpler way of inserting an user into the database.
    262261 *
    263262 * Creates a new user with just the username, password, and email. For a more
Note: See TracChangeset for help on using the changeset viewer.