Hello,
Thank you for trying to promote ACF Extended, but this is really not needed, and actually probably counter-productive. The Facebook/YouTube public isn’t really the targetted audience of this plugin.
In fact, most of users there look for a more “What You See Is What You Get” solution with a plug & play experience, where they don’t need to mess with actual code/documentation/hooks/debugging. And it’s perfectly fine. There are plenty very popular front-end forms solutions in the WP ecosystem, for every kind of user.
One of the 3 pillars of ACF Extended philosophy is: made by developers, for developers. And the fact is, Facebook and YouTube aren’t social media for developers, so I would rather prefer stay out of there. Please note this is not gatekeeping or an attempt to set a minimum level entrance. I simply believe that as a professional, it is important to know who you are talking to, and not trying to promote the wrong product to the wrong audience, at least for ethical reasons.
Regarding your question, if you’re trying to implement the “email already exists” validation in your User Action, please note this check has been added in the latest 0.9.0.6 version, as explained in my previous answer.
The form will now automatically display an error in this case (if you correctly enabled the “Built’in Validation” setting). So you don’t need to implement it.
Regarding the ACFE Form Validation hooks, the 3 hooks you see are the available hooks variations. It allows you to target the User Action Validation, in different ways.
For example, this hook will validate any User Action, in any form:
acfe/form/validate_user
This hook will validate any User Action, in the form named my-form:
acfe/form/validate_user/form=my-form
This hook will validate any User Action named my-user-action:
acfe/form/validate_user/action=my-user-action
Most of the time, you only have 1 User Action in a form, so it’s common to just use the /form=my-form variation. As in the code example in the documentation:
add_action('acfe/form/validate_user/form=my-form', 'my_user_validation', 10, 2);
function my_user_validation($form, $action){
// ...
}
This logic is inspired by the ACF hooks variation logic, which allow to target fields by their type, key, and name using the same syntax. See documentation.
// Target any field
add_filter('acf/update_value', ...);
// Target field with type "textarea"
add_filter('acf/update_value/type=textarea', ...);
// Target field named "hero_text"
add_filter('acf/update_value/name=hero_text', ...);
// Target field with key "field_123abcf"
add_filter('acf/update_value/key=field_123abcf', ...);
Hope it helps!
Regards.
