Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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, ...How to "Connect" DNN skins and containersHow to "Connect" DNN skins and containers
Previous
 
Next
New Post
5/27/2018 3:10 PM
 
James Brown


Joined: 6/29/2004
Posts: 319

An odd change in DNN 9.x now "connects" DNN skins and containers so that one cannot set the default container for a page unless it is somehow "connected" to the page theme.   Why this was done is completely beyond my comprehension.  I have containers that are skin agnostic, and do not need to be connected to any specific skin.  Although i can set the containers module by module this is a total PIA. 

What do I need to do to hook a set of containers to a specific skin?  In earlier DNN versions,  Skins and containers could be packaged together in one installation zip, but Timo's instructions at the top of this forum specifically state to not do that.

Is there a WIKI, short set of instructions, a post that I cannot find, some documentation somewhere that covers this?

Shouldn't the person who made the decision to do this be required to write the documentation and explain the rationale behind it before it gets implemented?
 
New Post
5/29/2018 9:14 AM
 
Timo Breumelhof


Timo Breumelhof's Avatar

www.40fingers.net
Joined: 2/9/2006
Posts: 4430
James Brown wrote:

An odd change in DNN 9.x now "connects" DNN skins and containers so that one cannot set the default container for a page unless it is somehow "connected" to the page theme.   Why this was done is completely beyond my comprehension.  I have containers that are skin agnostic, and do not need to be connected to any specific skin.  Although i can set the containers module by module this is a total PIA. 

What do I need to do to hook a set of containers to a specific skin?  In earlier DNN versions,  Skins and containers could be packaged together in one installation zip, but Timo's instructions at the top of this forum specifically state to not do that.

Is there a WIKI, short set of instructions, a post that I cannot find, some documentation somewhere that covers this?

Shouldn't the person who made the decision to do this be required to write the documentation and explain the rationale behind it before it gets implemented?

 I think what I stated is a way of packaging for DNN 4 you should not use any more, not about combing container and skin in one package in general.
Normally DNN connects the two when thy are installed together or have the same name (not 10%% sure about that one).
I think it's a good thing that by default DNN 9 shows the containers that "belong" to skin first as that's how it's used most.
But I do think it's wrong that you cannot get around that in DNN 9.

 

I think your only option at this moment is to have multiple copies of the same container (which is not optimal).
I hope this will be fixed in a future version of DNN 9 (did you log the issue?)

https://github.com/dnnsoftware/Dnn.Platform/issues
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How to "Connect" DNN skins and containersHow to "Connect" DNN skins and 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