I get exactly the same thing as Cathal and I'm not trying to be smug here either, just reporting the facts as I see it like Cathal, I'm not perfect I just do what I do.

I saved the home page of the default html page (with all the default text and all) using IE7 and uploaded it as a text file to the W3C validator, it worked fine for xhtml transitional.

Thoughts:

1) Nina's page is not vanilla, she is not using the default home supplied with DNN. So I would recommend testing with the default home page to start off with.

2) I think (check this could be wrong) I got different results saving Nina's page as a text file and uploading it which is odd. Mind you the point is moot, I still got errors.

3) It could be something to do with changes made to the text within the text/html module, some bug with DNN adding extra pages (Nav menu), or maybe the expand collapse visibility of modules could be something to do with it (it was a known bug that was apparently fixed).

4) We are certain this is not RC1 or RC2 n'est pas?

So whilst the default home page and text definately complies (at least locally, needs to be tested remotely right now) there could be something along the way that breaks it. Perhaps you could test with the default home page text Nina (just one page) and then see if you are able to break xhtml compliance by changing the pages slightly (expand/collapse sections, adding extra pages?) This will help us get to the bottom of this.

Thanks

Skins can be delivered as single zipped files with the skin files in them and the name of the skin - eg.. myfilename.zip used and uploaded as just a skin on it's own.

Containers can be delivered in the same way.

If this method was being used - I'd select the 'upload skins' option and upload the myfilename.zip file and then click the 'upload containers' and use the same method and upload the container files called 'myfilename.zip' as well. That's a two step procedure.

But, until now, you could create a skin package - that is - combine the skins and containers together and upload them in a single instance and it would then be one step procedure.

Packaging them was a little more work - eg.. you worked on your local machine and have containers/myfilename/container.ascx file ... and you would have skins/myfilename/skinname.ascx -  - you would zip the skin file up in a zipped file called.. skins.zip and you would, in the container folder, zip up the files and call  container.zip  - you would then copy the container.zip file and paste into the same folder where the skin.zip file was...  

That would give you two zipped files - one called skins.zip and one called containers.zip together and you'd right click in that folder where they are and zip the two zips to gether... and give that the myfilename.zip name.. which would be your skin package..

Also in that skin package - you could put an 'about.htm' file in there which give you information abou the skin, the author etc..  That was commonly known as a skin package and many skins on snowcovered are presented that way. 

But now, what happens that if you have a skin package - and you unzip that package - and you don't rename the skin.zip to the 'skinpackage'  name- it uploads to skins/skins/  - each and every skin you have will go to the same folder.

The same thing occurs with containers..

I know it has to be changed, but all the skins i have on my free skinning site now need to be repackaged completely to work in dnn 5.  This will take some time but it has to be done or we'll have lots of people unable to use the free skins I have.

Now, if the developers did what they say they do - that is allow for legacy skins, backward compatiblity it would buy time for those who provide skins for the community either free or commerical.

I vote we bring back 'legacy skin' support.  If you parse these skins - eg.. use the uploader, you'll find that now the 'about' skin will appear but will break the page becuase it has no 'tokens' in it. Before DNN knew that there was an about.htm skin and it remained that way - but now - that's all gone as well.

That's what I mean about impact on skinning...

Nina Meiers

http://www.dnnbeta.com/Home/tabid/92/Default.aspx

OK I have done this now - but it's not looking pretty -

It is using the index skin - and it still doesn't validate

I can also confirm i don't get the host/settings page -there is an error there.

Nina