Forums

[resolved] XHTML W3 Validator (4 posts)

  1. petekkia
    Member
    Posted 2 years ago #

    Hi there,
    in recent weeks I'm trying to make compatible my blog with W3 XHTML validator. It started reporting 89 errors, and change after change, I decreased them to 4 and 1 warning. But now I really don't now what to do, because i don't understand where i must look for them, either plugins or WP code or articles' html.

    Now the errors are:

    The website is http://www.leoclubrc.it (the source code is still the one not validatable).

    #  Error  Line 615, Column 26: end tag for "body" omitted, but OMITTAG NO was specified
    
    <!-- End Shadowbox JS …
    
    ✉
    
    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    # Info Line 50: start tag was here
    
    ><body>
    
    # Error Line 615, Column 26: end tag for "html" omitted, but OMITTAG NO was specified
    
    <!-- End Shadowbox JS …
    
    ✉
    
    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    # Info Line 2: start tag was here
    
    ><html xmlns="http://www.w3.org/1999/xhtml">
    
    # Error Line 615, Column 25: XML Parsing Error: Premature end of data in tag body line 50
    
    <!-- End Shadowbox JS -->
    
    ✉
    # Error Line 615, Column 25: XML Parsing Error: Premature end of data in tag html line 2
    
    <!-- End Shadowbox JS -->

    Can someone tell me where and what have I to change?
    Thanks!
    Fabrizio.

  2. @mercime
    Member
    Posted 2 years ago #

    open up your theme's footer.php and add the following at the very end of the footer.php

    </body>
    </html>
  3. petekkia
    Member
    Posted 2 years ago #

    Wow, thanks! It worked...
    Can I ask you another question? There's a warning which says:

    Warning Byte-Order Mark found in UTF-8 File.
    
          The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause problems for some text editors and older browsers. You may want to consider avoiding its use until it is better supported.

    Do you also know how to fix it?
    Thanks again!

  4. @mercime
    Member
    Posted 2 years ago #

    A fix found via Google .. basically use a plain text editor

Topic Closed

This topic has been closed to new replies.

About this Topic