forge12marc

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

Hello,
We do not have IP blocking yet, but I will add it to our feature list. Still our plugin works well on WooCommerce using the default protection methods (JavaScript, Blacklist, Multiple-Submission and Honeypot)

Best Regards

Hallo @knallblaumedia ,

wir haben den Support für FluentForms hinzugefügt.

Herzliche Grüße
Marc

Hi Marc,

Thanks for the clarification.

Even without a dedicated security plugin like WordFence, 403 errors can still occur due to server-level restrictions. Here are a couple of possibilities to check:

1. ModSecurity (Server-Side WAF):
   Many hosting providers have ModSecurity or similar protections enabled by default. These can block specific requests based on patterns or keywords (e.g. “blacklist”, “block”, etc.). It’s worth checking with your hosting provider if any rules were triggered during the save attempt.
2. .htaccess Rules or Server Config:
   Occasionally, rules in .htaccess (or nginx configuration) can inadvertently block POST requests or certain query parameters. If you’ve made recent changes to .htaccess, it may be worth reviewing or temporarily restoring a default version.

If you’d like, I can take a closer look at the specific request triggering the error—e.g. by enabling WP_DEBUG or inspecting the server logs.

Best regards,
Marc