Thread Starter
iqdot
(@iqdot)
How can I stop Word fence from over wring by custom htaccess entries when i change cache level ?
When options won’t save, usually it can be fixed by going to the options page and turning on “Disable config caching” to stop Wordfence options from being cached. (This isn’t a problem for most hosts, but some seem to have trouble with it.) Another possibility, if you’ve moved hosts or restored a backup, is that the database may not have the correct privileges.
Wordfence shouldn’t overwrite any custom .htaccess options, unless they are in between the comments that include “WFCACHECODE” and “WFIPBLOCKS”. Wordfence uses a comment at the start and end of each section, to determine which code to remove. If your custom code is already outside of these sections, can you post a copy on pastebin.com, and paste a link to it here?
Make sure to remove any sensitive information, like IP addresses.
If you can disable Falcon cache successfully, you won’t need to post the .htaccess file here, since Wordfence doesn’t currently modify .htaccess when Falcon is disabled.
-Matt R
