The Form validation rules are enforced even when the fields are hidden by the Conditional Rules.
Desired function: If the fields are hidden, they should not be checked.
Example:
If the user chooses an option 1 in a "Select Options" field, an additional "Textfield" field is displayed (via Conditional Rules) to enter a PromoCode. When submitted, the PromoCode field is checked for an allowable code (via the Form Validation rules). OK.
When the user chooses option 2, no additional "Textfield" field is displayed. OK.
But when submitted, the Form validation rule is still run; and throws an error because no code is entered.
The rule should not run, because the field is NOT displayed.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | webform_conditional-fix_hidden_required_elements-1597760-6.patch | 2.68 KB | john franklin |
| #5 | node-export 1597760-grid-fails.node_code.txt | 9.31 KB | john franklin |
| screen-capture-8.png | 21.55 KB | stevestaso | |
| screen-capture-7.png | 16.24 KB | stevestaso |
Comments
Comment #1
quicksketchSame-page conditionals are not provided by Webform core. You're probably describing behavior of http://drupal.org/project/webform_conditional, which enables same-age functionality. Moving this issue over there.
Comment #2
jessSchn commentedI am experiencing this same issue. Do we have any progress on a fix?
Although, I've noticed that if I have a conditional setup (select a radio button) and then when a radio button is selected and then I have another conditional (select a dropdown option - required). It seems that my form will only throw an error on the required nested conditional. All other required fields do not display an error. - If that makes any sense?
Comment #3
tedbowIs "Form Validation rules" another module? If so please provide a direct link.
Thanks
Comment #4
john franklin commentedI'm seeing a similar issue also with 6.x. I don't believe I'm using a "Form Validation" module, just the normal "required fields" stuff. I'll see if I can create a sample form and node export it.
Comment #5
john franklin commentedHere is a webform that demonstrates the failure. It works fine for textfield and select form components, but Grid components are required, even if hidden.
Comment #6
john franklin commentedSo, I could just special case the 'webform_grid' components and disable all the sub-FAPI elements, but why not take it to the next level and turn it into a hook so other webform modules can disable their own subfields, no matter how complicated they are?
This patch adds HOOK_webform_conditional_set_required(&$element, $value) and implements it for the set of base webform components. Other modules should implement it if they have complex subform that needs special attention when webform_conditional is tweaking the form in response to hiding or showing components.
Comment #7
jessSchn commentedSo, here is a newb question:
How do I apply the patch to the module?