| KissOfDeath |
02-24-2010 12:12 PM |
this mod gives me a whole heap of html invalidation errors...
Code:
# Warning Line 62, Column 64: cannot generate system identifier for general entity "langid"
…="text/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_man
✉
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.
# Error Line 62, Column 64: general entity "langid" not defined and no default entity
…="text/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_man
✉
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.
# Warning Line 62, Column 70: reference not terminated by REFC delimiter
…/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.c
✉
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.
# Warning Line 62, Column 70: reference to external entity in attribute value
…/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.c
✉
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 '&'.
# Error Line 62, Column 70: reference to entity "langid" for which no system identifier could be generated
…/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.c
✉
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.
# Info Line 62, Column 62: entity was defined here
…pe="text/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_m
# Warning Line 62, Column 73: cannot generate system identifier for general entity "d"
…s" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"
✉
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.
# Error Line 62, Column 73: general entity "d" not defined and no default entity
…s" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"
✉
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.
# Warning Line 62, Column 74: reference not terminated by REFC delimiter
…" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"…
✉
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.
# Warning Line 62, Column 74: reference to external entity in attribute value
…" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"…
✉
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 '&'.
# Error Line 62, Column 74: reference to entity "d" for which no system identifier could be generated
…" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"…
✉
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.
# Info Line 62, Column 71: entity was defined here
…css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.cs
# Warning Line 62, Column 76: cannot generate system identifier for general entity "sheet"
…href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css" />
✉
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.
# Error Line 62, Column 76: general entity "sheet" not defined and no default entity
…href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css" />
✉
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.
# Warning Line 62, Column 81: reference not terminated by REFC delimiter
…"css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css" />
✉
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.
# Warning Line 62, Column 81: reference to external entity in attribute value
…"css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css" />
✉
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 '&'.
# Error Line 62, Column 81: reference to entity "sheet" for which no system identifier could be generated
…"css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css" />
✉
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.
# Info Line 62, Column 74: entity was defined here
…" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"…
# Error Line 111, Column 91: document type does not allow element "link" here
…tp://devils-shadow.com/favicon.ico"/>
✉
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).
# Error Line 224, Column 92: document type does not allow element "script" here; assuming missing "li" start-tag
…umn1"><script type="text/javascript">
✉
# Warning Line 259, Column 129: character "&" is the first character of a delimiter but occurred as data
…pgrades.html">Hardware Modification & Upgrades</a>
✉
This message may appear in several cases:
* You tried to include the "<" character in your page: you should escape it as "<"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.
# Warning Line 292, Column 195: character "&" is the first character of a delimiter but occurred as data
…Lost In Nightmares Released For PS3 & Xbox 360</a></h4>
✉
This message may appear in several cases:
* You tried to include the "<" character in your page: you should escape it as "<"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.
# Error Line 402, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
</div> </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 ">".
# Info Line 224, Column 61: start tag was here
… <ul class="list_no_decoration" id="widgetlist_column1"><script type="text/javascript">
# Error Line 407, Column 20: document type does not allow element "div" here; assuming missing "li" start-tag
<div class="title">
✉
# Error Line 1062, Column 6: 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 ">".
# Info Line 407, Column 1: start tag was here
<div class="title">
# Error Line 1068, Column 82: document type does not allow element "div" here; assuming missing "li" start-tag
…ist_column3"><div class="cms_widget">
✉
# Error Line 1247, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
</div> </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 ">".
# Info Line 1068, Column 58: start tag was here
<ul class="list_no_decoration" id="widgetlist_column3"><div class="cms_widget">
# Error Line 1313, Column 4: document type does not allow element "tr" here; assuming missing "table" start-tag
<tr><td><script type="text/javascript">
✉
# Error Line 1320, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
</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 ">".
# Info Line 1313: start tag was here
><tr><td><script type="text/javascript">
# Error Line 62, Column 69: XML Parsing Error: EntityRef: expecting ';'
…t/css" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.
✉
# Error Line 62, Column 73: XML Parsing Error: EntityRef: expecting ';'
…s" href="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css"
✉
# Error Line 62, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…="css.php?styleid=6&langid=1&d=&sheet=forumhome_sub_forum_manager.css" />…
|
More Information