Opened 14 years ago
Last modified 3 weeks ago
#16833 new defect (bug)
Signup mechanism shortens usernames without warning
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | 3.0 |
Component: | Users | Keywords: | has-ux-feedback has-patch dev-feedback |
Focuses: | Cc: |
Description
When a user signs up for an account on a wordpress blog, if their chosen username is longer than the limit, wordpress chops of the end of the username, without warning the user, and without offering the user the opportunity to choose again.
Steps to reproduce: Go to a wordpress blog, sign up with a long username, and read the confirmation email. An example: forum.xbmc.org, which has a limit of 15 characters.
Attachments (1)
Change History (11)
#2
@
14 years ago
- Keywords has-patch added
I think we're missing some maxlength attributes - these would prevent someone submitting a too-long username in the first place. Elsewhere (e.g., in show_user_form()
) they are present.
Also the maxlength value for email was wrong - user_email accepts varchar(100)
.
#3
@
14 years ago
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
- Version set to 3.0
This ticket was mentioned in Slack in #design by karmatosed. View the logs.
8 years ago
#9
@
8 years ago
- Keywords has-ux-feedback added; ux-feedback removed
There should be a warning if this is a limit in place. Without it is unfair and unexpected for users.
#10
@
3 weeks ago
Hi All,
I have taken a look at this, and this still looks to be an issue on the sign up form. In the back office there is a max length applied to the username field. However this is not present on the registration form, so it is still possible to enter a username that is too long, which results in a truncated username. I believe that it would be best to get a notification in place for when the user's input hits that limit, but seeing as this issue has been around for a good few years now, just adding in the maxlength="60"
attribute to the field is probably enough for now?
In regards to a notification, I wonder if having text below the field saying something along the lines of "max 60 characters" would be enough? I wonder if we should hide/show it when they hit that limit, or get close to that limit?
Insert maxlength attribute into user_login field to prevent long usernames being truncated silently