as usuall.. i'm confused and going crazy...

In my original dnn registration setup a user would sign up for the website and have to verify their registration to become a "REGISTERED USER'.
Once the user verified via email.. they would be added to the role 'REGISTERED USER'.  But only after they verivied using the code given to the via core dnn.

Once i installed AS.... once a user registeres for the website they are now given access to be a 'REGISTERED USER' automatically.... they are no longer required to verify to become one.

I understand that the Member settings in the AS control panel can be configured for a member rol and community role which in turn give the user access to as functionality.  

I've tried multiple combinations of the member role and verified user role and cannont get the following to work:

1. When a user creates an account on the website i need them to have to verify their account...
2. Upon verfification i need them to be added to the 'registered' user role and given access to use AS functionality.
3. upon verification i need the auto friend and auto group to add the user to each one. (which depending on configuration doesn't happen)

Right now I have my  site set to verified.  The users are automatically put into the Registered user role without verification (which i don't want because we have multiple sections of our site that need access to be verified).  As member role: Verified.  as community role: verified (created the role in dnn).
and the site is requiring verification only to use the AS functionality...
Easy way to put it.... how do i remove the automatic 'registered user' role and keep all the functionality and have users put into the 'registerd user' role only after they are verified.

Hazen

Please see this topic and download the attached pdf.

http://www.activemodules.com/active...mentation/

Thanks for the prompt reply:
I've looked through the pdf file.... and have AS and DNN set up the same way...
The problem is that the users are being put into the role of registered users without having to verify their accounts immediately after filling out step 1 of the AS registration process.

That is the intended behavior. We suggest using the role you specify as the "verified" role to secure your site & modules.

OK.. so here's what happens.
I changed both the settings in AS Member control panel to Member Role: Registered Users / Community Role: Registered Users.
The outcome of this is as follows:
New user on step 1 is give access to be a registered user. The verification email is sent.. but it doesn't matter if the user verfies because they already have access.
(The user does get inserted into the default group and auto friended)
I checked the admin site settings and it is set to verified.
admin security roles.. Registered user... public checkbox is not checked... auto is...
What am i missing here?

Or... was i reading your reply wrong.. and you suggest changing the module settings so that users must have the "verfied" role. I understand that this would work.. the problem is that we would have to have all existing users, re-verify their accounts to give them access.. or import them all into the new role created for AS.

Hazen, your last post is correct as I understand it. I'm sure it makes perfect sense to some, but I don't like it.
It feels so kludgy if your site is already established and you use the registered role in all your existing modules and pages.

The registration process in Active Social is designed to help sites that wish to remove some of the barriers that are in the default DotNetNuke registration process. If you want to enforce verified registration and continue using the Registered users role then use the default DotNetNuke registration process. If you want a more streamlined method for acquiring new users and don't mind some additional setup, then Active Social and Community Role is your best option.

Using Active Social registration with the community role set to registered users will not have any benefit, from a verified user perspective.

Posted By Hazen Wilson on 26 Jan 2011 08:48 PM
Or... was i reading your reply wrong.. and you suggest changing the module settings so that users must have the "verfied" role. I understand that this would work.. the problem is that we would have to have all existing users, re-verify their accounts to give them access.. or import them all into the new role created for AS.

Is it not possible to create a new role and make it the auto/open/default role for all members. All members who verify their email address then get booted to registered user/community user?

This way, the existing members do not have to re-verify their accounts. I am just thinking loud so please correct me if I am wrong or let me know how my theory is problematic.

Thanks

Anyone know of a good module where you can import users from role to role..
ie.. i have 10000 users in Role A.. I just created role B and need to import all users in A to B.

Hazen

You don't need a module. Here is a way to use some sql scripts...
http://www.willstrohl.com/Blog/Entr...urity-Role