Last modified: 2014-06-27 17:28:55 UTC
Example for not registered username in User namespace: https://en.wikipedia.org/wiki/User:UserNamaseasca ''User account "UserNamaseasca" is not registered.'' I propose same message in Special:Contributions. The current page shows dialog for non-existing users as well, I've made an example how it can be done (see attachment). Optionally this text can be red.
Created attachment 14394 [details] Mockup
Probably an easy bug. One gotcha to look out for is to make sure the valid non-username things don't trigger warning. It also shouldn't include the warning for historical things like "45.76.2.xxx", or old usernames from the pre-phase 3 era that are invalid now (e.g. first letter lowercase). Also make sure it doesn't give warning if a non-registered user has edits (via importing perhaps)
There's already a subtle way to tell this, for what it's worth: where it says "whoever (talk | block log...", if the username itself is linked (blue or red), the account is registered; if it's not linked (gray), it's not.
(In reply to comment #3) > There's already a subtle way to tell this, for what it's worth: where it says > "whoever (talk | block log...", if the username itself is linked (blue or > red), > the account is registered; if it's not linked (gray), it's not. I've proposed this for the consequence. Userspace shows warning so it should as well.
I would like to work on this bug .Can someone please assign this to me?
Assigned (for the record, being assigned to a bug is optional for working on it)
Change 117854 had a related patch set uploaded by Ganeshaditya1: Display a warning when the user name looked up is not registered. https://gerrit.wikimedia.org/r/117854
Change 117854 merged by jenkins-bot: Display a warning when the user name looked up is not registered https://gerrit.wikimedia.org/r/117854
This should probably not appear for IPv4 ranges: [[Special:Contribs/127.0.0.1/16]]. It doesn't appear for IPv6 ranges.
Actually, the IPv4 range behavior is correct and the IPv6 range behavior is the bug.
I've filed a new bug for that problem, bug #67203.
