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

    I’ve installed MODx on a subfolder of my server to keep their current static website live while we fill the new website with content and set it up. I might have this wrong, but would it suffice to modify htaccess to rewrite to /website/index.php (/website being the subfolder where it’s installed) instead of index.php? If not, what settings would I need to change?

    Thanks!
      • 28554
      • 201 Posts
      Any thoughts?
        • 2611
        • 394 Posts
        I think you would need the RewriteBase to /website and if i’m right everything
        should work then...
          Follow me on twitter: @b03tz
          Follow SCHERP Ontwikkeling on twitter: @scherpontwikkel
          CodeMaster
          • 28215
          • 4,149 Posts
          And re-run setup in upgrade mode.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 2611
            • 394 Posts
            Re-run setup? Only for the core-config variables right..?

            Is "upgrading" the easy way to go...or the only way? (i might have to do this in the feature)
              Follow me on twitter: @b03tz
              Follow SCHERP Ontwikkeling on twitter: @scherpontwikkel
              CodeMaster
              • 28215
              • 4,149 Posts
              Well you can edit all the core.config.php files and core/config/config.inc.php manually, but we don’t recommend it. It’d be much easier to just run setup in upgrade mode.

              Note: you might also have to change the default workspace path in the modx_workspaces table; that might be a bug in RC-3.
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 2611
                • 394 Posts
                Yea that’s what i thought...or course an upgrade would be the clean way to go!
                It’s nice that it is possible that way...thanks for your answer.
                  Follow me on twitter: @b03tz
                  Follow SCHERP Ontwikkeling on twitter: @scherpontwikkel
                  CodeMaster
                  • 28554
                  • 201 Posts
                  Thanks for the reply guys. So I should leave everything as is, modify the RewriteBase to /website and then run an upgrade. What paths do I need to alter during setup? The current installation is in the folder /website/...
                    • 2611
                    • 394 Posts
                    If you are moving the complete site to /....then everything that was /website = now /...

                    If you are leaving the site in /website/ but only want to run it in the root...then i still
                    think everything should be /website....are you planning on moving the site to the root or
                    leave it in it’s current directory?
                      Follow me on twitter: @b03tz
                      Follow SCHERP Ontwikkeling on twitter: @scherpontwikkel
                      CodeMaster
                      • 28554
                      • 201 Posts
                      Quote from: b03tz at Jul 09, 2010, 09:13 AM

                      If you are moving the complete site to /....then everything that was /website = now /...

                      If you are leaving the site in /website/ but only want to run it in the root...then i still
                      think everything should be /website....are you planning on moving the site to the root or
                      leave it in it’s current directory?

                      Well, that’s what I’m still considering. My client really doesn’t care that much, so if it’s the easiest solution i’d just as glad leave it in /website/...