Hello,

Great articles.. I tried getting into Issue 25, but had to backtrack as I've been out of the DNN scene for quite a while. I backtracked to Issue 19 ( than went back to issue 7 to install the HouseMenu), and than went to Issue 20 to fix the XHTML issue (still in 4.6.2)..

By than, everything should be fine.. But I keep on getting one error on the Simple Red Leaf Skin.

The Markup Validation Service from W3C give me the following:

Line 33, Column 160: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.

…-->

do you have a live url we can look at, it could be a number of things. - What content have you added to the page?

Hello Lee,

Thanks for getting back to me. I managed to figure things out with that one, but upon a new install and a more deeper look into the Issue 20 problems, in DNN 4.6.2., I am getting the following error:

Line 79, Column 91: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.

…ary="SignIn Design Table" width="160">

Any ideas? I noticed in the Login.acsx (I suppose the new substitution for Signin.acsx from previous versions) there were some references to the "Design Table", but the widths did not match, so I left it at that.

This error is caused because a table is placed within a span tag (shoul be a div). I'm trying to find the file that causes this. I'l let you know if i find it.

Dirk

Got it! it's a forgotten property in the source code in login.ascx.vb:

  Private Sub DisplayLoginControl(ByVal authLoginControl As AuthenticationLoginBase, ByVal addHeader As Boolean, ByVal addFooter As Boolean)
            'Create a

Thanks for the info, I will give that a go.

I've just been experimenting with version 4.6 .2 and it's good that the default.aspx file now only needs a meta-tag adding to the file in order for it to be compliant. - I have been chatting with Cathal Connolly and hopefully the needed meta-tag should be added into the next version, so in future no changes should need to be made to the default.aspx file.

I've been digging some more: in the login module (with OpenID and/or LiveID enabled) lots of new xhtml incompatibilities have been introduced :-(

f.e. illegal attributes like csssel, csshover for the tabcontrol etc. But...i'm going to make this version xhtml complient!

Interesting, keep us informed and if you find solutions we can document it and put it together as a tutorial, cheers,