WordPress.org

Make WordPress Core

Opened 5 years ago

Last modified 7 weeks ago

#14215 new feature request

MultiSite: Add new > different username from blog title

Reported by: Person Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.0
Component: Networks and Sites Keywords: ux-feedback
Focuses: multisite Cc:

Description

I would like to request that the current system for adding a new blog site be expanded so that as admins, we can specify a different username that's unrelated to the blog title. That is, in Site Admin -> Add New, at the bottom of the page, add a new field specifically for the username. For that matter, it would be useful to also have a field to be able to specify the password, and perhaps a little checkbox that allows you to optionally prevent an email from being sent. These features are really useful when you're manually adding sites for employees, students, and the such.

I had provided a fix for wpmu 2.8.4 at one point (with a better explanation and details), you can see the thread here: http://mu.wordpress.org/forums/topic/12945

An example of the final result: http://img696.imageshack.us/img696/2551/addblogwordpress.png

Attachments (2)

visual_diff_wp3.7z (33.6 KB) - added by Person 5 years ago.
A visual diff of desired changes in wordpress 3.0
2014-02-15 at 3.03 PM.png (39.6 KB) - added by danielbachhuber 14 months ago.
Mockup of add existing vs. create new

Download all attachments as: .zip

Change History (8)

@Person5 years ago

A visual diff of desired changes in wordpress 3.0

comment:1 @nacin4 years ago

  • Milestone changed from Awaiting Review to Future Release

comment:2 @jeremyfelt20 months ago

  • Keywords ux-feedback added; multisite multiuser blog title username password email removed

comment:3 @jeremyfelt14 months ago

  • Component changed from Multisite to Networks and Sites
  • Focuses multisite added

comment:4 @jeremyfelt14 months ago

Thanks for the request, @Person. Sorry we haven't said anything in 4 years! :)

I agree that the current new site form is clunky. The existing behavior is described well:

A new user will be created if the above email address is not in the database. The username and password will be mailed to this email address.

The workflow to add a new site and invite a new user without that site's address becoming the username is:

  1. Create user on the network.
  2. Create site on the network, specifying the email address for that new user.

At the risk of adding too many options to this page, is there a way that we can streamline this?

I guess the one thing that stands out is whether other user information would need to be assigned as well. Maybe if we detect that the entered email address is a new user, additional form fields are presented to help create?

@danielbachhuber14 months ago

Mockup of add existing vs. create new

comment:5 follow-up: @danielbachhuber14 months ago

What about we decouple the behaviors of creating new sites and users? Instead, the behavior would be to add your "First Administrator", and you'd choose between an existing user or explicitly creating a new user. Something like this mockup:

https://core.trac.wordpress.org/raw-attachment/ticket/14215/2014-02-15%20at%203.03%20PM.png

Personally, I'm always afraid of entering the wrong email address. The auto-complete helps, but I think the two behaviors (create a site vs. create a user) should be completely decoupled.

And, having just said that, maybe the "Add New Site" form should only permit selecting an existing user.

comment:6 in reply to: ↑ 5 @jeremyfelt7 weeks ago

Replying to danielbachhuber:

Personally, I'm always afraid of entering the wrong email address. The auto-complete helps, but I think the two behaviors (create a site vs. create a user) should be completely decoupled.

And, having just said that, maybe the "Add New Site" form should only permit selecting an existing user.

I'm mixed on this. I agree mostly because I'm completely used to ensuring that a user exists on the network now before adding a site, but it seems like learned behavior more than anything.

If we do decouple the two actions, we need a nice way of explaining that a user should be created first. This could also be annoying for someone who has typed in all other site info only to find out that a user doesn't exist.

I think there's another ticket (or comment) somewhere that talks about a pre-flight check of sorts. It could be worth expanding this screen even more to cover theme, initial users, etc... An intuitive add/create user interface could be part of that.

Note: See TracTickets for help on using tickets.