Hi mellowvision!
Sorry to hear you are disappointed. We released this version with a notice so that people would be prepared and have time to find a replacement. We have explained our reasoning this blog post today. The caching features of Wordfence were always free and we have no intention of charging for them. Almost all features we add to the plugin are free too. I hope you are able to find a good replacement for caching.
@mellowvision,
I agree with you on this one. WordFence has been making too many drastic changes between versions. Add WAF, take away cache…it’s just not stable. BTW, WP Super Cache coupled with Autoptimize (or another JS & CSS minification/caching plugin) make a good replacement.
@wfasa,
If you guys can understand…that the way you’re making huge changes with little or no notice…can really damage trust in your plugin. It has drastic affects on user sites. Many of us have clients who rely on us, and changes affect them, then they blame us, and so on. Not good.
You really need to reconsider how you handle that. When you added the WAF in 6.1.1, it was a broken update and caused a lot of mayhem. (That’s when we left.) It was a major addition, and not well tested. Same with removing the cache. (Although, I never really thought it should have a cache…that never made sense.)
-
This reply was modified 9 years, 6 months ago by
redsand.
Hi redsand!
I’m sorry that you no longer have faith in our software. However, I will have to respectfully disagree with your description of the situation. The Firewall worked as intended on the vast majority of sites it was installed and we have not seen a decrease in usage of the plugin since it was introduced. The bugs that were reported were primarily related to particular setups on particular hosts. We have since continued to develop the Firewall to ensure it works smoothly in as many environments as possible.
Maybe one day we can make every single user of our software happy. We are not there yet but it is certaily something we strive for.
Thanks for your feeback!
The Firewall worked as intended on the vast majority of sites it was installed and we have not seen a decrease in usage of the plugin since it was introduced.
It may work now (I don’t know)…but it certainly didn’t work reliably when you first introduced it. Disagree all you like, but if you go back to the support forum on that day, it was lit up like crazy. That’s why you had to release updates rapidly over the next day.
Maybe one day we can make every single user of our software happy.
That’s a bit of a rude statement…implying that only a few people had issues. Your support forum only has 101 of 386 support threads resolved. Over 2/3 are unresolved. That’s not something to ignore.
You should take what I’m saying a bit more seriously. I’ve been a WordPress plugin developer for a decade, and am quite familiar with compatibility issues and the challenges of keeping all users happy. That’s not what the issue is. The issue is that you guys make drastic changes.
Hi again redsand,
that I disagree with your assessment of the situation doesn’t mean I don’t take you seriously. I talk to 300-400 customers every month and your feedback is just as important as everyone elses. We do watch for patterns in support requests and if something seems to be affecting a significant amount of users we try to fix it as soon as we can. As for the resolved ratio I’m currently in the process of going through old threads to make sure resolved threads are set to resolved and to pick up any threads we may have missed. Again, sorry you had a bad experience with Wordfence.
