The container is a key piece of the functionality needed so that the admin can apply settings to their modules. I have a blog post about the short-comings of the design if you care to know more. Containers and Menu Actions in DotNetNuke Yes, you need a container to align modules
One problem is with alignment settings. The wrapper used for the module when you uncheck "display container", puts the content in a span tag. Since span is an inline html element it does not have alignment capabilities (it is also an XHTML validation issue). You could make your own "no container" that does not have any visible presentation, but still allows alignment if you wanted to work around this. The easiest way is to just change the "no container" container to use a DIV instead. It is located in portals/_default/containers. Another option, is to put a div tag opener in the Header of Module Settings and a closing div tag in the Footer. Here is another slightly more advanced technique you can accomplish with the header and footer fields:
Positioning Modules in DotNetNuke Ok, triva question for anyone who has been around awhile :
What version of DNN was it that the Header and Footer fields were first introduced? And a little history for those that do not know:
The Header and The Footer fields were once the only way to do containers. We've come a long way baby!
[/quote] [/quote] [/quote] [/quote] |