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, ...Pane Level Containers...Pane Level Containers...
Previous
 
Next
New Post
10/11/2008 5:09 AM
 

We used to have the ability to specify a default container in the skin at the pane level using  Containrsrc="Default-H2.ascx" ContainerType="L" ContainerName="annexus-financial".  This is the second or third time that I've tried to use this lately and it seems to be being ignored by DNN.  Has this functin been removed or is it a bug that it is not being processed?  This has always been a good feature to help maintain the design on a web site.  Anybody know?

 

Dax

 
New Post
10/12/2008 11:09 AM
 

 We're doing it fine in DotNetNuke 4.9.0 .  Here's the HTML we use:

 

<div class="sectionNamePane" id="SectionName" runat="server" visible="true" ContainerType="L" ContainerName="PDNN5" containersrc="SectionName.ascx"></div>

When I believe that "L" means that the skin is located at /Portasl/#/Containers .  Make sure you're not putting the skin under the _default folder's container section.

 
New Post
10/12/2008 1:16 PM
 

Tony Valenti wrote
 

... "L" means that the skin is located at /Portasl/#/Containers

Yep.  Use a "G" for global containers located in the _default subdirectory.

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
1/7/2009 4:58 PM
 

Hello and thank you in advance:

I am new here and a TOTAL Newbie to DNN, so please forgive me...

I am creating a site with a basic BG and just a few panes/containers.  Nothing fancy.

I am confused by the skinning guid and the above post.  I am coding in HTML, not ASCX.  In the code above you mention "<...containersrc="SectionName.ascx>"  Would this code be inserted into my skin.htm document?  the XML document, or into another document?  Also, I dont understand what the SectionName.ASCX would be. How would i customize this?  

Thank you for your help!

 
New Post
1/8/2009 1:16 AM
 

dp wrote

Hello and thank you in advance:

I am new here and a TOTAL Newbie to DNN, so please forgive me...

I am creating a site with a basic BG and just a few panes/containers.  Nothing fancy.

I am confused by the skinning guid and the above post.  I am coding in HTML, not ASCX.  In the code above you mention "<...containersrc="SectionName.ascx>"  Would this code be inserted into my skin.htm document?  the XML document, or into another document?  Also, I dont understand what the SectionName.ASCX would be. How would i customize this?  

Thank you for your help!

In all honesty, if you're just starting with DNN, you may want to set this on your "to do" list.  I assume they are entering it into the ASCX file at the control call, (which is going to make your head explode this early on IMO).

There is extensive documentation here along with many other very useful online resources (DNNCreative.com comes to mind).

To start, just make a simple skin like this:

<div id="ControlPanel" runat="server" class="controlpanel></div>
<div class="LogoDIV">[LOGO]</div>
<div class="NavDIC">[NAV]</div>
<div id="ContentPane" runat="server" class="contentpane"></div>
<div class="LoginDIV">[LOGIN]</div>

(This is for pre-5.0, I haven't worked with it too much yet and they just overhauled the skinning system)

Make that your skin.html, then include it along with a skin.css file in a skin.zip file and upload it. That should provide you with a VERY basic skin with the most essential items (well, maybe not [LOGO]). You will notice that when you upload it, DNN will process the HTML into an ASCX file automatically and replace all the tokens [NAV], [LOGIN], etc. with the appropriate controls.

Another option is to just copy out the default skin and reverse-engineer it, which is the way I learned. It's alot easier than it first appears.

Also, check out these books:

DotNetNuke Skinning and Design
DotNetNuke for Dummies (Nothing personal, they just do a good job of explaining some of the more abstract ideas)


Wells Doty Jr
Online Content Development
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Pane Level Containers...Pane Level 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