Posts: 6,266
Threads: 181
Joined: Sep 2011
I am considering adding display name support for users to core.
This is a non security sensitive, non userid info field for a user to be used for public display, such as author, or updated by or logged in user etc. without worrying about exposing login credentials.
I think renaming username to userid would be wise, but it will cause confusion, so it will not change.
The new user field will simply be "name" or "displayname"
See attached image for settings example ( not a mockup )
Feedback welcome
Are there any core functions you guys know of that we need to add this field to or perhaps helpers like getusersname() etc.
Posts: 6,266
Threads: 181
Joined: Sep 2011
Also should this be added to the install ?
Maybe with some new tips also for the fields.
see attached
Or just make it optional to be filled in later ?
Posts: 290
Threads: 26
Joined: Oct 2010
Call a duck a duck?
Call the new display name "Display Name" (rather than just "Name")
-Rob A>
Posts: 6,266
Threads: 181
Joined: Sep 2011
Yeah I was kind of thinking along those lines as well, but we don't actually "display" anything by default, plugins would.
But it does convey that its intended to be a public title, and imagine users and devs would use it that way.
Plus we have "username" hence "displayname"
I edited main post to reflect this logical suggestion.
Posts: 661
Threads: 52
Joined: Feb 2011
I agree 100% this option should exist in the core. It can be used in many plugins.
displayname would be my preferred choice of node.
Posts: 679
Threads: 80
Joined: Nov 2009
Posts: 1,204
Threads: 30
Joined: Jun 2010
username should also appear in page's backup information table.
Both who deleted, and last edited the page would be great to know.
Especially when trying to find out who was responsible for breaking the page.
Addons: blue business theme, Online Visitors, Notepad
Posts: 661
Threads: 52
Joined: Feb 2011
yojoe Wrote:username should also appear in page's backup information table.
Both who deleted, and last edited the page would be great to know.
Especially when trying to find out who was responsible for breaking the page.
This would be great. Then I can tell a client they were the ones who broke it
Posts: 1,247
Threads: 82
Joined: Feb 2011
I think it's not needed to fill in at install. Especially since (what you say) it's only used in plugins.
p.s. Is there a thinkable (future) core function this can be used for?
Posts: 6,266
Threads: 181
Joined: Sep 2011
Posts: 687
Threads: 63
Joined: Nov 2011