Server Validation is wiping recordset data values from form?

What should the default value be for form fields on an UPDATE form? I have them set to values from a recordset because it is linked from a "Edit Profile" button on a previous page. When the user clicks that button it takes them to the UPDATE form page and the recordset is populated by a hidden ID form element also passed from the previous page. That works, and the correct data is displayed in the UPDATE form fields.

Except, when I click the submit button on the UPDATE form, it carries out the server validation on the form fields and then wipes all the values from the form! :(

I was thinking that I was misunderstanding this and that the default value should be validated entries but that won't work because on initial load of the page no validation has been carried out?

Is this a bug?

Page attached.
Thank you
NJ

in the server validation settings, set the fialied redirect to pass a URL variable:
myprofile.php?invalid=true


then in the initila value of the form elemnt, you can use isset() as a ternary expresion to use the validated entries if validation fails, or the recordset if not. For example, for the first name field:

<?php echo((isset($_GET["invalid"])?ValidatedField("myprofile_437","LEDUserFirstName"):"".$row_rsUSER['LEDUserFirstName']."")); ?>

That's great, thank you. Again, without knowledge of this it would be impossible to fathom it from the behaviours themselves.

I've also created an INSERT form which, obviously, doesn't need the recordset values as it is a new entry. I ran into the same problem - upon submit of the form and running of the server validation all of the fields data would be wiped - so I set the default value for every field to be:
value="<?php echo(ValidatedField("addcustomer_648","LEDUserFirstName")) ?>" etc

Problem now is, when I click submit and server validation runs, it is abbreviating my password. On test I am entering the following as the intial password:
password!"£$

When server validation runs, it abbreviates my password entry to just:
password!

...I'm assuming that this might be to do with allowing " in the password, but can you clarify as, again, there's no way of knowing this stuff using the behaviours alone.

Thank you
NJ

  Again, without knowledge of this it would be impossible to fathom it from the behaviours themselves.  

that is why the forum is here.

  I'm assuming that this might be to do with allowing " in the password  

yes, that is correct, quote characters should not be allowed in passwords.

What other characters shouldn't be allowed? I'll obviously need to add a "Restrict Content" server validation for that.

Thank you.
NJ

The Restrict Content server validation isn't allowing me to enter ". I guess that's why the forum is here. ;)
Also, when I enter anything in the Restrict Content server behaviour it isn't allowing me to edit the "Replace" section which just lists the same symbol/s as I'm trying to restrict which, in effect, renders the validation useless if it is just replacing with what you're trying to restrict.
Hope you can help.
Thank you
NJ

quotes are the only ones that shouldn't be allowed as they are string termination characters.

See my two replies above...thank you.

Restrict content is not the proper validation type for this.

use the alpha numeric validation type instead.

in the allow other section, you can enter the special characters that should be allowed. omit the quote characters in the allow other list.

Originally Said By: Jason Byrnes

  Restrict content is not the proper validation type for this.  

Perhaps a change of title is required?

I want to allow special characters, but only special characters that don't stop the whole thing working properly.
How should they be listed in the "Allow other" section? Comma separated?