ChimSeDiNang, Chim Sẻ Đi Nắng, aoe clip, aoe, video aoe, video đế chế, clip aoe, clip đế chế ...

cohet.vn
  • Domain Name
    cohet.vn
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #33236
  • Page Size
    59.5 KB
  • Ip Address
    210.245.91.234
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    29 GIF, 37 JPG, 1 PNG

Website Meta Analysis

  • Title
    Video Aoe Clip Aoe Video Đế Chế Mới Nhất Hay Nhất | ChimSeDiNang | Chim Sẻ Đi Nắng
  • Meta Keyword
    ChimSeDiNang, Chim Sẻ Đi Nắng, aoe clip, aoe, video aoe, video đế chế, clip aoe, clip đế chế, ipad, iphone, tutj, tieubachlong, chim se di nang
  • Meta Description
    ChimSeDiNang, Chim Sẻ Đi Nắng, aoe clip, aoe, video aoe, video đế chế, clip aoe, clip đế chế

Technical Analysis

  • Webserver
    Apache/2.2.22 (CentOS)
  • Ip Address
    210.245.91.234
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from cohet.vn.

HTML Analysis

  • date: Thu, 31 Jan 2013 16:10:08 GMT
  • server: Apache/2.2.22 (CentOS)
  • x-powered-by: PHP/5.2.17
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for cohet.vn

DNS Analysis


DNS servers
ns2.matbao.vn [210.245.124.171]
ns1.matbao.vn [203.162.163.44]


DNS Records

Answer records
cohet.vn A 210.245.91.234 3600s
cohet.vn NS  ns-bak.matbao.com 3600s
cohet.vn NS  ns1.matbao.vn 3600s
cohet.vn NS  ns2.matbao.vn 3600s
cohet.vn SOA
server: ns1.matbao.vn
email: admin@matbao.com
serial: 2012060769
refresh: 7200
retry: 1800
expire: 1209600
minimum ttl: 3600
3600s
cohet.vn MX
preference: 10
exchange: aspmx2.googlemail.com
3600s
cohet.vn MX
preference: 10
exchange: aspmx3.googlemail.com
3600s
cohet.vn MX
preference: 1
exchange: aspmx.l.google.com
3600s
cohet.vn MX
preference: 5
exchange: alt1.aspmx.l.google.com
3600s
cohet.vn MX
preference: 5
exchange: alt2.aspmx.l.google.com
3600s
cohet.vn TXT v=spf1 a mx ptr -all 3600s

Authority records

Additional records
ns1.matbao.vn A 203.162.163.44 3600s
ns2.matbao.vn A 210.245.124.171 3600s

IP 210.245.91.234 Analysis

  • Country Code
    VN
  • Country Code3
    VNM
  • Country Name
    Vietnam
  • City
    Hanoi
  • Continent Code
    AS
  • Latitude
    21.0333
  • Longitude
    105.85
  • % [whois.apnic.net node-7]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 210.245.80.0 - 210.245.95.255
    netname: FPT-STATICIP-NET
    country: vn
    descr: FPT Telecom Company
    descr: 2nd floor FPT Building, Pham Hung Road, Cau Giay District, Hanoi
    admin-c: TTH19-AP
    tech-c: NOC21-AP
    status: ALLOCATED NON-PORTABLE
    remarks: For spamming matters, mail to abuse@fpt.vn
    changed: hm-changed@vnnic.net.vn 20120809
    mnt-by: MAINT-VN-FPT
    mnt-irt: IRT-VNNIC-AP
    source: APNIC

    person: Tran Thanh Hai
    nic-hdl: TTH19-AP
    e-mail: haitt@fpt.net
    address: FPT Telecom
    address: 2nd floor FPT Building, Pham Hung Road, Cau Giay District, Hanoi
    phone: +84-90-4211450
    fax-no: +84-4-37262163
    country: vn
    changed: hm-changed@vnnic.net.vn 20111114
    mnt-by: MAINT-VN-VNNIC
    source: APNIC

    person: Network Operation Center
    nic-hdl: NOC21-AP
    e-mail: ftel.noc.net@fpt.com.vn
    address: FPT Telecom
    address: 2nd floor FPT Building, Pham Hung Road, Cau Giay District, Hanoi
    phone: +84-8-73093388
    fax-no: +84-8-73008889
    country: VN
    changed: hm-changed@vnnic.net.vn 20120809
    mnt-by: MAINT-VN-VNNIC
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 85 Errors
  • 51 Warnings
