Hello,

I was wondering if there were any additional steps needed to get DNN 4.8.0 working with XHTML compliance? I remember having to backtrack to past issues to get everything running, but it gets confusing with the constant revisions of DNN, so I was wondering if there has been any progress within the core that has actually helped relieve some of these steps to attain XHTML compliance?

If not, could anybody remember or drop a little primer as to which issues would still be relevant for 4.8.0?

I don't know which version or tutorial you were previously at but having successfully got transitional compliance following lee's issue 27 against DNN 4.7.0 and then upgrading to DNN 4.8.0, I needed the following additional fixes to regain compliance:

default.aspx
* Add utf-8 meta tag
* Remove autocomplete="off" attribute from form

Portals\_default\default.css
* change Body selector to body
* 650 Change to height: 16px;
* 946 delete display: -moz-inline-box; rule

The DNN developers are definitely not on the side of W3C compliance. Instead of fixing issues that Lee and others have identified (Some have been fixed to be fair), we are seeing more errors introduced. Someone needs to educate them!

I will now settle down to issue 28 and report back if I find any issues.

I have not yet had a chance to test 4.8 for compliance, so if you find any additional errors let me know. I will probably revisit the compliance tutorials in another dnn release or two, as they seem to be releasing new versions quickly at the moment.

Hi Lee and everyone else,

I've tried upgrading my XHTML compliant DNN 4.5 site to 4.8

I use hidden containers on home page so I had to change span to div 

again in NoContainer.ascx

autocomplete="off" was there too as mentioned above.

After all that I have 16 more errors from the Account Login module that I need on my home page. One of them for tabindex="-1" and rest for XML Parsing Errors for invalid characters or No SGML character numbers 17 and 18.

I will investigate further and come back if i find something. If anyone else does please post it.

Regards
Arif Shah

I did xhtml compliance on DNN 4.8.0 at www.AgingSafely.com for most of the pages. I had to do the default default.aspx and NoContainer.aspx changes. The skin and containers has been compliant in DNN 4.5.3.

There were modules that weren't compliant and I was able to fix some of them using PageBlaster's regex replacement rules. Others we so bad that I didn't even want to try.

This month Lee posted a multimedia interview with me that is way too long. However if you can sit thru it, I do cover how I did it. The PageBlaster rules I used are posted in PageBlaster's forum.

You are right about the DotNetNuke team fighting against those of us who what xhtml and css compliant skins. The nicest thing about making the skin and modules compliant was that I could now find the html bugs in the pages that I had created. It is amazing how IE and FF don't care about missing trailing tr's, td, & div some of the time. I was now able to find these and other potiential problems before they because an issue.

/DaveS