View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001685 | Composr | core_cns | public | 2014-08-31 15:46 | 2019-07-02 23:37 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0001685: Username suggestions | ||||
| Description | If a username is taken, don't just complain - provide alternatives. Seeding with requested username, or first and last names Prefixing 'The' Suffixing birth year Suffixing random codes Let user pick one. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | 4.5 | ||||
| Sponsorship open | |||||
|
|
Also consider the idea of allowing usernames to be autogenerated from email addresses, particular CPF combinations, etc. A bit like how display names can currently be configured. The use case is users who do not want people to have to pick a username, e.g. intranets. The problem is usernames have to be unique, so we'd have to do something to force uniqueness, like adding a suffix. |
|
|
The cns_check_name_valid is coded to be able to alter $username by reference parameter if $return_errors is set to true. Currently it's just not something we do, but we can do because cns_join_actual has been coded to respect this API. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-01-24 16:30 | Chris Graham | Note Added: 0005910 | |
| 2019-07-02 23:37 | Chris Graham | Note Added: 0006019 |
