forge12marc
Forum Replies Created
-
It seems someone changed the translation from “Avada” to “Optionen”. To use Avada enable the “Optionen” that should fix your issue. We will update the Plugin soon providing a fix for the naming issue.
Let me know if that solved your issue or if you need further assistance.
Best Regards
MarcHi Marc,
Avada Forms is still supported. Please go to Silentshield > Forms > Avada and ensure that it has been enabled. Disable the override toggle if not required.You can set the global CAPTCHA type within the protection settings.
If you need further assistance, do not hesitate to contact me.
Best Regards
MarcHello @bonaldi ,
unfortunatelly we did not receive any mail. Can you send us the data using wetransfer to [email protected] ?
Best Regards
MarcBonjour nathanstaing,
Merci pour ces informations détaillées !
La description du problème étant assez vague sans pouvoir y accéder directement, nous aimerions jeter un œil nous-mêmes. Pourriez-vous nous envoyer un accès à l’adresse suivante : [email protected]
Une fois que nous aurons pu analyser la situation, nous vous ferons part de nos conclusions ici dans le forum.
Merci et bonne journée !
Bonjour nathanstaing,
Merci pour votre message !
Pourriez-vous nous préciser les points suivants afin que nous puissions vous aider au mieux :
1. Quelle version du plugin SilentShield utilisez-vous actuellement ?
2. Quel est exactement le problème – la collecte de données s’est-elle complètement arrêtée, ou les données sont-elles simplement incomplètes ?
3. Y a-t-il des messages d’erreur qui s’affichent dans votre tableau de bord ?
Avec ces informations, nous pourrons trouver une solution rapidement.
CordialementHi @bonaldi,
yes that sounds very interesting. I didn’t reply because we try to figure out what’s the best way to allow the community to translate items.
Best Regards
MarcHello @bonaldi,
thank you for your feedback. Would it be possible to send us a copy using duplicator of the page via mail to [email protected] ?
Best Regards
MarcHello @bonaldi ,
Could you please verify this again?
We identified and resolved an edge case where the telemetry cron job was not being properly removed.
To ensure everything is now functioning correctly, please resave the settings once.
Best Regards
MarcHello @solanum,
thank you for your feedback. Glad it worked for you.
thank you very much for taking the time to share such detailed feedback — we really appreciate it.
We’ve already implemented several improvements based on feedback like yours to further optimize the captcha experience. The dashboard has been significantly reduced in size, and we’ve added more descriptive texts to better explain what is triggered and why.
Additionally, the TELEMETRY errors have been filtered — these are only relevant for support cases and shouldn’t clutter the interface anymore.
That said, feedback like yours is extremely valuable to us. If there are specific areas you still find unclear or confusing, we’d love to hear more details so we can continue improving the experience.
Thanks again for your input — it really helps us move the product in the right direction.
Hello @bonaldi,
thank you for your support. We’ve updated the plugin – can you verify if that solves your issue?Best Regards
MarcHello @bonaldi,
thank you for your detailed feedback. The issues you described have been identified and resolved in version 2.6.11.
If you still experience any problems after updating, feel free to reach out — we’re happy to take a closer look.
Best Regards
Marchello @solanum,
hello @blacckmamba,Thank you for your reports and detailed feedback.
The issues you described (especially login problems related to captcha validation and overly restrictive default settings) have been identified and resolved in version 2.6.11.
We’ve also simplified the configuration to address the concerns about increasing complexity. You can now enable or disable individual captcha methods directly via toggles under:
Silentshield → Forms
This allows much more precise control and prevents situations where global settings unintentionally block access (such as backend logins).
If you previously disabled the plugin due to these issues, we recommend updating to version 2.6.11 and reviewing the new form settings.
If you still experience any problems after updating, feel free to reach out — we’re happy to take a closer look.
Thank you again for pointing this out.
Best Regards
MarcHello @bonaldi ,
thank you for your response. I need the Information on the right side:
Can you provide a screenshot like this ?
Best Regards
Marc- This reply was modified 2 weeks, 6 days ago by forge12marc.
Hi @bonaldi,
thanks für your Feedback. Can you click on one of those “counts” lines to open the response from this call and send/submit the screenshot here ? This should contain the real counters/numbers from your database.
On our test enviroment everything works fine, therefor we need to check if it is backend/frontend related.
Thanks ,
MarcHello @bonaldi,
Thanks for your message.
We’ve identified the issue causing telemetry to trigger even when disabled. This will be resolved in the upcoming patch.
Please send us a screenshot of the Data Cleanup page.
Also, open the page and share the response from the following request:
/wp-json/f12-cf7-captcha/v1/cleanup/countsYou should find it in your browser’s developer console under the Network tab.
Best regards,
Marc