forge12marc

Hello @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,
Marc

Hello @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,
Marc

Hello @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 [email protected] 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 @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

Hi @bonaldi

thank you for raising your concerns – I value your contribution and the fact that you hold us to a high standard.

We just released a hotfix that should address the issues you mentioned:

1. CF7 / WP Form Lite forms disappearing – this was caused by a regression. The hotfix restores compatibility. If for any reason the forms are still missing, please go to Settings → Extended and simply re-enable the required services manually.
2. Code comments in German – agreed, this penalizes contributions. We have started translating all comments into English so that the codebase is accessible to everyone.
3. Telemetry toggle – fixed. The toggle now respects the user’s choice. Telemetry remains pseudonymized and limited to plugin usage data only (see updated README for the full list of collected fields).

On telemetry:
SilentShield does collect usage data by default, but it is fully pseudonymized and limited strictly to plugin-related technical information. We do not collect IP addresses, no form data, and no personal user data of any kind. Only plugin usage is measured – nothing that can identify a person or site visitor.

To make this transparent, we have updated the README to list every single field that is tracked:

• 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 complete list. Nothing else is collected.

The purpose is solely to understand which features are actually used, so we can improve defaults, remove unnecessary complexity, and keep the plugin lightweight.

SilentShield will always remain GDPR-compliant. But just as important: it will remain transparent – and you should know exactly what is being collected.

Best regards,
Marc

Hello @derroth ,

As we did not get any update, I’ll close the ticket for the moment. If you need further assistance, feel free to open a new ticket.

Best Regards,
Marc

Hello @pluggedindev ,

Thank you for your feedback. We’ve updated the Plugin releasing many bug fixes and improvements. Can you check if your issue has been resolved too?

Best Regards
Marc