Check the markup (HTML, XHTML, …) of Web documents
Jump To: Validation Output
Errors found while checking this document as XHTML 1.0 Transitional!
Result: 23 Errors, 10 warning(s)
Address:
Encoding: windows-1256 (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-
macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
Doctype: XHTML 1.0 Transitional (detect automatically) HTML5 (experimental) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
OptionsShow Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML Tidy
Help on the options is available.
↑ Top
Validation Output: 23 Errors
Line 1, Column 985: reference not terminated by REFC delimiter.
…net/admin/index.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48✉
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 1, Column 992: cannot generate system identifier for general entity "mode".
…in/index.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708f✉
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 1, Column 992: general entity "mode" not defined and no default entity.
…in/index.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708f✉
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 1, Column 996: reference not terminated by REFC delimiter.
…ndex.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c6✉
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 1, Column 996: reference to external entity in attribute value.
…ndex.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c6✉
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 1, Column 996: reference to entity "mode" for which no system identifier could be generated.
…ndex.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c6✉
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 1, Column 991: entity was defined here.
…min/index.forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708 Line 1, Column 1002: cannot generate system identifier for general entity "extended_admin".
…orum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa902✉
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 1, Column 1002: general entity "extended_admin" not defined and no default entity.
…orum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa902✉
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 1, Column 1016: reference not terminated by REFC delimiter.
…es&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245"✉
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 1, Column 1016: reference to external entity in attribute value.
…es&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245"✉
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 1, Column 1016: reference to entity "extended_admin" for which no system identifier could be generated.
…es&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245"✉
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 1, Column 1001: entity was defined here.
…forum?part=themes&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa90 Line 1, Column 1019: cannot generate system identifier for general entity "sid".
…sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245" re✉
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 1, Column 1019: general entity "sid" not defined and no default entity.
…sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245" re✉
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 1, Column 1022: reference not terminated by REFC delimiter.
…=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245" rel="✉
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 1, Column 1022: reference to external entity in attribute value.
…=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245" rel="✉
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 1, Column 1022: reference to entity "sid" for which no system identifier could be generated.
…=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245" rel="✉
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 1, Column 1018: entity was defined here.
…&sub=index&mode=tags&extended_admin=1&sid=48fd7708fd6c66fa9024fadad27b0245" r Line 88, Column 1995: ID "add-google" already defined.
…th="100%"></td></tr></table><div id="add-google" style="display:display:block✉
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 4, Column 1617: ID "add-google" first defined here.
…d valign="top" width="100%"><div id="add-google" style="display:display:block Line 88, Column 2524: document type does not allow element "td" here.
…3px"></div><td valign="top" width="0"><div id="emptyidright"></div></td></tr>✉
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 88, Column 2563: end tag for "td" omitted, but OMITTAG NO was specified.
…div id="emptyidright"></div></td></tr></tbody></table></div></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 4, Column 1578: start tag was here.
…"0"><div id="emptyidleft"></div></td><td valign="top" width="100%"><div id="a Line 1, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"…✉
Line 1, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"…✉
Line 1, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"…✉
Line 1, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"…✉
Line 88, Column > 80: XML Parsing Error: Opening and ending tag mismatch: td line 4 and tr.
…s_scroll_container', 'up', '2', '90', '300', 'genmed');//]]></script><table w…✉
Line 88, Column > 80: XML Parsing Error: Opening and ending tag mismatch: tr line 4 and tbody.
…s_scroll_container', 'up', '2', '90', '300', 'genmed');//]]></script><table w…✉
Line 88, Column > 80: XML Parsing Error: Opening and ending tag mismatch: tbody line 4 and table.
…s_scroll_container', 'up', '2', '90', '300', 'genmed');//]]></script><table w…✉
Line 88, Column > 80: XML Parsing Error: Opening and ending tag mismatch: table line 4 and div.
…s_scroll_container', 'up', '2', '90', '300', 'genmed');//]]></script><table w…✉
Line 89, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 4 and td.
…footer"><div align="center"><div class="gen"><strong></strong><span class="ge…✉
Line 89, Column > 80: XML Parsing Error: Opening and ending tag mismatch: td line 2 and tr.
…footer"><div align="center"><div class="gen"><strong></strong><span class="ge…✉
Line 89, Column > 80: XML Parsing Error: Opening and ending tag mismatch: tr line 2 and table.
…footer"><div align="center"><div class="gen"><strong></strong><span class="ge…✉
Line 90, Column 34: XML Parsing Error: Opening and ending tag mismatch: table line 2 and body.
fa_endpage();//]]></script></body></html>✉
Line 90, Column 41: XML Parsing Error: Opening and ending tag mismatch: body line 2 and html.
fa_endpage();//]]></script></body></html>✉
Line 90, Column 41: XML Parsing Error: Premature end of data in tag html line 1.
fa_endpage();//]]></script></body></html>✉
↑ Top
