movietorrents.eu

movietorrents.eu has Alexa Rank 28.915 and Google Page Rank is 2

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    movietorrents.eu
  • Favicon
  • Alexa Rank
    #28915
  • Google Page Rank
    PR 2
  • Ip Address
    31.7.56.90
  • Page Size
    251 B
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
  • Meta Keyword

Technical Analysis



  • Webserver
    nginx admin
  • Ip Address
    31.7.56.90
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from movietorrents.eu.

HTML Analysis

  • server: nginx admin
  • date: Mon, 13 May 2013 18:06:14 GMT
  • content-type: text/html;charset=urf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.10
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for movietorrents.eu

DNS Analysis


DNS servers
ns2.he.net [216.218.131.2]
ns5.he.net [216.66.80.18]
ns3.he.net [216.218.132.2]
ns1.he.net [216.218.130.2]
ns4.he.net [216.66.1.2]


DNS Records

Answer records
movietorrents.eu NS  ns1.he.net 3600s
movietorrents.eu MX
preference: 0
exchange: movietorrents.eu
3600s
movietorrents.eu NS  ns2.he.net 3600s
movietorrents.eu NS  ns4.he.net 3600s
movietorrents.eu NS  ns3.he.net 3600s
movietorrents.eu A 31.7.56.90 3600s
movietorrents.eu SOA
server: ns1.he.net
email: hostmaster@he.net
serial: 2012062319
refresh: 10800
retry: 1800
expire: 604800
minimum ttl: 86400
86400s
movietorrents.eu NS  ns5.he.net 3600s

Authority records

Additional records
ns2.he.net 28 [16 bytes] 86400s
ns3.he.net A 216.218.132.2 86400s
ns2.he.net A 216.218.131.2 86400s
ns1.he.net A 216.218.130.2 86400s
ns5.he.net 28 [16 bytes] 86400s
ns4.he.net 28 [16 bytes] 86400s
ns4.he.net A 216.66.1.2 86400s
ns3.he.net 28 [16 bytes] 86400s
ns5.he.net A 216.66.80.18 86400s

IP 31.7.56.90 Analysis

  • Country Code
    CH
  • Country Code3
    CHE
  • Country Name
    Switzerland
  • City
    EU
  • Continent Code
    47° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 31.7.56.90

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 359 Errors
  • 182 Warnings
Ratio Text/Html
  • 0.28685258964143423
