...but the same page is used. So when the user wants to update their profile, the registration instructions and the registration fields are also there and are required. That means that if they want to change their address or their email address, they have to choose a new password or they have to remember the one they had and reenter it. We are also confirming email address, and so they have to do that too.

 

Also, because the fields in the Dynamic Registration aren't also mapped to the DotNetNuke user profile fields, an administrator can’t update their information for them and users added via the Admin menu are not in the same tables as the users who registered. The internal help desk adds internal users and customers register. Chad, can you help?

 

Cynthia,

Hi. Actually the fields are not required for updating. For example, if you go and change one of your profile fields on our site you don't have to change passwords? Ill have to check if this is how it works for both client and server side validation but the bottom line is that passwords should only be required upon initial registration.

As far as you other issue, this was originally be design to post data to all core fields but not retrieve the data if it was updated via dynamic registration VS the core fields. After getting several comments from customers though *grin* we will be changing this to be linked in both directions. We will be releasing a patch by early next week as 2.3.3 and then the next release of 2.4 which is already in development should be ready by the middle of the month if not sooner.

-Chad

Hi Chad,

 

Using DNN 4.3.6 and Dyn. Reg. 2.3

 

I am having the same problem as Cynthia. 

 

When my users update their Registration the form returns the Confirm Password validation message.  When I enter the password and confirm password the form validates.

 

My form is set for Client and Server Validation.

Chad,

Your suggestion to uncheck the "Required Field" checkboxes solved the Password validation problem.  This also solved my Role update problem as I had guessed because the Role update process was obviously not completing without the passwords not validating.

Thanks