We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32424
    • 19 Posts
    Hello,
    We need to have our existing site in place while we develop the MODx site. MODx will need to reside in the top level of the web root, which is where our current site is as well. However, I need out current site to be there while we work on MODx, so this obviously creates a conflict in index files.

    I was thinking about putting the current site (which is static) in a subdirectory such as www.oursite.com/current/ and then setting up a redirect to take people there. But how would I be able to view the MODx site if I were to do this?

    Anyone else had a similar predicament? And ideas for running the two sites in parallel?

    TIA!
      • 33372
      • 1,611 Posts
      Well, you can actually install MODx in a subdirectory and develop it there. Then when you’re done, you can either use .htaccess (from your root directory; deleting the one in your MODx subdirectory) and friendly URLs to make it appear to visitors as if the MODx site were at the root (just add the subdirectory to your rewrite rule, per the instructions in the main .htaccess file), or you could move your MODx install to the root and just make sure that all of your image and other inserted links still work correctly. I find the latter to be more trouble than it’s worth, but it’s certainly doable (and if you pay attention to how you use your base_href tag and assets path configuration it’s usually not too difficult).
        "Things are not what they appear to be; nor are they otherwise." - Buddha

        "Well, gee, Buddha - that wasn't very helpful..." - ZAP

        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
        • 5727
        • 160 Posts
        If you have access to SSH or a good hosting panel, you could develop on a sub-domain (ie: dev.mydomain.com) and then move the directories(using SSH or other) when you’re ready for production.
          Olivier Deland
          Montreal, Canada - Web Developer
          • 4310
          • 2,310 Posts
          If your current site starts with index.html then leave it there and run MODx without furl enabled during development.
          When you want to activate MODx enable furls and delete the old site.
          That’s what I’ve done a few times.

          David
            • 34017
            • 898 Posts
            I posted a plugin that only allows logged in users to view the site (except for the login page).

            The link is: http://modxcms.com/forums/index.php/topic,14776.msg95891.html#msg95891
              Chuck the Trukk
              ProWebscape.com :: Nashville-WebDesign.com
              - - - - - - - -
              What are TV's? Here's some info below.
              http://modxcms.com/forums/index.php/topic,21081.msg159009.html#msg1590091
              http://modxcms.com/forums/index.php/topic,14957.msg97008.html#msg97008
              • 32424
              • 19 Posts
              Great answers! Thanks for the responses - I will probably try turning of furls first, then try that plugin if need be. Moving directories around seems like there is more potential for error, but I’ll save that option in case I need it.

              Thanks!
                • 21191
                • 236 Posts
                We use sub-domains, so, like

                http://4nsi.wavestatic.com, it’s a true live environment, using FURLs and all, I find you end up having to resave all documents once you turn on FURLS later if you develop in a sub-dir

                Setting up a subdomain to be a real environment and ot use FURLs can be tricky, we’re setup for it if you’re interested.

                http://wavestatic.com
                  ~Shawn Himmelberger
                  Check out my MODx Development and MODx Design Company - Himmelberger Design