Our webdesigner has been having a nightmare trying to make an XHTML strict skin for DNN - seems that the viewstate gets moved and placed outside of any div or fieldset tags. The solution we came up with was to get the source and alter the PageBase.vb file like this:


        ' This method overrides the Render() method for the page and moves the ViewState
        ' from its default location at the top of the page to the bottom of the page. This
        ' results in better search engine spidering.
        Protected Overrides Sub Render(ByVal writer As System.Web.UI.HtmlTextWriter)

            Dim stringWriter As System.IO.StringWriter = New System.IO.StringWriter
            Dim htmlWriter As HtmlTextWriter = New HtmlTextWriter(stringWriter)

            'Localize controls
            Trace.Write("LocalizedPage::PreRender", String.Format("Performing substitutions for {0}", Thread.CurrentThread.CurrentUICulture.Name))
            IterateControls(Controls, _localizedControls, LocalResourceFile)
            Trace.Write("LocalizedPage::Render", "Removing resourcekey attribute from controls")
            RemoveKeyAttribute(_localizedControls)

            MyBase.Render(htmlWriter)

            Dim html As String = stringWriter.ToString()
            Dim StartPoint As Integer = html.IndexOf("<input type=""hidden"" name=""__VIEWSTATE""")
            If StartPoint >= 0 Then    'does __VIEWSTATE exist?
                Dim EndPoint As Integer = html.IndexOf("/>", StartPoint) + 2
                Dim ViewStateInput As String = html.Substring(StartPoint, EndPoint - StartPoint)
                html = html.Remove(StartPoint, EndPoint - StartPoint)
                Dim FormEndStart As Integer = html.IndexOf("</form>")
                If FormEndStart >= 0 Then
                    html = html.Insert(FormEndStart, "<fieldset class=""viewstate"">" + ViewStateInput + "</fieldset>")
                End If
            End If
            writer.Write(html)

        End Sub

Any chance of getting this extremely simple change put into the full version? It would save the hassle of having to change the source every time we need to do an accessible and fully compliant deployment.

Speaking of XHTML Strict, how is the core Default.aspx page being addressed? It has a lot of uppercase tags, unquoted attribitutes etc. and considering it is the main page it would drastically reduce the number of XHMLT errors if some time was spent on it. I started doing my own but then realised I would have to maintain it each time a new version came out. I could help out if required?

---

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players