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, ...Nav displays incorrectly in Mozilla firefoxNav displays incorrectly in Mozilla firefox
Previous
 
Next
New Post
9/2/2010 5:51 PM
 
Yehuda Tiram


Joined: 12/3/2004
Posts: 362
A quick question, do you use skinName.doctype.xml along with the skin files? (In same skin folder)
Yehuda Tiram
AtarimTR
AtarimTR
972-2-5700114   |   972-54-4525492   |    http://www.atarimtr.co.il
 
New Post
9/3/2010 4:52 AM
 
Timo Breumelhof


Timo Breumelhof's Avatar

www.40fingers.net
Joined: 2/9/2006
Posts: 4430
95% of these kind of cross browser issues are caused by:

1. Not using an XHTML doctype
2. HTML errors

So first switch to XHTML (take a look at the xml file mentioned before that comes with the DNN default skin)
and then use a validator to get rid of the HTML errors.
 
New Post
9/3/2010 9:38 AM
 
karen

Joined: 2/9/2010
Posts: 12
Thanks. You've both given me a direction to run. I've been reading all the tutorials about skin development that I can lay my hands on, as well as using a book called "Beginning Dotnetnuke 4.0 Web site creation.." and I haven't seen a reference to a "skinName.doctype.xml. And the one search I did this morning after getting your emails said that the skin.doctype.xml was referenced in the default.aspx page?!?! Looks like I have a lot more reading to do about XHTML doctype and the relationship it has with skins. If either of you know of any books, links, references that might help me in building knowledge about the doctype and skins, I would appreciate it. As I said, I'm really a newby on DNN and its framework and really haven't worked much with XML or XHTML documents either - have more web development experience with Cold Fusion. I'm off now to do research on this and the use of a "validator to get rid of HTML error (I think I read I can do this is VS2008..). Thanks again for your responses.
 
New Post
9/3/2010 10:59 AM
 
karen

Joined: 2/9/2010
Posts: 12
In doing research on the doctype, I have found that the skin files that I copied and updated were from DNN for version 4.8.04. This is the version that was delivered to us from our software developer and it does not have a skin.doctype.xml associated in the skin folders - so no, I don't have a doctype reference for my skins - nor could I find a reference in any of the .htm or aspx files that I looked through. I did download the DNN 5.4.02 version to use "as my development" website and it does have a skin.doctype.xml associated with it when I look in it's skin folder. So, my question now is: Can I associate the skin.doctype.xml with this old version of DNN or do I have to go remove or update a reference in a different place in one of the folders for my old version? I found timo's thread regarding doctype (http://local.dotnetnuke.com/Community/Forums/tabid/795/forumid/109/postid/367577/scope/posts/Default.aspx) and was going to try and follow this, but will it work on the older version of DNN and do I have to alter some other page because it's such an old version? I figure in the mean time I'll try it and see what happens. Thanks for any information you can provide. Karen
 
New Post
9/3/2010 11:04 AM
 
Timo Breumelhof


Timo Breumelhof's Avatar

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

Skin Doctype

If you create a skin, the skin parser (which converts an HTML skin file to the actual skin usercontrol) only uses the HTML pages content between the body tags.

Anything outside the body tags is ignored.

This means the doctype of an HTML skin is not used by DotNetNuke.

This could lead to rendering difference if you use an XHTML doctype in your HTML skin, since DotNetNuke use a HTML 4 transitional doctype by default (to support legacy skins).

There are 2 ways to force DotNetNuke to use an XHTML doctype:

A. You can set the doctype for a specific skin by including a doctype.xml file.

The name of this file should be: "skinname".doctype.xml.

So of every HTML / ASCX file you will have to add an XML file.

The content of this file should be:

<SkinDocType>

            <![CDATA[<!DOCTYPE>]]>

</SkinDocType>

The <!DOCTYPE> part should be replaced with the HTML doctype.

XHTML 1.0 Transitional

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

XHTML 1.0 Strict

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

B. You can set the Fallback doctype from the host settings.

Choose Host > Host Settings and select the doctype under “Fallback Skin doctype”.

This will force all skins on all portals without a doctype.xml file to use the doctype you set.

Please beware that this could potentially lead to unwanted effects if there are non XHTML skins in other portals then the one you are targeting.

Xml Namespace for XHTML skins

If you use an XHTML doctype, the Xml Namespace will be added automatically to the HTML element by the Framework. (Result: <html xmlns="http://www.w3.org/1999/xhtml" >)
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Nav displays incorrectly in Mozilla firefoxNav displays incorrectly in Mozilla firefox


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