A few months ago, I remember seeing some agreement among users that having "real name" communities is a good idea. Has that gone any farther in AM's plans?  I would like to have the display name  on sign up be a read-only field, filled in with the entries in the first and last name fields.

Are there any plans for this?
Thanks,
Steven

The Display Name is part of the core DNN, and would be difficult to enforce entirely. I'm sure AM could write it into their regsitration process to force the display name to be a the real name, but there are also several areas where they can change it outside of the AM modules.

Admin > User Accounts > User Settings
Find the field for Display Name format and enter [FIRSTNAME] [LASTNAME]

Click Update

The Active Social SignUp wizard will then hide the Display Name input box.

more undocumented features....awesome to know....thanks Will

Now for someone to come up with a stored procedure for creating the display name from the other fields.

<div class='afquote'>Now for someone to come up with a stored procedure for creating the display name from the other fields.</div>
You mean...
UPDATE dbo.Users SET DisplayName = FirstName + ' ' + LastName

Posted By Will M on 24 Feb 2010 05:19 PM
Admin > User Accounts > User Settings
Find the field for Display Name format and enter [FIRSTNAME] [LASTNAME]

Click Update

The Active Social SignUp wizard will then hide the Display Name input box.

This is the way I have setup my community from the beginning. Then switched back because of one issue. It will work with vanity urls until there is a duplicate name. There doesn't seem to be a way around that one. And, because displayname no longer becomes an option for the user to change, (in theory) anyone with the same first name and last name will not be able to register if someone else already has.

This is true, but now that vanity name is handled separately from the display name we can drop that restriction.

Thanks, Will!

Posted By Will M on 24 Feb 2010 11:20 PM
This is true, but now that vanity name is handled separately from the display name we can drop that restriction.

I just did a test on this scenario when [FIRSTNAME] [LASTNAME] is forced as the displayname in the DNN settings.


1. User1 added with same firstname lastname as User: User1 gets a resulting vanity url with firstname-lastname1
2. User2 added with same firstname lastname as User: User2 gets a resulting vanity url with firstname-lastname1

The vanity url is not incrementing past the original and 1, IE: firstname-lastname2

Tested using Naming Rules: "Automatic and Open" and "Automatic and Protected"

I don't consider this an issue (others may) and am presuming it is by design, but when updating a profile and changing firstname or lastname, the vanity url does not change.

quote]1. User1 added with same firstname lastname as User: User1 gets a resulting vanity url with firstname-lastname1
2. User2 added with same firstname lastname as User: User2 gets a resulting vanity url with firstname-lastname1