Hi folks!

I am not able to apply container to my portal and need help!

Lets say, I have two containers A and B. I need to apply container A to all modules and container B only to module X.

My settings are following:

Host - Host settings

Host container: <not specified>, Admin container: <not specified>

Admin - Admin settings:

Portal container: container A, Admin container: container A

Module X settings:

Module container: container B

Containers are working as I need when logged in as Admin/Host but on portal they both change to default !!! Agrhhh ....

Are there any other settings I can use to apply containers?

Which SQL table is taking care of containers assignment?

Thanks for helping in advance !

Riko

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 - %$@*!

It seems like a strange bug to me as well. I am sure it is not related to caching, neither restarting application as tried it several times already.

I believe skins are handled in following SQL tables:

SQL table             DNN Interface                                                                Columns                                                                                                                    

Skins                    Host/Admin-Settings and Host/Admin-Skin           SkinType=0 for portal, SkinType=1 for Admin,  PortalID=NULL for Host

Tabs                     Page Settings - Page Skin/Container                       for each page by specific TabID (56 in my case)

TabModules       Arrow in top left container corner - Settings          for each page pane (specified in PaneName) for each page (TabID)

I could not find any Skinning information in Portals table (there are mainly Settings from Host-Host settings interface except Design settings)

Do you think upgrading to 4.8.2 (currently running 4.8.0) may fix the issue?