HI Chad,
The more I thought about it, I came to the same conclusion, that DNN would need to be set to verified.
Since I may have a combination of Private and Verified (using different DR modules) I believe I can accomplish what I need by removing the "Register" token from the skin, so it never shows up.
So this idea makes sense to others reading this post, I have custom registration pages, using DR, specific to certain customers. I send them to these pages by giving them the page links. So normally my registration is set to "None", since I don't have a single registration page for everyone.
In some cases, the customer registrants need to be manually authorized as in a Private setup, but for others, I am finding the automated Verification process is more appropriate and desirable.
The private registrants will not be given a verification code, so they won't be able to login until manually authorized. If they try to login, they will be asked for the code, which they won't have.
I just did a quick test of this and it appears to work (including the Dynamic Login module.)
Rob Ralston |