Author Topic: Best practice for modifying client-side (JS) validation? (Read 434 times)

JonGold · March 06, 2015, 08:02:20 am

I found a bug in the multisite module on CiviCRM 4.5, and could use some thought on how to fix this.

When multi-site is enabled, every group is required to have a parent group, so that field is set as required. When Eileen's multisite extension is installed, it's desirable to remove that requirement - which she does with hook_validateForm. In 4.4, that's fine, because there's only server-side validation. In 4.5, a group "settings" page is validated client-side, and the hook doesn't fire.

What's the best approach here? Should I just insert a Javascript file to replicate the hook logic? Is there a better approach?

Coleman Watts · March 06, 2015, 08:10:32 am

The clientside validate logic is based on css classes. The field is getting the class "required" because quickform thinks it is required. Probably the cleanest and most semanticly pleasing solution would be to use a buildForm hook to make that field not required.

JonGold · March 06, 2015, 08:48:04 am

It sounds so obvious once you say it. Thank you Coleman!

CiviCRM Community Forums (archive)

News:

Author Topic: Best practice for modifying client-side (JS) validation? (Read 434 times)

JonGold

Best practice for modifying client-side (JS) validation?

Coleman Watts

Re: Best practice for modifying client-side (JS) validation?

JonGold

Re: Best practice for modifying client-side (JS) validation?