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
When one edits a Member by first selecting a Group and then one of its Members, there is the Member_Validator (as defined in the injector) used (see Group#getCMSFields()). None of the possible MemberExtensions that implement updateValidator (see Member#getValidator()) are considered. Therefore the validation when editing a Member is inconsistent.
The text was updated successfully, but these errors were encountered:
Suggestion: Remove the setValidator in the Group::getCMSFields, and add an alias in Member from getValidator() to getCMSValidator(), which would cause the validator to be picked up on a per-record basis in the GridfieldDetailForm.
Alternatively, Update GridFieldDetailForm to check both getCMSValidator() and getValidator() on the record.
sminnee
changed the title
Editing a Member in a Group context uses different validator than direct edit
[ADMIN] Editing a Member in a Group context uses different validator than direct edit
Oct 6, 2018
sminnee
transferred this issue from silverstripe/silverstripe-framework
Nov 3, 2018
sminnee
changed the title
[ADMIN] Editing a Member in a Group context uses different validator than direct edit
Editing a Member in a Group context uses different validator than direct edit
Nov 3, 2018
When one edits a Member by first selecting a Group and then one of its Members, there is the
Member_Validator
(as defined in the injector) used (see Group#getCMSFields()). None of the possible MemberExtensions that implementupdateValidator
(see Member#getValidator()) are considered. Therefore the validation when editing a Member is inconsistent.The text was updated successfully, but these errors were encountered: