forge12marc
Forum Replies Created
-
Hi @bonaldi,
thanks for reporting the issue. Would it be possible to provide us a duplicator copy of your page via WeTransfer to info@forge12.com so we can check the issue and provide a solution?Unfortunately we do not have a “Pro”-Version of the SecuPress of the Plugin
Best Regards
MarcHallo @ilafarad,
vielen Dank für deine Nachricht. Das Problem sollte mit Version 3.2.1 behoben sein.
Viele Grüße
MarcHello @gromgrom,
Thanks — that registration form is generated by a WordPress plugin we don’t currently support, which is why you’re seeing “captcha failed.” Please share the plugin name + version (and a link), and we’ll evaluate a possible integration.
Hi @twuerzner ,
thanks for the update and for taking the time to track this down.
Good to know that the issue was caused by an interaction with Wordfence Login Security. We’ll keep this in mind and monitor potential compatibility improvements on our side.
Glad to hear it’s resolved. Thanks for closing the loop.
Hello @stdorsch
Thanks for the detailed bug report and the clear analysis – much appreciated.
You’re absolutely right about the observer feedback loop. We identified the same root cause: a rare edge case where DOM mutations triggered a captcha reload, which in turn caused further mutations, resulting in an infinite loop.
This issue has already been fixed and rolled out in Silentshield version 2.2.61.
Please update to the latest version and the infinite reloads should stop immediately.Thanks again for taking the time to report this so thoroughly.
Best regards
MarcDear Nicole,
thanks for the details. To properly investigate why the CF7 “mail” and “mail_2” emails are not sent after the double opt-in confirmation, please send us a full copy of the affected site as a Duplicator package (archive +
installer.php).Please upload it via WeTransfer and send the download link to info@forge12.com. Once we have the package, we’ll reproduce the issue and check it for you.
Best regards,
Marc / forge12 TeamHi Tobi,
thank you for the details.
From the screenshot it appears that the WordPress login page has been modified. In that case, SilentShield’s CAPTCHA script can no longer hook into the page correctly, which causes the login request to be flagged as spam. This would explain why the issue disappears once the “WordPress Login” protection is disabled.
To investigate this properly, we’ll need a bit more information:
– A link to the affected website.
– The name of the plugin or theme feature that modifies the WordPress login page.
– Ideally, a Duplicator archive (including the installer.php) so we can reproduce the issue on our end.
Please send the archive securely via WeTransfer to info@forge12.com.
Once we receive these details, we’ll analyze the environment and provide a solution.
Best wishes,
MarcDear Nicole,
thank you for reaching out.
If the CF7 “mail” and “mail_2” emails are not being sent after a successful double opt-in, this usually indicates that a CAPTCHA plugin is blocking the message as suspected spam.
Here’s what happens technically:
Our plugin stores the submitted form data and, after the user confirms the opt-in, resends it through the same process that Contact Form 7 normally uses. If a third-party CAPTCHA is active, the verification code is no longer valid at that second submission step. Most CAPTCHA plugins therefore block the email before CF7 can send it.For this reason, we recommend using our integrated CAPTCHA solution, SilentShield, which is fully compatible with the Double Opt-In workflow. SilentShield is available for free in the WordPress plugin directory.
This behavior is not a bug. It is the CAPTCHA preventing the re-submission. Switching to SilentShield should restore the expected CF7 email sending behavior.
If you need assistance verifying your setup, feel free to share your plugin versions or configuration details.
Best regards,
MarcHello @lebensweltenwanderin,
thanks for your message.To investigate the connection issues with ManageWP, we need more concrete information.
Could you please send us the Error Log and Access Logs of the affected site?Additionally, it would help significantly if you could create a temporary access for us:
• Access to the affected WordPress installation
• Optional but highly recommended: Access to your ManageWP environmentPlease send the access details securely to info@forge12.com.
Without this, it will be very difficult for us to identify the root cause.Thank you in advance!
@nils235 ,
thanks for the update.
We’re continuing to investigate the issue, but so far we haven’t been able to reproduce the problem in any of our test environments. All multi-step WPForms installations are functioning normally on our side.
Our current assumption is that this may be caused by a plugin or theme incompatibility in your specific setup. That makes it significantly harder for us to identify the root cause without a test environment where the issue actually occurs.
If you can provide access to a staging site where the problem is still reproducible, we can examine it in detail.
Best Regards
MarcHey @nils235 ,
yes, this does ring a bell.
From what I can see, reCAPTCHA is trying to call a JavaScript callback function that doesn’t exist in our plugin. At the same time, you seem to have both Google reCAPTCHA and our captcha plugin active in parallel. That’s usually where things start to collide – one script expects a function that the other plugin simply doesn’t provide.
Without knowing exactly which plugin is registering that callback and in which order the scripts are loaded, it’s very hard to reliably trace and fix this from the outside.
To look into this properly and safely on our side, it would be best if you could send us a password-protected archive (ZIP) of the site (files + database) via WeTransfer.
Please send the download link there, and the password separately via email to: info@forge12.comWe’ll set this up in our local environment, identify the conflicting plugin/implementation, and come back to you with a clean solution.
Best,
MarcHi @nils235 ,
thanks for reaching out.
The message “Captcha not valid: javascript-protection” is often caused by plugin or theme compatibility issues. On our end, Ultimate Member is running without any problems on the current version.To investigate this properly, we would need either
– access to a staging environment, or
– a full site copy via Duplicator.With that, we can reproduce the issue and analyze it in detail.
Best regards,
MarcDas Problem scheint behoben, ich schließe das Ticket damit.
Hallo @pigsound,
mit der Pro-Version läuft das einwandfrei. Wenn bei dir etwas hakt, schauen wir es uns gemeinsam an.
Hi @skyfly024 ,
Hotfix v2.2.56 is live. It addresses the issue you reported. Please confirm whether it’s resolved on your end.