Opened 3 years ago
Closed 2 years ago
#14756 closed defect (bug) (fixed)
Bug adding users in multisite
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | 3.1 |
| Component: | Network Admin | Version: | 3.1 |
| Severity: | major | Keywords: | needs-ui |
| Cc: | simon@… |
Description (last modified by jane)
In 3.0 multisite (site in question is wordcamp.org), am having trouble adding new users to an individual site. When you click Add new User, you get:
You can add new users to your site in two ways:
1. Enter the username and email address of an existing user on this site.
2. Enter the username and the email address of a person who is not already a member of this site. Choose the username carefully, it cannot be changed.
That person will be sent an email asking them to click a link confirming the invite. New users will then be sent an email with a randomly generated password and a login link.
A) We should update that text to say network instead of site.
B) When I entered someone's username and email who was already in the network user system, instead of adding them to site, I get two error messages:
Sorry, that username already exists''
Sorry, that email address is already used''
Catch-22.
Attachments (9)
Change History (27)
comment:3
simonwheatley
— 3 years ago
- Cc simon@… added
- Keywords ux-feedback added
- Version changed from 3.0 to 3.1
Part B also works for me, although I recommend we call the second button "Create User" for clarity. Attaching a minor patch create user.diff to do this.
Suggestion One: I wonder if the current screen couldn't be refactored though. Why do we need two areas? The more fields the more of a headache we're potentially causing users... could we have just one form and intelligently work out if we need to add or create and add the user.
Suggestion Two: If we want to keep the two form structure, then when someone mistakenly enters values in the "Create" section rather than the "Add" section should we (a) guess they want to add a user and just do it (assuming we have a user who matches both username and email), or should we add an error message with a button explaining that we think they meant to add a user, not create one, with these details and offering an "Add this user" button?
comment:4
ocean90
— 3 years ago
- Milestone changed from Awaiting Review to 3.1
jane, any problems here still?
comment:6
westi
— 3 years ago
We should use get_blog_option not raw SQL here in both cases.
Can probably move the setting of $default_role up to the top with $editblog_roles
comment:8
PeteMall
— 3 years ago
Leaving this open if someone wants to tweak the forms... See http://make.wordpress.org/ui/2010/12/14/203/.
comment:10
JohnONolan
— 3 years ago
- Keywords needs-ui added; ux-feedback removed
comment:11
ryan
— 3 years ago
In the bug scrub, we discussed changing just the button text for 3.1 and pushing the more thorough rework to 3.2.
comment:12
ryan
— 3 years ago
- Resolution set to fixed
- Status changed from new to closed
comment:13
ryan
— 3 years ago
Modest string changes for 3.1. Further UI revamp pushed to 3.2. Accounting for being able to create and/or add users and the single site and multisite variations make this too big for 3.1.
comment:14
westi
— 3 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Should we not do this text clarification on the wp-admin/users.php page too as that always says Add New which is confusing when a user can only Add Existing.
comment:15
nacin
— 2 years ago
That's really trivial. "Add Existing" without "User" would look odd there I think. When they go to the page, it is clear that they're adding existing vs new. Close and revisit in 3.2?
comment:16
westi
— 2 years ago
That re-uses the strings in both places and makes the it clearer for users who can only promote that they are not entering some secret place they shouldn't go.
comment:17
westi
— 2 years ago
Seems I misinterpreted nacins feedback and got my consistency all wrong :-(
comment:18
westi
— 2 years ago
- Resolution set to fixed
- Status changed from reopened to closed
The network/site confusion was fixed in [15310].
Also, part B) works for me. Is it a specific user name/email combo or are all failing?
(Maybe the check in user-new.php lines 58/59 should use username_exists and email_exists like wpmu_validate_user_signup instead of the direct query)