Hi all,
I’m new to the forum. MODx looks like a great solution but I need to know some more about where to install it and what the system requirements are. I have a client with an unusual set up where all php files need to be served from within a cgi-bin directory but the site needs to be deployed in their regular web directory. So, I guess my question is: Can I install MODx in the cgi-bin directory and then use it to create a site that is located in the regular WWW directory? Again, php will not work in the WWW directory. It will only work in the cgi-bin directory. Will any PHP snippets still work? Can the output of MODx be plain HTML even though it uses php to build certain parts of a page?
I would appreciate any advice.
Thanks in advance.
Joel
-
☆ A M B ☆
- 24,524 Posts
All html pages are built from the main index.php, and all manager pages are built from the manager/index.php script. So I guess you’ll need to install MODx in the cgi-bin directory, then figure out where the non-php files (.js, .css, images, etc) need to be, and adjust paths as necessary. It should be interesting. Maybe someone else has had experience with the same server configuration and has better advice.
Thanks for the information Susan. Can anyone tell me where I would set the paths? I’d appreciate it.
Joel
-
☆ A M B ☆
- 24,524 Posts
Well, usually the path to .css files and .js files are set in the <head>...</head> part of the HTML template. So you would have to set the links to wherever you end up putting those files. But then I really don’t know how a dynamically built site would work under the circumstances you’ve described. Considering how php can be embedded in an html file, it kind of eludes me.
I think what I will have to do is use Apache to map all requests to the regular web directory to the cgi-bin directory. Does anyone know of any good explanations of how to do this? Basically what I need is a rule that sends a / requests to /cgi-bin/.
Thanks for all the help!
Joel
