index.php in server root instead of install directory

I have installed modX in www.domain.com/modx/
I would like to access the site with www.domain.com

I know that it’s possible with the httpd.conf file or with .htaccess. But to the first i have no access (shared hosting) and with .htaccess it’s a pain in the ass (at least in my case).

It would be GREAT!!! If the modx’s index.php could be installed into www.domain.com/ instead of www.domain.com/modx/ so all these problems would be solved! That would be no great deal to modify the modx installer to ask the user where he wants his index.php and then automatically generate all the necessary links which point to the index.php

thats my only wish at the moment, which would help a lot of users, i think.

cheers!
Thiemo

You might want to take a look at this
[Plugin] Subsites/Subdomains

;D

Hi and thanks for your answer.

Unfortunately i don’t think that’s a solution to my problem. I’m sorry my English is not that good, so the description of my problem could’ve led to a missunderstanding.

I don’t wanna have a subdomain like sub.domain.com. I just don’t want the user to notice the subdirectory where modX is installed in. Although modX is installed in a Subdirectory: www.domain.com/sub/page.htm the user should see www.domain.com/page.htm . I tried together with a master of .htaccess. The problem is that the same page is accessible under www.domain.com/page.htm and www.domain.com/sub/page.htm Thats a serious problem, because search engines punish you for having the same content twice.

Look, the problem is: modx has too many files and directories to have it directly in the server root (so it would be accessible via www.domain.com). It’s a horror to manage a CMS directly in the server root. I think it’s normal to create a subdirectory where you install it. But then, the URL looks like that: www.domain.com/sub/
The easiest workaround would be if the index.php, which creates all the output, would not sit in the subdirectory but in the server root.
1) Not such a mess, because all the other files are still in the subdirectory
2) although we have a nice URL, because the index.php lies in the server root directory

best wishes,
Thiemo

just make a index.html with a forward to index.php on the subdir
(but how many files are in the root?
when you install modx there are only 2 or 3 files in the root the rest of modx is in the folder manager and assets etc.)

?? index.php, the assets folder, the manager folder, and the ht.access file. That doesn’t seem like so many files and directories.

I can’t see any reason of why you need to put 2 files and 2 folders in a subdir, while you can just put those 4 things under the root without affecting your site? You can also change your domain hosting to point to the sub directory, instead of root directory, right? I might need a little justification in here, before I can help your further

MODx has 2 folders and 2 files in root, total is 4, I think its not a pain to manage it

Here is the list:

1) index.php
2) .htaccess
3) assets/
4) manager/

Its simple... isnt it ?

(lots of same replies )

Zi, don’t forget the .htaccess for linux/unix to use SEF URL

Quote from: Djamoer at Feb 15, 2006, 08:32 AM

Zi, don’t forget the .htaccess for linux/unix to use SEF URL

Thanks buddy ! .. updated

Quote from: thiemo at Feb 15, 2006, 08:08 AM

Hi and thanks for your answer. Unfortunately i don’t think that’s a solution to my problem. I’m sorry my English is not that good, so the description of my problem could’ve led to a missunderstanding. I don’t wanna have a subdomain like sub.domain.com. I just don’t want the user to notice the subdirectory where modX is installed in.

No it’s not your english but my quick reading that did the deed
I get it, you want MODx installed in a subdir but running transparently as if in root... interresting question, and interresting answers I am learning there...