Buy Now
Sign in

Selected radio button value not getting posted on site homepage, but is posted correctly when using frontend preview

SimonvD , August 18 2021, 15:36
S
SimonvD 2
August 18 2021, 15:36 #396950
Hi,
I have a weird issue where on the frontend of my site, my radio buttons aren't posted correctly. Using the debug option you can see that the field 'aanhef' is empty:
Array
(
[chronoform] => offerte
[gpage] => actions
[bedrijfsnaam] => 6
[aanhef] =>
While when you try to submit the form using the 'preview form at frontend' function you get this:
Array
(
[chronoform] => offerte
[gpage] => actions
[bedrijfsnaam] => 6
[aanhef] => De heer
The only difference is that i load the form on the homepage using the standard CF7 module. I can not for the life of me figure out why this is happening since the radio values simply dissapear and no further processing is done at this point
Thanks in advance,
Simon
GreyHead 65
August 19 2021, 09:43 #396958
Hi Simon,
Please can you post or PM a link to the form page so we can take a quick look.
Bob
If you'd like to buy me a coffee or two, thank you very much
S
SimonvD 2
August 19 2021, 11:01 #396960
Hi Bob,
I currently cannot send private messages since i get the error 'You can not send private messages yet', Can i send you a mail instead (or can the resctriction be lifted?).
Thanks,
Simon
E
Erik66 72
August 20 2021, 13:58 #396962
I just sent a PM
GreyHead 65
August 20 2021, 14:33 #396963
Hi,
Thank you for the link. It appears to me that the template is over-writing the format of the radio buttons with a button of its own and is then setting the opacity of the ChronoForms checkbox to 0 so it is hidden. We've seen this before with some template families. Try turning off this option in the template settings; or using a url with &tmpl=component to load the form in the module.
Bob
If you'd like to buy me a coffee or two, thank you very much
E
Erik66 72
August 20 2021, 15:48 #396964
Thank you for the analysis and your insight Bob. But I don't get it completely. These fields are mandatory and validated. If we were seeing another field instead fo the CF form field, and we're entering values in the visible field, wouldn't validation then return a error/message on the CF field(s) as they are left empty? Also, there is Contact form on this website that uses the (as far as I can see) exact same field and it's settings, rendered under the same template, and this form returns the field's value without problems. I'm still puzzled :/
GreyHead 65
August 20 2021, 16:03 #396965
Hi Erik,
The JavaScript validation might not pick up the omission as the inputs are hidden - I'm not sure about that. However, server side validation should pick up the error.
Bob
If you'd like to buy me a coffee or two, thank you very much