Hi Matt,
Thank you for reaching out and for the incredibly detailed troubleshooting you’ve already done.
I’ve been testing this on my end using Otter Blocks and Orbit Fox, but so far, I haven’t been able to replicate the disappearance of the Captcha box in my clean environment. This suggests the issue might be specific to the code being injected or a unique combination of settings.
To help us, could you provide a bit more detail?
- Script Contents: Do you have any specific scripts (tracking pixels, custom JS, etc.) currently active within the Header Footer Scripts module? If so, did you try disabling those? Without disabling the entire Header Footer Scripts module.
- The “Mystery” Form: For the one form that still doesn’t work even with the module off, is there anything unique about that page? (e.g., is it inside a popup, a specific layout builder, or using a different template?)
Kind regards!
Script Contents: The only thing I am (was) using Header Scripts for our Facebook embedded live video feed. (No Footer scripts are being used at this point.) The Facebook code can be found at <https://developers.facebook.com/docs/plugins/embedded-video-player/>. But the odd thing is that the pages where I use header/footer script and where I use Otter forms with Captcha are mutually exclusive. That is, there is nothing in the header/footer scripts for the pages with forms.
The “Mystery” form: working in my offline copy of the site, I deactivated every plugin except Otter Blocks, and the Captcha still didn’t appear. Then I realized that that form also has a Gutena form on it, as I was trying to decide which of the two form builders to go with. After removing the Gutena form (which was displaying the Captcha) the Captcha began appearing on the Otter form.
With that bit resolved, I then reactivate the Orbit Fox plugin and… the Captcha disappears. So now it is 100% consistent for me: With Orbit Fox’s Header/Footer scripts enabled, my Otter forms do not display Captchas. Disable Header/Footer scripts and the Captchas return.
So how to we debug this further? I reproduced this on an offline copy of the WP site. I could continue to reduce the complexity of the offline site until I either locate another source of the conflict or end up with something small enough to zip and send over to you. Of course, you probably have better methods of debugging than that, and I am fully open to any suggestion.
I have to go to a meeting now. When I return, I will check for further instructions from you. Lacking that, I will begin reducing the site to see how lean I can make it.
I didn’t mention (here) that this site is running a child theme based on Neve FSE. Not sure if that helps, but having everything inside the Themeisle house certainly should make debugging it a bit easier!
Thanks again,
m
OK, I stripped everything out of the site except Otter Blocks, Orbit Fox, and Backuply. Then I made a backup of the site and restored it to a fresh clean local site. The bug persists.
The resulting .gz file is 32.7MB — if you would like to have it so you can attempt to reproduce the bug, let me know how to get it to you.
Hi Matt,
Thank you for going through those troubleshooting steps and stripping the site down; that’s very helpful data.
While I appreciate the offer to send the backup file, I’m unable to accept or debug custom site backups or local environments due to security and the various server configurations involved.
To help me investigate this effectively, could you please set up a TasteWP instance? If you can reproduce the bug there using only the necessary plugins, please share the login link with me. This allows me to see the issue in a standardized environment and get straight to the root of the problem.
Thank you!
On Feb 17, 2026, at 6:09 AM, WordPress.org Forums <noreply@wordpress.org> wrote:
To help me investigate this effectively, could you please set up a *TasteWP ( https://tastewp.com/ )* instance? If you can reproduce the bug there using only the necessary plugins, please share the login link with me. This allows me to see the issue in a standardized environment and get straight to the root of the problem.
What a frustrating experience! First, that site is apparently incompatible with Safari: attempting to set options for a plugin results in a blank page.
So I switched to Chrome, and still can’t get far before hitting errors. I attempt to upload assets and am faced with a progress bar that never progresses. I can’t even upload my Neve FSE child theme.
So I attempted to install Neve FSE via the standard “Add Theme” route, and… that fails too.
But at lease here’s something for you to investigate: I’ve been seeing this “Function _load_textdomain_just_in_time was called incorrectly” error on my own site, but was ignoring it because I couldn’t see any trouble. But in this environment Neve FSE fails altogether. So…
Here’s the login info: https://tastewp.com/r/QxH0mSrb
I don’t know if you need this as well, but I don’t much care if the password is exposed, because it’s all temporary…
Site name: Lewd Planes
URL: https://lewdplanes.s5-tastewp.com
User: matthewstrange
Pw: -TEGbDG8310
Log in, switch to Appearance > Themes, and activate Neve FSE. You should see the error mentioned above. That’s got me stopped cold.Sort that out an then I can get back to demonstrating the Otter/Orbit conflict.
Thank you,
m
Back to the original report: I was out most of the day, but I was thinking through this issue, and it dawned on me that I never tested against a different theme. It turns out it is something in my Neve FSE child theme. Both Twenty twenty-five and Neve FSE show the Captcha as they should.
So I’ll go digging about in my theme to see what could be causing it. Meanwhile, maybe you can investigate that Function error noted above.
Thanks,
m
Hi Matt,
I’m glad to hear that thing with the Captcha is on the right path.
Regarding the error, thank you for sharing it. It is already reported here https://github.com/Codeinwp/neve-fse/issues/170
Kind regards!
I’ve checked the GitHub report and since you already have it on your radar, I will close out the TasteWP site.
I think this topic has come to the end. Thanks!
m
