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, ...DNN 4 skins and content panesDNN 4 skins and content panes
Previous
 
Next
New Post
6/28/2006 4:57 PM
 
 

I may have found the problem, at least this is working for me now. (The skin documentation from the install seemed to help me more than my copy of Professional DotNetNuke ASP.NET Portals on this one.)

In my scenario, I have three content columns: LeftPane, CenterPane, RightPane.  I also had included the skin.xml file with the content panes defined.  After some tweaking (and looking at some more examples), I figured out that my main content pane must be labled "ContentPane" and not CenterPane, since this is what my content in the database was already set to.  Also, in my HTML file, the token for the main pane is [CONTENTPANE], not [CONTENTPANE:1].  Here's what I have:

In my HTML template:

<!--other stuff-->
  <div id="right_pane">[CONTENTPANE:3]</div><!--these are floated by CSS-->
  <div id="left_center_wrap">
    <div id="left_pane">[CONTENTPANE:2]</div>
    <div id="center_pane">[CONTENTPANE]</div>
  </div>
<!--/other stuff-->

In my skin.xml file:

<Objects>
 <Object>
  <Token>[CONTENTPANE]</Token>
  <Settings>
   <Setting>
    <Name>ID</Name>
    <Value>ContentPane</Value>
   </Setting>
  </Settings>
 </Object>
 <Object>
  <Token>[CONTENTPANE:2]</Token>
  <Settings>
   <Setting>
    <Name>ID</Name>
    <Value>LeftPane</Value>
   </Setting>
  </Settings>
 </Object>
 <Object>
  <Token>[CONTENTPANE:3]</Token>
  <Settings>
   <Setting>
    <Name>ID</Name>
    <Value>RightPane</Value>
   </Setting>
  </Settings>
 </Object>
</Objects>

This has eliminated my errors and has reinserted my database content into the correct content panes. My only problem now is getting the <div>content panes</div>s to float correctly.

 
New Post
6/30/2006 8:44 PM
 

Some links on getting 2 and 3 panes to float nicely using CSS, not tables, albeit not DNN specific:

http://css.maxdesign.com.au/floatutorial/ (check out the liquid 2 and 3 column tutorials at the bottom)

http://www.blextar.net/index.php?post=47

http://www.positioniseverything.net/articles/pie-maker/pagemaker_2_9_home.html

 
New Post
7/1/2006 12:17 AM
 

Well there is alot of talk about tableless skinning in DNN - and there even a couple of skins around that boast being tableless, if you of course modifiy with JS, and to make xhtml compliant, modify the core or module files that manage it.

However, in my opinion, and that's all I can give you based on having developed literally thousands of skins files, I'm yet to see a commercial site which behaves perfectly in both user and and admin mode (since you can't deliver to someone a site that looks a complete mess when logged in). And telling clients they can only use a couple of modules if they really want to be compliant doesn't cut it for most of them. EG. to be truly compliant you would also be limited to the modules used in DNN for the time being.

And it's not just DNN - I've spoken with some skilled people who struggle to get client's requirements and completely CSS driven skins. And that's not including the compatiblity issues which occur which require you to spend so many hours in making work, in a fragile method, that I've found it not commercially viable. Having said that - I do know there are very positive steps moving ahead to work with DNN, more compliancy (which is not tableless) and even in the future, better module comlpiancy, and modules that allows you to control the doc header for that skin, so as not to affect the whole portal.

I have been working at a close level with some of the most experienced DNN & CSS people and they too agree that it's just not there at the moment.  In some portals that basically require a simple left and content pane, or similar to wordpress layout with content/right pane structure, it's not as much of a challenge, but for those who have multiple panes required in a fluid site allowing for text and width changing, I think it's a huge job 

I have been asked only once by a client who wanted tableless skinning, and after looking at his project said no, it wasn't possible in the time frame, the budget and the management level with the mutiple custom modules being created for them, that displayed information in a grid format, that had tables in - since that's what the grid control being used provided as an output - thereofore totally a waste of time in the whole scheme of things- why develope a skin that has no tables to carry information that is rendered in tables.

But due to his concerns, I did make quite an effort to reduce the amount of tables in the design, and the closest we got was to create a single 2 pane skin, with the div tags holding the multiple panes in the left, and div tags for the content and right panes..

Was it perfect? In a tableless world - NO, but did it get the result - YES, the compromise was - consideration to client's needs, constantly researching to see new changes and tweaking further for new projects and a deliverable result.  They tried for 4 months before contact me - with *experts* and were unsuccessful.  And I didn't want to go down that track, so the advice I offered helped the job come to a close - and in the end in a business world, that's what we has to be done.  They were extremely happy with the results but I suppose the mistake was initially -those who briefed them in the project were not aware on the challenges and just assumed it was possible.

Having said all this - it's of great interest to me and I'm looking forward to seeing the results that come through because eventually it will all happen.

I'm just a sceptical person these days - reading lots of *how to's* without any real world experience frustrates me sometimes when there is no backing behind the information and we're finding some misinformation and confusion for newcomers coming in thinking they can achieve their perfect DNN site without even understanding DNN in the first place and then complaining about it.  Maybe some of these designers should wear different shoes!! - The bill paying ones.

Man I hope I don't sound too hard.. that's not my intentions  - it's just very disappointing that people give up on DNN because it's got tables..  when I wish more time was spent discovering what a fantastic product this is, in spite of having to use tables.   If you've got the time though - then please do continue.

I know the core team is working on these areas and you will see in the future great improvements to DNN in the compliancy side of it.

And I might even cop a grilling by some on this area, but this is just my thoughts and I believe that since I'm walking the talk, (limping at times too) delivering sites to clients on a commercial basis, I think I'm not alone with other people who have to work on very complex client requirements. 

Just my 2 cents.. OK OK 10 cents..  in an area that is very dear to my heart and if I can share just a fraction of my experiences to help you save time and hopefully continue being inspired by DNN, then I guess I've done my job.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
7/1/2006 12:20 AM
 

Oh and I did get sidetracked didn't I - what I also meant to say is that I've tested all my skins on DNN 4 without any problems and currently working with the new solpart menu which does allow for horizontal menus - tableless deployment.  Now isn't that a great benefit!

I'm working on it this weekend and it will be part of a free skin I will be offering so you can learn how the new menu with DNN works.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
7/5/2006 4:21 PM
 
Thanks Nina. I guess I don't feel so bad putting in most of a week trying to get CSS to work and getting most of the way there - but with a solution that did indeed break when various modules were introduced...
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN 4 skins and content panesDNN 4 skins and content panes


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