宇宙电影点播网,宇宙点播网提供百度影音最新最快的影视资讯和在线播放 ...

yzdb.tv
  • Domain Name
    yzdb.tv
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #33068
  • Page Size
    74.9 KB
  • Ip Address
    58.64.155.185
  • Heading
    H1: 1, H2: 6, H3: 5, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 38 JPG, 1 PNG

Website Meta Analysis

  • Title
    宇宙电影点播网,2013最好看的美剧|电影|电视剧,百度影音免费在线看电影
  • Meta Keyword
    宇宙电影点播网,宇宙影视,宇宙电影,宇宙点播,百度影音,免费在线电影,电视剧,美剧,韩剧,日剧,动漫,综艺,
  • Meta Description
    宇宙电影点播网,宇宙点播网提供百度影音最新最快的影视资讯和在线播放

Technical Analysis

  • Webserver
    nginx/1.2.3
  • Ip Address
    58.64.155.185
  • Domain Age
    1 Years, 2 Months, 29 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from yzdb.tv.

HTML Analysis

  • server: nginx/1.2.3
  • date: Thu, 26 Sep 2013 14:20:34 GMT
  • content-type: text/html;Charset=utf-8
  • connection: close
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for yzdb.tv

DNS Analysis


DNS servers
f1g1ns1.dnspod.net [119.167.195.12]
f1g1ns2.dnspod.net [112.90.143.29]
Query for DNS records for yzdb.tv failed: Timed out

DNS Records

