Download thousands of verified movie torrents easy, fast and beautiful. ...

movietorrents.eu
  • Domain Name
    movietorrents.eu
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #32585
  • Page Size
    25.9 KB
  • Ip Address
    31.7.56.90
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 1 JPG, 6 PNG

Website Meta Analysis

  • Title
    MovieTorrents - Download the latest and verified movie torrents
  • Meta Keyword
    download movies, movie torrents, free movies, latest movies, download free movies
  • Meta Description
    Download thousands of verified movie torrents easy, fast and beautiful.

Technical Analysis

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

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

HTML Analysis

  • server: nginx admin
  • date: Tue, 05 Feb 2013 10:04:02 GMT
  • content-type: text/html;charset=iso-8859-1
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.10
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • content-length: 5623
  • age: 14
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 364 Errors
  • 182 Warnings
Ratio Text/Html
  • 0.6930666967950891
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 124, 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 137, Column 16: document type does not allow element "td" here; assuming missing "tr" start-tag
                <td>
  • Error Line 157, 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 137, Column 13: start tag was here
                <td>
  • Error Line 175, 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 175, 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 187, 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 187, 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 188, 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 189, 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 189, 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 189, 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 204, 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 214, 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 214, 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 214, 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 218, 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 218, 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 218, 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 218, 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 218, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 218, 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 219, 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 219, 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 219, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 219, 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 220, 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 220, 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 220, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 220, 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 221, 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 221, 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 221, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 221, 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 222, 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 222, 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 222, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 222, 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 223, 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 223, 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 223, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 223, 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 224, 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 224, 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 224, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 224, 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 225, 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 225, 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 225, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 225, 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 226, 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 226, 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 226, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 226, 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 227, 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 227, 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 227, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 227, 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 228, 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 228, 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 228, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 228, 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 229, 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 229, 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 229, 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 218, Column 58: entity was defined here
    …ass="Meniui"><a href="torrents-search.php?search=&cat=0&lang=5">DVDRip</a></li>
  • Warning Line 229, 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 234, 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 234, 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 234, 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 236, Column 54: document type does not allow element "table" here; assuming missing "li" start-tag
    		<table  border="0"  cellpadding="2" cellspacing="0">
  • Error Line 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 239, 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 240, 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 240, 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 240, 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 240, 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 239, 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 240, 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 240, 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 240, 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 239, 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 241, 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 241, 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 241, 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 241, 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 239, 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 241, 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 241, 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 241, 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 239, 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 242, 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 242, 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 242, 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 242, 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 239, 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 242, 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 242, 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 242, 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 239, 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 243, 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 243, 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 243, 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 243, 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 239, 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 243, 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 243, 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 243, 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 239, 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 247, 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 247, 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 247, 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 247, 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 239, 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 247, 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 247, 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 247, 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 239, 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 248, 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 248, 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 248, 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 248, 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 239, 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 248, 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 248, 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 248, 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 239, 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 249, 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 249, 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 249, 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 249, 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 239, 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 249, 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 249, 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 249, 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 239, 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 250, 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 250, 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 250, 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 250, 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 239, 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 250, 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 250, 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 250, 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 239, 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 251, 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 251, 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 251, 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 251, 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 239, 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 251, 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 251, 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 251, 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 239, 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 255, 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 257, 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 257, 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 257, 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 257, 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 239, 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 257, 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 257, 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 257, 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 239, 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 258, 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 258, 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 258, 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 258, 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 239, 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 258, 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 258, 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 258, 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 239, 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 259, 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 259, 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 259, 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 259, 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 239, 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 259, 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 259, 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 259, 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 239, 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 260, 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 260, 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 260, 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 260, 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 239, 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 260, 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 260, 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 260, 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 239, 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 261, 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 261, 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 261, 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 261, 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 239, 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 261, 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 261, 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 261, 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 239, 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 265, 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 265, 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 265, 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 265, 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 239, 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 265, 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 265, 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 265, 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 239, 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 266, 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 266, 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 266, 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 266, 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 239, 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 266, 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 266, 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 266, 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 239, 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 267, 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 267, 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 267, 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 267, 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 239, 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 267, 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 267, 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 267, 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 239, 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 268, 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 268, 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 268, 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 268, 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 239, 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 268, 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 268, 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 268, 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 239, 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 269, 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 269, 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 269, 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 269, 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 239, 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 269, 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 269, 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 269, 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 239, 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 273, 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 275, 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 275, 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 275, 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 275, 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 239, 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 275, 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 275, 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 275, 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 239, 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 276, 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 276, 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 276, 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 276, 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 239, 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 276, 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 276, 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 276, 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 239, 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 277, 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 277, 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 277, 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 277, 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 239, 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 277, 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 277, 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 277, 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 239, 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 278, 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 278, 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 278, 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 278, 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 239, 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 278, 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 278, 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 278, 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 239, 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 279, 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 279, 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 279, 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 279, 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 239, 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 279, 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 279, 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 279, 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 239, 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 284, 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 289, 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 290, 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 236, Column 3: start tag was here
    		<table  border="0"  cellpadding="2" cellspacing="0">
  • Error Line 295, 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 295, 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 295, 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 306, 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 306, 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 306, 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 312, 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 312, 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 312, 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 318, 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 187, Column 2: start tag was here
    	<a href="/"><img src="http://movietorrents.eu/themes/default/images/logo.gif" …
  • Error Line 343, 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 340, Column 11: start tag was here
              <td valign="top">
  • Error Line 343, 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 338, Column 6: start tag was here
         <tr>
  • Error Line 343, 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 337, Column 5: start tag was here
        <table cellspacing="0" cellpadding="7" width="100%" border="0">
  • Error Line 347, 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 364, 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 364, 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 364, 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 364, 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 364, 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 364, 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 365, 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 365, 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 365, Column 85: cannot generate system identifier for general entity "hit"
    …rents.eu/torrents-details.php?id=3801&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 365, Column 85: general entity "hit" not defined and no default entity
    …rents.eu/torrents-details.php?id=3801&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 365, Column 88: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3801&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 365, Column 88: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3801&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 365, Column 88: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3801&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 365, Column 163: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …es/38010' alt="38010 / Drama"   class=index_posters_big1 title=Anna.Karenina.2…
  • Error Line 365, Column 188: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ama"   class=index_posters_big1 title=Anna.Karenina.2012.DVDRip.XviD.iNT-cYnTh…
  • Error Line 365, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …renina.2012.DVDRip.XviD.iNT-cYnThiA  ><span class=poster_titles>Anna Karenina …

    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 365, Column 92: start tag was here
    …u/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/images/3801…
  • Error Line 365, Column 245: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DVDRip.XviD.iNT-cYnThiA  ><span class=poster_titles>Anna Karenina (2012)</span…
  • Error Line 365, Column 294: document type does not allow element "td" here
    …es>Anna Karenina (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 365, Column 311: 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 365, Column 322: 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 365, Column 388: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3800&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 365, Column 388: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3800&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 365, Column 388: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3800&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 365, Column 464: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/38000' alt="38000 / Comedy"   class=index_posters_big1 title=Two.Little.Boys…
  • Error Line 365, Column 489: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …edy"   class=index_posters_big1 title=Two.Little.Boys.2012.DVDRiP.AC3-NOGRP  >…
  • Error Line 365, Column 529: end tag for "img" omitted, but OMITTAG NO was specified
    …o.Little.Boys.2012.DVDRiP.AC3-NOGRP  ><span class=poster_titles>Two Little Boy…

    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 365, Column 392: start tag was here
    …u/torrents-details.php?id=3800&hit=1'><img  border='0'src='uploads/images/3800…
  • Error Line 365, Column 541: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.2012.DVDRiP.AC3-NOGRP  ><span class=poster_titles>Two Little Boys (2012)</sp…
  • Error Line 365, Column 592: document type does not allow element "td" here
    …>Two Little Boys (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 365, Column 609: 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 365, Column 620: 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 365, Column 686: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3799&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 365, Column 686: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3799&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 365, Column 686: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3799&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 365, Column 761: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …es/37990' alt="37990 / Drama"   class=index_posters_big1 title=Digging.To.Chin…
  • Error Line 365, Column 786: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ama"   class=index_posters_big1 title=Digging.To.China.1997.720p.BluRay.x264-R…
  • Error Line 365, Column 831: character "[" not allowed in attribute specification list
    ….To.China.1997.720p.BluRay.x264-ROUGH [PublicHD]  ><span class=poster_titles>D…
  • Error Line 365, Column 832: end tag for "img" omitted, but OMITTAG NO was specified
    …To.China.1997.720p.BluRay.x264-ROUGH [PublicHD]  ><span class=poster_titles>Di…

    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 365, Column 690: start tag was here
    …u/torrents-details.php?id=3799&hit=1'><img  border='0'src='uploads/images/3799…
  • Error Line 365, Column 856: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …y.x264-ROUGH [PublicHD]  ><span class=poster_titles>Digging to China (1997)</s…
  • Error Line 365, Column 908: document type does not allow element "td" here
    …Digging to China (1997)</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 365, Column 925: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …(1997)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 365, Column 936: 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 365, Column 1002: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3798&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 365, Column 1002: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3798&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 365, Column 1002: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3798&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 365, Column 1078: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/37980' alt="37980 / Comedy"   class=index_posters_big1 title=Afterglow.1997.…
  • Error Line 365, Column 1103: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …edy"   class=index_posters_big1 title=Afterglow.1997.720p.BluRay.x264-ROUGH [P…
  • Error Line 365, Column 1141: character "[" not allowed in attribute specification list
    …Afterglow.1997.720p.BluRay.x264-ROUGH [PublicHD]  ><span class=poster_titles>A…
  • Error Line 365, Column 1142: end tag for "img" omitted, but OMITTAG NO was specified
    …fterglow.1997.720p.BluRay.x264-ROUGH [PublicHD]  ><span class=poster_titles>Af…

    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 365, Column 1006: start tag was here
    …u/torrents-details.php?id=3798&hit=1'><img  border='0'src='uploads/images/3798…
  • Error Line 365, Column 1166: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …y.x264-ROUGH [PublicHD]  ><span class=poster_titles>Afterglow (1997)</span></a…
  • Error Line 365, Column 1211: document type does not allow element "td" here
    …titles>Afterglow (1997)</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 365, Column 1228: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …(1997)</span></a> <td>&nbsp;<td class=poster_area><a href='http://movietorrent…
  • Error Line 365, Column 1239: 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 365, Column 1305: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3797&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 365, Column 1305: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3797&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 365, Column 1305: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3797&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 365, Column 1382: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/37970' alt="37970 / Mystery"   class=index_posters_big1 title=The.Black.Box.2…
  • Error Line 365, Column 1407: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ery"   class=index_posters_big1 title=The.Black.Box.2005.720p.BluRay.x264-ROUG…
  • Error Line 365, Column 1449: character "[" not allowed in attribute specification list
    …Black.Box.2005.720p.BluRay.x264-ROUGH [PublicHD]  ><span class=poster_titles>L…
  • Error Line 365, Column 1450: end tag for "img" omitted, but OMITTAG NO was specified
    …lack.Box.2005.720p.BluRay.x264-ROUGH [PublicHD]  ><span class=poster_titles>La…

    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 365, Column 1309: start tag was here
    …u/torrents-details.php?id=3797&hit=1'><img  border='0'src='uploads/images/3797…
  • Error Line 365, Column 1474: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …y.x264-ROUGH [PublicHD]  ><span class=poster_titles>La boîte noire (2005)</sp…
  • Error Line 365, Column 1525: document type does not allow element "td" here
    …>La boîte noire (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 365, Column 1542: 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 365, Column 1553: 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 365, Column 1619: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3796&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 365, Column 1619: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3796&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 365, Column 1619: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3796&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 365, Column 1694: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …es/37960' alt="37960 / Drama"   class=index_posters_big1 title=Knife.Fight.201…
  • Error Line 365, Column 1719: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ama"   class=index_posters_big1 title=Knife.Fight.2012.UNRATED.720p.WEB-DL.H26…
  • Error Line 365, Column 1765: character "[" not allowed in attribute specification list
    …ght.2012.UNRATED.720p.WEB-DL.H264-NGB [PublicHD]  ><span class=poster_titles>K…
  • Error Line 365, Column 1766: end tag for "img" omitted, but OMITTAG NO was specified
    …ht.2012.UNRATED.720p.WEB-DL.H264-NGB [PublicHD]  ><span class=poster_titles>Kn…

    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 365, Column 1623: start tag was here
    …u/torrents-details.php?id=3796&hit=1'><img  border='0'src='uploads/images/3796…
  • Error Line 365, Column 1790: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-DL.H264-NGB [PublicHD]  ><span class=poster_titles>Knife Fight (2012)</span><…
  • Error Line 365, Column 1837: document type does not allow element "td" here
    …tles>Knife Fight (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 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1834: start tag was here
    …_titles>Knife Fight (2012)</span></a> <td>&nbsp;</table><table align=left clas…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1532: start tag was here
    …®te noire (2005)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1522: start tag was here
    …les>La boîte noire (2005)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1218: start tag was here
    …Afterglow (1997)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1208: start tag was here
    …er_titles>Afterglow (1997)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 915: start tag was here
    … to China (1997)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 905: start tag was here
    …es>Digging to China (1997)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 599: start tag was here
    …ttle Boys (2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 589: start tag was here
    …les>Two Little Boys (2012)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 301: start tag was here
    … Karenina (2012)</span></a> <td>&nbsp;<td class=poster_area><a href='http://mo…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 291: start tag was here
    …itles>Anna Karenina (2012)</span></a> <td>&nbsp;<td class=poster_area><a href=…
  • Error Line 365, Column 1851: end tag for "td" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1: start tag was here
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Error Line 365, Column 1851: end tag for "tr" omitted, but OMITTAG NO was specified
    …ht (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 365, Column 1: start tag was here
    <td class=poster_area><a href='http://movietorrents.eu/torrents-details.php?id=…
  • Error Line 365, Column 1865: 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 365, Column 1876: 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 365, Column 1894: 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 365, Column 1908: 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 365, Column 1916: 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 365, Column 1927: 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 365, Column 1951: 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 365, Column 1956: 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 366, 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 368, 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 368, Column 88: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3784&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 368, Column 88: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3784&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 368, Column 88: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3784&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 368, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ds/images/37840' alt=" / Drama" class=index_posters_big1 title=The.Master.2012…
  • Error Line 368, Column 181: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Drama" class=index_posters_big1 title=The.Master.2012.DVDRiP.AC3-5.1.XviD-AXED…
  • Error Line 368, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …aster.2012.DVDRiP.AC3-5.1.XviD-AXED  ><span class=poster_titles>The Master (20…

    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 368, Column 92: start tag was here
    …u/torrents-details.php?id=3784&hit=1'><img  border='0'src='uploads/images/3784…
  • Error Line 368, Column 236: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …VDRiP.AC3-5.1.XviD-AXED  ><span class=poster_titles>The Master (2012)</span></…
  • Error Line 368, Column 282: document type does not allow element "td" here
    …itles>The Master (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 368, Column 309: 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 368, Column 386: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3783&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 368, Column 386: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3783&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 368, Column 386: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3783&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 368, Column 454: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ds/images/37830' alt=" / Drama" class=index_posters_big1 title=The.Haunting.in…
  • Error Line 368, Column 479: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Drama" class=index_posters_big1 title=The.Haunting.in.Connecticut.2.Ghosts.of.…
  • Error Line 368, Column 559: end tag for "img" omitted, but OMITTAG NO was specified
    …orgia.2013.HDRip.XVID.AC3-AbSurdiTy  ><span class=poster_titles>The Haunting i…

    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 368, Column 390: start tag was here
    …u/torrents-details.php?id=3783&hit=1'><img  border='0'src='uploads/images/3783…
  • Error Line 368, Column 571: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DRip.XVID.AC3-AbSurdiTy  ><span class=poster_titles>The Haunting in Connecticu…
  • Error Line 368, Column 655: document type does not allow element "td" here
    …hosts of Georgia (2013)</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 368, Column 682: 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 368, Column 759: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3779&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 368, Column 759: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3779&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 368, Column 759: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3779&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 368, Column 831: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mages/37790' alt=" / Animation" class=index_posters_big1 title=Wreck.It.Ralph.…
  • Error Line 368, Column 856: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ation" class=index_posters_big1 title=Wreck.It.Ralph.2012.DVDSCR.XViD.AC3-LEGi…
  • Error Line 368, Column 901: end tag for "img" omitted, but OMITTAG NO was specified
    …t.Ralph.2012.DVDSCR.XViD.AC3-LEGi0N  ><span class=poster_titles>Wreck-It Ralph…

    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 368, Column 763: start tag was here
    …u/torrents-details.php?id=3779&hit=1'><img  border='0'src='uploads/images/3779…
  • Error Line 368, Column 913: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….DVDSCR.XViD.AC3-LEGi0N  ><span class=poster_titles>Wreck-It Ralph (2012)</spa…
  • Error Line 368, Column 963: document type does not allow element "td" here
    …s>Wreck-It Ralph (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 368, Column 990: 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 368, Column 1067: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3773&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 368, Column 1067: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3773&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 368, Column 1067: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3773&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 368, Column 1135: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ds/images/37730' alt=" / Drama" class=index_posters_big1 title=Argo.(2012).720…
  • Error Line 368, Column 1160: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Drama" class=index_posters_big1 title=Argo.(2012).720p.BrRip.x264-YIFY  ><span…
  • Error Line 368, Column 1165: an attribute value must be a literal unless it contains only name characters
    …" class=index_posters_big1 title=Argo.(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 368, Column 1195: end tag for "img" omitted, but OMITTAG NO was specified
    …le=Argo.(2012).720p.BrRip.x264-YIFY  ><span class=poster_titles>Argo (2012)</s…

    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 368, Column 1071: start tag was here
    …u/torrents-details.php?id=3773&hit=1'><img  border='0'src='uploads/images/3773…
  • Error Line 368, Column 1207: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2).720p.BrRip.x264-YIFY  ><span class=poster_titles>Argo (2012)</span></a> <td…
  • Error Line 368, Column 1247: document type does not allow element "td" here
    …ster_titles>Argo (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 368, Column 1274: 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 368, Column 1351: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3772&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 368, Column 1351: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3772&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 368, Column 1351: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3772&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 368, Column 1420: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/37720' alt=" / Action" class=index_posters_big1 title=Gangster.Squad.…
  • Error Line 368, Column 1445: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ction" class=index_posters_big1 title=Gangster.Squad.2013.R6.HDRiP.XVID-1MPERi…
  • Error Line 368, Column 1490: end tag for "img" omitted, but OMITTAG NO was specified
    …r.Squad.2013.R6.HDRiP.XVID-1MPERiUM  ><span class=poster_titles>Gangster Squad…

    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 368, Column 1355: start tag was here
    …u/torrents-details.php?id=3772&hit=1'><img  border='0'src='uploads/images/3772…
  • Error Line 368, Column 1502: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….R6.HDRiP.XVID-1MPERiUM  ><span class=poster_titles>Gangster Squad (2013)</spa…
  • Error Line 368, Column 1552: document type does not allow element "td" here
    …s>Gangster Squad (2013)</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 368, Column 1579: 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 368, Column 1656: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=3762&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 368, Column 1656: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=3762&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 368, Column 1656: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=3762&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 368, Column 1725: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s/images/37620' alt=" / Comedy" class=index_posters_big1 title=The.Coalition.[…
  • Error Line 368, Column 1750: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …omedy" class=index_posters_big1 title=The.Coalition.[2013].BRRip.720p.H264-ETR…
  • Error Line 368, Column 1764: an attribute value must be a literal unless it contains only name characters
    …ndex_posters_big1 title=The.Coalition.[2013].BRRip.720p.H264-ETRG  ><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 368, Column 1794: end tag for "img" omitted, but OMITTAG NO was specified
    …alition.[2013].BRRip.720p.H264-ETRG  ><span class=poster_titles>The Coalition …

    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 368, Column 1660: start tag was here
    …u/torrents-details.php?id=3762&hit=1'><img  border='0'src='uploads/images/3762…
  • Error Line 368, Column 1806: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3].BRRip.720p.H264-ETRG  ><span class=poster_titles>The Coalition (2013)</span…
  • Error Line 368, Column 1855: document type does not allow element "td" here
    …es>The Coalition (2013)</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 368, Column 1879: 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 367, Column 1: start tag was here
    <tr>
  • Error Line 368, Column 1893: 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 368, Column 1904: 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 368, Column 1922: 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 368, Column 1936: 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 368, Column 1944: 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 368, Column 1955: 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 368, Column 1979: 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 368, Column 1984: 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 369, 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 371, 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 371, 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 371, 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 371, 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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 371, 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 371, 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 371, 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 371, Column 92: start tag was here
    …u/torrents-details.php?id=1740&hit=1'><img  border='0'src='uploads/images/1740…
  • Error Line 371, 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 371, 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 371, 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 371, 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 371, 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 371, 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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 371, 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 371, 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 371, 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 371, 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 371, Column 389: start tag was here
    …u/torrents-details.php?id=1569&hit=1'><img  border='0'src='uploads/images/1569…
  • Error Line 371, 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 371, 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 371, 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 371, 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 371, 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 371, 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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 371, 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 371, 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 371, 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 371, Column 699: start tag was here
    …u/torrents-details.php?id=1898&hit=1'><img  border='0'src='uploads/images/1898…
  • Error Line 371, 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 371, 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 371, 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 371, 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 371, 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 371, 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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 371, 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 371, 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 371, 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 371, Column 1003: start tag was here
    …u/torrents-details.php?id=2746&hit=1'><img  border='0'src='uploads/images/2746…
  • Error Line 371, 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 371, 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 371, 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 371, Column 1295: 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 371, Column 1295: 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 371, Column 1295: 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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 371, Column 1367: 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 371, Column 1392: 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 371, Column 1405: "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 371, Column 1410: "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 371, Column 1420: 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 371, Column 1299: start tag was here
    …eu/torrents-details.php?id=757&hit=1'><img  border='0'src='uploads/images/7570…
  • Error Line 371, Column 1432: 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 371, Column 1488: document type does not allow element "td" here
    …y, Stupid, Love. (2011)</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 371, Column 1515: 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 371, Column 1592: reference not terminated by REFC delimiter
    …ts.eu/torrents-details.php?id=2092&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 371, Column 1592: reference to external entity in attribute value
    …ts.eu/torrents-details.php?id=2092&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 371, Column 1592: reference to entity "hit" for which no system identifier could be generated
    …ts.eu/torrents-details.php?id=2092&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 365, Column 84: entity was defined here
    …rrents.eu/torrents-details.php?id=3801&hit=1'><img  border='0'src='uploads/ima…
  • Error Line 371, Column 1660: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ds/images/20920' alt=" / Drama" class=index_posters_big1 title=Barfi.(2012).DV…
  • Error Line 371, Column 1685: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Drama" class=index_posters_big1 title=Barfi.(2012).DVDscr.Rip.1CD.XviD.[DDR-Ex…
  • Error Line 371, Column 1691: an attribute value must be a literal unless it contains only name characters
    … class=index_posters_big1 title=Barfi.(2012).DVDscr.Rip.1CD.XviD.[DDR-Exclusiv…

    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 371, Column 1737: end tag for "img" omitted, but OMITTAG NO was specified
    …VDscr.Rip.1CD.XviD.[DDR-Exclusive]   ><span class=poster_titles>Barfi! (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 371, Column 1596: start tag was here
    …u/torrents-details.php?id=2092&hit=1'><img  border='0'src='uploads/images/2092…
  • Error Line 371, Column 1749: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …D.XviD.[DDR-Exclusive]   ><span class=poster_titles>Barfi! (2012)</span></a> <…
  • Error Line 371, Column 1791: document type does not allow element "td" here
    …er_titles>Barfi! (2012)</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 371, Column 1815: end tag for "tr" omitted, but OMITTAG NO was specified
    …titles>Barfi! (2012)</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 370, Column 1: start tag was here
    <tr>
  • Error Line 371, Column 1834: end tag for element "td" which is not open
    …titles>Barfi! (2012)</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 373, 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 375, 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 377, 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 384, 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 392, 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 398, 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 398, Column 26: start tag was here
    <center><span> Community <br></span></center>
  • Warning Line 402, 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 402, 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 402, 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 402, 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 402, 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 402, Column 74: entity was defined here
    …ontact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='C…
  • Warning Line 402, 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 402, 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 402, 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 402, Column 74: entity was defined here
    …ontact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='C…
  • Error Line 402, 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 404, 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 406, 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 410, 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 395, Column 13: start tag was here
                <td>&nbsp;<div class="our_friends">
  • Error Line 410, 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 394, Column 9: start tag was here
            <tr>
  • Error Line 410, 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 393, Column 5: start tag was here
        <tbody>
  • Error Line 410, 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 392, Column 1: start tag was here
    <table align="center" width="940" height="250" border="0">
  • Error Line 410, 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 411, 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 414, 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 414, Column 35: start tag was here
    <center><span> Sites we recommend <br></span></center>
  • Error Line 417, Column 171: required attribute "alt" not specified
    …iends/swesub.png' class='favicons' width='16' height='16' />&nbsp;Swesub.tv</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 420, 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 423, 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 430, 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 432, 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 432, 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 432, 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 432, 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 432, 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 432, 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 434, 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 435, 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 436, 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 440, 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 440, Column 1: start tag was here
    <br>
  • Error Line 442, 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 445, 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 450, 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 450, 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 451, 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.950 visits
Daily Visitor