forge12marc
Forum Replies Created
-
Hello @bonaldi,
thank you for your feedback. Would it be possible to send us a copy using duplicator of the page via mail to info@forge12.com ?
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 4 months, 2 weeks 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,
MarcHello @bonaldi
thanks for pointing this out — you’re absolutely right.
We’re aware that using translatable strings inside .json files creates limitations with the current wp.org tooling, and we take this seriously. An incomplete or inconsistent translation experience is not acceptable for us.
We’re currently working on a solution that aligns better with the existing translation ecosystem, so the community — and especially contributors like you — can reliably add and maintain translations again.
Appreciate your note on the French translations as well. We’ll review and correct those to properly follow the locale guidelines.
Thanks again for your input — this is exactly the kind of feedback that helps us improve the product in the right direction.
Best,
MarcHello @groovyx9,
thanks for your honest feedback — we understand the frustration.
You can disable the plugin completely for specific forms using the per-form override:
Forms → WordPress Login → enable the override.Once enabled, all features are turned off by default for that form, giving you full control without interference.
We’re actively working on simplifying the experience and making sure it stays lightweight and intuitive.
Thanks again for taking the time to share your thoughts.
Best Regards
MarcHello @bonaldi ,
thanks for your feedback. The update including the bugfix has been released.
Best Regards
MarcHello @bonaldi ,
thanks for your feedback. I’ve updated the translation files. Hopefully i understand you correct. Let me know if you have additional feedback.
Best Regards
MarcHello @bonaldi ,
thank you for reporting this issue. I’ve prepared a quickfix (2.6.6) solving the issue.
Best Regards
MarcHello @tigere,
yes – you have to remove it. Also ensure that you do not have any keywords within the tab “discussion”. Contact Form 7 also uses this entries to verify with their internal keyword base spam protection.
Best Regards
Marc