Giving WordPress Its Own Directory (GWIOD)

Home Forums BulletProof Security Pro Giving WordPress Its Own Directory (GWIOD)


Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #24183
    Janne K.


    Our site broke up after recent update, but I’m not totally sure if it was broken before that. I mean non-www to www and force https didn’t work. I had working custom htaccess code for that I recall having tested non-www > www and force https was working two months ago during site launch. And our testers should have picked up earlier so it might have been that it broke after the recent update.

    Now I noticed that saving the secure file and enabling it saved it into *subdirectory*, and not root?

    In Site General Settings the WordPress Address (URL) is set with ending while Site Address (URL) is

    And in BPS Security > System Info
    Website Root URL:
    Document Root Path: /home/domain/public_html
    WP ABSPATH: /home/domain/public_html/wp/

    AITpro Admin

    BPS creates the BPS secure root htaccess file in the WordPress installation folder – /wp.  The site root htaccess file is an additional htaccess file for WP GWIOD sites that you can manually edit.  The site root htaccess file only needs generic/default WordPress htaccess code.  What does “Our site broke” mean?  Describe what is not working in specific detail.

    GWIOD HTTPS/SSL site root htaccess code is below.  For the HTTPS/SSL htaccess code for your WordPress installation folder/BPS secure root htaccess file see the “WordPress SSL/HTTPS htaccess code” link below.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTPS} !=on
    RewriteCond %{SERVER_PORT} ^80
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R,L]
    RewriteRule . /index.php [L]
    # END WordPress

    Relevant/related links:
    Giving WordPress Its Own Directory
    WordPress SSL/HTTPS htaccess code
    BPS Pro standard troubleshooting steps

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.