Hi there. Could somebody please help?

I am trying to apply a different container to different modules on a page. eg. I have an HTML module I want to apply a blue container to, an event module a green container, a survey module an orange container etc.

I have created the skins and the all work. However, when I select the container from the settings for, shall we say, the html module, all the modules on that page end up being updated with the same container.

I have followed Lee's video tutorial to the letter and still end up with the same problem....i.e I am unable to apply different containers to different modules on the same page. Even the modules where I have not specified a container are updated with the skin selected on the other module.

I am using DNN 4.9. Can anybody help?

many thanks

My guess is that you are selecting a default container for the page. Instead, apply the containers to the modules separately, using each module's Settings page.

If you specify a default module for the page, then ALL modules on that page will have that container. You specify a specific container for a specific module to override the default selection.

Thank for taking the time to reply.

But I am doing exactly what the video turtorial shows:

1. Select module "settings"
2. Then in Page Settings select  "Module Container" and select the container.

I am doing this and it changes all the modules on the page to the same container.

I guess it's just one of those inexpicbale computing things.

Thanks again. Looks like it's bacl to Joomla and PHP ..sigh!!!!

One last thing, Joe. You say .."If you specify a default module for the page"...how do I go about specifying a default "module". I have searched everywhere and cannot find how to set a default "module" on  a page.

Thanks again.

Make sure that under Page Settings, Advanced Settings that you haven't checked the boxes "Set as Default Settings" or "Apply to All Modules."

You really can change to container for a single module.

Wrong word.  I meant to say "Default Skin."

Here is the hierarchy:

• Host Skin
• Site Skin
• Page Skin

For containers it is:

• Host Container
• Site Container
• Page Container
• Module-specific Container
  

No, nothing is inexplicable.  Sometimes the explanations are difficult to find.

Case in point:  I was having a multiple-day catastrophe trying to figure out why a special skin was rendering differently in Firefox and IE.  It turns out that the name of the "doctype" file for that particular skin was spelled wrong.  That caused the browsers to operate in quirks mode.

How I found it, I'll never know ... but I was on the verge of something by the time that I found it

Did you solve the problem? - If you go to page settings and set a container it will set the container for all modules on that page.

If you then go to the module settings menu and select a container to use for that module it should override the container specified for the page settings and display a container on that module.

Thanks,

Hi Lee & Joe,

I'm actually having exactly the same problem as platypus08.

I know how to set both a site and page's default container. This works as expected and I have done this. However, I also want to specify a single module's container. Clicking on "Settings" for a module, I'm taken to the "Module Settings" page, but then when I select a Module Container on this page, it changes the containers for all modules on the page!

I'm using a custom skin and containers. However, these were based on skin/container files that did allow me to change an individual container and I don't think I've changed anything that would cause this (mostly just changed .css).

I'm also using DNN 4.09

Anyone else experienced this issue and resolved it?

Thanks in advance for any help.

Make sure that "Apply to All Modules?" and "Set As Default Settings?" aren't checked under Page Settings, Advanced Settings.

Yep, they're definitely not checked.

I really have no idea what could be causing this. I've tested so many different settings, but will continue looking at it more today.

Just an FYI, "Apply to All Modules?" and "Set As Default Settings?" do work as expected. When checked, they do what they say they will do.

I still haven't figured out the problem; however, I have found that the issue is only with my custom containers. If I apply an older container, it will only apply to the one module.

Figured it out - and now it's so obvious!

For anyone else who comes here with this problem:

I was lazy and had used the same .ascx file and .css files for 6 different containers. Which is fine, but I was really lazy and didn't change the name of the CSS classes for any of the containers, I had just changed the actual styles in the .css file. Therefore, every container used the same class names.

Knowing this, it's quite obvious that all modules would have the same container. When a page has multiple different containers (all with the same CSS classes) only one instance of the class is actually applied to all modules.

A real forehead slapper.

Many thanks to vincentp for figuring this one out and for taking the time to post a reply.

Talk about major frustration!!!! You really saved the day for me!

Hi there. Could somebody please help?
I'm using Dnn4.9.I'm having 10skins in my Dnn4.9.I want to know is,can we assign only 3 to 4 skins for a new portal out of the 10skins I'm having,and another 3 to 4 skins to to other portals.So when new user logins he should be able to see only 3 to 4 skins available.If this is possible please let me know how can I solve this issue.If it is not possible also please let me know why?

I think that the only way to do this is to install skins at the Site level, not at the Host level.  So, as Host, you would upload the skins that you want to use in a particular site for that site.

The downside of this is that, for multiple sites, you will have multiple copies of the same skins in multiple sites.  Other than the labor of setting things up and extra disk storage space, this shouldn't be a problem.