Validating forms
Permalink
Not sure if this is the right place to post this or not... I'm trying to go through my site and validate all the pages via the WC3. I'm using the forms block and it's throwing several errors that seem to be related to using & instead of & but I'm no programmer and can't seem to find where the code is generated. I thought it was line 45 of the controller.php for the forms block, but that doesn't seem to be it. Anyone have any suggestions of how to validate a forms block?
(I'm just proud of myself that I figured out how to remove the "border=0" on the image block that kept throwing errors!)
(I'm just proud of myself that I figured out how to remove the "border=0" on the image block that kept throwing errors!)
I realize it's not all that important, but it's driving me nuts that I can't figure out where the code is generated that won't validate! Just a matter of personal pride now. Where are those ampersands created and how can I change them to & ? If I change line 12 of the form view.php it will validate, but won't post... Just so I can sleep at night, anyone have a clue of how to solve my validation fixation?
I'm having the same problem, did anyone ever answer your question or did you find a solution?
If so, please help, I've also searched every form block php file. I found the string quoted in the validation error but anything I changed did not correct it.
Thanks for your help.
If so, please help, I've also searched every form block php file. I found the string quoted in the validation error but anything I changed did not correct it.
Thanks for your help.
Sorry to be the bearer of bad news, but trying to get a Concrete5 site to validate is an exercise in futility. There are too many places scattered throughout the system that serve up invalid code (sometimes for understandable architectural reasons, sometimes just because nobody ever changed it and the core team has not deemed it a high enough priority to fix).
As for your specific issue -- it looks like the OP found the proper place to edit the code so the ampersand gets outputted differently, but if that wound up breaking the form submit functionality then there's not going to be any way around it.
Wish I had a better answer for you :(
-Jordan
As for your specific issue -- it looks like the OP found the proper place to edit the code so the ampersand gets outputted differently, but if that wound up breaking the form submit functionality then there's not going to be any way around it.
Wish I had a better answer for you :(
-Jordan
Pretty sure the extended forms in the marketplace boasts validating with the W3C.
I have to agree with Jordan here about validation. Those ampersands will get you (!) and there seems to be no easy way around them. Like you both here, I override/change what I can and hope that everything else works out.
Not ideal, but it is what it is.
I have to agree with Jordan here about validation. Those ampersands will get you (!) and there seems to be no easy way around them. Like you both here, I override/change what I can and hope that everything else works out.
Not ideal, but it is what it is.
