Nested Modx Installations

Hi All,
Love Modx! Love it so much we want to expand our use of it. Right now we have four instances of Modx running sites for different campuses of our college. They run in sub-folders inside web root. It’s really taken off so I’d like to install Modx at our site root. I’m wondering if anyone is aware of any issues installing Modx higher in the directory tree leaving operating copies in sub-directories. Any advice would be welcome.

Thanks and great CMS!
jp

I would modify the .htaccess of the root-level installation so that any requests for pages inside sub-folders (i.e. any requests headed over to the existing MODx installations) are allowed to pass-through without the root-level install trying to handle the request. This would only be relevant if you have friendly URLs enabled... if you aren’t using friendly URLs, you don’t have to worry about this because the default .htaccess file will work just fine.

But if you are using friendly URLs... then you need to tell the root-level install to ignore the contents of certain directories. I don’t know my .htaccess commands well enough to tell you how to do this off the top of my head... but essentially the default .htaccess file says "if there is a file or a directory on the web server that exists, then just grab and display that file/folder to the browser, otherwise treat the request as an argument for MODx". You can think of the MODx front-end as an application, and that application lives in the root-level index.php... with friendly URLs enabled, a request for "some/page.html" gets passed as an argument to the index.php page, which looks up a corresponding row in the database.

This response was longer than I intended... hope it made some sense.