PostL

Finally got somewhat of a reply from GoDaddy. He acts “confused” lol even though when I bought the service on Tues I asked him about this specific scenario since I don’t feel comfortable enough with my networking/php and cc knowledge to use the MultiSite option.

Anyways, this is the reply:

“I’m not totally sure what you need to do with an index.php swapping. I can tell you how to move a wordpress install from one folder to another or I can give you the steps on how to have anyone that goes to your domain.com to route them to your domain.com/wp.

To move a wordpress to another folder follow these direction:
http://help.securepaynet.net/article/6495?pl_id=1&locale=en&ci=46061

To redirect people to the folder your wordpress is installed to please follow these directions:
http://help.securepaynet.net/article/234?pl_id=1&locale=en&ci=46061 “

I looked over both and wouldn’t mind using the options laid out on the 2d one (lose the index.php file I put in root, then simply redirect domain1.com visitors to domain1.com/wp then repeat process for the other two domains), BUT it isn’t all too clear on what file it is I am using the suggested code in.

I am new to this, but am also a quick learner lol, thanks for your patience and assistance.

I set up my first site. Didn’t put WorPress in root, it was in its own folder. To get people to see it as ‘www,domain.com’ and NOT ‘www.domain.com/wp’ I had to move the index.php file into root and change one line in it.

I then made domain2.com and domain3.com, each in their own folders. Now if you go to domain2.com or domain3.com you actually see domain.com, because of that moved index.php file.

Obviously I dont want that and I don’t want you have to go to domain.2com/wp etc… either.

So the question is, how do I make it where to get to domain2 or domain3 you DON’T have to have the ‘.com/wp’ at the end?

There is only one index.php in that root but it is directing the 2d & 3d domains to the 1st. That needs to change but I am lost as to how to do it.

Thanks.

I finally got a reply from the Theme’s creator and they were able to resolve the issue for me. I still couldn’t tell you what that issue was, but they seemed to find a work around for me. Thanks for the reply though!