Description
ACF reCAPTCHA brings Google reCAPTCHA to Advanced Custom Fields, to be used on frontend forms.
Features include:
- ACF reCAPTCHA Protection ensures that spambots cannot circumvent reCAPTCHA to submit forms on the server-side
- ACF-compliant client-side validation which prompts the user if reCAPTCHA is not clicked or had expired
- Customizable reCAPTCHA options, including theme (light/dark), type (image/audio) and size (normal/compact)
- Compatible with ACF Conditional Logic feature, which allows hiding/showing certain fields until the reCAPTCHA has been passed
For more detailed setup instructions, or to report an issue, please head over to the GitHub repository here.
ACF Frontend Forms
ACF reCAPTCHA is meant to be used only on frontend forms, in order to protect them from spam by spambots.
To create a frontend form programmatically, please view the official documentation on the ACF website here.
ACF Compatibility
ACF reCAPTCHA is currently only compatible with ACF v5 at the moment. If you would like to help to add support for v4, do submit a PR on GitHub.
GitHub
Screenshots
ACF reCAPTCHA customization in the ACF backend page. Enter your site and secret keys here. 
ACF reCAPTCHA Protection toggle under Field Group Settings. Use this to ensure that your forms are fully protected against spambots. 
Example frontend form with ACF reCAPTCHA used with Conditional Logic. The textarea is only displayed when the reCAPTCHA is solved.
Installation
In order to use ACF reCAPTCHA, you need to generate your reCAPTCHA API keys for your domain at the Google reCAPTCHA Dashboard first.
- In the ACF field group edit page, click Add Field to add a new field.
- Find the reCAPTCHA field type under Custom.
- Enter your site key and secret key that was generated previously.
- (optional) Configure the theme, size and type of the reCAPTCHA widget.
- Important: Scroll down to the bottom of the page, and enable ACF reCAPTCHA Protection for the field group.
Reviews
Matthias Honert
January 15, 2019
If you using Advanced Forms with ACF and you need spam protection for your front end form — this is the perfect solution.
Plugin works great. I had a few questions and ideas, and the dev was amazingly quick to respond, eager to help, and very collaborative. 5 stars!
Tried using this with an acf_form that created a new post, using the method to put it inside the acf_form() function. It worked, but you have to submit the form once before you can fill out the rest of the form. This actually creates blank posts!
And configuration is just very convoluted.
Some other reviews say it worked out of the box. What? Not for me. But I’m not using it in a field group, because it should only appear for guests. Oh well.
Thank you for contributing this!
Had some issues in the past, but have edited this review as this plugin has been updated and works perfectly now.
Although it seems this plugin was broken and not maintained for several months, I’ve installed it just now, exactly one week since it’s last update – and it’s simple functionality just – works.
I hope it will continue to work and that Google won’t change much in their API, but in case something does break, I will return here to add comments to this review.
Till then, I believe the author deserves 5 stars for his effort, at least to improve the overall rating of the plugin which is currently (unjustified) 3.3
Keep up the good work!
Contributors & Developers
“Advanced Custom Fields: reCAPTCHA Field” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Advanced Custom Fields: reCAPTCHA Field” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.3.3
- Fix undefined index errors
1.3.2
- Disable plugin on ACF versions which are not supported (e.g. ACF v4)
1.3.1
- Fixed settings page link from the Plugins page
- Removed shorthand array syntax (not supported on PHP < 5.4)
1.3.0
- Added settings page to configure site-wide default reCAPTCHA keys, if not specified
1.2.1
- Better handling of server-side reCAPTCHA verification errors
- Accepted ‘true’ as a string value when using acf_form() to set the flag directly
- Perform server-side verification of recaptcha fields in form even if recaptcha flag is not set (to catch misconfigurations)
1.2.0
- Fixed an important security bug, which allowed bots to bypass reCAPTCHA. Read more here
- Multiple reCAPTCHA widgets will be able to render on the same page
- Removed AJAX verification of reCAPTCHA values and instead perform it only during form submission
- Expiry of reCAPTCHA value will trigger an ACF validation error on the client side
- Made help text and links available in the Field Group settings page to reference ACF reCAPTCHA Protection easily
1.1.1
- Added an Upgrade Notice box for future important upgrade notices
- Make Google reCAPTCHA API JS load asynchronously to prevent possible race conditions
1.1
- Bump to version 1.1 (no changes since 1.0.8), as the plugin was not following semantic versioning earlier. Revamped the README and added a fresh new icon to celebrate! ??
- Summary of new features since 1.0:
- Removed requirement for cURL to be used
- Add support for ACF conditional logic
- Numerous other bugfixes
1.0.8
- Fixes bug in not allowing Options Page to save.
1.0.7
- Fix regression caused in 1.0.6.
1.0.6
- Add support for ACF conditional logic.
1.0.5
- Uses
wp_remote_postmethod for the reCAPTCHA POST request. This removes the need for cURL on your server.
1.0.4
- Fix WSOD errors
1.0.3
- Added fixes for some issues
1.0.2
- Prevent reCAPTCHA from showing up on backend
1.0.1
- Support translation of error messages
- Fix for reCAPTCHA API not being enqueued in certain themes
1.0
- Initial version