IP 58.64.155.185 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 58.64.155.185

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 79 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.8305075903803015
Message Error
  • Error Line 2, Column 13: there is no attribute "XMLNS"
    <HTML xmlns="http://www.w3.org/1999/xhtml">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 4, Column 68: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    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 4, Column 69: character data is not allowed here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    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.
  • Warning Line 5, Column 60: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

    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 7, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …eta name="keywords" content="宇宙点播网,美剧在线点播,宇宙点播网,百度影音点播,行尸走肉,吸血鬼日记,生活大爆炸,尼基塔" />

    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 8, Column 163: NET-enabling start-tag requires SHORTTAG YES
    …视剧、韩剧、日剧、美剧、综艺的在线观看和剧集交流场所,在线观看分为普通视频模式、快播等播放高清播放模式,每天第一时间更新,放送最新好看的高清免费电视剧" />

    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 8, Column 163: document type does not allow element "META" here
    …视剧、韩剧、日剧、美剧、综艺的在线观看和剧集交流场所,在线观看分为普通视频模式、快播等播放高清播放模式,每天第一时间更新,放送最新好看的高清免费电视剧" />

    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 9, Column 78: document type does not allow element "LINK" here
    <LINK rel="stylesheet" type="text/css" href="/template/qire/images/reset.css">

    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 10, Column 77: document type does not allow element "LINK" here
    <link type="text/css" rel="stylesheet" href="/template/qire/images/base.css">

    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 11, Column 80: document type does not allow element "LINK" here
    <LINK rel="stylesheet" type="text/css" href="/template/qire/images/qirebox.css">

    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 12, Column 57: document type does not allow element "LINK" here
    <link href="/favicon.ico" type="image/x-icon" rel="icon">

    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 13, Column 66: document type does not allow element "LINK" here
    <link href="/favicon.ico" type="image/x-icon" rel="shortcut icon">

    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 14, Column 8: required attribute "TYPE" not specified
    <script>var maccms_path = "/";</script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 19, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 20, Column 6: document type does not allow element "BODY" here
    <body>

    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 45, Column 22: required attribute "TYPE" not specified
                  <script>history_Look(10);</script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 45, Column 22: start tag for "LI" omitted, but its declaration does not permit this
                  <script>history_Look(10);</script>
  • Error Line 47, Column 16: end tag for element "P" which is not open
                </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.

  • Error Line 121, Column 48: required attribute "TYPE" not specified
            <script src="/template/qire/ads/ad1.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 127, Column 48: required attribute "TYPE" not specified
            <script src="/template/qire/ads/ad5.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 129, Column 49: required attribute "TYPE" not specified
            <script src="/template/qire/ads/ad11.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 149, Column 113: there is no attribute "ONERROR"
    …<img border="0" alt="唐顿庄园第三季" onerror="src='/template/qire/images/nopic_big.gi…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 572, Column 44: required attribute "TYPE" not specified
        <script src="/template/qire/ads/ad5.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 584, Column 245: NET-enabling start-tag requires SHORTTAG YES
    …3504579068.jpg" class="pics8"  alt="行尸走肉第三季" /><SPAN class="play-icon"> </SPAN>

    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 589, Column 921: document type does not allow element "A" here
    …E%B7%E9%B2%81%C2%B7%E6%9E%97%E8%82%AF'>安德鲁·林肯</a>&nbsp;<a target='_blank' href…

    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 589, Column 1060: document type does not allow element "A" here
    …1%A9%C2%B7%E5%8D%A1%E4%B8%BD%E4%B8%9D'>莎拉·韦恩·卡丽丝</a>&nbsp;<a target='_blank' h…

    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 589, Column 1178: document type does not allow element "A" here
    …=%E5%A4%A7%E5%8D%AB%C2%B7%E8%8E%AB%E7%91%9E%E7%91%9F'>大卫·莫瑞瑟</a>&nbsp;</a></LI>

    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 777, Column 276: NET-enabling start-tag requires SHORTTAG YES
    …90980906.jpg" class="pics8"  alt="PRICELESS" /><SPAN class="play-icon"> </SPAN>

    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 782, Column 926: document type does not allow element "A" here
    …=%E6%9C%A8%E6%9D%91%E6%8B%93%E5%93%89'>木村拓哉</a>&nbsp;<a target='_blank' href='…

    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 782, Column 1024: document type does not allow element "A" here
    …=%E4%B8%AD%E4%BA%95%E8%B4%B5%E4%B8%80'>中井贵一</a>&nbsp;<a target='_blank' href='…

    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 782, Column 1113: document type does not allow element "A" here
    …?starring=%E9%A6%99%E9%87%8C%E5%A5%88'>香里奈</a>&nbsp;<a target='_blank' href='/…

    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 782, Column 1210: document type does not allow element "A" here
    …arch.php?starring=%E8%97%A4%E8%B0%B7%E5%A4%AA%E8%BE%85'>藤谷太辅</a>&nbsp;</a></LI>

    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 792, Column 29: ID "SYNCH1" already defined
                        <LI id="synch1" class="active" onMouseOver="setTab('synch',…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 599, Column 29: ID "SYNCH1" first defined here
                        <LI id="synch1" class="active" onMouseOver="setTab('synch',…
  • Error Line 793, Column 29: ID "SYNCH2" already defined
                        <LI id="synch2" onMouseOver="setTab('synch',2,5);">江苏卫视</LI>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 600, Column 29: ID "SYNCH2" first defined here
                        <LI id="synch2" onMouseOver="setTab('synch',2,5);">老友记</LI>
  • Error Line 794, Column 29: ID "SYNCH3" already defined
                        <LI id="synch3" onMouseOver="setTab('synch',3,5);">北京卫视</LI>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 601, Column 29: ID "SYNCH3" first defined here
                        <LI id="synch3" onMouseOver="setTab('synch',3,5);">好汉两个半</L…
  • Error Line 795, Column 29: ID "SYNCH4" already defined
                        <LI id="synch4" onMouseOver="setTab('synch',4,5);">东方卫视</LI>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 602, Column 29: ID "SYNCH4" first defined here
                        <LI id="synch4" onMouseOver="setTab('synch',4,5);">超人前传</LI>
  • Error Line 796, Column 29: ID "SYNCH5" already defined
                        <LI id="synch5" onMouseOver="setTab('synch',5,5);">浙江卫视</LI>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 603, Column 29: ID "SYNCH5" first defined here
                        <LI id="synch5" onMouseOver="setTab('synch',5,5);">越狱</LI>
  • Error Line 798, Column 27: ID "CON_SYNCH_1" already defined
                      <OL id="con_synch_1" class="ui-synch-item">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 605, Column 27: ID "CON_SYNCH_1" first defined here
                      <OL id="con_synch_1" class="ui-synch-item">
  • Error Line 805, Column 27: ID "CON_SYNCH_2" already defined
                      <OL id="con_synch_2" class="ui-synch-item fn-hide">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 612, Column 27: ID "CON_SYNCH_2" first defined here
                      <OL id="con_synch_2" class="ui-synch-item fn-hide">
  • Error Line 812, Column 27: ID "CON_SYNCH_3" already defined
                      <OL id="con_synch_3" class="ui-synch-item fn-hide">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 619, Column 27: ID "CON_SYNCH_3" first defined here
                      <OL id="con_synch_3" class="ui-synch-item fn-hide">
  • Error Line 819, Column 27: ID "CON_SYNCH_4" already defined
                      <OL id="con_synch_4" class="ui-synch-item fn-hide">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 626, Column 27: ID "CON_SYNCH_4" first defined here
                      <OL id="con_synch_4" class="ui-synch-item fn-hide">
  • Error Line 826, Column 27: ID "CON_SYNCH_5" already defined
                      <OL id="con_synch_5" class="ui-synch-item fn-hide">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 633, Column 27: ID "CON_SYNCH_5" first defined here
                      <OL id="con_synch_5" class="ui-synch-item fn-hide">
  • Error Line 1470, Column 27: ID "MOVIE" already defined
      <div class="maxBox" id="movie">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 575, Column 27: ID "MOVIE" first defined here
      <div class="maxBox" id="movie">
  • Warning Line 1479, Column 250: NET-enabling start-tag requires SHORTTAG YES
    …261345952036.jpg" class="pics8"  alt="复仇者联盟" /><SPAN class="play-icon"> </SPAN>

    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 1484, Column 976: document type does not allow element "A" here
    …6%AF%C2%B7%E5%9F%83%E6%96%87%E6%96%AF'>克里斯·埃文斯</a>&nbsp;<a target='_blank' hre…

    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 1484, Column 1119: document type does not allow element "A" here
    …7%E5%A7%86%E6%96%AF%E6%B2%83%E6%96%AF'>克里斯·海姆斯沃斯</a>&nbsp;<a target='_blank' h…

    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 1484, Column 1246: document type does not allow element "A" here
    …%E5%98%89%E4%B8%BD%C2%B7%E7%BA%A6%E7%BF%B0%E9%80%8A'>斯嘉丽·约翰逊</a>&nbsp;</a></LI>

    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 1760, Column 61: cannot generate system identifier for general entity "keyword"
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>

    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 1760, Column 61: general entity "keyword" not defined and no default entity
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>

    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 1760, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1761, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=海贼王">海贼王</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1762, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …          <dd><a href="http://yzdb.tv/search.php?type=4&keyword=妖精">妖精</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1763, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …          <dd><a href="http://yzdb.tv/search.php?type=4&keyword=柯南">柯南</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1764, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …          <dd><a href="http://yzdb.tv/search.php?type=4&keyword=死神">死神</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1765, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=奥特曼">奥特曼</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1766, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …       <dd><a href="http://yzdb.tv/search.php?type=4&keyword=蜡笔小新">蜡笔新</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1767, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …          <dd><a href="http://yzdb.tv/search.php?type=4&keyword=铠甲">铠甲</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1768, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …      <dd><a href="http://yzdb.tv/search.php?type=4&keyword=哆啦a梦">哆啦a梦</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Error Line 1769, Column 68: reference to entity "keyword" for which no system identifier could be generated
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=倒霉熊">倒霉熊</a></dd>

    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 1760, Column 60: entity was defined here
    …        <dd><a href="http://yzdb.tv/search.php?type=4&keyword=火影忍者">火影</a></dd>
  • Warning Line 1773, Column 61: cannot generate system identifier for general entity "area"
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>

    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 1773, Column 61: general entity "area" not defined and no default entity
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>

    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 1773, Column 65: reference to entity "area" for which no system identifier could be generated
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>

    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 1773, Column 60: entity was defined here
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>
  • Error Line 1774, Column 65: reference to entity "area" for which no system identifier could be generated
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=大陆">大陆</a></dd>

    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 1773, Column 60: entity was defined here
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>
  • Error Line 1775, Column 65: reference to entity "area" for which no system identifier could be generated
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=欧美">欧美</a></dd>

    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 1773, Column 60: entity was defined here
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>
  • Warning Line 1779, Column 75: cannot generate system identifier for general entity "year"
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>

    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 1779, Column 75: general entity "year" not defined and no default entity
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>

    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 1779, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1780, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2011">2011</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1781, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2010">2010</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1782, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2009">2009</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1783, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2008">2008</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1784, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2007">2007</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1785, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2006">2006</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1786, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2005">2005</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 1787, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2004">2004</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Warning Line 1837, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …/134397141410.jpg" class="pics8"  alt="康熙来了" /><SPAN class="play-icon"> </SPAN>

    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 1842, Column 506: document type does not allow element "A" here
    …?starring=%E8%94%A1%E5%BA%B7%E6%B0%B8'>蔡康永</a>&nbsp;<a target='_blank' href='/…

    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 1842, Column 594: document type does not allow element "A" here
    … href='/search.php?starring=%E5%BE%90%E7%86%99%E5%A8%A3'>徐熙娣</a>&nbsp;</a></LI>

    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 2029, Column 44: required attribute "TYPE" not specified
        <script src="/template/qire/ads/ad5.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 2045, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2012">2012</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2046, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2011">2011</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2047, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2010">2010</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2048, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2009">2009</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2049, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2008">2008</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2050, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2007">2007</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2051, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2006">2006</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2052, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2005">2005</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2053, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=2&year=2004">2004</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2066, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2012">2012</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2067, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2011">2011</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2068, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2010">2010</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2069, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2009">2009</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2070, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2008">2008</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2071, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2007">2007</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2072, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2006">2006</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2073, Column 81: reference to entity "year" for which no system identifier could be generated
    …target="_blank" href="http://yzdb.tv/search.php?type=1&year=2005">2005</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2079, Column 65: reference to entity "area" for which no system identifier could be generated
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>

    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 1773, Column 60: entity was defined here
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>
  • Error Line 2080, Column 65: reference to entity "area" for which no system identifier could be generated
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=大陆">大陆</a></dd>

    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 1773, Column 60: entity was defined here
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>
  • Error Line 2081, Column 65: reference to entity "area" for which no system identifier could be generated
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=欧美">欧美</a></dd>

    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 1773, Column 60: entity was defined here
                  <dd><a href="http://yzdb.tv/search.php?type=4&area=日本">日本</a></dd>
  • Error Line 2082, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2083, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2011">2011</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2084, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2010">2010</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2085, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2009">2009</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2086, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2008">2008</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2087, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2007">2007</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2088, Column 79: reference to entity "year" for which no system identifier could be generated
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2006">2006</a></dd>

    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 1779, Column 74: entity was defined here
    …a rel="nofllow" href="http://yzdb.tv/search.php?type=4&year=2012">2012</a></dd>
  • Error Line 2115, Column 21: ID "FORMSEARCH" already defined
              <form id="formsearch" name="formsearch" method="get" action="/search.…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 54, Column 21: ID "FORMSEARCH" first defined here
              <form id="formsearch" name="formsearch" method="get" action="/search.…
  • Error Line 2116, Column 36: ID "KEYWORD" already defined
                <input type="text" id="keyword" name="keyword" class="input-txt" va…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 55, Column 36: ID "KEYWORD" first defined here
                <input type="text" id="keyword" name="keyword" class="input-txt" va…
  • Error Line 2207, Column 49: required attribute "TYPE" not specified
            <script src="/template/qire/ads/ad12.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 2208, Column 103: required attribute "ALT" not specified
    …yzdb.tv" target="_blank"><img height="204" width="929" src="/ad/picAD.jpg"></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 2218, Column 33: required attribute "TYPE" not specified
          <p><script src="/js/tj.js"></script></p>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 2226, Column 35: there is no attribute "ID"
    <script type="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left"…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 2226, Column 53: there is no attribute "DATA"
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></script>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 2226, Column 65: cannot generate system identifier for general entity "img"
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&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 2226, Column 65: general entity "img" not defined and no default entity
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></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.

  • Error Line 2226, Column 68: reference to entity "img" for which no system identifier could be generated
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></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 2226, Column 64: entity was defined here
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></script>
  • Warning Line 2226, Column 71: cannot generate system identifier for general entity "pos"
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&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 2226, Column 71: general entity "pos" not defined and no default entity
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></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.

  • Error Line 2226, Column 74: reference to entity "pos" for which no system identifier could be generated
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></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 2226, Column 70: entity was defined here
    …e="text/javascript" id="bdshare_js" data="type=slide&img=4&pos=left" ></script>
  • Error Line 2232, Column 28: required attribute "TYPE" not specified
    <script language=javascript>      

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Visitor Analysis

Daily Visitor
  • 583 visits