Plugin Support
Kim L
(@kimmyx)
Hi @realact,
Thanks for the report!
Our dev team is already aware of this and is looking into it.
We’ll get back to you as soon as we receive feedback. 🙏
We appreciate your patience and let us know if you have other questions.
@realact – Sorry for the delays. v2.6.0 should clear that up, once WordFence updates it to cleared as well.
IMHO Ultra Low level at best, but they don’t ask us. Your site can’t be hacked, nothing can be changed etc.
Took longer than expected to come up with a simple & elegant solution that didn’t break anything else along the way.
Ultimately you had to have already chosen to expose your protected content in archives with a “Restricted Content” style notice in place of its content for this to have had any impact. You can read about it here: https://contentcontrolplugin.com/docs/security/preventing-bots-from-discovering-restricted-content/#how-content-can-be-exposed
Thread Starter
Eli
(@realact)
@kimmyx and @danieliser thanks for the update and clarification.
