• Resolved zeno001

    (@zeno001)


    Although I saw the note, I forgot I had two WordPress installations on the same web account (one in root and another in a subdirectory) and installed the WAF in the root installation first.

    The note says: “NOTE: If you have separate WordPress installations with Wordfence installed within a subdirectory of this site, it is recommended that you perform the Firewall installation procedure on those sites before this one.”

    Is there a problem doing this or if it all seems to work, is it OK? Should I delete the auto_prepend_file line for the installation in root, configure the WAF in the installation in the subdirectory then re-install in the root WordPress?

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Hi,

    In our testing, setting up the firewall in either order worked, though there can be significant variation between hosting companies (or even within a single hosting company’s various servers).

    If you know how to easily remove the ‘auto_prepend_file’ line from the main site, that may be best, in case your host uses a configuration we have not seen. Let us know if you do have any trouble!

    -Matt R

    Thread Starter zeno001

    (@zeno001)

    Thanks, Matt.

    Do I have to delete the Wordfence WAF lines in .htaccess AND in .user.ini (or delete it – it contains nothing else) in the root install, then configure (or re-configure) WAF in the install in the subdirectory?

    Once that’s done, if I go back to the root directory install, will Wordfence ask me to configure it again or do I just reinstate the deleted lines in both files?

    Plugin Author WFMattR

    (@wfmattr)

    Hi,

    Sorry for the delayed response. Yes, removing those lines (or the blank .user.ini file if nothing is left) is recommended.

    Wordfence will prompt you to do the install again on the main site after this — basically, once the auto_prepend_file line is gone, it will notice that the firewall is not fully installed with the extended protection level.

    -Matt R

    Thread Starter zeno001

    (@zeno001)

    Matt

    That’s great. All done now and everything seems to be working OK.

    Thanks for all your help.

    Alan

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WordPress in root and another in a subdirectory’ is closed to new replies.