Plugin prevents users from logging in (Captcha Error)

I’ve had the same problem with all client websites that use the plugin since at least version 2.6.8. I was hoping the update to 2.6.9 would fix it, but no luck. I’ve deactivated the plugin everywhere until there’s a solution. Making the settings more restrictive without consulting the users is unacceptable. That’s really intrusive. Besides, the plugin has become unnecessarily complicated. Its simplicity was the main reason I chose this plugin in the first place.

Hi Marc, thank you so much for the quick reply! I ran a test on a website and disabled all plugins except Elementor and Elementor Pro. It’s working now with the update to 2.6.11 (login is working again). And thank you for making it clearer and now allowing you to immediately see whether something is enabled or disabled by color. One tip: Some presets were unnecessarily enabled (e.g., WooCommerce, Fluent Forms, JetForm, etc., even though they weren’t installed). It’s also unclear what the small arrows in the settings are for, as there’s no interaction with them. It might also be interesting to know that if you go to Plugins -> Silent Shield -> Settings, you still end up at the old user interface (wp-admin/admin.php?page=f12-cf7-captcha) and you don’t have any permissions to make changes there. It says (in German, in my case): “Du bist leider nicht berechtigt, auf diese Seite zuzugreifen.” (e.g., wp-admin/admin.php?page=f12-cf7-captcha_f12-cf7-captcha-extended). I was briefly pleased that you had reverted to the old user interface because I found it so intuitive and easy to use (especially with the clear explanations for each setting on the right side of the screen – you immediately understood what you were doing). Unfortunately, no. The new interface is still confusing and unnecessarily unclear, but the main thing is that it works again. One more thing: When you go to “View Audit Logs” in the dashboard widget, the missing access permission message appears again (wp-admin/admin.php?page=f12-cf7-captcha-audit-log). And what’s the point of the telemetry under “Recent Issues” that only shows errors? (TELEMETRY_UNEXPECTED_RESPONSE
Telemetry API returned HTTP 401)? All I can say is: For users like me, it’s incredibly frustrating when a plugin is changed so drastically that you no longer understand every other function and have to painstakingly work your way through it. The explanations that were previously available are gone everywhere. And the nagging feeling that something might not be working or isn’t configured correctly remains. I also wasn’t aware that I was missing a “protection score” (Schutz-Score) in the WordPress dashboard, which takes up an insane amount of space and contains virtually no useful information. Then “Data cleanup”: Delete all logs. Delete old logs… One has a trash can icon (logical), the other a clock (illogical). Where do you delete them? Trial and error… Guys, go back to your good old user interface. It was so much better.