We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25519
    • 265 Posts
    Hello all – I’m a modx noob with reasonable cms experience ‘elsewhere’ (joomla/mambo).

    I’ve had great fun and results thus far transferring a clients’ site from static xhtml into modx but am running into a major sticking point converting to friendly url’s (furls). This is crucial for the site in question and I’ve been trying all I can in relation to the documentation and forum posts with no joy, although I feel I’ve followed instructions to the letter.

    The site in question is hosted on a 1and1 server (I have seen previous posts about 1and1 in relation to this) and the index.php page is at server root level.

    My site configuration is as follows:
    friendly url’s:YES
    friendly aliases: YES
    friendly alias path and duplicates: NO
    automatically generate alias: NO

    Because the site is at server root and not in a sub-directory I haven’t altered ht.access at all other than re-naming them both (root and manager) to .htaccess – thus I still have the following unchanged settings in the root level file:
    RewriteBase /
    RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

    Unfortunately I am not getting any change in the url’s at all with these settings – can anyone tell me what I’m doing wrong please?

    thanks
      • 22303 MODX Staff
      • 10,725 Posts
      I think the RewriteBase / could be your issue. Try it without that line.
        • 25519
        • 265 Posts
        Thanks for the reply, but unfortunately that makes no difference.
        Just a thought - I’m running the modx installation alongside the existing html site, ie both at root level. Would this be causing the problem? If so, maybe I should re-setup the whole shebang in a sub-sirectory as I could redirect the domain name.

        thanks
          • 6726
          • 7,075 Posts
          Indeed if you have both index.html and index.php the .html in most server this will override your index.php page, I definitely either would move the install in a subdir or edit server’s config...
            .: COO - Commerce Guys - Community Driven Innovation :.


            MODx est l'outil id
            • 25519
            • 265 Posts
            Okay, thanks for the info - i’m in the process of pointing the .html site to a different directory so that the index.php file will be at root level. Gonna test a little first with another domain but I’ll let you know whether it worked or not.
              • 25519
              • 265 Posts
              I’ve tried all suggestions but unfortunately no furl’s are happening. To recap, this is what i’ve done:
              > removed all trace of the .html pages so that index.php is the server root/homepage - that works fine
              > commented out RewriteBase/
              > cleared my browser cache
              > commented back in RewriteBase/
              > again commented out RewriteBase/
              > included ’use friendly alias path’ and ’allow duplicate aliases’

              None of the above work. One thought, the server has .lck copies of each file (including .htaccess.LCK) - could these be holding info which overwrites any new settings?
              Again, it’s a 1and1 server - maybe somebody knows if this causes any problems with modx settings?

              It’s a great shame that this is happening as the site has transfered well into modx, except for this one last thing, and I really do have to get furl’s working. If anyone can help it would be much appreciated.

              Thanks
                • 25519
                • 265 Posts
                thanks for that - would i be able to safely delete the .lck files from the server and not affect the cms?
                  • 25519
                  • 265 Posts
                  wow! read the article and i’ll definitely be addressing this both at server level and dreamweaver level... maybe adobe should fess up too?!
                  thanks for the info on that.
                    • 25663 MODX Staff
                    • 12,272 Posts
                    Dreamweaver’s FTP abilities caused me to stop using Dreamweaver long ago. I suspect you may also have a corrupt file. Try re-uploading your site with a dedicated FTP client.
                      Ryan Thrash, MODX Co-Founder
                      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me