-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disable_on_hide bugs #87
Comments
Additional disable_on_hide bug: when a repeater is inside a group with ISSUE 3 : https://conditional-fields-cf7.bdwm.be/form-tester/?test-form=Github+issue+87+%283%29 ✅ Fixed in 2.1.1 |
One more issue: it's possible to submit empty required fields when the parent group has the ✅ Fixed in 2.1.1 |
It's possible to move to next step when the parent group has the disable_on_hide property. ISSUE 4: https://conditional-fields-cf7.bdwm.be/form-tester/?test-form=Github+issue+87+%284%29 ✅ Fixed in 2.1.3 |
* check for user_cap 'wpcf7_edit_contact_forms' instead of 'wpcf7_edit_contact_form' in several places. Thanks, [@PayBox](https://wordpress.org/support/topic/some-notices-appearing-fix-suggested/)! * PRO multistep: make "Next step" and "Previous step" buttons translatable by third party plugins like wpml and loco translate. * PRO multistep: show spinner while validating a step. * PRO Fix additional disable_on_hide bug with multistep [GH issue 87-4](#87) * Replace all occurences of text domain 'contact-form-7' with 'cf7-conditional-fields'
When a field inside a group with the
disable_on_hide
prop is used in a condition, weird stuff happens. Needs to be fixed and create e2e tests.ISSUE 1 : https://conditional-fields-cf7.bdwm.be/form-tester/?test-form=Github+issue+87
✅ Fixed in 2.1.1. Because a field is considered non-existing when it's disabled, the conditions with such a field make no sense. The behaviour for now is that the group will always be visible, if the condition has a non-existing field.
The text was updated successfully, but these errors were encountered: