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, ...Sitewide management of skin/containersSitewide management of skin/containers
Previous
 
Next
New Post
4/23/2013 4:10 AM
 
HI.
Can you set particular skin containers at skin level?.

I have a responsive template which requires a particular footer container and I want to use another container for the content areas.
As far as I can see you can either set containers at page or module level, not both.

As the footer will be on every page of the site I do not want to set this manually on every page module.

 
New Post
4/23/2013 5:47 AM
 

Hi,

there is no site-wide solution for that, but you can define a default container for a pane in your skin. See this Wiki entry.

Best wishes
Michael


Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
4/23/2013 6:43 AM
 
Michael Tobisch wrote:

Hi,

there is no site-wide solution for that, but you can define a default container for a pane in your skin. See this Wiki entry.

Best wishes
Michael

 Thanks Michael, that seems to have worked a treat. I have set the panes to the containers I wanted in both the footer and content areas and any new pages using that skin auto pick up the containers.

The inability to assign modules/styles to menu options like Joomla for example, is the only drawback in DNN. I hope I never have to re assign modules from page to page accross a whole site in the future.
I assume it could be done in the database so if anyone has a query for this or a pointer as to which tables I should look I would be grateful.

 

 
New Post
4/23/2013 8:05 AM
 
Hi,

I think this would be quite a challenge to realize, because DNN is so extensible. The only "must" for a skin is a ContentPane, there is no restriction for how many panes have to be on a skin or how they have to be named. And then: It is possible to use different skins for every page, so if you have a central tool saying: In every FooterPane, the default container is the MySkin-Footer container, this can only work, when every skin in use has a FooterPane. Imagine you need a skin with a FooterRightPane and a FooterLeftPane for some reason on a single page....

Best wishes
Michael

Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
4/23/2013 8:35 AM
 

Sorry Michael , what I was really meaning was the assignment of Modules.

Many CMS's let you assign modules sitewide by selecting a checkbox against the menu items for the pages they need to be on, If you then need to change the selection list it is a simple procedure to select or deselect from the list.
I shudder to think how much work DNN would be, if for e.g a local goverment site decided to hide modules from half its pages or add a new module to the sidebar for a say a couple of hundred pages.
We are actually evaluating whether DNN pro could be an alternative to our commercial CMS for our local goverment sites, and this lack of sitewide management may well go against DNN.

I suppose you would have to create specific skin ascx's to handle the different layout options of often repeated elements.
Can a module be added to a skin file direct??, if yes that might be an option.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Sitewide management of skin/containersSitewide management of skin/containers


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