Errors found while checking this document as XHTML 1.0 Transitional!
Validation Output: 34 Errors
-
Line 178, Column 6:
document type does not allow element "br" here; assuming missing "li" start-tag
<br /><br /> -
Line 180, Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
-
Line 187, Column 5:
end tag for "li" omitted, but OMITTAG NO was specified
</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 178:
start tag was here
><br /><br /> -
Line 266, Column 263:
document type does not allow element "div" here
…only="readonly"> <div align="center"><a target="_blank" href="http://www.soldThe element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 266, Column 415:
end tag for "img" omitted, but OMITTAG NO was specified
…enentag.png" border="0" alt="GB"></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 266, Column 331:
start tag was here
…/www.soldeye-gfx.de" title="GB Pics"><img src="http://www.soldeye-gfx.de/gbpi -
Line 267, Column 5:
end tag for "br" omitted, but OMITTAG NO was specified
<br><a href="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea><br…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 267:
start tag was here
…<br><a href="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea><br… -
Line 284, Column 263:
document type does not allow element "div" here
…only="readonly"> <div align="center"><a target="_blank" href="http://www.soldThe element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 284, Column 420:
end tag for "img" omitted, but OMITTAG NO was specified
…freunde.gif" border="0" alt="GB"></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 284, Column 331:
start tag was here
…/www.soldeye-gfx.de" title="GB Pics"><img src="http://www.soldeye-gfx.de/gbpi -
Line 285, Column 5:
end tag for "br" omitted, but OMITTAG NO was specified
<br><a href="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea></d…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 285:
start tag was here
…<br><a href="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea></d… -
Line 302, Column 263:
document type does not allow element "div" here
…only="readonly"> <div align="center"><a target="_blank" href="http://www.soldThe element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 302, Column 414:
end tag for "img" omitted, but OMITTAG NO was specified
…umprinz.gif" border="0" alt="GB"></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 302, Column 331:
start tag was here
…/www.soldeye-gfx.de" title="GB Pics"><img src="http://www.soldeye-gfx.de/gbpi -
Line 303, Column 5:
end tag for "br" omitted, but OMITTAG NO was specified
<br><a href="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea><br…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 303:
start tag was here
…<br><a href="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea><br… -
Line 345, Column 83:
document type does not allow element "a" here
…atis.com/45624.html" target="_blank">');The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 355, Column 7:
end tag for "div" omitted, but OMITTAG NO was specified
</body>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
-
Line 26:
start tag was here
><div id="hauptcontainer"> -
Line 266, Column > 80:
XML Parsing Error: Opening and ending tag mismatch: img line 266 and a
…class="textarea_getcode" name="textarea41" cols="30" rows="3" onclick="focus(… -
Line 267, Column 64:
XML Parsing Error: Opening and ending tag mismatch: br line 267 and div
…="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea><br /> -
Line 267, Column 76:
XML Parsing Error: Opening and ending tag mismatch: a line 266 and textarea
….de"><b>GB Pics</b></a></div> </textarea><br /> -
Line 284, Column > 80:
XML Parsing Error: Opening and ending tag mismatch: img line 284 and a
…class="textarea_getcode" name="textarea41" cols="30" rows="3" onclick="focus(… -
Line 285, Column 64:
XML Parsing Error: Opening and ending tag mismatch: br line 285 and div
…="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea></div> -
Line 285, Column 76:
XML Parsing Error: Opening and ending tag mismatch: a line 284 and textarea
….de"><b>GB Pics</b></a></div> </textarea></div> -
Line 302, Column > 80:
XML Parsing Error: Opening and ending tag mismatch: img line 302 and a
…class="textarea_getcode" name="textarea41" cols="30" rows="3" onclick="focus(… -
Line 303, Column 64:
XML Parsing Error: Opening and ending tag mismatch: br line 303 and div
…="http://www.soldeye-gfx.de"><b>GB Pics</b></a></div> </textarea><br /> -
Line 303, Column 76:
XML Parsing Error: Opening and ending tag mismatch: a line 302 and textarea
….de"><b>GB Pics</b></a></div> </textarea><br /> -
Line 312, Column 12:
XML Parsing Error: Opening and ending tag mismatch: textarea line 302 and div
</div></div></div></div></div></div></div> -
Line 312, Column 30:
XML Parsing Error: Opening and ending tag mismatch: textarea line 284 and div
</div></div></div></div></div></div></div> -
Line 355, Column 7:
XML Parsing Error: Opening and ending tag mismatch: textarea line 266 and body
</body> -
Line 356, Column 7:
XML Parsing Error: Opening and ending tag mismatch: div line 266 and html
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag div line 261
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag div line 213
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag div line 210
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag div line 194
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag div line 26
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag body line 22
</html> -
Line 356, Column 7:
XML Parsing Error: Premature end of data in tag html line 2
</html>
![<?=$cfg['site_name']?>](/images/link-commander-logo.gif)
