Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Not able to apply containers to a portalNot able to apply containers to a portal
Previous
 
Next
New Post
4/19/2008 10:15 PM
 

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

 
New Post
4/20/2008 3:39 AM
 

To apply the container to a specific portal, try this:

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.

 

 
New Post
4/20/2008 7:23 PM
 

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

 
New Post
4/20/2008 8:15 PM
 

This almost sounds like a weird caching issue.  However, the difference when logged makes me think that there may be a bug instead.  Have you tried recycling or restarting the application?  You can do this when logged in as a host, at the bottom of Host Settings.  Then logout and see if the problem persists. 

You can check the individual assigment of module containers in the TabModules table.  The portal level assignments I believe occur at the Portals table.  (I do not have an install on this machine, so I am not 100% positive about the table names.)


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
4/21/2008 4:32 AM
 

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?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Not able to apply containers to a portalNot able to apply containers to a portal


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out