1. The plugin does not use any .htaccess whatsoever. So no nginx either.
2. All of my plugins are aimed at stellar performance and flexibility. No conflicts at all.
3. BBQ (free) works great with or without .htaccess rules in place.
4. BBQ Pro is like the free version combined with 5/6G Firewalls. None of my plugins involve any .htaccess whatsoever. They all work fine if you are using .htaccess, but none require or conflict with any .htaccess.
Thanks for quick reply. when I was on your page about the bbq pro I followed the link to your 5/6G firewalls page and under requirements I read this:
Before installing 6G, please make sure that your setup meets the requirements:
Apache version 2 or better, .htaccess files enabled on your server, and a link to read more about htaccess…
I put some htaccess rules in my nginx.conf because my server set up doesn’t use htaccess at all — and your excellent code hasn’t conflicted with my current nginx configuration.
— the way you designed them to function: htaccess/apache is required for bbq pro? and htaccess not required for free version of block bad bot or free bbq?
I really appreciate your time and attention — and your great products.
Glad to help. It looks like you were reading the requirements for the 5G/6G Firewalls, which do require .htaccess. My plugins, however, do not require .htaccess.
Here is a summary of requirements, just to be absolutely 100% clear:
– 5G/6G Firewall : these require Apache/.htaccess
– All of my WP plugins : do NOT require any .htaccess whatsoever, only WordPress
Again, my plugins are all totally compatible with .htaccess, but none of them use/require .htaccess in any way. I hope this is clear, please let me know if I can elaborate.
Oh my gosh! That is fabulous! Thanks so much for making it clear to me. I love the idea of the bot getting tricked for a change! I’m very glad to have found your plugins and your great resources. . Thanks again so much for your help! ciao!
