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, ...Help Needed in Resolving CSS Layout IssuesHelp Needed in Resolving CSS Layout Issues
Previous
 
Next
New Post
5/28/2012 11:43 AM
 
I'm inclined to think that if you have the skills and the site access to create/modify a skin (you clearly do) then anything that should be on EVERY page I might prefer to code directly in the skin.

If it's on some-but-not-all pages then it's a closer call between several near duplicate skins and repeating modules on multiple pages.

I have have tried both 'display module on every page' and adding existing modules to a page and I have never been fully satisifed with the results.

However - maybe I just didn't properly appreciate how those features were supposed to be used.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
5/29/2012 8:32 AM
 

HI,

for beginning I think one of the skins that is shipped with dnn would be the best start.  To learn and look how it works you could also look to some skins on codeplex.

If you add more then one module to a pane the modules will be each other.  If it is needed you could create 3 or more panes side by side, with different IDs eg Contentpaneleft, Contentpane, contentpane right and set all by own CSS design.

 
New Post
5/29/2012 5:49 PM
 

I've made some changes to the CSS and DIVs.  The pertinent CSS is as follows:

#footerleftpane, #footerRightPane
{
    width: 300px;
    float: left;
}

#footerMidPane
{
    width: 340px;
    float: left;
    padding: 10px;
}

The div structure is now as follows:

<div id="footer">

<div id="footerleftpane" runat="server">

<dnn:LOGO id="dnnLogo" runat="server" />

<h3>Driving business performance.</h3>

<h3>Practical Sales and Operations Planning</h3>

<h3>for medium sized businesses.</h3>

</div>

<div id="footerRightPane" runat="server">

<dnn:COPYRIGHT id="dnnCopyright" runat="server" /><br />

<dnn:PRIVACY id="dnnPrivacy" runat="server" />

<dnn:TERMS id="dnnTerms" runat="server" />

</div>

<div id="footerMidPane" runat="server">

</div>

</div>

What further changes are needed to ensure these 3 DIVs align next to each other?

 
New Post
5/31/2012 2:14 AM
 
I missed the css classes on all divs. How the div's should know the css settings?
 
New Post
5/31/2012 2:50 AM
 

You should uses classes to address your Panes, not id's.
The reason for this is that the id's are being changed by ASP.NET on rendering.

<div id="ContentPane" class="ContentPane" runat="server" />

Will be rendered as

<div id="dnn_ContentPane" class="ContentPane" ></div>

Because in future versions (of asp.net) this could change, it's best to add a unique class to every Pane and address that:

.ContentPane
instead of
#ContentPane or #dnn_ContentPane

BTW, this is due to the way ASP.NET works, not really caused by DNN

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Help Needed in Resolving CSS Layout IssuesHelp Needed in Resolving CSS Layout Issues


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