-
Notifications
You must be signed in to change notification settings - Fork 29
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
isValidEmail validator doesn't work if field is outside default fieldset #172
Comments
Pfew, that was a debug session for me. Found it, I think: collective.easyform/src/collective/easyform/fields.py Lines 27 to 53 in 1efc2f2
This FieldExtenderValidator only adapts fields directly on IEasyFormForm, which are fields in the default 'group'. But the fields in the fieldselts are in an IGroup (or actually an plone.z3cform.fieldsets.group.Group object), not an IEasyForm, so the FieldExtenderValidator is never called for fields in fieldsets. Gonna patch the 1.x branch directly and provide a pull request with added tests for 2.x |
The isvalidEmail validator doesn't work if you put in on a required field that is outside the default fieldset. Tested in easyform 1.x branch on Plone4 and easyform 2.1.0 on Plone 5.
Maybe also related to #157 where the defaut expression no longer works if the field is in a fieldset. Some actions are not run on fields in fieldsets. Also #132 relates to things not working in a fieldset
The text was updated successfully, but these errors were encountered: