Joe,

I found another important one this morning in the web store.  If you are in a child site's web store, add a product, then add an offer, then add 1 or 2 products to the offer and click on one of the edit links next to a product in that offer and try to save or delete the product from the offer.  This produces an error and is linked back to the parent site.

Thanks,

Mike

Joe,

I downloaded the latest source, rebuilt, ran setup & tested last week.  I should have a chance to do this again this weekend.  Thanks for making the fixes.  Let me know if you have time to fix to the last couple items I reported and I will get the new code & test your fixes this weekend.

Thanks!

Mike

Ah, that makes total sense.  Hopefully that will solve most of these parent/child link issues.  I did notice that many of these things were happening on pages/controls using Ajax postbacks... except for stuff like emails that had links that pointed back to the parent site for example.

One feature I would recommend is adding an UpdateProgress template to all of the pages that use ajax.  Sometimes async calls are firing back to the server but I'm not aware they are being made and I click something too soon and cause an error.  A simple "Working..." div or animated gif would probably do the trick.

Thanks for making the fixes, I may be able to get the code today and test it if I can squeeze in some time.  I just bought you a beer for your help.. enjoy it!  Thanks again for working on these issues.

- Mike

Joe,

I tested all the fixes and they are working now.  Thanks for your efforts.

Quick question...

Is it possible to have 2 seperate installations of mojoPortal on 2 different hosting spaces that both point to the same database server?

For example,

• Installation 1 - http://www.mymojoportal.com  (Root SiteID = 1)  (Web Server 1)
• Installation 2 - http://www.secondmojoportal.com (Root Site ID = 7)  (Web Server 2)

But both of these sites connect to the same MSSQL Server instance and set of tables (have same connection strings).  I tried changing "UseRelatedSiteMode" = True and "RelatedSiteID "=7 on Installation 2 but when I hit the root of Installation 2 - it still points to SiteID=1.  I also moved Data/Sites/7/ folder to Installation 2.  Is there a web.config setting I can change that will let me choose the root site (parent site) to be ID 7 instead of 1?

I know this sounds confusing but I only have 1 SQL server instance but I have 2 seperate hosting spaces that I'd like to install mojoportal on.

Thanks for your help.

Mike

Joe,

That makes sense; however, I'm using "folder mappings" instead of "host names" for my configuration on my sites so I don't think this will work.  I'm still messing with some things to see if I can get it to work using folder mappings.

Any ideas on this would be appreciated.

============== Here are some steps I've taken to try to get it working ===============

I did what you said so far... went into the first site and created a new site, installed features in the new site and started adding some pages.  Since I'm using folder mappings, I got it setup on (Web Server 1) by adding a folder mapping for it (www.myfirstmojoportalsite.com/newchildsite1 - SiteID=7).

Then I installed mojoportal on (Web Server 2) and the address for it is:  (www.mysecondmojoportalsite.com).  So essentially when I hit mysecondmojoportalsite, it just needs to go to the content for SiteID=7 instead of SiteID=1 which is www.myfirstmojoportalsite.com.

You are right, the content for both sites is the same starting out (SiteID=1).  I tried adding a Redirect.aspx page at the root of mysecondmojoportalsite and set my default documents to be "Redirect.aspx, Default.aspx".  The code in the redirect fires first before any of the mojoportal stuff fires.  I added code to redirect any hostnames to point to a folder mapping like this:

Redirect.aspx:

<script language=C# runat="server">
    private void Page_Load(object sender, System.EventArgs e)
    {
    String siteNameUrl=null;    
    siteNameUrl = Request.ServerVariables.Get("SERVER_NAME");
         
    switch (siteNameUrl)
    {
     default:
             {
        Response.Redirect("~/newchildsite1/");
            break;
         }
    }     
    }
</script>

This actually works and fires before any folder mapping code in the mojoportal site (since Redirect.aspx is the first default document).  So I added a folder on mysecondmojoportalsite.com/mychildsite1/ and dropped a Default.aspx page in it.  The redirect works great, however, I only get a blank Default.aspx page and it doesn't load the content for SiteID=7.  I'll keep messing with it.

====================================================================