There is another issue with wordfence that happend to me. When you optimize your firewall you have to save .htaccess file before. That is important now, because when wordfence updates the htaccess file the block ‘# BEGIN WordPress’ is not found in htaccess because we now have ‘# BEGIN ClassicPress’, so the complete block from ‘# BEGIN ClassicPress’ to ‘# END ClassicPress’ it will be deleted by wordfence…
I just did a quick test and WordFence did not delete this block for me, it just added its own rules to the end of the file.
Hmmm, I also did test it again and you are right.
It definitely happend to me a few times but that might have been caused by another issue…
This time in my test it does not change/delete the block like I wrote …
I’m sorry for this confusion…
2 Likes
Let us know if you find the issue again, but really, any plugin or program that modifies the .htaccess file needs to leave a section alone if it doesn’t know what it is…