Unique username generation fails when uppercase usernames exist
Bug #823080 reported by
Richard Mansfield
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
Medium
|
Richard Mansfield | ||
Bug Description
If you register with the name "Nigel McNie", the default username that gets picked for you is "nigelmcnie", and if there's already a "nigelmcnie" user, you get "nigelmcnie1".
But if there's already a "NigelMcNie" user, you *should* get "nigelmcnie1", but you get "nigelmcnie" because the check is case-sensitive. This causes a duplicate key error when you confirm registration.
| Changed in mahara: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Richard Mansfield (richard-mansfield) |
| milestone: | none → 1.5.0 |
Revision history for this message
| Mahara Bot (dev-mahara) wrote A change has been merged | #1 |
| Changed in mahara: | |
| status: | Confirmed → Fix Committed |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Hugh Davenport (<email address hidden>)
Branch: master
commit 2e59cda64813e3f
Author: Richard Mansfield <email address hidden>
Date: Tue Aug 9 17:48:54 2011 +1200
Use case-insensitive check for existing usernames (bug #823080)
Change-Id: I5b07f6bd45ac7f
Signed-off-by: Richard Mansfield <email address hidden>