Hi Chris,

1. Any host that supports mojoportal should be fine but how many sites you can host and performance will depend on the robustness of the hosting package and the aggregate traffic of all the sites. I don't really have a report card for different hosts. Have heard some complaints about WebHost4ASP recently but used them in the past and they were decent. For shared hosting I currently use DiscountASP or CrystalTech, for dedicated servers I use 1and1.com. I'm in the 1and1 affiliate program so if you go with a dedicated server from them please click this link and I can get a little commission. I'm not an affiliate with any others, I just list hosts that I'm aware of that do host mojoportal.

2. It can be done, its not trvial but its not extremely difficult. You would backup the site file system and database and restore in a new location then delete unwanted sites from the db using Site Settings in the root admin site, then delete unwanted /Sites/[SiteID] folders. Probably would be best toi query around in the db and make sure all unwanted site data from other sites is gone.  Once upon a time joeaudette.com was running from the same installation as mojoportal.com but I separated them a good while back with this approach.

3. the IIS logs would include all sites traffic because its really all one site from IIS point of view. But google analytics and woopra work just fine because they don't rely on IIS logs they track to their own data from javascript. ASP.NET doesn't have any logging for web requests, its IIS that does the logging. The mojoportal log is also per installation so events/errors of all sites appear in the same mojoportal log. Only the root admin site has visibility to the mojoportal log via the UI.

I generally don't host different customer sites in the same installation (though some people do). I host multiple sites for the same customer that way sometimes. There is no good way currently to backup or restore a specific site from a multi site installation. If you restore the db its restores the whole db.

Hope it helps,

Joe

Folder sites can only be 1 folder deep, so the admin site has to be at localhost, not localhost/mojo.

Hope it helps,

Joe

Get the first site running at http://localhost not http://localhost/mojo

You may want to start with a clean db because you alreadty created url mappings for  /mojo/pagename.aspx

Start with a clean db, get the first site running at http://localhost, then create the folder site at http://localhost/mojoFrance/Default.aspx

If you want it to work with http://localhost/mojoFrance/ without the Default.aspx then you need to actually create a folder named /mojoFrance and put an empty text file there named Default.aspx

Hope it helps,

Joe 

No, I say point the root web site at the same folder where you have the virtual directory pointing at then delete the virtual directory. 

It can't work in a Virtual Directory the admin site must be a root web site.

In IIS on XP there is only 1 web site "Default Web Site" and there is a limitation that there can only be one web site because MS doesn't want you to use XP as a server, on a server you can create multiple Web Sites, or you can explore workarounds like Slaven suggested.

For using folder based sites in mojoPortal, the first site must be a root web site NOT a Virtual Directory. Currently you have a Virtual Directory named mojo that points to the folder where the mojoportal files live. You need to point Default Web  Site at that folder, right click Default Web Site and go to properties point  Home Directory to the mojoportal. Then the first site will work at http://localhost, which corresponds to Default Web Site.

Hope it helps,

Joe

No, you don't need any Virtual Directory for the folder sites, once mojoportal is running at http://localhost just go to Administration Menu > Site Settings, see the dropdown near the site name, choose new site, create the site, then on the Folder Mappings tab create the folder mojofrance, now it will work you can visit the new site at http://localhost/mojofrance/Default.aspx, if you want it to work without the Default.aspx then create a folder beneath the root of the main site at /mojofrance using Windows Explorer. Put an empty text file there and name it Default.aspx

Hope it helps,

Joe

This is a bug that has been fixed if you upgrade to version 2.2.9.5

Best,

Joe

If you have the 2.2.8.6 source code you can copy the newest version of Web/Components/UrlReWriter.cs to get the bug fix and then produce your own build.

Other than that the only way to get bug fixes is upgrading.

I don't like it when people ask a bunch of questions on a thread with an unrelated topic or change the topic after I answer.

1. No, if you need something custom you have to implement it.

2. All database platforms have their own tools for backup and restore of databases, its not needed to iimplemnt it in mojoPortal. Maybe someday we will implement import and export to makwe it possible to move from on db plaform to another but its not a hihg priority.

3. If a user searches they only see results if they are in a role with permission to view the page, result are filtered according to the user's roles.

4. You can enable caching at the module level, click the gears next to the title of the module. It works well for Html module but not for any module that does postback or uses ajax so use it with caution if you do use it. For most installations in shared hosting you don't have enough memory available and if you start caching too much it will run out of memory and recycle the app frequently. Caching should only be used to solve a perfomance problem for a site that gets a lot of traffic an is under heavy load. It is disabled by default because it can be problematic to use it. To enable it you need to add this to user.config or Web.config

<add key="DisableContentCache" value="false" />

5. By default we already trackuser ip addresses, you can see it if you click the gear next to a user name on member list to get to user management, then look on the location tab to see ip addresses the user has used.

Hope it helps,

Joe

And also you will find you get more help if you ask 1 question per thread as I said before and make the topic be related to the question. This helps everyone because now if someone searches mojoportal site for "ip address, location", now the result for this thread will say "Hosting Multiple Sites" which is not related at all to the question so the user may not click that result and yet this thread now has the answer.

But still I can't answer every single question, I'm just telling you I'm more likely to answer questions if you post 1 question per thread.

Best,

Joe

You are not hearing what I'm saying, I'm not going to tell you again, your new question has nothing to do with this thread, you keep asking new questions on an unrelated thread. If you have a new developer question you should start a new thread in the developer forum and quit asking more questions on this thread.