One of the common requests we received with Active Profile was, "How could every user have a default profile?". Active Social uses the built-in profile information from DotNetNuke. This has several advantages:
1) Every user will now have a profile.
2) The profile can be maintained in one location.
3) Custom profile fields in DotNetNuke are immediately available in Active Social.
While relying on the DotNetNuke profile mechanism provides the best form of integration, we did face some challenges.
1) We wanted to be able to register and complete profile information as a seamless process.
2) We wanted to have the option to upload a picture as part of the initial registration.
3) We needed to preserve all of the existing DotNetNuke registration logic.
4) We wanted to add further options that allow you to have better control and greater flexibility for the registration process. New options include:
a) Registration blacklist by email and username
b) Option to require unique email address
c) Option to require unique display name
d) Option to use email address in place of username.
e) Option to disable display name.
f) Option to force profile update.
5) The profile display, edit and registration process needed to be 100% template driven.
Below are a few screen shots that will show some of the items I have listed above.