Support » Plugin: Wordfence Security - Firewall, Malware Scan, and Login Security » Wordfence saves in incorrect .htaccess file

  • Hi and thanks for a great plugin.

    I originally installed WordPress in a subdirectory while building the site with Wordfence working perfectly.

    When the site went live I changed the Site Address (URL) to the Root directory edited index.php to point to the subdirectory and placed that in the Root directory.

    After doing this when enabling Falcon engine Wordfence places the code in the old .htaccess file in the subdirectory not the root

    It is also not connecting to the API servers either. On the Dashboard it constantly displays “We’re collecting data, please check back soon.”

    Can you help?

    Thanks

    Peter

    https://wordpress.org/plugins/wordfence/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Check the site and home urls in the WP settings page to be sure they don’t have the old path.
    If that’s fine then do a complete reinstall.
    Check the option to competent remove Wordfence tables and data on deactivation (bottom of options page). Export your settings (also bottom of options page) then deactivate the plugin. You can re-activate at this point but if it was me, I’d remove the Wordfence plugin via Ftp and readd it Then import settings again (also bottom of options page) That should fix it please let me know

    Tim

    Thread Starter bond138

    (@bond138)

    Thanks Tim

    The URl’s in the WP settings are correct.

    I had already tried deactivating and clearing the DB to no avail.

    I have just deactivated clearing the DB and deleted Wordfence via FTP. I’ve installed it again but unfortunately it hasn’t resolved my issue.

    Do you have any other suggestions, thanks?

    Peter

    This problem was raised a year ago: https://wordpress.org/support/topic/falcon-activation-problem-and-a-workaround

    I hope Wordfence Support will come up with a solution soon. Having WordPress in its own directory is not unusual, surely?

    Thread Starter bond138

    (@bond138)

    @therapyindex

    I agree it’s not unusual at all. I developed my site in the subdirectory then when the site went live I changed the Site Address (URL) to the Root directory edited index.php to point to the subdirectory and placed that in the Root directory. The are a number of websites that describe the procedure to do this and I found it quite easy.

    I have the WordPress SEO plugin by Yoast, when I applied the above change that plugin had not difficulty finding the correct .htaccess file!

    I noticed this question is marked as resolved when actually it isnt: https://wordpress.org/support/topic/falcon-activation-problem-and-a-workaround

    I’m having a few issues with Wordfence at the moment so I’m trying it on a test site where it is the only plugin installed and unfortunately the issues persist.

    I hope the developers can iron out all the issues because I do prefer Wordfence out of all the security plugins.

    Peter

    @bond Sorry, but this rotated of my screen and I missed getting back to it. Can you email me at tim [at] wordfence.com so I can ask some specifics?

    tim

    Same problem – likewise install in subdirectory. I tried the deactivation with removal of all settings then reactivation and settings re-import (described above) but to no avail. Modifications are made to the copy of the .htaccess file in the subdirectory, and Falcon still doesn’t work.

    Since subdirectory install instructions tell you to simply copy the .htaccess file from the subdirectory into the root one, I tried replacing the root directory one with a symbolic link to the subdirectory one. The site still functions fine, but Falcon still isn’t doing anything (as evidenced by clearing its cache and my browser cache, and refreshing pages – the Cache stats still say nothing in them, and there’s no debug text appearing at the foot of the page.)

    Incidentally, weirdly, before I started, the cache stats showed some pages had been cached, but nothing I could do would make them change, or serve me a page with the debug text on. I have a nasty feeling that, while core WordFence is repelling boarders magnificently, Falcon is not in fact doing anything on any of the sites I manage 🙁

    You might want to view it through a proxy to see the html comment. I believe the wordpress cookie you get when logged in prevents the comment from showing.

    tim

    Ah! That’s a bit weird… surely it’s when you’re logged in and messing with it that you’re most likely to be debugging?!? Anyway, that might just be worth putting in the documentation!! Thanks 🙂

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Wordfence saves in incorrect .htaccess file’ is closed to new replies.