We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 9714
    • 38 Posts
    Hello,

    First of some basic info:
    My Site: http://team-tactics.co.cc/
    Sub-domain: http://team-tactics.110mb.com/
    PHP Info: http://team-tactics.co.cc/php-info.php
    My Host: http://www.110mb.com
    Host Server info:
    OS: Debian Linux
    PHP Ver: 5.1.6
    MySQL Ver: 5.0.27
    Modx Version:
    modx-0.9.6.3

    The Problem:
    Ok here is the story. I first had my site on another server but the server were getting so many 500 errors and crashing I said enough is enough. So I got a new server and started working on it with the sub-domain they gave me(team-tactics.110mb.com). After some time developing the new site, I was ready to switch over to the main domain of the new server.

    I am sure the DNS servers switched over to the new host(It’s been over 4 day’s) and I have everything needed to run friendly urls since I can run it in the sub-domain.
    I know it’s got to be modx because I have a SMF Forum and it works fine on the main domain and sub-domain.

    Is it some kind of caching problem? I tried everything I can think of, which is not much since I know very little about PHP & MySQL(I am trying to learn it), I know more (x)html & CSS.

    Does anyone have any idea?
    -FireDart


    EDIT:
    The problem was on my host’s side, they needed to upgrade my .htaccess file so it was up to date with my domain name.
      -FireDart
      • 3749
      • 24,544 Posts
      Does the .htaccess file in the MODx root directory still have the subdirectory name in the rewrite rules? If so, you’ll have to edit it.

        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 9714
        • 38 Posts
        I don’t think so but I am not sure, do you mind pointing out what you mean so I know in the future?
        # 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. If you have
        # problems with your .htaccess working at all, try un-commenting the first 
        # line above the "RewriteEngine On" directive.
        #
        # 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]
        
        #Options +FollowSymlinks
        RewriteEngine On
        RewriteBase /
        
        
        # Fix Apache internal dummy connections from breaking [(site_url)] cache
        RewriteCond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
        RewriteRule .* - [F,L]
        
        
        # Rewrite www.domain.com -> domain.com -- used with SEO Strict URLs plugin
        #RewriteCond %{HTTP_HOST} .
        #RewriteCond %{HTTP_HOST} !^example-domain-please-change\.com [NC]
        #RewriteRule (.*) http://example-domain-please-change.com/$1 [R=301,L]
        #
        # or for the opposite domain.com -> www.domain.com use the following
        # >>> DO NOT USE BOTH THE ABOVE AND BELOW <<<
        #
        #RewriteCond %{HTTP_HOST} .
        #RewriteCond %{HTTP_HOST} !^www\.example-domain-please-change\.com [NC]
        #RewriteRule (.*) http://www.example-domain-please-change.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.com/$1 [R=301,L]
        
        
        
        # The Friendly URLs part
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
        
        
        
        # 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 but 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
        
          -FireDart
          • 3749
          • 24,544 Posts
          That looks normal (assuming that it’s named .htaccess and not ht.access).

          You might try uncommenting the "follow symlinks" line to see if that helps.
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 9714
            • 38 Posts
            My .htaccess file is as it should be ".htaccess", and uncommenting the: "#Options +FollowSymlinks" did not do anything.

            Nothing in the .htaccess file in the manager folder would cause a problem would it?

            -FireDart
              -FireDart
              • 4310
              • 2,310 Posts
              All your menu links apart from to the Forum are being redirected to http://www.singerpictures.com
              There’s something seriously not right happening, the menu links on hover and in the source code are fine, but clicking them takes you to singerpictures.com
              Is there an .htaccess file in the root doing this?
              Is ’singerpictures.com’ one of your sites?
              Or has your server been hacked?
              Might be time to get in touch with the hosting company.
                • 9714
                • 38 Posts
                Well the host I use uses "http://www.singerpictures.com" as a 404 page(Makes extra money for them), thought I can change this I have not done so so far.
                The .htaccess is in the root(and in the manager)

                -FireDart
                  -FireDart
                  • 3749
                  • 24,544 Posts
                  The .htaccess in the Manager folder should just have a single line in it: RewriteEngine Off. That file should have no effect on the front end anyway.

                  Check in tools | configuration on the FURL tab and see if you have any FURL prefix set. Delete the prefix if there is one. Also turn off friendly aliases and paths for now.

                  Next, confirm that the site works ok with FURLs turned off and no .htaccess file (rename it to ht.access).
                    Did I help you? Buy me a beer
                    Get my Book: MODX:The Official Guide
                    MODX info for everyone: http://bobsguides.com/modx.html
                    My MODX Extras
                    Bob's Guides is now hosted at A2 MODX Hosting
                    • 9714
                    • 38 Posts
                    Quote from: BobRay at May 18, 2009, 10:24 PM

                    The .htaccess in the Manager folder should just have a single line in it: RewriteEngine Off. That file should have no effect on the front end anyway.
                    The .htaccess in the manager does have "RewriteEngine Off":
                    RewriteEngine Off
                    
                    <IfModule mod_security.c>
                    # Turn the filtering engine Off
                    SecFilterEngine Off
                    </IfModule>
                    


                    Quote from: BobRay at May 18, 2009, 10:24 PM

                    Check in tools | configuration on the FURL tab and see if you have any FURL prefix set. Delete the prefix if there is one. Also turn off friendly aliases and paths for now.

                    Next, confirm that the site works ok with FURLs turned off and no .htaccess file (rename it to ht.access).
                    The site does work, thought I only changed the .htaccess to ht.access in the root becuase you said it should not effect any thing.

                    Is this a problem? Does this mean it’s not reading the .htaccess file?
                    -FireDart
                      -FireDart
                      • 3749
                      • 24,544 Posts
                      With friendly URLs on, you need the .htaccess file in the root to do the rewrites. With FURLS off, you want no rewriting of the URLS and one surefire way of accomplishing that is to rename it to ht.access, which the server will ignore completely.

                      The .htaccess file in the Manager folder turns the rewrite engine off because you don’t want things rewritten when you’re in the Manager. That file (the .htaccess in the Manager folder) has no effect on the front end because no one there accesses the manager folder.

                        Did I help you? Buy me a beer
                        Get my Book: MODX:The Official Guide
                        MODX info for everyone: http://bobsguides.com/modx.html
                        My MODX Extras
                        Bob's Guides is now hosted at A2 MODX Hosting