Would someone review our HT Access file?

thank you in advance for any help you can offer -

Would you take a look at our HT access file - see below and let me know if there's anything that you think we could do to acheive our goals -- GoDaddy has been absolutely no help and neither has any of the documentation I've found online re this issue.

We created a new site for www.totalfitnessclubs.com with modx Revolution site developed in sub-folder (new-site) on the root with a subdomain of development.totatfitnessclubs.com

On the root: the htaccess contains the 301redirect to the subdomain. we commented out the rewrite and friendly urls in this file also the base which pointed to the root - but we could try and change to the subdirectory path? in the new-site - htaccess file the rewrite - has a 301 in it which I tried to delete but it didn't work rewrite on the url should be development.totalfitnessclubs to totalfinessclubs



htaccess file In the root (GoDaddy generated the rewrite rule:

rewriteengine on
rewritecond %{HTTP_HOST} ^www.totalfitnessclubs.com$ [OR]
rewritecond %{HTTP_HOST} ^totalfitnessclubs.com$
rewriterule ^(.*)$ "http\:\/\/development\.totalfitnessclubs\.com\/$1" [R=301,L] #50e0f21947479


addhandler x-httpd-php-cgi .php4
addhandler x-httpd-php5-cgi .php5
addhandler x-httpd-php5-cgi .php
# For full documentation and other suggested options, please see
# http://svn.modxcms.com/docs/display/MODx096/Friendly+URL+Solutions
# including for unexpected logouts in multi-server/cloud environments
#Options +FollowSymlinks
#RewriteBase /
# Fix Apache internal dummy connections from breaking [(site_url)] cache
# Rewrite domain.com -> www.domain.com -- used with SEO Strict URLs plugin
#RewriteCond %{HTTP_HOST} .
#RewriteCond %{HTTP_HOST} !^example\.com [NC]
#RewriteRule (.*) http://example.com/$1 [R=301,L]
# Exclude /assets and /manager directories from rewrite rules
# For Friendly URLs
# Reduce server overhead by enabling output compression if supported.
#php_flag zlib.output_compression On
#php_value zlib.output_compression_level 5
#rewritecond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
#rewriterule .* - [F,L]
#rewriterule ^(manager|assets) - [L]
#rewritecond %{REQUEST_FILENAME} !-f
#rewritecond %{REQUEST_FILENAME} !-d
#rewriterule ^(.*)$ index.php?q=$1 [L,QSA]


htacccess file in subfolder:


# MODX supports Friendly URLs via this .htaccess file. You must serve web
# pages via Apache with mod_rewrite to use this functionality, and you must
# change the file name from ht.access to .htaccess.
#
# Make sure RewriteBase points to the directory where you installed MODX.
# E.g., "/modx" if your installation is in a "modx" subdirectory.
#
# You may choose to make your URLs non-case-sensitive by adding a NC directive
# to your rule: RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC]

RewriteEngine On
RewriteBase /home/content/05/4954105/html/new-site

# Rewrite www.totalfitnessclubs.com -> totalfitnessclubs.com -- used with SEO Strict URLs plugin
# RewriteCond %{HTTP_HOST} .
# RewriteCond %{HTTP_HOST} !^totalfitnessclubs\.com [NC]
# RewriteRule ^(.*) http://totalfitnessclubs.com/$1 [R=301,L,NC]
#
# or for the opposite domain.com -> www.domain.com use the following
# DO NOT USE BOTH
#
# RewriteCond %{HTTP_HOST} .
# RewriteCond %{HTTP_HOST} !^www\.development.totalfitnessclubs\.com [NC]
# RewriteRule (.*) http://www.totalfitnessclubs.com/$1 [R=301,L]

# Rewrite secure requests properly to prevent SSL cert warnings, e.g. prevent
# https://www.domain.com when your cert only allows https://secure.domain.com
#RewriteCond %{SERVER_PORT} !^443
#RewriteRule (.*) https://example-domain-please-change.com/$1 [R=301,L]

# The Friendly URLs part
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC]

# Make sure .htc files are served with the proper MIME type, which is critical
# for XP SP2. Un-comment if your host allows htaccess MIME type overrides.

#AddType text/x-component .htc

# If your server is not already configured as such, the following directive
# should be uncommented in order to set PHP's register_globals option to OFF.
# This closes a major security hole that is abused by most XSS (cross-site
# scripting) attacks. For more information: http://php.net/register_globals
#
# To verify that this option has been set to OFF, open the Manager and choose
# Reports -> System Info and then click the phpinfo() link. Do a Find on Page
# for "register_globals". The Local Value should be OFF. If the Master Value
# is OFF then you do not need this directive here.
#
# IF REGISTER_GLOBALS DIRECTIVE CAUSES 500 INTERNAL SERVER ERRORS :
#
# Your server does not allow PHP directives to be set via .htaccess. In that
# case you must make this change in your php.ini file instead. If you are
# using a commercial web host, contact the administrators for assistance in
# doing this. Not all servers allow local php.ini files, and they should
# include all PHP configurations (not just this one), or you will effectively
# reset everything to PHP defaults. Consult www.php.net for more detailed
# information about setting PHP directives.


