rbkinsey
Posts: 42
|
| Posted: 03/26/2008, 8:45 AM |
|
I've only installed my code where the domain name was the same as the root. I could either install my code to the root or make a folder with it in it and redirect to the folder.
However, now I have a client who uses several domains out of one hosting plan. He just sets the cPanel for the SubDomain to point to the folder the Store package has been installed in. Example: www.store.com is called I have a default.asp file with a redirect to call www.store.com/store/ which calls the default.asp out of the correct folder now. However, I have had a few other problems dealing with similar thing.
When trying to goto Administration after login, I had a problem where login called www.store.com/store/store/Admin/AdmMenu.asp, so a change Login.asp to call Default.asp and made the user click on Administration a second time once the login was provided it would work fine.
Next User maintenance would not longer work. That's when I decided I better ask for help and see what the official way of dealing with the Common.asp file is when you have a subdomain situation?
In a domain only situation I changed only the connection string to the one needed for the host and everything else hooked alright.
|
 |
 |
wkempees
Posts: 1679
|
| Posted: 03/26/2008, 11:35 AM |
|
Read Help and Docs, search for server profile.
In the case you describe here I would:
create a new (second) Server Profile.
Set the project directory to reflect the subdirectory structure.
Then Publish through FTP.
CCS caters for secondarey and third,fourth and so on, profiles each for their own target server. Almost all parameters will follow the settings in that profile.
Almost never need to manually adjust any of the common files.
Walter
_________________
Origin: NL, T:GMT+1 (Forumtime +9)
CCS3/4.01.006 PhP, MySQL .Net/InMotion(Vista/XP, XAMPP)
if you liked this info PAYPAL me: http://donate.consultair.eu
|
|
|
|
|
