Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 35, Column 10:
ID "navipad" already defined.<span id="navipad"><a href="/submit.php" title="Submit Listing" rel="nofollow">SAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 34, Column 10:
ID "navipad" first defined here.<span id="navipad"><a href="http://www.lobolinks.com/" title="Web Directory">Web<span id="navipad"><a href="http://www.lobolinks.com/top-hits.html" title="PopulAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 34, Column 10:
ID "navipad" first defined here.<span id="navipad"><a href="http://www.lobolinks.com/" title="Web Directory">Web<span id="navipad"><a href="http://www.lobolinks.com/latest-links.html" title="LAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 34, Column 10:
ID "navipad" first defined here.<span id="navipad"><a href="http://www.lobolinks.com/" title="Web Directory">Web<span id="navipad"><a href="http://www.lobolinks.com/blog/" title="Blog">Blog</aAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 34, Column 10:
ID "navipad" first defined here.<span id="navipad"><a href="http://www.lobolinks.com/" title="Web Directory">Web<span id="navipad"><a href="http://www.lobolinks.com/affiliates/" title="AffiliaAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 34, Column 10:
ID "navipad" first defined here.<span id="navipad"><a href="http://www.lobolinks.com/" title="Web Directory">Web</tr></table>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 68, Column 5:
start tag was here.</td><td width="33%"><img src="/templates/LoboLinks/images/cats/folder.png" widt<div id="sinside">An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 56, Column 9:
ID "sinside" first defined here.<div id="sinside">
Line 79, Column 108:
cannot generate system identifier for general entity "align".…ntent/plugins/tse/js.php?type=banner&align=center&zone=1'></script>An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 79, Column 108:
general entity "align" not defined and no default entity.…ntent/plugins/tse/js.php?type=banner&align=center&zone=1'></script>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 79, Column 113:
reference not terminated by REFC delimiter.…/plugins/tse/js.php?type=banner&align=center&zone=1'></script>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 79, Column 113:
reference to external entity in attribute value.…/plugins/tse/js.php?type=banner&align=center&zone=1'></script>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 79, Column 113:
reference to entity "align" for which no system identifier could be generated.…/plugins/tse/js.php?type=banner&align=center&zone=1'></script>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 79, Column 107:
entity was defined here.…ontent/plugins/tse/js.php?type=banner&align=center&zone=1'></script>…/tse/js.php?type=banner&align=center&zone=1'></script>An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 79, Column 121:
general entity "zone" not defined and no default entity.…/tse/js.php?type=banner&align=center&zone=1'></script>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 79, Column 125:
reference not terminated by REFC delimiter.…/js.php?type=banner&align=center&zone=1'></script>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 79, Column 125:
reference to external entity in attribute value.…/js.php?type=banner&align=center&zone=1'></script>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 79, Column 125:
reference to entity "zone" for which no system identifier could be generated.…/js.php?type=banner&align=center&zone=1'></script>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 79, Column 120:
entity was defined here.…s/tse/js.php?type=banner&align=center&zone=1'></script><div id="sinside">An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 56, Column 9:
ID "sinside" first defined here.<div id="sinside"><div id="sinside">An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 56, Column 9:
ID "sinside" first defined here.<div id="sinside"><div id="sinside">An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 56, Column 9:
ID "sinside" first defined here.<div id="sinside"></div>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 142, Column 5:
start tag was here.</td><td width="80%"><div align="left">We always appreciate more customer feedba</div>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 140, Column 20:
start tag was here.<table width="100%"><tr><td width="30%" align="center"></div>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 140, Column 0:
start tag was here.<table width="100%"><tr><td width="30%" align="center"></td></tr></table>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 144, Column 9:
end tag for element "tr" which is not open.</td></tr></table>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 144, Column 17:
end tag for element "table" which is not open.</td></tr></table>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 147, Column 17:
end tag for element "div" which is not open.</div></div></div></div><div id="bottom"><div id="footerlinks">© Lobo LinksThe Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 147, Column 23:
end tag for element "div" which is not open.</div></div></div></div><div id="bottom"><div id="footerlinks">© Lobo LinksThe Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Support this tool, become a
This is the W3C Markup Validator, v0.8.4.
Copyright © 1994-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.