I am unable to get any of the validation related messages to work.

1. Uner 'Question Validation' - what's the point of 'Required Text' and 'Required Field Error' when neither of these show up on the form prior to submit (I assume the 'Required Text' should) and when neither shows up on submit when there's an error (I assume that 'Required field Error' text should show up on submit - adjacent to the field?)

2. Seems to me that there should be a nice little arrow or red star next to required fields prior to submit

3. And that on submit, if there's an error - those fields in error should somehow be highlighted

4. Last question re the Password field. On a registration update one should be able to update the password or not, but not be required to re-enter the password and confirm password, if the update is for some other field. So ... is it not possible to pre-populate the password and confirm password fields with the current passwords (actual characters masked by bullets)? Then, if you want to change the password, you can, but if you don't, you don't.

Please help!!!

Thanks

David,

Hi. Let me see if I can answer some of your questions here. First, understand that some of the way these function right now has a lot to do with the history of Dynamic Registration and supporting/retrofitting previous upgrades, automatically features built-in etc... Just an FYI when I go into explanation mode

In response to your specific questions:
1. When using Client Side and Server Side Validation the required field text / required field error fields are used for client side validation only. One appears to the right of the field such as * and one appears in the validation summary. Also there is the option to show the validation summary on top/button/hide it etc... The end result is that the text shows next to the field and the error shows up top such as Error: First Name is required and next to the first name field you would see *

2. You can easily do this now (and we have for clients when we have helped in implementation). Simply (and I won't actually use the full HTML here since it would show) you would set the example text to the field to be:

(remember to add the carrows at from and back of this html)

img src="http://old.datasprings.com/images/required.gif"

So that you would end up with a next to each field. If you wanted to set all fields to show this you could probably do a mass update with a SQL query under host SQL. Something like

Update DynamicRegistration_Question Set ExampleText = etc....

3. Version 3.0 now supports a feature under server side validation (must be set in the configuration area) to actually change the field stylesheet class based on an error. For example, if a field was an error it could highlight the field as red etc... Right now you can specify the field class globally using the DNN Core Stylesheet NormalTextBox, or if you use the Dynamic Registration stylesheet class I think its DynamicRegistration_Textbox. You can also override this class within each field settings if you wish. Finally, when a field is in error it and the feature is turned on it will change the stylesheet class to be: DynamicRegistration_FieldError. I just tested this locally and it appears to be working a designed.

4. Yes, password and confirm password have their own built in functionality to save you from having to create compare validation controls and so forth. Because of this it will automatically create a password client side validation control /compare validation control for you when a user initially registers (unless you show to hide the password controls or have the userID/password auto created). The field is then left blank for registration updates and the user can either choose to leave it blank (not change their password) or change it. We have discovered a bug though where if you leave the password field as 'Required' it will fire off a validation error when updating registration. So... Just don't set that field as required, don't worry it will automatically still be marked as required when registering the user initially so you shouldn't need to set it. This has more to do with the original functionality in previous versions and we are reviewing how this will work later to provide the most flexibility. Either way, for now just don't mark the field as required for password/confirm password.

Hope this answers some of your questions, please don't hesitate to comment on any of these as we are working to make sure the module offers the most flexible and powerful validation controls.

-Chad

I want just add one little precision in the DR style sheet there is a little mistake.

There is not .DynamicRegistration_Textbox but .DynanmicRegistration_Textbox

A little n is in adding after a when you look the html source code

Michel