Thanks for the reaction Timo.
Just to be sure, I repeated the whole process again, running DNN6.2.1. For the test I used the free Greytness skin by Adammer (http://www.adammer.com/).

Logged in as host, I added the skin package via Admin -> Extensions -> Wizard.
Again, the new skin files were placed in the _default folder, and the new skin was available to all portals.

In the SkinPackages database table the new skin has the PortID column set to the proper portal (the DarkKnight skin has NULL here, probably indicating it is a host skin). But none of the skin/container selectors seem to be taking this information into account.

The skin package values also point to the _default folder, e.g. Portals\_default\Skins\Greytness2 but that seems to be correct (http://www.dotnetnuke.com/Resources/Wiki/Page/Manifest-Skin-Component.aspx).

Moving the Skin and Container files to the correct portal directory seems to be the only option for now.

Regards, Willem

Yes, I tested with a clean copy of our production server. Also retried in 6.2.2 with the same result. The issue is logged: http://support.dotnetnuke.com/issue/V...