This is a real newbie question, but what’s the best way to develop a test area for developing a new MODX site based on an existing production site? This is basically just a redesign of a live site, to be put into ModX. I’m trying to avoid doing all the development locally, but if necessary, I guess I can try to do so using XAMPP.
Originally I tried installing to our host (easycgi). I installed ModX in a subdirectory, but despite a successful install, it seemed to have lots of problems because the subdirectory is not a site root. There were quite a few broken links, and the admin area could not see the default installed editor. The hosting plan we have does not allow multiple domains, so we can’t point another domain to the subdirectory where MODx is installed.
Is there a way to install ModX to a site subdirectory? Or given the situation, is my only option for development to do it locally?
thanks!
-
MODX Staff
- 10,725 Posts
MODx works fine within sub-directories of the web root, though there are certainly things that have to be configured properly when doing so. For instance, if turning on friendly URLs, you’ll need to edit the .htaccess file with the path in RewriteBase.
Is there a place that lists all the required configuration changes to get the core ModX functions to work? (such as being able to use the included text editor)?
The EasyCGI hosting plan we’re using is an IIS/Windows 2003 web server. Does MODx have any issues or special configurations to work properly in this environment?
I’m trying to avoid setting the test area locally using XAMPP because
(1) A web interface would allow multiple people to work on the site redesign...
(2) XAMPP would not be the same web server environment as the final EasyCGI IIS environment
thanks again!