#php_flag register_globals Off

# For servers that support output compression, you should pick up a bit of
# speed by un-commenting the following lines.


#php_flag zlib.output_compression On
#php_value zlib.output_compression_level 5

# The following directives stop screen flicker in IE on CSS rollovers. If
# needed, un-comment the following rules. When they're in place, you may have
# to do a force-refresh in order to see changes in your designs.

#ExpiresActive On
#ExpiresByType image/gif A2592000
#ExpiresByType image/jpeg A2592000
#ExpiresByType image/png A2592000
#BrowserMatch "MSIE" brokenvary=1
#BrowserMatch "Mozilla/4.[0-9]{2}" brokenvary=1
#BrowserMatch "Opera" !brokenvary
#SetEnvIf brokenvary 1 force-no-vary

Use the MODX htaccess file in your root, and add the additional rules that godaddy applied (although you may not need them all). Or add the pertinent parts of the file to your godaddy generated file.

Uncomment rewrite Base / if you use the godaddy file.

Additionally, make sure to check ALL the config files listed in the moving servers documentation (halfway down that page). Your original subfolder install was written to the subfolder, and you've got to make sure that the root install is not looking to that old subfolder now (sounds like it still is).

You may want to make use of the Redirector package if you've got any specific outstanding url's that you want to 301 redirect to.

Quote from: frogabog at Dec 31, 2012, 02:48 PM

Use the MODX htaccess file in your root, and add the additional rules that godaddy applied (although you may not need them all). Or add the pertinent parts of the file to your godaddy generated file.

Uncomment rewrite Base / if you use the godaddy file.

Additionally, make sure to check ALL the config files listed in the moving servers documentation (halfway down that page). Your original subfolder install was written to the subfolder, and you've got to make sure that the root install is not looking to that old subfolder now (sounds like it still is).

You may want to make use of the Redirector package if you've got any specific outstanding url's that you want to 301 redirect to.

Thank you - I will show to my designer. You have been great about trying to help me out!

Let us know how it goes :~}

I'm curious about this:



Where the heck did that come from? This is an extremely old, bad, and non-existent url referencing from what I can tell, an old Evo doc file. Huh? Godaddy do this for you? If so they've got their heads in... the sand.

Frogabog - again thank you for your trying to help us. AND Happy New Year! GoDaddy has been anything but helpful.

not sure I explained properly before...

a new site was developed while the current site, developed with modx evolution, remained live in the root. Revolution 2.2 installed and built in subfolder on the root called new-site. We wanted to keep it there, for now anyways until the root can get cleared out.

I was trying to redirect the primary domain which is currently pointed to subdomain name (development.totalfitnessclubs.com) which points to the new-site folder on the root and then a rewrite so that it isn't totatlfitnessclubs.com/new-site/ or development.totalfitnessclubs.com Also wondering if the redirect should go to the folder and not to the subdomain go daddy set up.

many thanks!!

OK, gotcha.

A few months back Susan described how to rewrite .htaccess with subdomains. I located a thread where I referenced her post, and a few others here:
https://forums.modx.com/thread/?thread=73954#dis-post-410673

Susan's very informative post is here:
https://forums.modx.com/thread/73312/add-on-domain-and-htaccess-file-setting#dis-post-410056

Hi Frogabog,

Again - thank you for your trying to help us with this. I have tried everything they suggested and can't get it to work - either an error with too many http redirect errors, permanent redirect, 500 errors and 404s

It worked at one point- very briefly. Then when it seemed to be working, the styles and assets weren't showing. The config files had correct path but html code for the page was picking up some of the old assets -

per go daddy I had been doing the redirects via the hosting cpanel .I tried doing a redirect to the sub folder instead of the subdomain, that didn't work either - duplicated the folder name a bizillion times (well a lot) -

I uncommented the rewrite rule that was generated by the go daddy redirect and tried something from one of the posts:
RewriteEngine On
RewriteRule ^manager$ /new-site/manager/ [R=301,L]
RewriteCond %{HTTP_HOST} ^totalfitnessclubs\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.totalfitnessclubs\.com$
RewriteCond %{REQUEST_URI} !^/new-site/
RewriteRule (.*) /new-site/$1

this didn't work - I got a 500 internal error

I had been using the go daddy htaccess file in the root and renamed the htacess file in new-site folder.

now I am unsure of what the base href should be in the templates -- "/" "new-site" or "subdomain"

right now my head is spinning… I had started cleaning out the root folder -- not sure if thats when it started looking for the old assets -- I can't believe it, but a reinstall is starting to look like a better option - when you move the site it is recommended to do a reinstall….this sucks -- this should not be this difficult, people have to do it all the time when they are redesigning/redeveloping existing sites. Is it the weird goddady file? is it trying to redirect a primary domain to a subdomain (of the primary) and rewrite the subdomain to the primary url? (which sounds shaky and why I thought going to the subfolder would work --/