We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 23491 ☆ A M B ☆
    • 1,056 Posts
    Interesting... it appears that this is not working for me huh (0.9.5 build) In fact, when I enable alias path, NONE of my alias’ documents work. Help!
      Mike Reid - www.pixelchutes.com
      MODx Ambassador / Contributor
      [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
      ________________________________
      Where every pixel matters.
      • 1932
      • 137 Posts
      @pixelchutes: What does your .htaccess look like?

      It’s working great with MODx SVN rev 2165 and lighttpd.
        • 23491 ☆ A M B ☆
        • 1,056 Posts
        Quote from: ApoXX at Jan 10, 2007, 09:48 PM

        @pixelchutes: What does your .htaccess look like?

        It’s working great with MODx SVN rev 2165 and lighttpd.

        Hmm...I’ll grab a fresh SVN now and let you know...

        Quote from: "my

        <IfModule mod_rewrite.c>

        RewriteEngine On
        RewriteBase /

        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ http://%{SERVER_NAME}/index.php?q=$1 [L,QSA]

        </IfModule>

        DirectoryIndex index.php index.html

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

        php_flag zlib.output_compression On
        php_value zlib.output_compression_level 5

        UPDATE:

        So, I’m now running

        MODx version  	   	0.9.5.1
        Version codename 	  	rev 2220
        

        ...and it sort of works... Why are my URLs placing /1/ after my domain???

        Works, but why the /1/ http://www.pixelchutes.com/1/portfolio/child

        Doesn’t work, but is desired format http://www.pixelchutes.com/portfolio/child

        NOTE: I noticed the /1/ before I installed the SVN, but didn’t think much of it. In other words, nothing has changed from 0.9.5 to SVN rev 2220 as far as what I’m experiencing is involved. I just didn’t test /1/portfolio/child till after SVN was in place wink

        Where is /1/ coming from? How can I get it to work as desired...? Anyone seen this one before?
          Mike Reid - www.pixelchutes.com
          MODx Ambassador / Contributor
          [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
          ________________________________
          Where every pixel matters.
          • 23491 ☆ A M B ☆
          • 1,056 Posts
          Quote from: pixelchutes at Jan 10, 2007, 08:09 PM

          Maybe I’ve missed a really important thread, or there’s something in the works, but is there a solution yet for MODx aliasing w/ directories?

          e.g.




          Ok, stupid me. Long story short, you see that image up there? Notice anything??

          Yeah, for some reason I thought it’d be cool to place all of my website files into a container called, "Website" (How original!)

          So, yeah, it didn’t have an alias, which explains the /1/... alias path did warn of use resulting in "Absolute Path" ...now I finally understand where it was referring to smiley

          Fixed. http://www.pixelchutes.com/portfolio/child cool

            Mike Reid - www.pixelchutes.com
            MODx Ambassador / Contributor
            [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
            ________________________________
            Where every pixel matters.
            • 11389
            • 4 Posts
            I have a strange problem with FURL and modX. My host ist 1&1.
            Everything works fine, except 1 Problem: When I type a nonexistent directory as URL, I will be redirected to the custom 404-Error-Site, but all Links contain the nonexistent directory in the URL then (also css-styles doesn´t work because of false URL).
            Examples of my site:
            - This works as intended (xyz.html doesn´t exist): http://www.cosinex.de/xyz.html
            - This doesn´t work: http://www.cosinex.de/xyz/
            - This doesn´t work: http://www.cosinex.de/xyz/xyz.html

            I spent hours with mod_rewrite-codes, but nothing except RedirectMatch works.
            This is the code in the htaccess-File:

            RewriteEngine On
            RewriteBase /
            RewriteCond %{REQUEST_FILENAME} !-f
            RewriteCond %{REQUEST_FILENAME} !-d
            RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
            
            RedirectMatch  permanent  ^/cms/  http://www.cosinex.de/



            These are the Settings in my ModX Friendly URL Settings Panel:

            Use friendsly URL: Yes
            Prefix: [Blank]
            Suffix: .html
            Use friendly Alias: Yes
            Use friend paths: No
            Allow duplicates: No
            Automatically Generate: Yes


            Friend Paths "Yes" doesn´t make a difference.
            I use ModX 0.9.5.

            What might help, would be to define the URL of the 404-Error-Dokument somewhere in the modX-Backend with absolute paths and not with relative ones.
            Or there is a special regex-variable like
            RedirectMatch  permanent  ^/$/  http://www.cosinex.de/404.html

            for redirecting all non-existent directories to the 404-Site with the valid URL.

            I would appreciate any comments on this issue.
              • 22303 MODX Staff
              • 10,725 Posts
              groooo, <base href="[(site_url)]" /> in your templates before any relative paths will solve this.
                • 11389
                • 4 Posts
                It works! Additionally I changed the css-Link in an absolute Path, so everything works now. Thank you for your fast support. I enjoy modX a lot!
                  • 29181
                  • 480 Posts
                  RewriteEngine On

                  RewriteCond %{REQUEST_FILENAME} !-f
                  RewriteCond %{REQUEST_FILENAME} !-d

                  # If your MODx installation is in a subdirectory, change the following line to match the physical
                  # path to the "root" of the site as follows:
                  # RewriteRule ^(.*)$ /path/to/subdirectory/index.php?q=$1 [L,QSA]

                  RewriteRule ^(.*)$ /index.php?q=$1 [L,QSA]

                  For these to work, I need webspace where mod_rewrite will work? I’ve been trying for a few hours unsuccessfully. After using Google, it would appear that my webspace doesnt offer this and everyone has similar problems, no matter what CMS they use.

                  Thanks for any insight.

                  Taff
                    Adrian Lawley: www.adrianlawley.com
                    • 29181
                    • 480 Posts
                    The simple solution was to change my webhost and I got it working in about 30 secs.
                      Adrian Lawley: www.adrianlawley.com
                      • 18077
                      • 1 Posts
                      Hi everyone,
                      I’ve got the most annoying and weird error at one of my MODx installations with Friendly URLs: the URL is correctly re-written as http://mysite.br/directory/archive.html but the web server tries to retrieve http://mysite.br/directory.html/archive.html shocked
                      What am I doing wrong? Maybe something within the configuration of the mod_rewrite?
                      I have already declared a base_url but did no good. The error seems to be happening somewhere else.

                      My .htaccess has these lines:

                      RewriteEngine On
                      RewriteBase /~userdir
                      RewriteCond %{REQUEST_FILENAME} !-d
                      RewriteCond %{REQUEST_FILENAME} !-f
                      RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

                      huh
                      Thanks in advance!

                      This discussion is closed to further replies. Keep calm and carry on.