I just upgraded my web site www.AgingSafely.com from DNN 4.5.3 to 4.8.0 and noticed some important differences.

• My site also has several sub portals (parent portals). Each had a photo on the home page that was actually located in portal 0. The path was /Portals/0/Photos/HousePhoto.jpg.  When I went to test everything online these photos were missing, but didn't show a broken link. When I went into FCKeditor to fix them they showed up in the editor. My ultimate fix was to upload a copy of the photo in the  parent portal. But want is important is that FCKedit and the HTML page appear to have different permissions or file paths.  One of them must be wrong!
• My skin and containers are xhtml compliant. Of the 40 pages on the primary site all but three validated with DNN 4.5.3 without any "magic". After upgrading to DNN 4.8.0 and fixing the xhtml issues in the DNN 4.8.0 Default.aspx, NoContainer.aspx and the non-compliant css code in Default.css 100% of my pages were still non-compliate. Somewhere between DNN 4.5.3 and DNN 4.8.0 someone stuck a autocomplete="off" in the search box "input tag" that broke every page with an invalid argument.

It would be good if the release testing for DNN included some css and xhtml testing. I don't expect them to fix all of the bad html code in one release but it would be nice if we could stop taking steps backwards. If each new module release could attack the xhtml issues we would have those fixed in a year.

Testing for compliance find xhtml bugs in the pages that I develop, but if the DNN framework has constantly bad html code then I can't use tools like the W3C validator to test and fix my own code.  The original exercise of making site xhtml compliant found many flaws in my html code. Now that they are fixed be behaves much more uniformally accross browsers.

Regards,

I ASSUME that the FCKeditor is using the same link and the Text/Html module. One can see it and the other can't.