Hi Joe, if you go to Site Settings from the master site and select a child site, the skin name that defaults on the General tab is from the master site, not the child site. If you then make any settings changes and save, the child site gets assigned the master site's skin. To fix it, you need to go to the child site and select the correct skin from there.

Jamie

Hi Joe, I just downloaded the latest changes and did a full rebuild and deploy from source, but I still had the issue. I debugged and was able to fix it by commenting out the following statement in EnsureItems() in skinSettings.ascx.cs:

if ((dd.Items.Count > 0)&&(!catalogChanged)) { return; }

It seems that catalogChanged is not being updated reliably when selecting a new site. Hope that helps.

Jamie