Title: Root?
Last modified: August 21, 2016

---

# Root?

 *  Resolved [NeHoMaR](https://wordpress.org/support/users/nehomar/)
 * (@nehomar)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/)
 * On FAQ and plugin itself, root is referring to wordpress installation root? no?
   this plugin only works inside the folder the wp is installed? and never touch
   the real root of the site, etc?
 * [http://wordpress.org/extend/plugins/bulletproof-security/](http://wordpress.org/extend/plugins/bulletproof-security/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/#post-3873152)
 * BPS checks the website root folder where the website is installed in order to
   create the correct .htaccess code for that website.
 * The website root folder is technically the actual folder where the WordPress 
   installation/the website is installed.
    Example: If you have WordPress installed
   in a folder named “myBlog”. /xxxxx/xxxxx/public_html/myBlog
 * The Document Root folder for a hosting account is going to be the root folder
   for the entire hosting account.
    Examples: /xxxxx/xxxxx/public_html/ or /xxxxx/
   xxxxx/html/ or /xxxxx/xxxxx/htdocs/ etc, etc, etc. depending on what your particular
   host chooses for the name of the Document Root folder.
 * If you have your website installed in the Document Root folder then the path 
   to your website root folder is going to also be the Document Root folder: /xxxxx/
   xxxxx/public_html/
 * If you have created/installed/setup a Giving WordPress Its Own Directory (GWIOD)
   type of installation/website then you would need to do the additional requirements
   explained in the WordPress Codex link below for that WordPress installation type.
 * **WordPress GWIOD installation/setup: **[http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory](http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory)
 * Note: We have scheduled the task of adding additional checking code for BPS to
   detect and handle GWIOD installation types and the additional GWIOD steps will
   be handled automatically by BPS. The time frame for adding this additional feature
   is not known at this point, but this task has been scheduled for future development.
 *  Thread Starter [NeHoMaR](https://wordpress.org/support/users/nehomar/)
 * (@nehomar)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/#post-3873170)
 * What about if I have 2 wordpress stand-alone installations, not using any multisite
   feature, one in “/public_html/myBlog1” and other in “/public_html/myBlog2”, that
   installations will have the same root, if I understand correctly. What BPS do
   in that case?
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/#post-3873179)
 * Each installation of WordPress/website would have BPS installed on it and BPS
   would get the correct website root folder (RewriteBase, RewriteRule, etc) for
   each website when you click the AutoMagic buttons and activate BulletProof Modes.
 * The RewriteBase for the WordPress installation in this folder: myBlog1 is RewriteBase/
   myBlog1/
    The RewriteBase for the WordPress installation in this folder: myBlog2
   is RewriteBase /myBlog2/
 * .htaccess files in general are designed to be heirarchical/recursive. The parent
   folder will be the RewriteBase and the child folders will be all folders under/
   below the parent folder.
 * In regards to website security in general, the best site architecture compartmentalizes
   website security per website. By compartmentalizing your security per website
   you can make customizations to your security (via .htaccess files or other methods)
   per website instead of trying to create working rules from a root parent folder(
   example: Document Root folder) to child folders (example: individual/separate
   websites) that contain individual/separate websites. Generally the best site 
   architecture already compartmentalizes per site so website security should follow
   the same best practices/site architecture.
 *  Thread Starter [NeHoMaR](https://wordpress.org/support/users/nehomar/)
 * (@nehomar)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/#post-3873188)
 * Thanks. So, I can just add all WP stand-alone installations I want, and just 
   add BPS to each one without any conflict? (or have wp installations without protection,
   without BPS)
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/#post-3873189)
 * Yes, correct.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Root?’ is closed to new replies.

 * ![](https://ps.w.org/bulletproof-security/assets/icon-128x128.png?rev=1731938)
 * [BulletProof Security](https://wordpress.org/plugins/bulletproof-security/)
 * [Support Threads](https://wordpress.org/support/plugin/bulletproof-security/)
 * [Active Topics](https://wordpress.org/support/plugin/bulletproof-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bulletproof-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bulletproof-security/reviews/)

## Tags

 * [root](https://wordpress.org/support/topic-tag/root/)

 * 5 replies
 * 2 participants
 * Last reply from: [AITpro](https://wordpress.org/support/users/aitpro/)
 * Last activity: [12 years, 11 months ago](https://wordpress.org/support/topic/root-3/#post-3873189)
 * Status: resolved