Falcon engine, why not a separate plugin?

  • Resolved allm

    (@realblueorange)


    10 years, 7 months ago

    @mark

    I am wondering why the falcon engine was not made into a separate plugin. It seems so out of place in WordFence. Having it as a separate plugin would give people an easy choice if they wanted to use that. Now the plugin that I have come to like very much has a large unknown chunk in it that I really don’t need.

    I guess a lot of your user base already has some kind of caching going on.

    Furthermore, where can I find what the new version will do to my .htaccess and under what circumstances? I have my own .htaccess and don’t want WordFence to mess with it. But I still want to be able to block IP’s. I was happy with the way it was.

    Mark, would you reconsider adding falcon engine to Wordfence? A separate plugin seems to be the optimal way to go.

    https://www.ads-software.com/plugins/wordfence/

Viewing 2 replies - 16 through 17 (of 17 total)
  • Plugin Author Wordfence Security

    (@mmaunder)

    Hi,

    Yes live traffic still works with falcon off.

    OK we’re going to decouple how we block IP’s from whether you have caching enabled or not. So you can choose how you want to block IP addresses. Will be in the next release.

    Regards,

    Mark.

    Thread Starter allm

    (@realblueorange)

    @mark

    That is much appreciated! I’ll see it when it comes out.
    I’ll set this to resolved.
    Best wishes!

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Falcon engine, why not a separate plugin?’ is closed to new replies.

Tags