Message Error
  • Error Line 5, Column 12: there is no attribute "NAME"
    <META NAME="Keywords" CONTENT="download movies, movie torrents, free movies, la…

    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 5, Column 31: there is no attribute "CONTENT"
    <META NAME="Keywords" CONTENT="download movies, movie torrents, free movies, la…

    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 5, Column 115: element "META" undefined
    …oad movies, movie torrents, free movies, latest movies, download free movies ">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 6, Column 107: element "META" undefined
    …ENT="Download thousands of verified movie torrents easy, fast and beautiful."> 

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 45, Column 8: required attribute "type" not specified
    <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 50, Column 32: character ";" not allowed in attribute specification list
       for (var i=0; i<sfEls.length; i++) {
  • Error Line 50, Column 32: element "sfEls.length" undefined
       for (var i=0; i<sfEls.length; i++) {

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 60, Column 9: end tag for "sfEls.length" omitted, but OMITTAG NO was specified
    </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 50, Column 19: start tag was here
       for (var i=0; i<sfEls.length; i++) {
  • Error Line 64, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 6, Column 1: start tag was here
    <META NAME="Description" CONTENT="Download thousands of verified movie torrents…
  • Error Line 64, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 5, Column 1: start tag was here
    <META NAME="Keywords" CONTENT="download movies, movie torrents, free movies, la…
  • Error Line 65, Column 78: document type does not allow element "div" here; assuming missing "body" start-tag
    …id="overDiv" style="position:absolute; visibility:hidden; z-index:1000;"></div>
  • Error Line 66, 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 70, Column 5: end tag for element "br" which is not open
    </br></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 70, Column 10: end tag for element "br" which is not open
    </br></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 72, Column 18: document type does not allow element "td" here; assuming missing "tr" start-tag
    <td align="left" >
  • Error Line 75, Column 56: there is no attribute "fb:like:layout"
    <a class="addthis_button_facebook_like" fb:like:layout="button_count"></a>

    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 88, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 72, Column 1: start tag was here
    <td align="left" >
  • Error Line 101, Column 16: document type does not allow element "td" here; assuming missing "tr" start-tag
                <td>
  • Error Line 106, Column 12: end tag for "tr" omitted, but OMITTAG NO was specified
        </tbody>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 101, Column 13: start tag was here
                <td>
  • Error Line 124, Column 79: there is no attribute "width"
    …images/search_button_green.png" width="25" height="25" class="searchbox_submit…

    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 124, Column 91: there is no attribute "height"
    …h_button_green.png" width="25" height="25" class="searchbox_submit" value="" /…

    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 136, Column 13: document type does not allow element "a" here; assuming missing "li" start-tag
    	<a href="/"><img src="http://movietorrents.eu/themes/default/images/logo.gif" …
  • Error Line 136, Column 105: required attribute "alt" not specified
    …movietorrents.eu/themes/default/images/logo.gif" class="logo" border="0" /></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 137, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="Meniui0"><a href="index.php">home</a></li>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 138, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="Meniui0"><a href="torrents.php?parent_cat=Movies"><span>genre</span…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 138, Column 84: "if" is not a reserved name
    …rent_cat=Movies"><span>genre</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 138, Column 103: "endif" is not a reserved name
    …pan>genre</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Warning Line 153, Column 60: character "&" is the first character of a delimiter but occurred as data
    		<li class="Meniui"><a href="torrents.php?cat=67">musical & dance</a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 163, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="Meniui0"><a><span>quality</span><![if gt IE 6]></a><![endif]><!--[i…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 163, Column 48: "if" is not a reserved name
    …s="Meniui0"><a><span>quality</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 163, Column 67: "endif" is not a reserved name
    …n>quality</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Warning Line 167, Column 59: cannot generate system identifier for general entity "cat"
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>

    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 167, Column 59: general entity "cat" not defined and no default entity
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 167, Column 62: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 167, Column 62: reference to external entity in attribute value
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 167, Column 62: reference to entity "cat" for which no system identifier could be generated
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 167, Column 69: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 168, Column 62: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=11">BRRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 168, Column 62: reference to external entity in attribute value
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=11">BRRip</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 168, Column 62: reference to entity "cat" for which no system identifier could be generated
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=11">BRRip</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 168, Column 69: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=11">BRRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 169, Column 62: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=12">BDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 169, Column 62: reference to external entity in attribute value
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=12">BDRip</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 169, Column 62: reference to entity "cat" for which no system identifier could be generated
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=12">BDRip</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 169, Column 69: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=12">BDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 170, Column 62: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=10">HDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 170, Column 62: reference to external entity in attribute value
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=10">HDRip</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 170, Column 62: reference to entity "cat" for which no system identifier could be generated
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=10">HDRip</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 170, Column 69: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=10">HDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 171, Column 65: reference not terminated by REFC delimiter
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=3">480p</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 171, Column 65: reference to external entity in attribute value
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=3">480p</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 171, Column 65: reference to entity "cat" for which no system identifier could be generated
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=3">480p</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 171, Column 72: reference not terminated by REFC delimiter
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=3">480p</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 172, Column 65: reference not terminated by REFC delimiter
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=1">720p</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 172, Column 65: reference to external entity in attribute value
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=1">720p</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 172, Column 65: reference to entity "cat" for which no system identifier could be generated
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=1">720p</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 172, Column 72: reference not terminated by REFC delimiter
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=1">720p</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 173, Column 62: reference not terminated by REFC delimiter
    …lass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=2">1080p</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 173, Column 62: reference to external entity in attribute value
    …lass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=2">1080p</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 173, Column 62: reference to entity "cat" for which no system identifier could be generated
    …lass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=2">1080p</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 173, Column 69: reference not terminated by REFC delimiter
    …lass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=2">1080p</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 174, Column 62: reference not terminated by REFC delimiter
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=9">3D</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 174, Column 62: reference to external entity in attribute value
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=9">3D</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 174, Column 62: reference to entity "cat" for which no system identifier could be generated
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=9">3D</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 174, Column 69: reference not terminated by REFC delimiter
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=9">3D</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 175, Column 62: reference not terminated by REFC delimiter
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=8">R5</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 175, Column 62: reference to external entity in attribute value
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=8">R5</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 175, Column 62: reference to entity "cat" for which no system identifier could be generated
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=8">R5</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 175, Column 69: reference not terminated by REFC delimiter
    …i class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=8">R5</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 176, Column 62: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">DVDscr</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 176, Column 62: reference to external entity in attribute value
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">DVDscr</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 176, Column 62: reference to entity "cat" for which no system identifier could be generated
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">DVDscr</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 176, Column 69: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">DVDscr</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 177, Column 62: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">VoDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 177, Column 62: reference to external entity in attribute value
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">VoDRip</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 177, Column 62: reference to entity "cat" for which no system identifier could be generated
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">VoDRip</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 177, Column 69: reference not terminated by REFC delimiter
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=7">VoDRip</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 178, Column 62: reference not terminated by REFC delimiter
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=4">DVDR</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 178, Column 62: reference to external entity in attribute value
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=4">DVDR</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 178, Column 62: reference to entity "cat" for which no system identifier could be generated
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=4">DVDR</a></li>

    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 167, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 178, Column 69: reference not terminated by REFC delimiter
    …class="Meniui"><a href="torrents-search.php?search=&cat=0&lang=4">DVDR</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 183, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="Meniui0"><a><span>release</span><![if gt IE 6]></a><![endif]><!--[i…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 183, Column 48: "if" is not a reserved name
    …s="Meniui0"><a><span>release</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 183, Column 67: "endif" is not a reserved name
    …n>release</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 185, Column 54: document type does not allow element "table" here; assuming missing "li" start-tag
    		<table  border="0"  cellpadding="2" cellspacing="0">
  • Error Line 188, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">201…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 188, Column 68: cannot generate system identifier for general entity "x"
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    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 188, Column 68: general entity "x" not defined and no default entity
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 188, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 188, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 188, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 188, Column 72: cannot generate system identifier for general entity "y"
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    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 188, Column 72: general entity "y" not defined and no default entity
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 188, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 188, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 188, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 189, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">201…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 189, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">2011</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 189, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">2011</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 189, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">2011</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 189, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">2011</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 189, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">2011</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 189, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2011&x=0&y=0">2011</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 190, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">201…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 190, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">2010</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 190, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">2010</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 190, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">2010</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 190, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">2010</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 190, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">2010</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 190, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2010&x=0&y=0">2010</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 191, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 191, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">2009</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 191, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">2009</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 191, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">2009</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 191, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">2009</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 191, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">2009</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 191, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2009&x=0&y=0">2009</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 192, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 192, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">2008</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 192, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">2008</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 192, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">2008</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 192, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">2008</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 192, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">2008</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 192, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2008&x=0&y=0">2008</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 196, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 196, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">2007</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 196, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">2007</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 196, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">2007</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 196, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">2007</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 196, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">2007</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 196, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2007&x=0&y=0">2007</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 197, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 197, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">2006</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 197, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">2006</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 197, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">2006</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 197, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">2006</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 197, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">2006</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 197, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2006&x=0&y=0">2006</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 198, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 198, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">2005</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 198, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">2005</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 198, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">2005</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 198, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">2005</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 198, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">2005</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 198, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2005&x=0&y=0">2005</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 199, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 199, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">2004</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 199, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">2004</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 199, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">2004</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 199, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">2004</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 199, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">2004</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 199, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2004&x=0&y=0">2004</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 200, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 200, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 200, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 200, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 200, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 200, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 200, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 204, Column 13: end tag for "tr" which is not finished
            </tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 206, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 206, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 206, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 206, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 206, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 206, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 206, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2003&x=0&y=0">2003</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 207, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 207, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">2002</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 207, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">2002</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 207, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">2002</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 207, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">2002</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 207, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">2002</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 207, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2002&x=0&y=0">2002</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 208, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 208, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">2001</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 208, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">2001</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 208, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">2001</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 208, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">2001</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 208, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">2001</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 208, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2001&x=0&y=0">2001</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 209, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">200…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 209, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">2000</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 209, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">2000</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 209, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">2000</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 209, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">2000</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 209, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">2000</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 209, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=2000&x=0&y=0">2000</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 210, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 210, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">1999</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 210, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">1999</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 210, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">1999</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 210, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">1999</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 210, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">1999</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 210, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1999&x=0&y=0">1999</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 214, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 214, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">1998</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 214, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">1998</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 214, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">1998</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 214, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">1998</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 214, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">1998</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 214, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1998&x=0&y=0">1998</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 215, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 215, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">1997</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 215, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">1997</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 215, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">1997</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 215, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">1997</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 215, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">1997</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 215, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1997&x=0&y=0">1997</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 216, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 216, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">1996</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 216, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">1996</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 216, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">1996</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 216, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">1996</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 216, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">1996</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 216, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1996&x=0&y=0">1996</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 217, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 217, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">1995</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 217, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">1995</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 217, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">1995</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 217, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">1995</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 217, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">1995</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 217, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1995&x=0&y=0">1995</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 218, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 218, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 218, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 218, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 218, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 218, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 218, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 222, Column 13: end tag for "tr" which is not finished
            </tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 224, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 224, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 224, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 224, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 224, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 224, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 224, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1994&x=0&y=0">1994</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 225, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 225, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">1993</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 225, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">1993</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 225, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">1993</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 225, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">1993</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 225, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">1993</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 225, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1993&x=0&y=0">1993</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 226, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 226, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">1992</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 226, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">1992</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 226, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">1992</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 226, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">1992</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 226, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">1992</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 226, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1992&x=0&y=0">1992</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 227, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 227, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">1991</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 227, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">1991</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 227, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">1991</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 227, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">1991</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 227, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">1991</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 227, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1991&x=0&y=0">1991</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 228, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">199…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 228, Column 69: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">1990</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 228, Column 69: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">1990</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 228, Column 69: reference to entity "x" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">1990</a></li></td>

    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 188, Column 67: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Warning Line 228, Column 73: reference not terminated by REFC delimiter
    …>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">1990</a></li></td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 228, Column 73: reference to external entity in attribute value
    …>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">1990</a></li></td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 228, Column 73: reference to entity "y" for which no system identifier could be generated
    …>&nbsp;<li><a href="torrents-search.php?search=1990&x=0&y=0">1990</a></li></td>

    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 188, Column 71: entity was defined here
    …>&nbsp;<li><a href="torrents-search.php?search=2012&x=0&y=0">2012</a></li></td>
  • Error Line 233, Column 13: end tag for "tr" which is not finished
            </tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 238, Column 6: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li><a href="torrents-search.php">Search for more, click here</a></li>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 239, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
    	</ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 185, Column 3: start tag was here
    		<table  border="0"  cellpadding="2" cellspacing="0">
  • Error Line 244, Column 20: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="Meniui0"><a><span>sort</span><![if gt IE 6]></a><![endif]><!--[if lt…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 244, Column 44: "if" is not a reserved name
    …lass="Meniui0"><a><span>sort</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 244, Column 63: "endif" is not a reserved name
    …span>sort</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 255, Column 20: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="Meniui0"><a href="torrents-search.php"><span>search</span><![if gt I…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 255, Column 73: "if" is not a reserved name
    …nts-search.php"><span>search</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 255, Column 92: "endif" is not a reserved name
    …an>search</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 261, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="Meniui0"><a href="about-us.php"><span>about us</span><![if gt IE 6]…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 261, Column 69: "if" is not a reserved name
    …about-us.php"><span>about us</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 261, Column 88: "endif" is not a reserved name
    …>about us</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 267, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
    	</ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 136, Column 2: start tag was here
    	<a href="/"><img src="http://movietorrents.eu/themes/default/images/logo.gif" …
  • Error Line 292, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 289, Column 11: start tag was here
              <td valign="top">
  • Error Line 292, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 287, Column 6: start tag was here
         <tr>
  • Error Line 292, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 286, Column 5: start tag was here
        <table cellspacing="0" cellpadding="7" width="100%" border="0">
  • Error Line 296, Column 104: document type does not allow element "link" here
    …pe="text/css" href="lightbox/js/lightbox/themes/default/jquery.lightbox.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 311, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table align=left class=index cellpadding=0 cellspacing=0 width=895 ><div class…
  • Error Line 311, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table align=left class=index cellpadding=0 cellspacing=0 width=895 ><div class…
  • Error Line 311, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le align=left class=index cellpadding=0 cellspacing=0 width=895 ><div class="h…
  • Error Line 311, Column 57: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …class=index cellpadding=0 cellspacing=0 width=895 ><div class="headlines"><a h…
  • Error Line 311, Column 65: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dex cellpadding=0 cellspacing=0 width=895 ><div class="headlines"><a href="tor…
  • Error Line 311, Column 92: document type does not allow element "div" here
    …ng=0 width=895 ><div class="headlines"><a href="torrents.php">Latest Uploads</…

    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 312, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Error Line 312, Column 22: document type does not allow element "td" here; assuming missing "tr" start-tag
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Warning Line 312, Column 85: cannot generate system identifier for general entity "hit"
    …rents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/imag…

    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 312, Column 85: general entity "hit" not defined and no default entity
    …rents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/imag…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 312, Column 88: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 312, Column 88: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 312, Column 88: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 312, Column 164: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/39970' alt="39970 / Comedy"   class=index_posters_big1 title=Movie 43.[2013]…
  • Error Line 312, Column 189: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …edy"   class=index_posters_big1 title=Movie 43.[2013].R5.DVDRIP.DIVX.[Eng]-DUQ…
  • Error Line 312, Column 195: "43." is not a member of a group specified for any attribute
    … class=index_posters_big1 title=Movie 43.[2013].R5.DVDRIP.DIVX.[Eng]-DUQAÂ  ><…
  • Error Line 312, Column 234: end tag for "img" omitted, but OMITTAG NO was specified
    …3.[2013].R5.DVDRIP.DIVX.[Eng]-DUQAÂ  ><span class=poster_titles>Movie 43 (2013…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 92: start tag was here
    …u/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/images/3997…
  • Error Line 312, Column 246: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DVDRIP.DIVX.[Eng]-DUQAÂ  ><span class=poster_titles>Movie 43 (2013)</span></a>…
  • Error Line 312, Column 290: document type does not allow element "td" here
    …_titles>Movie 43 (2013)</span></a> <td>&nbsp;<td class=poster_area><a href='ht…

    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 312, Column 307: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …(2013)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 312, Column 318: document type does not allow element "td" here
    …n></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrents.eu/torren…

    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 312, Column 384: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3996&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 312, Column 384: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3996&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 312, Column 384: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3996&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 312, Column 461: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/39960' alt="39960 / Fantasy"   class=index_posters_big1 title=Constantine.(20…
  • Error Line 312, Column 486: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …asy"   class=index_posters_big1 title=Constantine.(2005).BDRip.720p.DTS.multis…
  • Error Line 312, Column 498: an attribute value must be a literal unless it contains only name characters
    …=index_posters_big1 title=Constantine.(2005).BDRip.720p.DTS.multisub.Highcode-…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 312, Column 549: "PublicHD" is not a member of a group specified for any attribute
    …720p.DTS.multisub.Highcode- PublicHD  ><span class=poster_titles>Constantine (…
  • Error Line 312, Column 550: end tag for "img" omitted, but OMITTAG NO was specified
    …20p.DTS.multisub.Highcode- PublicHD  ><span class=poster_titles>Constantine (2…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 388: start tag was here
    …u/torrents-details.php?id=3996&hit=1'><img  border='0'src='uploads/images/3996…
  • Error Line 312, Column 562: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …isub.Highcode- PublicHD  ><span class=poster_titles>Constantine (2005)</span><…
  • Error Line 312, Column 609: document type does not allow element "td" here
    …tles>Constantine (2005)</span></a> <td>&nbsp;<td class=poster_area><a href='ht…

    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 312, Column 626: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …(2005)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 312, Column 637: document type does not allow element "td" here
    …n></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrents.eu/torren…

    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 312, Column 703: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3995&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 312, Column 703: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3995&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 312, Column 703: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3995&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 312, Column 779: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/39950' alt="39950 / Action"   class=index_posters_big1 title=Because.I.Love.…
  • Error Line 312, Column 804: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ion"   class=index_posters_big1 title=Because.I.Love.You.2012.1080p.WEB-DL.AAC…
  • Error Line 312, Column 867: end tag for "img" omitted, but OMITTAG NO was specified
    …080p.WEB-DL.AAC2.0.H.264-CtrlHD.mkv  ><span class=poster_titles>Because I Love…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 707: start tag was here
    …u/torrents-details.php?id=3995&hit=1'><img  border='0'src='uploads/images/3995…
  • Error Line 312, Column 879: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AAC2.0.H.264-CtrlHD.mkv  ><span class=poster_titles>Because I Love You (2012)<…
  • Error Line 312, Column 933: document type does not allow element "td" here
    …cause I Love You (2012)</span></a> <td>&nbsp;<td class=poster_area><a href='ht…

    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 312, Column 950: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …(2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 312, Column 961: document type does not allow element "td" here
    …n></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrents.eu/torren…

    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 312, Column 1027: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3994&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 312, Column 1027: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3994&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 312, Column 1027: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3994&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 312, Column 1106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9940' alt="39940 / Animation"   class=index_posters_big1 title=Scooby-Doo.Mask…
  • Error Line 312, Column 1131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ion"   class=index_posters_big1 title=Scooby-Doo.Mask.Of.The.Blue.Falcon.2012.…
  • Error Line 312, Column 1193: character "[" not allowed in attribute specification list
    …lue.Falcon.2012.720p.BluRay.x264-DATA [PublicHD]  ><span class=poster_titles>S…
  • Error Line 312, Column 1194: end tag for "img" omitted, but OMITTAG NO was specified
    …ue.Falcon.2012.720p.BluRay.x264-DATA [PublicHD]  ><span class=poster_titles>Sc…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1031: start tag was here
    …u/torrents-details.php?id=3994&hit=1'><img  border='0'src='uploads/images/3994…
  • Error Line 312, Column 1218: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ay.x264-DATA [PublicHD]  ><span class=poster_titles>Scooby-Doo! Mask of the Bl…
  • Error Line 312, Column 1295: document type does not allow element "td" here
    …lue Falcon (Video 2012)</span></a> <td>&nbsp;<td class=poster_area><a href='ht…

    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 312, Column 1312: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … 2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 312, Column 1323: document type does not allow element "td" here
    …n></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrents.eu/torren…

    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 312, Column 1389: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3993&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 312, Column 1389: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3993&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 312, Column 1389: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3993&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 312, Column 1468: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9930' alt="39930 / Adventure"   class=index_posters_big1 title=The.Hobbit.An.U…
  • Error Line 312, Column 1493: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ure"   class=index_posters_big1 title=The.Hobbit.An.Unexpected.Journey.2012.10…
  • Error Line 312, Column 1556: character "[" not allowed in attribute specification list
    …Journey.2012.1080p.BluRay.x264-SPARKS [PublicHD]  ><span class=poster_titles>T…
  • Error Line 312, Column 1557: end tag for "img" omitted, but OMITTAG NO was specified
    …ourney.2012.1080p.BluRay.x264-SPARKS [PublicHD]  ><span class=poster_titles>Th…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1393: start tag was here
    …u/torrents-details.php?id=3993&hit=1'><img  border='0'src='uploads/images/3993…
  • Error Line 312, Column 1581: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….x264-SPARKS [PublicHD]  ><span class=poster_titles>The Hobbit: An Unexpected …
  • Error Line 312, Column 1650: document type does not allow element "td" here
    …expected Journey (2012)</span></a> <td>&nbsp;<td class=poster_area><a href='ht…

    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 312, Column 1667: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …(2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 312, Column 1678: document type does not allow element "td" here
    …n></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrents.eu/torren…

    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 312, Column 1744: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3992&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 312, Column 1744: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3992&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 312, Column 1744: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3992&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 312, Column 1823: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9920' alt="39920 / Adventure"   class=index_posters_big1 title=The.Hobbit.An.U…
  • Error Line 312, Column 1848: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ure"   class=index_posters_big1 title=The.Hobbit.An.Unexpected.Journey.2012.72…
  • Error Line 312, Column 1910: character "[" not allowed in attribute specification list
    ….Journey.2012.720p.BluRay.x264-SPARKS [PublicHD]  ><span class=poster_titles>T…
  • Error Line 312, Column 1911: end tag for "img" omitted, but OMITTAG NO was specified
    …Journey.2012.720p.BluRay.x264-SPARKS [PublicHD]  ><span class=poster_titles>Th…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1748: start tag was here
    …u/torrents-details.php?id=3992&hit=1'><img  border='0'src='uploads/images/3992…
  • Error Line 312, Column 1935: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….x264-SPARKS [PublicHD]  ><span class=poster_titles>The Hobbit: An Unexpected …
  • Error Line 312, Column 2004: document type does not allow element "td" here
    …expected Journey (2012)</span></a> <td>&nbsp;</table><table align=left class=i…

    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 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 2001: start tag was here
    … Unexpected Journey (2012)</span></a> <td>&nbsp;</table><table align=left clas…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1657: start tag was here
    …d Journey (2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1647: start tag was here
    … Unexpected Journey (2012)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1302: start tag was here
    …con (Video 2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1292: start tag was here
    …e Blue Falcon (Video 2012)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 940: start tag was here
    … Love You (2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 930: start tag was here
    …>Because I Love You (2012)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 616: start tag was here
    …nstantine (2005)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 606: start tag was here
    …_titles>Constantine (2005)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 297: start tag was here
    …>Movie 43 (2013)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 287: start tag was here
    …ter_titles>Movie 43 (2013)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 312, Column 2018: end tag for "td" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1: start tag was here
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Error Line 312, Column 2018: end tag for "tr" omitted, but OMITTAG NO was specified
    …ey (2012)</span></a> <td>&nbsp;</table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 312, Column 1: start tag was here
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Error Line 312, Column 2032: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n></a> <td>&nbsp;</table><table align=left class=index cellpadding=0 cellspaci…
  • Error Line 312, Column 2043: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …&nbsp;</table><table align=left class=index cellpadding=0 cellspacing=0 width=…
  • Error Line 312, Column 2061: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le align=left class=index cellpadding=0 cellspacing=0 width=895 border=0><div …
  • Error Line 312, Column 2075: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …class=index cellpadding=0 cellspacing=0 width=895 border=0><div class="headlin…
  • Error Line 312, Column 2083: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dex cellpadding=0 cellspacing=0 width=895 border=0><div class="headlines"></br…
  • Error Line 312, Column 2094: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ding=0 cellspacing=0 width=895 border=0><div class="headlines"></br><a href="n…
  • Error Line 312, Column 2118: document type does not allow element "div" here
    …th=895 border=0><div class="headlines"></br><a href="new.php">New Releases</a>…

    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 312, Column 2123: end tag for element "br" which is not open
    …5 border=0><div class="headlines"></br><a href="new.php">New Releases</a></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 313, Column 5: end tag for element "tr" which is not open
    </tr>

    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 315, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Warning Line 315, Column 88: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3966&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 315, Column 88: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3966&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 315, Column 88: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3966&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 315, Column 159: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …images/39660' alt=" / Thriller" class=index_posters_big1 title=Dead.End.2012.D…
  • Error Line 315, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …iller" class=index_posters_big1 title=Dead.End.2012.DVDRip.XViD-juggs  ><span …
  • Error Line 315, Column 218: end tag for "img" omitted, but OMITTAG NO was specified
    …tle=Dead.End.2012.DVDRip.XViD-juggs  ><span class=poster_titles>Hard Shoulder …

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 92: start tag was here
    …u/torrents-details.php?id=3966&hit=1'><img  border='0'src='uploads/images/3966…
  • Error Line 315, Column 230: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….2012.DVDRip.XViD-juggs  ><span class=poster_titles>Hard Shoulder (2012)</span…
  • Error Line 315, Column 279: document type does not allow element "td" here
    …es>Hard Shoulder (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 315, Column 306: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 315, Column 383: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3957&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 315, Column 383: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3957&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 315, Column 383: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3957&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 315, Column 452: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/39570' alt=" / Comedy" class=index_posters_big1 title=Stitches.(2012)…
  • Error Line 315, Column 477: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …omedy" class=index_posters_big1 title=Stitches.(2012).720p.BrRip.x264-YIFY  ><…
  • Error Line 315, Column 486: an attribute value must be a literal unless it contains only name characters
    …ass=index_posters_big1 title=Stitches.(2012).720p.BrRip.x264-YIFY  ><span clas…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 315, Column 516: end tag for "img" omitted, but OMITTAG NO was specified
    …titches.(2012).720p.BrRip.x264-YIFY  ><span class=poster_titles>Stitches (2012…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 387: start tag was here
    …u/torrents-details.php?id=3957&hit=1'><img  border='0'src='uploads/images/3957…
  • Error Line 315, Column 528: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2).720p.BrRip.x264-YIFY  ><span class=poster_titles>Stitches (2012)</span></a>…
  • Error Line 315, Column 572: document type does not allow element "td" here
    …_titles>Stitches (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 315, Column 599: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 315, Column 676: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3953&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 315, Column 676: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3953&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 315, Column 676: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3953&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 315, Column 745: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/39530' alt=" / Action" class=index_posters_big1 title=Solid.State.201…
  • Error Line 315, Column 770: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=Solid.State.2012.DVDRip.x264.AC3-FooKaS …
  • Error Line 315, Column 812: end tag for "img" omitted, but OMITTAG NO was specified
    …d.State.2012.DVDRip.x264.AC3-FooKaS  ><span class=poster_titles>Solid State (2…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 680: start tag was here
    …u/torrents-details.php?id=3953&hit=1'><img  border='0'src='uploads/images/3953…
  • Error Line 315, Column 824: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….DVDRip.x264.AC3-FooKaS  ><span class=poster_titles>Solid State (2012)</span><…
  • Error Line 315, Column 871: document type does not allow element "td" here
    …tles>Solid State (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 315, Column 898: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 315, Column 975: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3934&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 315, Column 975: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3934&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 315, Column 975: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3934&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 315, Column 1044: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/39340' alt=" / Comedy" class=index_posters_big1 title=Playing.for.Kee…
  • Error Line 315, Column 1069: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …omedy" class=index_posters_big1 title=Playing.for.Keeps.2012.BDRip.XviD-SPARKS…
  • Error Line 315, Column 1112: end tag for "img" omitted, but OMITTAG NO was specified
    …ng.for.Keeps.2012.BDRip.XviD-SPARKS  ><span class=poster_titles>Playing for Ke…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 979: start tag was here
    …u/torrents-details.php?id=3934&hit=1'><img  border='0'src='uploads/images/3934…
  • Error Line 315, Column 1124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….2012.BDRip.XviD-SPARKS  ><span class=poster_titles>Playing for Keeps (2012)</…
  • Error Line 315, Column 1177: document type does not allow element "td" here
    …laying for Keeps (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 315, Column 1204: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 315, Column 1281: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3933&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 315, Column 1281: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3933&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 315, Column 1281: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3933&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 315, Column 1350: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/39330' alt=" / Action" class=index_posters_big1 title=Red.Dawn.2012.D…
  • Error Line 315, Column 1375: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=Red.Dawn.2012.DVDRip.XviD-SPARKS  ><span…
  • Error Line 315, Column 1410: end tag for "img" omitted, but OMITTAG NO was specified
    …le=Red.Dawn.2012.DVDRip.XviD-SPARKS  ><span class=poster_titles>Red Dawn (2012…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 1285: start tag was here
    …u/torrents-details.php?id=3933&hit=1'><img  border='0'src='uploads/images/3933…
  • Error Line 315, Column 1422: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2012.DVDRip.XviD-SPARKS  ><span class=poster_titles>Red Dawn (2012)</span></a>…
  • Error Line 315, Column 1466: document type does not allow element "td" here
    …_titles>Red Dawn (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 315, Column 1493: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 315, Column 1570: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3899&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 315, Column 1570: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3899&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 315, Column 1570: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3899&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 315, Column 1642: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mages/38990' alt=" / Animation" class=index_posters_big1 title=Rise.of.the.Gua…
  • Error Line 315, Column 1667: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ation" class=index_posters_big1 title=Rise.of.the.Guardians.2012.DVDSCR.LiNE.X…
  • Error Line 315, Column 1719: end tag for "img" omitted, but OMITTAG NO was specified
    …ardians.2012.DVDSCR.LiNE.XViD-sC0rp  ><span class=poster_titles>Rise of the Gu…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 1574: start tag was here
    …u/torrents-details.php?id=3899&hit=1'><img  border='0'src='uploads/images/3899…
  • Error Line 315, Column 1731: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….DVDSCR.LiNE.XViD-sC0rp  ><span class=poster_titles>Rise of the Guardians (201…
  • Error Line 315, Column 1788: document type does not allow element "td" here
    …of the Guardians (2012)</span></a> <td>&nbsp;</td></td></table><table align=le…

    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 315, Column 1812: end tag for "tr" omitted, but OMITTAG NO was specified
    …/span></a> <td>&nbsp;</td></td></table><table align=left class=index cellpaddi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 314, Column 1: start tag was here
    <tr>
  • Error Line 315, Column 1826: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>&nbsp;</td></td></table><table align=left class=index cellpadding=0 cellspaci…
  • Error Line 315, Column 1837: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …></td></table><table align=left class=index cellpadding=0 cellspacing=0 width=…
  • Error Line 315, Column 1855: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le align=left class=index cellpadding=0 cellspacing=0 width=895 border=0><div …
  • Error Line 315, Column 1869: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …class=index cellpadding=0 cellspacing=0 width=895 border=0><div class="headlin…
  • Error Line 315, Column 1877: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dex cellpadding=0 cellspacing=0 width=895 border=0><div class="headlines"></br…
  • Error Line 315, Column 1888: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ding=0 cellspacing=0 width=895 border=0><div class="headlines"></br><a href="m…
  • Error Line 315, Column 1912: document type does not allow element "div" here
    …th=895 border=0><div class="headlines"></br><a href="most.php">Most Popular</a…

    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 315, Column 1917: end tag for element "br" which is not open
    …5 border=0><div class="headlines"></br><a href="most.php">Most Popular</a></di…

    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 316, Column 5: end tag for element "tr" which is not open
    </tr>

    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 318, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Warning Line 318, Column 88: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=1740&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 318, Column 88: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=1740&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 318, Column 88: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=1740&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 318, Column 157: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/17400' alt=" / Action" class=index_posters_big1 title=The.Avengers.20…
  • Error Line 318, Column 182: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=The.Avengers.2012.DVDRip.XviD-NYDIC   ><…
  • Error Line 318, Column 221: end tag for "img" omitted, but OMITTAG NO was specified
    …he.Avengers.2012.DVDRip.XviD-NYDIC   ><span class=poster_titles>The Avengers (…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 318, Column 92: start tag was here
    …u/torrents-details.php?id=1740&hit=1'><img  border='0'src='uploads/images/1740…
  • Error Line 318, Column 233: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2012.DVDRip.XviD-NYDIC   ><span class=poster_titles>The Avengers (2012)</span>…
  • Error Line 318, Column 281: document type does not allow element "td" here
    …les>The Avengers (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 318, Column 308: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 318, Column 385: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=1569&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 318, Column 385: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=1569&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 318, Column 385: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=1569&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 318, Column 454: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/15690' alt=" / Action" class=index_posters_big1 title=The.Hunger.Game…
  • Error Line 318, Column 479: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=The.Hunger.Games.(2012).DVDRip.XviD-MAXS…
  • Error Line 318, Column 496: an attribute value must be a literal unless it contains only name characters
    …x_posters_big1 title=The.Hunger.Games.(2012).DVDRip.XviD-MAXSPEED   ><span cla…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 318, Column 527: end tag for "img" omitted, but OMITTAG NO was specified
    ….Games.(2012).DVDRip.XviD-MAXSPEED   ><span class=poster_titles>The Hunger Gam…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 318, Column 389: start tag was here
    …u/torrents-details.php?id=1569&hit=1'><img  border='0'src='uploads/images/1569…
  • Error Line 318, Column 539: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …).DVDRip.XviD-MAXSPEED   ><span class=poster_titles>The Hunger Games (2012)</s…
  • Error Line 318, Column 591: document type does not allow element "td" here
    …The Hunger Games (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 318, Column 618: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 318, Column 695: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=1898&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 318, Column 695: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=1898&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 318, Column 695: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=1898&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 318, Column 764: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/18980' alt=" / Action" class=index_posters_big1 title=Men.In.Black.3.…
  • Error Line 318, Column 789: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=Men.In.Black.3.2012.DVDRip.XviD-DEPRiVED…
  • Error Line 318, Column 833: end tag for "img" omitted, but OMITTAG NO was specified
    ….Black.3.2012.DVDRip.XviD-DEPRiVED   ><span class=poster_titles>Men in Black 3…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 318, Column 699: start tag was here
    …u/torrents-details.php?id=1898&hit=1'><img  border='0'src='uploads/images/1898…
  • Error Line 318, Column 845: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2.DVDRip.XviD-DEPRiVED   ><span class=poster_titles>Men in Black 3 (2012)</spa…
  • Error Line 318, Column 895: document type does not allow element "td" here
    …s>Men in Black 3 (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 318, Column 922: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 318, Column 999: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=2746&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 318, Column 999: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=2746&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 318, Column 999: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=2746&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 318, Column 1068: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/27460' alt=" / Action" class=index_posters_big1 title=Total.Recall.20…
  • Error Line 318, Column 1093: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=Total.Recall.2012.DVDRip.XviD-Lum1x   ><…
  • Error Line 318, Column 1132: end tag for "img" omitted, but OMITTAG NO was specified
    …otal.Recall.2012.DVDRip.XviD-Lum1x   ><span class=poster_titles>Total Recall (…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 318, Column 1003: start tag was here
    …u/torrents-details.php?id=2746&hit=1'><img  border='0'src='uploads/images/2746…
  • Error Line 318, Column 1144: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2012.DVDRip.XviD-Lum1x   ><span class=poster_titles>Total Recall (2012)</span>…
  • Error Line 318, Column 1192: document type does not allow element "td" here
    …les>Total Recall (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 318, Column 1219: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 318, Column 1296: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3542&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 318, Column 1296: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3542&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 318, Column 1296: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3542&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 318, Column 1365: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/35420' alt=" / Action" class=index_posters_big1 title=Django.Unchaine…
  • Error Line 318, Column 1390: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=Django.Unchained.2012.DVDSCR.X264.AAC-P2…
  • Error Line 318, Column 1435: end tag for "img" omitted, but OMITTAG NO was specified
    …Unchained.2012.DVDSCR.X264.AAC-P2P   ><span class=poster_titles>Django Unchain…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 318, Column 1300: start tag was here
    …u/torrents-details.php?id=3542&hit=1'><img  border='0'src='uploads/images/3542…
  • Error Line 318, Column 1447: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …12.DVDSCR.X264.AAC-P2P   ><span class=poster_titles>Django Unchained (2012)</s…
  • Error Line 318, Column 1499: document type does not allow element "td" here
    …Django Unchained (2012)</span></a> <td>&nbsp;</td></td><td class=poster_area><…

    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 318, Column 1526: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an></a> <td>&nbsp;</td></td><td class=poster_area><a href='http://movietorrent…
  • Warning Line 318, Column 1602: reference not terminated by REFC delimiter
    …nts.eu/torrents-details.php?id=757&hit=1'><img  border='0'src='uploads/images/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 318, Column 1602: reference to external entity in attribute value
    …nts.eu/torrents-details.php?id=757&hit=1'><img  border='0'src='uploads/images/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 318, Column 1602: reference to entity "hit" for which no system identifier could be generated
    …nts.eu/torrents-details.php?id=757&hit=1'><img  border='0'src='uploads/images/…

    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 312, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3997&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 318, Column 1674: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mages/7570.jpg' alt=" / Comedy" class=index_posters_big1 title=Crazy Stupid Lo…
  • Error Line 318, Column 1699: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …omedy" class=index_posters_big1 title=Crazy Stupid Love (2011)   ><span class=…
  • Error Line 318, Column 1712: "Stupid" is not a member of a group specified for any attribute
    …index_posters_big1 title=Crazy Stupid Love (2011)   ><span class=poster_titles…
  • Error Line 318, Column 1717: "Love" is not a member of a group specified for any attribute
    …_posters_big1 title=Crazy Stupid Love (2011)   ><span class=poster_titles>Craz…
  • Error Line 318, Column 1727: end tag for "img" omitted, but OMITTAG NO was specified
    …ig1 title=Crazy Stupid Love (2011)   ><span class=poster_titles>Crazy, Stupid,…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 318, Column 1606: start tag was here
    …eu/torrents-details.php?id=757&hit=1'><img  border='0'src='uploads/images/7570…
  • Error Line 318, Column 1739: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …azy Stupid Love (2011)   ><span class=poster_titles>Crazy, Stupid, Love. (2011…
  • Error Line 318, Column 1795: document type does not allow element "td" here
    …y, Stupid, Love. (2011)</span></a> <td>&nbsp;</td></td></table>		            <…

    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 318, Column 1819: end tag for "tr" omitted, but OMITTAG NO was specified
    …Stupid, Love. (2011)</span></a> <td>&nbsp;</td></td></table>		            </td>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 317, Column 1: start tag was here
    <tr>
  • Error Line 318, Column 1838: end tag for element "td" which is not open
    …Stupid, Love. (2011)</span></a> <td>&nbsp;</td></td></table>		            </td>

    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 320, Column 23: end tag for element "tr" which is not open
                      </tr>

    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 322, Column 12: end tag for element "table" which is not open
        </table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 324, 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 331, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 339, Column 42: there is no attribute "height"
    <table align="center" width="940" height="250" border="0">

    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 345, Column 36: end tag for "br" omitted, but OMITTAG NO was specified
    <center><span> Community <br></span></center>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 345, Column 26: start tag was here
    <center><span> Community <br></span></center>
  • Warning Line 349, Column 75: cannot generate system identifier for general entity "lightbox"
    …ntact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='Co…

    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 349, Column 75: general entity "lightbox" not defined and no default entity
    …ntact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='Co…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 349, Column 83: reference not terminated by REFC delimiter
    …ntact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='Contact' c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 349, Column 83: reference to external entity in attribute value
    …ntact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='Contact' c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 349, Column 83: reference to entity "lightbox" for which no system identifier could be generated
    …ntact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='Contact' c…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 349, Column 74: entity was defined here
    …ontact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='C…
  • Warning Line 349, Column 104: reference not terminated by REFC delimiter
    …dth]=500&lightbox[height]=500&lightbox' title='Contact' class='lightbox' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 349, Column 104: reference to external entity in attribute value
    …dth]=500&lightbox[height]=500&lightbox' title='Contact' class='lightbox' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 349, Column 104: reference to entity "lightbox" for which no system identifier could be generated
    …dth]=500&lightbox[height]=500&lightbox' title='Contact' class='lightbox' targe…

    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 349, Column 74: entity was defined here
    …ontact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='C…
  • Error Line 349, Column 258: required attribute "alt" not specified
    …ges/contact.png'  class='favicons' width='25' height='25'   />&nbsp;Contact</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 351, Column 186: required attribute "alt" not specified
    …ebook.png' class='favicons' width='25' height='25' />&nbsp;Facebook Fanpage</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 353, Column 149: required attribute "alt" not specified
    …eu/images/rss.png' class='favicons' width='25' height='25' />&nbsp;RSS Feed</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 357, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div></td>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 342, Column 13: start tag was here
                <td>&nbsp;<div class="our_friends">
  • Error Line 357, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div></td>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 341, Column 9: start tag was here
            <tr>
  • Error Line 357, Column 6: end tag for "tbody" omitted, but OMITTAG NO was specified
    </div></td>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 340, Column 5: start tag was here
        <tbody>
  • Error Line 357, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div></td>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 339, Column 1: start tag was here
    <table align="center" width="940" height="250" border="0">
  • Error Line 357, Column 11: end tag for element "td" which is not open
    </div></td>

    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 358, Column 16: document type does not allow element "td" here
                <td>&nbsp;

    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 361, Column 45: end tag for "br" omitted, but OMITTAG NO was specified
    <center><span> Sites we recommend <br></span></center>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 361, Column 35: start tag was here
    <center><span> Sites we recommend <br></span></center>
  • Error Line 364, Column 177: required attribute "alt" not specified
    …s/torrentz.png' class='favicons' width='16' height='16' />&nbsp;Torrentz.eu</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 367, Column 175: required attribute "alt" not specified
    …ds/btscene.png' class='favicons' width='16' height='16' />&nbsp;Btscene.org</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 371, Column 16: document type does not allow element "td" here
                <td>&nbsp;

    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 373, Column 36: there is no attribute "data-href"
    <div class="fb-like-box" data-href="http://www.facebook.com/MovieTorrentseu" da…

    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 373, Column 89: there is no attribute "data-width"
    …ebook.com/MovieTorrentseu" data-width="300" data-height="250" data-show-faces=…

    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 373, Column 107: there is no attribute "data-height"
    …rentseu" data-width="300" data-height="250" data-show-faces="true" data-stream…

    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 373, Column 129: there is no attribute "data-show-faces"
    …00" data-height="250" data-show-faces="true" data-stream="false" data-header="…

    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 373, Column 148: there is no attribute "data-stream"
    …250" data-show-faces="true" data-stream="false" data-header="false"></div></td>

    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 373, Column 168: there is no attribute "data-header"
    …250" data-show-faces="true" data-stream="false" data-header="false"></div></td>

    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 375, Column 5: end tag for element "tr" which is not open
    </tr>

    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 376, Column 12: end tag for element "tbody" which is not open
        </tbody>

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

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 381, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 381, Column 1: start tag was here
    <br>
  • Error Line 383, 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 386, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 65, Column 1: start tag was here
    <div id="overDiv" style="position:absolute; visibility:hidden; z-index:1000;"><…
  • Error Line 391, Column 5: end tag for element "br" which is not open
    </br></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 391, Column 10: end tag for element "br" which is not open
    </br></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 392, Column 21: document type does not allow element "div" here
    <div class="domains">

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

Visitor Analysis

Daily Visitor
  • 5.483 visits
Daily Visitor

In Page Analysis