Hi Richard,

Thanks for checking, anyway... the location you are referring to does indeed set the default container, but playing with it doesn't make any difference. It did lead me to find, though, that it's not just my container for which the CSS is not being applied for normal users; not even the default container CSS is being loaded! I had not noticed because there was no specific style change I was looking for from that container. But all through my site, regardless of what container is selected for any module, the container.css file is only referenced in the page returned to the admin/superuser. Regular users get all the content, skin stylesheets, etc, but there is no reference in the page source to container.css.

I guess I have a bigger problem now! Can anyone explain to me how and why the container.css stylesheet is supposed to be loaded in the normal state of affairs, or suggest why it might not be loaded for certain security roles?

The only time you can see the styled container when logged in and do not see the style when logged out is when the module is set not to display the container.
Module settings >> page settings >>display container ?
check to display styled container, un check not to display the container style.

If this is does not help there could be an issue with conflicting css styles, post the link to the page and we can have a look.

---

WSI - DNN Gold Partner | WSI - Internet Marketing
Matt Jura - blog on design, web and DotNetNuke | Twitter @MattsDailyTweet