Ratio Text/Html
  • 0.7344516849137436
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <br />

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 1, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2, Column 54: character data is not allowed here
    … Undefined index:  HTTP_ACCEPT in <b>/home/admin/clipvmg.cohet.vn/index.php</b…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 2, Column 94: end tag for element "B" which is not open
    …ACCEPT in <b>/home/admin/clipvmg.cohet.vn/index.php</b> on line <b>40</b><br />

    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.

  • Error Line 2, Column 106: document type does not allow element "B" here
    …ACCEPT in <b>/home/admin/clipvmg.cohet.vn/index.php</b> on line <b>40</b><br />

    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).

  • Warning Line 2, Column 117: NET-enabling start-tag requires SHORTTAG YES
    …ACCEPT in <b>/home/admin/clipvmg.cohet.vn/index.php</b> on line <b>40</b><br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2, Column 117: document type does not allow element "BR" here
    …ACCEPT in <b>/home/admin/clipvmg.cohet.vn/index.php</b> on line <b>40</b><br />

    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 3, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/…
  • Warning Line 8, Column 177: NET-enabling start-tag requires SHORTTAG YES
    …ế, clip aoe, clip đế chế, ipad, iphone, tutj, tieubachlong, chim se di nang" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 9, Column 128: NET-enabling start-tag requires SHORTTAG YES
    …im Sẻ Đi Nắng, aoe clip, aoe, video aoe, video đế chế, clip aoe, clip đế chế"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 10, Column 127: NET-enabling start-tag requires SHORTTAG YES
    …m Sẻ Đi Nắng, aoe clip, aoe, video aoe, video đế chế, clip aoe, clip đế chế" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 11, Column 45: NET-enabling start-tag requires SHORTTAG YES
    <meta name="robots" content="index, follow" /> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 13, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …k rel="shortcut icon" href="http://cohet.vn/favicon.ico"  type="image/x-icon"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 21, Column 31: NET-enabling start-tag requires SHORTTAG YES
    <base href="http://cohet.vn/" /> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 22, Column 63: NET-enabling start-tag requires SHORTTAG YES
    <meta property="og:image" content="http://s0.cohet.vn/aoe.jpg"/> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 26, Column 67: NET-enabling start-tag requires SHORTTAG YES
    <meta property='og:site_name' content='Video Aoe Clip Aoe Đế Chế' />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 28, Column 53: NET-enabling start-tag requires SHORTTAG YES
    <meta property="fb:admins" content="100000414814176"/> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 35, Column 9: end tag for element "SCRIPT" which is not open
    </script> 

    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.

  • Warning Line 44, Column 197: NET-enabling start-tag requires SHORTTAG YES
    …">Dự AOE</span> <img src="http://game.cohet.vn/css/images/news.gif"/></div></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 55, Column 65: character data is not allowed here
    …document.createElement('script'); po.type = 'text/javascript'; po.async = true;

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 59, Column 13: end tag for element "SCRIPT" which is not open
    				</script>

    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.

  • Error Line 61, Column 9: end tag for element "DIV" which is not open
    			</div>

    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.

  • Error Line 62, Column 29: document type does not allow element "DIV" here
    			<div style="float:right;">

    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 69, Column 34: document type does not allow element "SCRIPT" here
    			<script type="text/javascript">

    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 84, Column 8: end tag for element "DIV" which is not open
    		</div>

    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.

  • Error Line 85, Column 21: document type does not allow element "DIV" here
    		<div id="sub-menu">

    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 95, Column 7: end tag for element "DIV" which is not open
    	</div>

    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.

  • Error Line 96, Column 6: end tag for element "DIV" which is not open
    </div>

    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.

  • Error Line 97, Column 50: document type does not allow element "DIV" here
        <div id="main-wap" style="position: relative"> 

    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).

  • Warning Line 99, Column 107: cannot generate system identifier for general entity "oacute"
    …trong><span style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><spa…

    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 "&amp;" (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 &aelig; 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 99, Column 107: general entity "oacute" not defined and no default entity
    …trong><span style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><spa…

    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.

  • Error Line 99, Column 113: reference to entity "oacute" for which no system identifier could be generated
    …<span style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span styl…

    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 99, Column 106: entity was defined here
    …strong><span style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><sp…
  • Warning Line 99, Column 117: cannot generate system identifier for general entity "igrave"
    …n style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="c…

    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 "&amp;" (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 &aelig; 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 99, Column 117: general entity "igrave" not defined and no default entity
    …n style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="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.

  • Error Line 99, Column 123: reference to entity "igrave" for which no system identifier could be generated
    …e="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="color: …

    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 99, Column 116: entity was defined here
    …an style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="…
  • Error Line 99, Column 133: reference to entity "oacute" for which no system identifier could be generated
    …#ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="color: #0000ff;">…

    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 99, Column 106: entity was defined here
    …strong><span style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><sp…
  • Warning Line 99, Column 174: cannot generate system identifier for general entity "nbsp"
    …</span><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><span…

    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 "&amp;" (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 &aelig; 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 99, Column 174: general entity "nbsp" not defined and no default entity
    …</span><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><span…

    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.

  • Error Line 99, Column 178: reference to entity "nbsp" for which no system identifier could be generated
    …an><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><span sty…

    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 99, Column 173: entity was defined here
    …?</span><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><spa…
  • Error Line 99, Column 245: reference to entity "nbsp" for which no system identifier could be generated
    …"><span style="color: #ff0000;">-&nbsp;</span></span><span style="color: #ff00…

    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 99, Column 173: entity was defined here
    …?</span><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><spa…
  • Warning Line 99, Column 362: cannot generate system identifier for general entity "ecirc"
    …lass="vtip" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2…

    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 "&amp;" (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 &aelig; 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 99, Column 362: general entity "ecirc" not defined and no default entity
    …lass="vtip" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2…

    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.

  • Error Line 99, Column 367: reference to entity "ecirc" for which no system identifier could be generated
    …"vtip" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m…

    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 99, Column 361: entity was defined here
    …class="vtip" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-…
  • Warning Line 99, Column 372: cannot generate system identifier for general entity "agrave"
    …" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aacu…

    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 "&amp;" (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 &aelig; 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 99, Column 372: general entity "agrave" not defined and no default entity
    …" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aacu…

    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.

  • Error Line 99, Column 378: reference to entity "agrave" for which no system identifier could be generated
    …e="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y G…

    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 99, Column 371: entity was defined here
    …p" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aac…
  • Error Line 99, Column 393: reference to entity "agrave" for which no system identifier could be generated
    …anh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="..…

    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 99, Column 371: entity was defined here
    …p" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aac…
  • Warning Line 99, Column 408: cannot generate system identifier for general entity "aacute"
    …H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-T…

    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 "&amp;" (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 &aelig; 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 99, Column 408: general entity "aacute" not defined and no default entity
    …H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-T…

    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.

  • Error Line 99, Column 414: reference to entity "aacute" for which no system identifier could be generated
    …ve; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-Thanh-N…

    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 99, Column 407: entity was defined here
    … H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-…
  • Error Line 99, Column 545: reference to entity "ecirc" for which no system identifier could be generated
    …html">[Video] GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m…

    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 99, Column 361: entity was defined here
    …class="vtip" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-…
  • Error Line 99, Column 556: reference to entity "agrave" for which no system identifier could be generated
    …o] GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y G…

    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 99, Column 371: entity was defined here
    …p" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aac…
  • Error Line 99, Column 571: reference to entity "agrave" for which no system identifier could be generated
    …anh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV</a>&nbsp;…

    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 99, Column 371: entity was defined here
    …p" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aac…
  • Error Line 99, Column 592: reference to entity "aacute" for which no system identifier could be generated
    …ve; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV</a>&nbsp;-&nbsp;</span></span>…

    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 99, Column 407: entity was defined here
    … H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-…
  • Error Line 99, Column 610: reference to entity "nbsp" for which no system identifier could be generated
    …y 31-1-2013 m&aacute;y GameTV</a>&nbsp;-&nbsp;</span></span><span style="color…

    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 99, Column 173: entity was defined here
    …?</span><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><spa…
  • Error Line 99, Column 617: reference to entity "nbsp" for which no system identifier could be generated
    …2013 m&aacute;y GameTV</a>&nbsp;-&nbsp;</span></span><span style="color: #ff00…

    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 99, Column 173: entity was defined here
    …?</span><span style="color: #0000ff;">&nbsp;<span style="color: #ff0000;"><spa…
  • Error Line 99, Column 711: reference to entity "agrave" for which no system identifier could be generated
    …tip" title="TTTT 10h 1.2.2013 H&agrave; Nội vs Trường Ph&aacute;t EC - T&igrav…

    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 99, Column 371: entity was defined here
    …p" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aac…
  • Error Line 99, Column 736: reference to entity "aacute" for which no system identifier could be generated
    …2013 H&agrave; Nội vs Trường Ph&aacute;t EC - T&igrave;m lại ch&iacute;nh m&ig…

    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 99, Column 407: entity was defined here
    … H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-…
  • Error Line 99, Column 752: reference to entity "igrave" for which no system identifier could be generated
    …ội vs Trường Ph&aacute;t EC - T&igrave;m lại ch&iacute;nh m&igrave;nh" href=".…

    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 99, Column 116: entity was defined here
    …an style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="…
  • Warning Line 99, Column 762: cannot generate system identifier for general entity "iacute"
    …ng Ph&aacute;t EC - T&igrave;m lại ch&iacute;nh m&igrave;nh" href="../../tin-a…

    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 "&amp;" (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 &aelig; 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 99, Column 762: general entity "iacute" not defined and no default entity
    …ng Ph&aacute;t EC - T&igrave;m lại ch&iacute;nh m&igrave;nh" href="../../tin-a…

    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.

  • Error Line 99, Column 768: reference to entity "iacute" for which no system identifier could be generated
    …aacute;t EC - T&igrave;m lại ch&iacute;nh m&igrave;nh" href="../../tin-aoe/TTT…

    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 99, Column 761: entity was defined here
    …ờng Ph&aacute;t EC - T&igrave;m lại ch&iacute;nh m&igrave;nh" href="../../tin-…
  • Error Line 99, Column 780: reference to entity "igrave" for which no system identifier could be generated
    …- T&igrave;m lại ch&iacute;nh m&igrave;nh" href="../../tin-aoe/TTTT-10h-1-2-20…

    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 99, Column 116: entity was defined here
    …an style="color: #ff0000;">C&oacute; g&igrave; h&oacute;t?</span><span style="…
  • Error Line 99, Column 934: reference to entity "agrave" for which no system identifier could be generated
    …: #ff0000;">TTTT 10h 1.2.2013 H&agrave; Nội vs Trường Ph&aacute;t EC</span></a…

    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 99, Column 371: entity was defined here
    …p" title="GameTV vs Thanh Ni&ecirc;n H&agrave; Nội ng&agrave;y 31-1-2013 m&aac…
  • Error Line 99, Column 959: reference to entity "aacute" for which no system identifier could be generated
    …2013 H&agrave; Nội vs Trường Ph&aacute;t EC</span></a></span></span></strong><…

    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 99, Column 407: entity was defined here
    … H&agrave; Nội ng&agrave;y 31-1-2013 m&aacute;y GameTV" href="../../GameTV-vs-…
  • Warning Line 204, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT Chủ nhật …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 206, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT 10h 1.2.2…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 208, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 210, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 212, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT 12h Thứ 5…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 212, Column 357: end tag for element "A" which is not open
    …/1234.html">TTTT 12h Thứ 5 - 31/01/2013 Thanh niên HN - GameTV Handsome</a></p>

    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.

  • Warning Line 214, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="Đã hoãn 19h 30…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 216, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 218, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 220, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 222, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 224, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT 12h ngày …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 226, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="Tin tức Team A…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 228, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 230, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 232, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT 13h30 ngà…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 234, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 236, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 238, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT 12h30' ng…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 240, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 242, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" style="color: maroon …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 244, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="TTTT 12h ngày …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 246, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="Blog Aoe Đấu g…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 248, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="Blog Aoe Tâm s…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 250, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …="http://cohet.vn/css/images/news.gif"/> <a class="vtip" title="Đã hoãn 14h ng…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 574, Column 10: invalid comment declaration: found name start character outside comment but inside comment declaration
    				<!-- End FaceBook FanBox -->
  • Info Line 569, Column 5: comment declaration started here
    				<!-- Begin FaceBook FanBox 
  • Warning Line 691, Column 72: cannot generate system identifier for general entity "callback"
    …er.zing.vn/lview?loc=_adb_22_10002338&callback=crystal2.addStaticSlot"></scrip…

    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 "&amp;" (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 &aelig; 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 691, Column 72: general entity "callback" not defined and no default entity
    …er.zing.vn/lview?loc=_adb_22_10002338&callback=crystal2.addStaticSlot"></scrip…

    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.

  • Error Line 691, Column 80: reference to entity "callback" for which no system identifier could be generated
    …r.zing.vn/lview?loc=_adb_22_10002338&callback=crystal2.addStaticSlot"></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.

  • Info Line 691, Column 71: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10002338&callback=crystal2.addStaticSlot"></scri…
  • Error Line 695, Column 23: document type does not allow element "DIV" here
        <div class="clear"></div>

    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 696, Column 31: document type does not allow element "DIV" here
        <div id="footer-copyright">

    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).

  • Warning Line 700, Column 21: cannot generate system identifier for general entity "copy"
    					<br>Copyright &copy Cohet Group 2011. All Right Reserved.

    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 "&amp;" (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 &aelig; 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 700, Column 21: general entity "copy" not defined and no default entity
    					<br>Copyright &copy Cohet Group 2011. All Right Reserved.

    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.

  • Error Line 700, Column 25: reference to entity "copy" for which no system identifier could be generated
    					<br>Copyright &copy Cohet Group 2011. All Right Reserved.

    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 700, Column 20: entity was defined here
    					<br>Copyright &copy Cohet Group 2011. All Right Reserved.
  • Error Line 709, Column 77: document type does not allow element "SCRIPT" here
    … type="text/javascript" src="http://s0.cohet.vn/js/jquery.jticker.js"></script>

    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 710, Column 76: document type does not allow element "SCRIPT" here
    … type="text/javascript" src="http://s0.cohet.vn/js/jquery.cookie.js"></script> 

    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 712, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript"> 

    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 734, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript">

    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 743, Column 31: document type does not allow element "DIV" here
    <div id="boxes" class="closex">

    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 757, Column 68: document type does not allow element "DIV" here
    	<div class="chat" style="display:none;bottom: 25px;" id="chat-box">

    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).

  • Warning Line 758, Column 325: cannot generate system identifier for general entity "amp"
    …reen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999…

    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 "&amp;" (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 &aelig; 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 758, Column 325: general entity "amp" not defined and no default entity
    …reen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999…

    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.

  • Error Line 758, Column 328: reference to entity "amp" for which no system identifier could be generated
    …n"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 337: reference to entity "amp" for which no system identifier could be generated
    … value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999&amp;r=10…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 346: reference to entity "amp" for which no system identifier could be generated
    …id=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999&amp;r=100&amp;v=0…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 359: reference to entity "amp" for which no system identifier could be generated
    …458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0" nam…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 372: reference to entity "amp" for which no system identifier could be generated
    …amp;f=50&amp;l=999999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0" name="flashvars"…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 382: reference to entity "amp" for which no system identifier could be generated
    …mp;l=999999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0" name="flashvars"><embed wi…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 390: reference to entity "amp" for which no system identifier could be generated
    …999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0" name="flashvars"><embed width="220…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 477: reference to entity "amp" for which no system identifier could be generated
    …"320" flashvars="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 486: reference to entity "amp" for which no system identifier could be generated
    …shvars="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999&amp;r=10…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 495: reference to entity "amp" for which no system identifier could be generated
    …id=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999&amp;r=100&amp;v=0…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 508: reference to entity "amp" for which no system identifier could be generated
    …458&amp;b=60&amp;f=50&amp;l=999999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 521: reference to entity "amp" for which no system identifier could be generated
    …amp;f=50&amp;l=999999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" all…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 531: reference to entity "amp" for which no system identifier could be generated
    …mp;l=999999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscre…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Error Line 758, Column 539: reference to entity "amp" for which no system identifier could be generated
    …999&amp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true…

    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 758, Column 324: entity was defined here
    …creen"><param value="cid=1321242437458&amp;b=60&amp;f=50&amp;l=999999&amp;q=99…
  • Warning Line 758, Column 544: cannot generate system identifier for general entity "s"
    …mp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" typ…

    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 "&amp;" (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 &aelig; 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 758, Column 544: general entity "s" not defined and no default entity
    …mp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" typ…

    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.

  • Error Line 758, Column 545: reference to entity "s" for which no system identifier could be generated
    …p;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type…

    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 758, Column 543: entity was defined here
    …amp;q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" ty…
  • Warning Line 758, Column 548: cannot generate system identifier for general entity "t"
    …=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="a…

    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 "&amp;" (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 &aelig; 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 758, Column 548: general entity "t" not defined and no default entity
    …=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="a…

    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.

  • Error Line 758, Column 549: reference to entity "t" for which no system identifier could be generated
    …999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="ap…

    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 758, Column 547: entity was defined here
    …q=999999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="…
  • Warning Line 758, Column 552: cannot generate system identifier for general entity "aa"
    …999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="appli…

    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 "&amp;" (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 &aelig; 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 758, Column 552: general entity "aa" not defined and no default entity
    …999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="appli…

    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.

  • Error Line 758, Column 554: reference to entity "aa" for which no system identifier could be generated
    …9&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="applica…

    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 758, Column 551: entity was defined here
    …9999&amp;r=100&amp;v=0&amp;w=0&s=1&t=0&aa=1" allowfullscreen="true" type="appl…
  • Error Line 760, Column 73: document type does not allow element "DIV" here
    <div class="chat-box" onClick="clickx()" style="bottom: 0px;" id="taskx">

    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 766, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript"> 

    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 876, Column 7: end tag for element "BODY" which is not open
    </body>

    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.

  • Error Line 877, Column 7: end tag for element "HTML" which is not open
    </html>

    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.

Visitor Analysis

Daily Visitor
  • 5.950 visits
Daily Visitor