I just used  FF user agent switcher to visit Nina's site and if I "pretend to be the W3C validator", I get the HTML as in my post above. and the errors...

(and fooled myself, forgot to switch back before trying to post, which does not work ;-)

OK - I'm going to drop this build now - and redo - if you give me a few moments - I can see on Jan's site - the page renders differently - which makes me think that with two live instances, there is some issue - i will use another url for now in a new folder - incase there is some IIS caching that I'm not aware of in the IIS instance.. because I can see discrepancies on that site although I have completely deleted and started from new.

Let me do another build quickly - and i will tell you the method I used to create this one - I use the auto install - I modified the install file to put in my smtp settings and user name and such and did the install that way.

I will use the wizard to go through the procedure and see what it produces.

If that fails, then I will look at the patches and updates on our server to see if there is a .net app patch somewhere along the line to have made this render this way.

Nina

thanks Nina - it's 1am here now & I have to go to bed as I've an early start tommorow, so I'm unlikely to get a chance to look at anything for a bit. Tommorow I hope I can locate some hosting space and run through a larger battery of tests.

Judging by the various accounts it's safe to say that dnn 5 will validate based on certain user agents - to me it's most important it validates in IE & firefox, and that we ensure that App_Browsers works correctly to detect the W3C validator and render valid output as many users assume that it's results are definitive and don't understand that the browsing device effects the rendering.

Cathal