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 440 new skindoctype in default.aspx - how does it work?dnn 440 new skindoctype in default.aspx - how does it work?
Previous
 
Next
New Post
12/28/2006 3:49 PM
 

Hello

If a folder contained several skins, each requiring the same Doctype. Then, would a single universal named: skin.docktype.xml file meet the requirements of each skin/page within the folder? Or must each page within the folder require it's own SkinName.docktype.xml? 


www.seemalta.net
 
New Post
12/28/2006 7:20 PM
 

Hello

I can now answer my own question. However, the answer I have found does not seem quite right.

I have a skin folder which contains 10 myskinpage.ascx  pages, the skins have no tables and are css based therefore I needed a xhtml DocType.

I tried just using 1 myfoldername.docktype.xml file but it didn't work. I found I needed to create 10 individual MySkinName.docktype.xml files within the one folder to make the xhtml  docktype work in my skin.

I am sure somebody will enlighten me to a more efficient method of doing this as the above seems a tad excessive, or maybe I have misunderstood something.

Lynn


www.seemalta.net
 
New Post
12/29/2006 7:44 PM
 

You know what - I've been playing around with this now - and I had problems with the doctype being rendered using xml - I think that is because the skin file is called skin.html and skin.ascx - now that I think about it.. but I just dropped this -

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

into the html file - and when it rendered it was in the ascx file - much more simple, no extra xml file to have in there. 

We're doing a run of css skins for the http://www.skincovered.com January Goodie bag.. and incorporating different menus we're trying out as well as a new menu John is doing, and you know what - it's a simple solution.. And what I like about this more is that I can have a mix of skins sitting in the folder. EG - If I do a suite of skins, some may be more difficult and require tables or using the default settings.  And also - it's nice to work with if you're using something like expression studio which allows you to work in quirks mode - and see, before you upload, how it should look.

More than that - I thought that it would let me put in a custom docheader for any file I have in there, without having to have lots of skin folders which I hate.  You don't have to create any Lynn, just drop the code into the html file and it works..  Nice and neat and tidy!! 

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
12/29/2006 8:27 PM
 

OK I have to retract that Lynn sorry - I thought it was simple but it appears it doesn't actually parse it - it's just looking at the skin folder.

So if you put into the ascx or html file like I cleverly did -   - following every other way I've worked with DNN - it won't work, it puts 2 docheaders in the default.aspx file. When I initially checked the source file of the skin - I had a bit of scroll happening, so didn't pick up 2 in the first place, but I just looked and there are two - which is not a suitable option.

Sorry for the bum steer - but I'm talking to John about it at the moment - so for now - you're going to have to have lots of xml files in your skin folder. As soon as I know more I'll post here.

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
12/29/2006 8:44 PM
 
cathal wrote

I blogged the details @ http://www.dotnetnuke.com/Community/BlogsDotNetNuke/tabid/825/EntryID/1226/Default.aspx , sorry for the delay (xmas turkey induced coma :) ). I'll update the skinning documentation when I get a chance. Ill also blog a little about the reasons for the current implementation and some other bits and pieces tommorow (i've received half a dozen emails  already so I'll aggregate my answers into a blog post)

I originally found a note on the Microsoft site advising against using an explicit DOCTYPE declarations in the ascx file itself (as an ascx is a page fragment it can cause a failure to load). As John notes, as doctype is now controlled by a server tag, you can of course update the reference via the ascx i.e. skindoctype.text="....", which is safer as the page event model will handle any multiple declarations.

Cathal

Hi  Nina

Thanks for the info.

 I no longer do skins in html but ascx, which  has so far taken me ages to attain.

Therefore in order to efficently use Doctype I must  now create html skins, or am I mistaken?

Regards

Lynn

 

 


www.seemalta.net
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...dnn 440 new skindoctype in default.aspx - how does it work?dnn 440 new skindoctype in default.aspx - how does it work?


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