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, ...Container CSS when using IEContainer CSS when using IE
Previous
 
Next
New Post
3/12/2010 2:19 PM
 

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" >)

 
New Post
3/13/2010 3:33 AM
 

Kim,

Thanks for the screenshots of the container in action. It does look like an issue you can fix by changing the Doctype to XHTML.

Please let us know if this is the case, if not we can explore another avenue.

Regards,

Rick.



PSDtoDNN - You supply the artwork... we'll build the skins!™
Website | Twitter | YouTube | Skype
 
New Post
3/13/2010 8:53 PM
 
Thank you both for your help! I have solved my issue, I tried changing the doctype to the strict one and it did not change the way IE was rendering my containers so I changed it back to the transitional. I went back to my skin.html file and added a second "STYLES" object and turned off "UseSkinPath" and set the path (relative) to where the container's css was and it worked! All is well now :) Here is a final screen shot if anyone is interested. Of course the favicon and logo will change whenever we/they decide on what to use, but for now it is still in development. :) http://screencast.com/t/YTA1MzA3N Thank you again for all your help!
 
New Post
3/14/2010 7:01 AM
 

Kim,

That's no problem, and thanks for posting the solution you found for the issue.

Rick.



PSDtoDNN - You supply the artwork... we'll build the skins!™
Website | Twitter | YouTube | Skype
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Container CSS when using IEContainer CSS when using IE


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