Oh hi there @wfasa
Why do you keep telling me it’s not a problem when my host says it IS a problem?
No, I’m not worried about being ‘friendly’ here — you’re not getting my meaning and so I have to be SUPER CLEAR. If you take offense to that that is an error on your part. I’m being exceptionally blunt in hopes that you’ll FINALLY get my meaning.
But apparently you either are unwilling to hear what I have to say or unable to hear it. That’s bothersome. And that just draws out conversation and leads to nothing getting done.
If you had told me from the beginning that the option no longer existed to disable cookies, not anywhere…then I could have solved my issue sooner.
Now, I’ve wasted time trying to re-state my issue over and over again, in hopes that you’d finally ‘get’ what I’m saying. To find out if Wordfence will allow users to disable its use of cookies.
Now, you tell me that there is not a way to disable cookies, not in any way.
That’s not good.
The problem isn’t WHERE Wordfence uses cookies — it’s that they use cookies at all.
Again — this is what my host confirmed. It is not a ‘guess’ or a ‘maybe’ — and it is not a problem, lol, with a particular cookie.
And again, I’ll state that this is a problem that Wordfence has known about for years — that’s why the helpfile I linked to at the start of this post existed. Because it was, and is, a known problem. But for some ungodly reason, Wordfence chose to take that solution away that they developed….WHY IN THE WORLD they’d do that, I have no idea.
It’s still a problem.
And for some reason, you’re trying to deflect blame for Wordfence un-solving a problem that the Wordfence plugin is known to cause. Just admit Wordfence made a very bad decision to take away that option for us to solve their incompatibility with managed hosting/CDN caching…and let them know to fix it, please.
Because at this point, all you’re doing is giving me “explanations” to a problem that is not the actual problem.
The problem is not “we disabled cookies on the front end, so all should be okay!”….the fact that you took away the ability for users to turn off your use of cookies is the problem, not, lol….the fact that cookies were used on the front end.
It’s that Wordfence uses cookies, takes them away from the host’s/CDN’s cache system. SO that renders it inoperable.
Front end cookies vs. back end cookies? IRRELEVANT.
And your, lol, taking them away on the front end is not a solution; it is possibly even a detriment.
Wordfence cannot take control of cookies over the site’s host taking control of cookies for its caching system. It’s just not gonna work. So we need to STILL have that option to shut them off.
Capesh?
AND HOW do I know that disabling all Wordfence cookies is STILL a valid solution….?
Well!
I went ahead and restored an older copy to my site; the only difference being the Wordfence plugin being from when you could still disable cookies….juuuuust like your own helpfile says to do.
And guesssss what?
My host no longer says that their cache is disabled because of Wordfence using cookies. Of Wordfence taking control of cookies away from my host’s cache system.
It’s Wordfence’s issue. One they knew about for years. One that they even went so far as to write a help page for it, to have users resolve it.
Why in the WORLD would Wordfence take away a solution from users? While not solving the problem on Wordfence’s end — the problem being that Wordfence battles with a host’s caching system, takes its use of cookies away from it…and renders that host’s caching UNABLE TO WORK AT ALL…??? This ‘cookie battle’ is a known problem, again……one that Wordfence has known about for years. It’s not like we can ‘uninstall’ these caches. We depend on them to keep our sites functional. And since I can’t uninstall my managed host/CDN’s caches, and DEPEND on them to have my site remain FUNCTIONAL…I have to either use an older copy of Wordfence where they STILL allowed us to solve the issue, lol…or upgrade to a version of Wordfence that no longer allows users to solve this issue.
You know how super not-intelligent that is of Wordfence to have done? How incredibly non-productive, non-helpful, and non-wise it is? It renders Wordfence USELESS.
SO for now, I’m using an old version of Wordfence. And looking at other security solutions as a result.
Great job on castrating your own plugin. Wonderful.
Please find a fix for this — I mean, seriously….give us back the option to disable cookies in the upcoming versions OR get your program to play nice with host caching/CDNs.
At the very least, if you’re gonna take control of cookies away from my host and render its caching system useless, then give us a warning. Say that Wordfence is no longer compatible on managed hosting/CDN plans.
Because it isn’t.
And that’s the truth.
And lol, no….Wordfence did NOT solve anything by taking cookies away from ‘the front end’…LOL omfg. It’s that Wordfence uses cookies. Period. Doesn’t matter where it uses them, because it always uses them like a greedy child. And doesn’t allow anyone else to use them.
Fix that, and you’ll have fixed the issue Wordfence KNEW ABOUT FOR YEARS and has now no longer allowed users to rectify. LOL YOU WROTE A HELP ARTICLE ABOUT IT, hahaha…..this is NOT NEW NEWS.
FFS.
