forge12marc
Forum Replies Created
-
Hi Werner (@wauf),
thank you for the detailed report. We’ve identified the issue you described and fixed it in the latest release. Please update to version 2.2.47, which ensures CAPTCHA images are refreshed correctly on each page load.
If everything works smoothly now, we’d greatly appreciate your feedback here:
https://wordpress.org/support/plugin/captcha-for-contact-form-7/reviews/#new-postBest regards,
MarcHello @pluggedindev
thank you for sending over the debug log. We’ve identified the issue and resolved it in version 2.2.46. Please update to the latest release.
If you find everything working well now, we’d greatly appreciate your feedback here:
https://wordpress.org/support/plugin/captcha-for-contact-form-7/reviews/#new-postBest regards,
MarcHello @bonaldi
thank you for pointing this out.
You’re right – labels like Extended and Dashboard should be translatable for a perfect interface. We already have this on our roadmap, but it’s not the highest priority at the moment.Still, we’ll make sure it’s included in a future update. Thanks again for the feedback!
Best regards,
MarcHello Daniel (@danielbinda ),
I’m very glad to hear that version 2.2.45 resolved the issue on both of your websites without any extra action. Thank you for letting us know!
Your feedback helps us a lot in keeping the project growing.
Best regards,
MarcHello @senjoralfonso
thank you for sending the log file via email.
From what I can see, it looks like the default settings were overwritten – in the log I only see that the protection options are disabled. Please try the following steps:
1) Go to SilentShield → Settings → Dashboard and make sure the main CAPTCHA option is enabled (checkbox).
2) Then go to SilentShield → Settings → Extended and select the module you want to protect (e.g. Contact Form 7, Avada, WordPress Login/Registration, etc.).
3) Save the settings and test again.If the issue still occurs after that, please send us a new log file together with the link to the affected website so we can check more closely.
Additionally, we recommend enabling Browser Protection and JavaScript Protection in the settings for stronger security.
Best regards,
MarcHello @pluggedindev
thank you for the update — glad to hear the critical error is fixed.
For the new error on form submission, could you please enable WordPress debug logging so we can analyze it further?
1) In
wp-config.php, set:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);2) Submit the affected form once to trigger the error.
3) A logfile should then be created under:
wp-content/uploads/f12-logs/plugins-2025-09-22.log4) Please send this file to info@forge12.com with a short note about which form/page you tested.
This will allow us to track down the issue quickly.
Hello @senjoralfonso
First, can you please confirm that you are running the latest release 2.2.44 of SilentShield?
This version includes a fix for the Arithmetic CAPTCHA issue in Contact Form 7.If you are already on 2.2.44 and the problem still persists, please enable WordPress debug logging so we can analyze it further:
1) In
wp-config.php, set:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);2) Submit the affected form once to trigger the error.
3) A logfile should be created under:
wp-content/uploads/f12-logs/plugins-2025-09-22.log4) Please send this file to info@forge12.com with a short note about which form/page you tested.
This will allow us to track down the issue quickly.
Hello @senjoralfonso
the shortcode-based CAPTCHA integration was already marked as deprecated in version 2.0 and has been fully removed with version 2.2.4 to keep the codebase clean and maintainable.
To restore CAPTCHA in your Contact Form 7 forms, please go to:
SilentShield → Settings → Extended
and enable the Contact Form 7 integration there. This will automatically protect all your CF7 forms without requiring shortcodes.Our goal is to provide an invisible shield – effective protection against spam that works seamlessly, without disrupting your visitors.
Best regards,
MarcHello @wauf ,
thank you for providing the log file – this allowed us to identify the issue.
We have fixed the problem, and it is already corrected in the latest release of SilentShield.
Please update the plugin, and the form should be protected again as expected.Thank you for your support and feedback.
Best regards,
MarcHello @pluggedindev ,
thank you for reporting this.
The critical error has already been fixed in the latest release.Please update SilentShield to the newest version – it should now run without any issues.
Best regards,
MarcHello @bonaldi
thank you for reporting this.
The issue with the manual delete buttons has already been fixed in the latest release.Please update SilentShield to the newest version, and the buttons should now work as expected.
Best regards,
MarcHi @bonaldi ,
thank you for testing again and for your feedback.
On telemetry:
SilentShield does not send any personal data. Only technical plugin usage information is collected.
There are no emails, no names, no IP addresses, and no form content being transmitted.As mentioned above, the complete list of collected fields is:
plugin_slug(technical identifier)plugin_version(release used)snapshot_date(collection date)settings_json(active configuration options, pseudonymized)features_json(which features are enabled)created_at,first_seen,last_seen(timestamps, anonymized)counters_json(usage counts of spam protection events)wp_version(WordPress version)php_version(PHP version)locale(site language)
That’s the full scope. Nothing else is collected.
SilentShield remains completely GDPR-compliant, as no personal data is ever processed.Best regards,
MarcHello @wauf ,
thanks for the detailed report and the version info.
First, please try a quick reset of the integration state:
1) Open SilentShield → Settings and click Save once (even if nothing changed).
2) Go to SilentShield → Settings → Extended, make sure WordPress Login and Elementor are enabled, then Save again.
3) Clear any page/cache plugin you might use and test the login page + an Elementor form.If the CAPTCHA still doesn’t appear:
4) Enable WordPress debugging so we can capture a clean trace:
- In
wp-config.php, set:define('WP_DEBUG', true);define('WP_DEBUG_LOG', true);define('WP_DEBUG_DISPLAY', false);
5) Submit the affected form once and also visit the WP login page to trigger the hooks.
6) A log file should be created at:wp-content/uploads/f12-logs/plugins-2025-09-22.log
7) Please email that file to info@forge12.com with a short note about which page/form you tested.
This will let us pinpoint the cause quickly. If anything changes after re-saving the settings, let us know.
Hello @pluggedindev ,
sorry for the critical error – that should not happen.
Could you please enable WordPress debug mode (WP_DEBUG) and share the exact error message or stack trace from your log?
This will help us identify the cause immediately.We want SilentShield to be stable and lightweight – thanks for reporting this so we can fix it quickly.
Best regards,
MarcHello @businessdesign20,
thank you for your question.
SilentShield is provided completely free of charge. Because of this, we unfortunately cannot support every premium plugin on the market – otherwise our maintenance costs would explode.
At the moment we therefore do not plan to integrate EventsManager into the free version of SilentShield.
However, we are considering offering a premium solution in the future that could cover such integrations.Our focus remains: providing strong, reliable spam protection for the most widely used WordPress form plugins, free for everyone.
Best regards,
Marc