Thomas wrote
Log in as host, then on the host menu choose Portals. Then click on the portal you want to upload or assign the container to. Now go to the Skins menu and upload or assign the container. That should fix it for you.
Thanks Thomas, but this does not help either :(
As far as I find out, what you wrote has the same effect as assigning Skins/Containers in Host - Host Settings (The result is a change of value in the SQL table "Skins")
My SQL tables values are following (I want Container B to be assigned only to modules located in ContentPane on page TabID 56 on my root portal PortalID 0)
Table "Skins"
PortalID SkinRoot SkinSrc SkinType
0 Containers [L]Containers/My containers/Container A.ascx 0
0 Containers [L]Containers/My containers/Container A.ascx 1
0 Skins [L]Skins/My skin/skin.ascx 0
0 Skins [L]Skins/My skin/skin.ascx 1
Table "Tabs"
TabID PortalID ContainerSrc SkinSrc
56 0 [L]Containers/My containers/Container A.ascx [L]Skins/My skin/skin.ascx
Table "TabModules"
TabID PaneName ContainerSrc
56 ContentPane [L]Containers/My container/Container B.ascx
56 TopPane NULL
56 BottomPane NULL
ContentPane module is using Container B only in Admin/Host. On the portal module is still using default container stored in Portals/_default/Containers/_default/No Container.ascx.
Are there any other tables where it can take this default settings from?
PS: I've tried to assign this Containers to my other subportals and it work fine both on Host/Admin and Portal. Than I've also tried to apply default DNN-Blue to the ContentPane and again it was working only in Admin/Host - %$@*!