Opened 11 years ago
Closed 11 years ago
#32684 closed defect (bug) (fixed)
wp_update_user() is the 'user_email' now a required $userdata arg for updating a user ?
| Reported by: | imath | Owned by: | boonebgorges |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.3 |
| Component: | Users | Version: | 4.3 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
in r32820 there's a new check on $userdata['user_email'] to see if an email should be send if i understand well.
My problem is: if i want to update the display name, doing something like this :
// Update the display_name wp_update_user( array( 'ID' => $user_id, 'display_name' => $display_name, ) );
Then i get an error because $userdata['user_email'] is not set in my array.
If the user_email is now required, then simply close this ticket.
imho maybe an isset( $userdata['user_mail'] ) before comparing it to $useruser_email would be nice, because i might not be the only one using wp_update_user() the way i've described above.
Attachments (1)
Change History (4)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Confirmed. This change is also breaking a lot of unit tests.