Does not work with Fluent Forms.
-
My testing environment is the WordPress Playground, and sometimes that is the issue…
So I created a sample Fluent Form and per instructions, I created an HTML field and added the shortcode [raptcha integration=”fluentforms”]. On the front instead of seeing Raptcha I’m getting the shortcode instead.
I tried as a logged in user and logged off, same result, only the shortcode is being displayed.
-
@nick6352683, don’t you know this just opened a whole can of worms that was unexpected. Part of the problem is how one plugin handles nested shortcodes versus another. For instance CF7 is all shortcodes, and yet, the Raptcha challenge works as expected. Getting it to play nice with all the form plugins is a little like whackamole. Add on top of that how two of the form plugins are still using old textdomain methods that don’t break anything yet, but basically flood the debug.log with warnings about how they need to update their form plugins, and it just adds to the challenge. And one of those is FluentForms. This is going to take some time, so please stand by. That said, I really, truly do appreciate your taking the time to ferret out bugs like this. Thank you.
I use ACF extensively in my builds with custom post types and a variety of custom fields. I’ve tested it with one website using Kadence forms and it behaves as expected. I do not have the pro version of ACF, so I can’t test Advanced Forms. I’ve cursorily checked out the free Advanced Forms from PhilKurth. He says he’s been inundated with other projects. Ajax in forms (like forminator) plays tricks on Raptcha integration, so it may be necessary to auto-inject just before the submission button. There may be security concerns for Ajax submission. Let’s leave it at “maybe” for now? I have some ideas for wider adoption, but they’re on a back burner for now. Like Phil, I’m about to head into a heavy project season.
@nick6352683 after looking at Phil’s github repo, I’ve been able to create an automatic method for Advanced Forms.
Version 1.4.1.
I have not tried it yet, but Plugin-Check passes it, and it uses the nearly identical methodology as several other proven form integrations (WPForms, Ninja Forms, Forminator).
The auto-injection approach was specifically chosen to avoid AJAX vulnerabilities – the CAPTCHA is injected directly into the form structure before any AJAX submissions occur, so it can’t be bypassed by DOM manipulation or inline field validation updates. This actually strengthens defense against AJAX-based bypass attempts.
Let me know if it works for you. If not, I can remove the integration.
You must be logged in to reply to this topic.
