-
☆ A M B ☆
- 894 Posts
Just install it to a modx directory then change the path of the domain to point to modx directory as the home url when done.
Hi benmarte,
but if you do this without step 2 and 3 as described above it will not work...
Is your client’s current website just static html on an Apache server?
If so, you could install MODx directly into the webroot, as long as there aren’t any files or folders that will be overwritten or conflict with MODx (such as a pre-existing /assets or /manager folder).
Apache web servers usually have multiple default documents defined, with index.html preceding index.php. In this case, the existing site’s index.html will remain default even after MODx is installed. To switch to your new MODx site later, simply remove (or rename) the index.html file, so that MODx’s index.php become the default document.
I normally install in a directory, then when ready to put live I move all the files out of the directory and do what you mention in step 2 and also amend the the system setting etc in the manager.
I’ve never had an issues so far, but I of course make a back up of their current site so can upload again if any issues.
-
☆ A M B ☆
- 894 Posts
Quote from: Gerdi at Oct 24, 2010, 01:49 PM
Hi benmarte,
but if you do this without step 2 and 3 as described above it will not work...
I don’t know dude I just select my MODx directory as the host root folder and it all works no need to mess around with the config.php or any other stuff.
I have 2 sites running MODx like this one with Revo the other with evo, one is a subdomain though.
