You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Destroying does not remove the parsley validation from field nor form instances, triggers still get called and UI is still affected. Don't know if this is expected behavior, but doesn't help when you want to do dynamic validation.
Instead as a work around I've used excluded option with "[disabled] value and just disable the form elements i don't want validated.
I must say I'm also confused as to why destroy on the form doesn't work, I think it should. On the field is not useful, as it will be rebound automatically, but you can use data-parsley-excluded=true on those if you want.
Doesn't disabling create issues as it won't be sending values in the POST/GET request?
Well fortunately for me, i don't use the fields that i disable. Thanks for taking the time to look at this, and thanks for the suggestion, I'll try that rather than disabling them.
Destroying does not remove the parsley validation from field nor form instances, triggers still get called and UI is still affected. Don't know if this is expected behavior, but doesn't help when you want to do dynamic validation.
Instead as a work around I've used excluded option with "[disabled] value and just disable the form elements i don't want validated.
https://jsfiddle.net/SLG_Shark6/ou2msa3q/14/
Sorry it wasn't a codepen.
The text was updated successfully, but these errors were encountered: