The reason we do not write htaccess code to the site root htaccess file for a “Giving WordPress It’s Own Directory (GWIOD)” Site is that if the site root is the hosting account root folder (/public_html/) then that could cause problems for any child folders in the hosting account root folder, unless of course you add this additional code: http://forum.ait-pro.com/forums/topic/htaccess-files-for-multiple-website-domains/. In most cases, it is best to compartmentalize website security per folder/directory/website.
BPS and iThemes Security were not compatible at one point briefly during several versions of iThemes Security, but I believe that they are compatible currently. Since both plugins write htaccess code and some of that htaccess code is redundant then you would choose which htaccess code you want to use. Or it is probably possible to use all iThemes Security htaccess code and add it to BPS Custom Code. BPS differs in that it is a Master htaccess file editor and has the advanced extended capability to manage htaccess code that is created by other htaccess plugins. So you want to use the BPS Custom Code advanced htaccess file managedment tool to combine any/all other htaccess code that other htaccess writing plugins create.
-
This reply was modified 7 hours, 38 minutes ago by
AITpro Admin.
