I've got a basic design question when used with Dynamic Registration...

1. I must validate an INITIAL registration using an email (domain) address. Assuming "microsoft.com", my regular expression would be

\w*Microsoft.com

I do not anticipate this to be a problem

2. After registration, the user can go to their user profile and modify the email address to any one of their choosing.

My question is, if I set up a User Profile registration page, and the email gets validated at microsoft.com, how do I allow the user to later modify this setting without the expression causing the different email to fail the email REGEX?

One thought is (this is a question, BTW) how about if I put TWO User Profile modules in the site, where one uses the email REGEX and the other doesn't. Does this seem workable, or is there a better solution/suggestion?

Mike,

Well your idea of using two user profiles pages isn't a big deal, we have many clients use multiple registration pages/update pages per portal. The main problem here is with the current DotNetNuke design you have to have only one 'User Page' defined for the register/update link within the skin. We are making this feature a request with the core team as I think this would be a great feature for many implementations.

Another option which would work would be to hide the '2nd' email field during initial registration. You can do this within advanced settings by setting a field to be hidden from anonymous or hidden by role (maybe hide the one with the regular expression once they have signed in). The only downside here is that you would need to execute a SQL Event to update both fields during initial registration etc...

Option 3 would be a nice enhancement we might look to add similar to what we added with Dynamic Events. The ability to fire the event only on initial registration, registration updates, both, etc... We might look to add something for validation where you can select that the validation should fire upon initial registration, updates, or both.

-Chad