Hi All,

My DNN installation wont parse the correct Doctype which I have set in my Home.xml file. Is there any reason this would happen?

I worked on another project in DNN 5.6.2 without any problems but this is now causing me some headaches.

Here's a sample of my xml file:

[SkinDocType]
[![CDATA[[!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xht...tional.dtd">]]>
[/SkinDocType]

I have changed all instances of < to [ as they do not render properly in these forums.

Thanks

There's a lot to be said for implementing skins at the ascx level and forgoing the html version. I prefer to build the ascx skins directly. See our "DotNetNuke ASCX Skinning for Professional Skinners" tutorial.

You might find the 40Fingers.net Style Helper Skin Object useful. It simplifies the conditional stuff, and also allows your to use conditions on other browsers.

There's a lot to be said for implementing skins at the ascx level and forgoing the html version. I prefer to build the ascx skins directly. See our "DotNetNuke ASCX Skinning for Professional Skinners" tutorial.

You might find the 40Fingers.net Style Helper Skin Object useful. It simplifies the conditional stuff, and also allows your to use conditions on other browsers.

For your DOCTYPE issue, take a look at this tutorial: Browser Quirks, Standard Compliance modes and Doc Types

Using a DOCTYPE file is the preferred approach. Take a look at the installed Minimal Extropy skin.

Thanks Joseph. Can the tutorials be bought as a once off per tutorial or would I have to by a subscription?

Chat soon...James

Subscription.

Thanks Jo!

Strange thing is that I have installed a clean version of DNN 5.6.2 and have tried parsing the site with the correct DTD xml files and still no joy. Although I understand developing directly on the ASCX pages would be quicker, we still have a team of people working on pages and someone might just make the mistake of parsing the skin. Is there maybe a way to prevent parsing the skin by other users?

"Parsing the skin" is essentially the process of compiling the HTML file into the .ascx file. So, you could simple remove the html files from your skin's folder after you're created the ascx files. Then, there will be nothing to parse.

Thanks Joseph. I noticed that we actually had downloaded the tutorial you mentioned last year and started working through it but there is going to be a slight learning curve which comes with this and although I see the benefits, we're working on a deadline project and need for the skins to parse correctly.

At this stage, when we parse the skin, the correct DTD is not parsing as it should so we sit with the wrong DTD when loading the site in IE.

Is there perhaps something else you could think of that might cause DNN to not parse skins properly? A bug maybe?

Here's the site I refer to. http://bit.ly/q2wwJx. You will see in IE browsers the site is wrong altogether.

Thanks!

Just add a DocType file for each of your skins.

The more recent versions of DotNetNuke also have a "fallback doctype" setting in Host Settings. You might want to set that so that, if your skin doesn't have a proper doctype, DotNetNuke will set it for you.

Yowser! It was exactly that, thanks Joseph!