WordPress.org

Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#15453 closed defect (bug) (fixed)

Use “Username”, not “Login”, for column header in users.php

Reported by: demetris Owned by:
Milestone: 3.1 Priority: normal
Severity: normal Version: 3.1
Component: UI Keywords: ux-feedback
Focuses: Cc:

Description

Is there a reason “Username” changed to “Login”, or did “Login” just slip in there?

Attachments (1)

t15453-login-username-users-php.diff (1.1 KB) - added by demetris 10 years ago.
Replaces Login with Username in column header in users.php

Download all attachments as: .zip

Change History (9)

@demetris
10 years ago

Replaces Login with Username in column header in users.php

#1 @nacin
10 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [16428]) s/Login/Username/ to restore 3.0 string. props demetris, fixes #15453.

#2 @nacin
10 years ago

  • Milestone changed from Awaiting Review to 3.1

#3 @scribu
10 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Yes, there was a reason: 'Login' | 'Name' is clearer than 'Username' | 'Name'

#4 @scribu
10 years ago

Alternatively, we could have 'Username' | 'Displayname'

#5 @nacin
10 years ago

We don't make silent changes without UX feedback on that.

#6 @scribu
10 years ago

  • Keywords ux-feedback added; has-patch removed

Understood. So, which do we choose?

#7 @demetris
10 years ago

@scribu: I understand your reasoning, and I imagined some idea like might have been behind the change, but I think the Username/Name is the best. Consider the alternatives:

  • Login/Name: You say it is clearer, but I don’t think many user would agree. Also, it also introduces inconsistencies in our usage.
  • Username/Displayname: Problematic, because the display name is not always the real name.
  • Username/Real name: A nonstarter. :-)
  • Login name/Name: Clear, but incosistent with our usage and also with the general usage.

In short, I think what we had before was just fine.

#8 @scribu
10 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Ok, thanks for the explanation.

Note: See TracTickets for help on using tickets.