Hi Joe,

 I think I'm close to solving this , one of your answers from other same forum topic goes like this

"Oh, I thought of something else you will need to do to make this work. When you create the second (or nth) site using the Admin > Site Settings of the first site, it will create a folder in the first site at Data/Sites/[new site id], so the second site will be Data/Sites/2 and the 3rd site will be Data/Sites/3 and so on. Since the additional sites are using their own web installation you will need to copy these folders to the correct location in the additional sites because by default there is only 1 folder at Data/Sites/1."

I just got confused with the part where you say "Since the additional sites are using their own web installation you will need to copy these folders to the correct location" do you mean that I have to have another "mojoportal" folder  inside the "Data/Sites/2" ?

Thanks again,

Gil

Thanks Joe I think I finally got the whole concept of adding additional sites, so I changed my 'host name' and selected a new skin to be modified, then I ran the dev machine and gave me this

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Does this error make sense to you? did I do something wrong with pointing hostnames?, additional fyi we're using WINS to resolve IP address in our dev boxes here in the office.

Thanks truly,

-gil

Hi Joe sorry about posting all those errors won't happen again, anyway, I finally realized something tell me if this is correct.

What I did was, I created a separate copy of mojoportal and then assigned the new hostname to that copy I created (which was the same hostname that I set up on the First site when I created a new site). This will not work since I think what you were trying to tell me is that when I create a new site using hostname-base all contents and data are related to that SiteID I newly created, thus the new site.

my manager want's to have a separate folder (another mojoportal) but using same DB and point the hostname (new site domain) to that new folder.  I can apply the multi-site FOLDER-based setup right?

Don't worry once I have this down, I can take it from here, since I have mastered the art of skinning MP and I'll be able to start redesigning the new site.

Once again for untiring support - thanks!

Hi Joe, appreciate the reply so much, I will just have to do the folder-based one then, since I'm having problem using hostname-based.

cheers!

-gil