Hello @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/counts
You should find it in your browser’s developer console under the Network tab.
Best regards,
Hi Marc,
I’m not sure if that’s what you asked me, but anyway.
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 ,
Hi Marc,
Hello @bonaldi ,
thank you for your response. I need the Information on the right side:
Can you provide a screenshot like this ?
Best Regards
This reply was modified 5 days, 13 hours ago by forge12marc
Hi Marc,
Everything is at zero even though multiple accesses have occurred.
Furthermore, there are database records that may be related?
Regards.
Hello @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
Hi Marc,
Since the number of templates has increased, you could avoid having to retranslate with each change by replacing “Yes. Choose from 3 built-in templates” in the wp.org readme file with “Yes. Choose from various built-in templates“.
Regards.
Hi again about telemetry…
“We’ve identified the issue causing telemetry to trigger even when disabled. This will be resolved in the upcoming patch. “
This isn’t resolved: the cron job is still running .
Furthermore, it’s opt-out, which isn’t ideal for a plugin that promises GDPR compliance.
Hello @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
OK, I will check in the coming days.
Danke.
