I have completed a skin sing this techniques from Issue 25 and started on making sure that it is css and xhtml compliant. I am using DNN 4.5.3 rather than DNN 4.4.0 as you used.

 

I applied the changes to Default.aspx and other DNngiblets outlined in your two issues covering that. As a check I went back to you DNN_layouts 2pane_main skin and still have 36 errors. Most the errors have to do with the Solpart menu bits being included and the poor html used to call them {upper case no ending /’s etc} Red highlights some the errors.

 

<SCRIPT SRC="/ASI3/controls/SolpartMenu/spmenu.js"></script></script>ID="dnn_dnnMENU_ctldnnMENU_divOuterTables">

 …pan id="dnn_dnnMENU_ctldnnMENU" name="dnn$dnnMENU$ctldnnMENU" BackColor="#333

 IconBackgroundColor="#333333" HlColor="#FF8080" ShColor="#40

The aspx from your sink on DNN 4.5.3 DOES include a call to the

Solpart bits when DNN converts HTML to aspx.

<%</span><span style="color: blue;">@</span><span style=""> <span style="color: rgb(163, 21, 21);">Register</span> <span style="color: red;">TagPrefix</span><span style="color: blue;">="dnn"</span> <span style="color: red;">TagName</span><span style="color: blue;">="MENU"</span> <span style="color: red;">Src</span><span style="color: blue;">="~/Admin/Skins/SolPartMenu.ascx"</span> <span style="background: yellow none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">%>

However, deleting it doesn’t seem to help. Any idea on where to goto next in 
figuring our how the solpart bits are getting included?

In my case I always only do the aspx and have no HTML files at all.

I also have located an error in the html generated by the Snapsis 3.0 silver 
tab hover menu that I use where the W3C validator caught a couple extra 
ending ’s generated by it when that page had children.

Also I have grave dificulties in getting the IE type sizes correct because 
the changes in the iehacks.css file didn’t work at all. After some digging 
I realized that Lee has his FCKeditor set up to use 
 aroung t
ext or 
’s for newlines.  I have mine set up for 
 
 around 
paragraphs.  IE would only be happy with the font-soze CSS if I included 
it in the p{font-size: x-small;} rather than then 
body p{font-size: x-small;}.  
That took a few hours before I thought of it and tried it! 

Regards,

Dave Snow 

Just for the heck of it, I upgraded to DNN 4.7.0 to see what happened and to start evaluating if I can upgraded to 4.7.* or have they broke anything that I depend on.

Needless to say I expected to have to re-apply the fixes to Default.aspx and friends. To my surprise it appear rhat Deafult.aspx may have all of thefixes it it.  However, the Solpart bits are still there as well.

/Dave

Hello,

You will find that as each new release of DotNetNuke happens you will have to do less code changes to make DotNetNuke compliant. - in 4.7 you only need to add one line of code to the default .aspx file, which is:

< meta http-equiv="Content-Type" content="text/html;charset=utf-8" / >

(without the spaces around the tags)

To completely remove the Solpart menu from being called you also need to remove it from your containers and use the drop down actions. -   Make sure that when you test for validation in a localhost installation that you log out, otherwise it will be validating all of the extra admin sections which will have invalid code.

I was using the dropdown actions. What does "remove it from your containers" really mean?
Do the actionbuttons somehow use the SolPart bits?

I am still seeing

SCRIPT SRC=......


and its follwing 6 errors even when the page has no container and no Snapsis 
menu on it. Any suggestions here? 
I have tried searching the DNNbits for the source of this code, but Vista's search 
stinks!

On a seperate note is the extra spaces between the lt gt and / how you get the 
html into this editor?

/DaveS

Hello,

To remove the Solpart menu, all I have done is use a different menu and use a drop down actions for the containers.

Check the source code of:  http://skintemplates.dnncreative.com
(running version 4.5.3)

- to post code either add spaces in or do a find and replace on the code before posting it in: - Find < and > and replace with [ and ]

If you are getting validation errors, try adding just a text HTML module to the page which uses a transparent container. -  validation errors occur if you select not to display a container on a module.