Keeping Falcon Engine For Caching

  • Resolved Dutchman

    (@rotju)


    8 years, 1 month ago

    Hi there,

    After hearing that you guys are removing the falcon engine completely from Wordfence, I tried to replace it with other caching plugins. Unfortunately I have not manage to get the same results (after almost a year of trying hundreds of settings and following so many tips and tricks, with almost any caching plugin) as Falcon Caching.

    So I’m thinking of keeping an outdated Wordfence purely for Falcon Engine so I can keep my network running fast and I’ll replace the security with another plugin.

    Just wondering if it was possible to detach Falcon Engine into a separate plugin or use a code snippet to remove all the other options from Wordfence, so I’m only having Falcon caching options?

    Cheers.

Viewing 5 replies - 1 through 5 (of 5 total)
  • David

    (@david_wethinkapp)

    Please, keep falcon engine. This was a great feature in Wordfence.

    None of the Wordfence caching ever worked for me. Glad to hear it worked for someone else. Plugins that don’t work should be fixed or discontinued. MTN

    Honestly, I’m thinking about following Dutchman’s lead and not updating Wordfence so I can keep Falcon Cache. I’ve also tried several other caching plugins and Falcon Cache outperforms them all. I don’t want to lose it!

    The last people people should want is for WordFence to become bloatware.
    It should stay being a high-performance firewall with no “bells and whistles!”

    Hi guys,
    I’m afraid we have no plans to maintain the Falcon code in any shape or form. You can read more about our decision to remove it on our blog.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Keeping Falcon Engine For Caching’ is closed to new replies.