Swesub.tv är Sveriges största sida för svensktextade filmer och tv-serier, ladda ner tusentals filmer och tv-serier helt gratis. ...

swesub.tv
  • Domain Name
    swesub.tv
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #21866
  • Page Size
    34.4 KB
  • Ip Address
    31.7.56.90
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 24 JPG, 1 PNG

Website Meta Analysis

  • Title
    Swesub.tv - Ladda ner swesub filmer och tv-serier gratis
  • Meta Keyword
    swesub, ladda ner filmer, laste ner film, swesub filmer, swesub tv-serier, gratis filmer, tankaner, tankafetast, undertexter, senaste filmer, svensktextade filmer, 2012 filmer
  • Meta Description
    Swesub.tv är Sveriges största sida för svensktextade filmer och tv-serier, ladda ner tusentals filmer och tv-serier helt gratis.

Technical Analysis

  • Webserver
    nginx admin
  • Ip Address
    31.7.56.90
  • Domain Age
    4 Years, 3 Months, 25 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx admin
  • date: Wed, 07 Aug 2013 22:21:14 GMT
  • content-type: text/html;charset=iso-8859-1
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.10
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • last-modified: Wed, 07 Aug 2013 22:21:14 GMT
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for swesub.tv

DNS Analysis


DNS servers
ns2.he.net [216.218.131.2]
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
swesub.tv NS  ns2.he.net 3600s
swesub.tv SOA
server: ns1.he.net
email: hostmaster@he.net
serial: 2012062322
refresh: 10800
retry: 1800
expire: 604800
minimum ttl: 86400
86400s
swesub.tv NS  ns3.he.net 3600s
swesub.tv NS  ns4.he.net 3600s
swesub.tv MX
preference: 0
exchange: swesub.tv
3600s
swesub.tv NS  ns1.he.net 3600s
swesub.tv NS  ns5.he.net 3600s
swesub.tv A 31.7.56.90 3600s

Authority records

Additional records
ns3.he.net 28 [16 bytes] 86400s
ns5.he.net A 216.66.80.18 86400s
ns2.he.net 28 [16 bytes] 86400s
ns1.he.net A 216.218.130.2 86400s
ns3.he.net A 216.218.132.2 86400s
ns5.he.net 28 [16 bytes] 86400s
ns4.he.net A 216.66.1.2 86400s
ns2.he.net A 216.218.131.2 86400s
ns4.he.net 28 [16 bytes] 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
  • 404 Errors
  • 146 Warnings
Ratio Text/Html
  • 0.7396369008722334
Message Error
  • Error Line 5, Column 12: there is no attribute "NAME"
    <META NAME="Keywords" CONTENT="swesub, ladda ner filmer, laste ner film, swesub…

    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="swesub, ladda ner filmer, laste ner film, swesub…

    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 208: element "META" undefined
    …, tankafetast, undertexter, senaste filmer, svensktextade filmer, 2012 filmer">

    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 164: element "META" undefined
    … filmer och tv-serier, ladda ner tusentals filmer och tv-serier helt gratis."> 

    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 42, 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="Swesub.tv är Sveriges största sida för svensk…
  • Error Line 42, 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="swesub, ladda ner filmer, laste ner film, swesub…
  • Error Line 44, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br> <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 44, Column 1: start tag was here
    <br> <br> 
  • Error Line 44, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    <br> <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 44, Column 6: start tag was here
    <br> <br> 
  • Error Line 47, Column 7: document type does not allow element "td" here; assuming missing "tr" start-tag
    	 <td >
  • Error Line 50, Column 30: there is no attribute "border"
    				<td align="right" 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 56, 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 47, Column 3: start tag was here
    	 <td >
  • Error Line 64, Column 27: document type does not allow element "td" here; assuming missing "tr" start-tag
                <td border="0">
  • Error Line 66, Column 15: there is no attribute "WIDTH"
    <IFRAME WIDTH="160" HEIGHT="600" SCROLLING="No" FRAMEBORDER="0" MARGINHEIGHT="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 66, Column 28: there is no attribute "HEIGHT"
    <IFRAME WIDTH="160" HEIGHT="600" SCROLLING="No" FRAMEBORDER="0" MARGINHEIGHT="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 66, Column 44: there is no attribute "SCROLLING"
    …ME WIDTH="160" HEIGHT="600" SCROLLING="No" FRAMEBORDER="0" MARGINHEIGHT="0" MA…

    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 66, Column 61: there is no attribute "FRAMEBORDER"
    …IGHT="600" SCROLLING="No" FRAMEBORDER="0" MARGINHEIGHT="0" MARGINWIDTH="0" SRC…

    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 66, Column 78: there is no attribute "MARGINHEIGHT"
    …ING="No" FRAMEBORDER="0" MARGINHEIGHT="0" MARGINWIDTH="0" SRC="http://imp.cdns…

    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 66, Column 94: there is no attribute "MARGINWIDTH"
    …RDER="0" MARGINHEIGHT="0" MARGINWIDTH="0" SRC="http://imp.cdnspstr.com/adifram…

    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 66, Column 102: there is no attribute "SRC"
    … MARGINHEIGHT="0" MARGINWIDTH="0" SRC="http://imp.cdnspstr.com/adiframe/3.0/11…

    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 66, Column 220: element "IFRAME" undefined
    …b1=Swesub;sub2=;sub3=;sub4=;;rdclick="><script language="javascript" src="http…

    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 66, Column 378: required attribute "type" not specified
    …b1=Swesub;sub2=;sub3=;sub4=;;rdclick="></script><noscript><a href="http://imp.…

    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 66, Column 670: required attribute "alt" not specified
    …ub2=;sub3=;sub4=;" border="0" width="160" height="600"></a></noscript></IFRAME>

    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 66, Column 674: end tag for "img" omitted, but OMITTAG NO was specified
    …ub2=;sub3=;sub4=;" border="0" width="160" height="600"></a></noscript></IFRAME>

    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 66, Column 524: start tag was here
    …b;sub2=;sub3=;sub4=;" target="_blank"><img src="http://imp.cdnspstr.com/adserv…
  • Error Line 71, 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 64, Column 13: start tag was here
                <td border="0">
  • Error Line 86, 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 86, Column 1: start tag was here
    <br> 
  • Error Line 88, Column 134: required attribute "alt" not specified
    …mes/default/images/logo.gif" class="logo" width="222" height="39" border="0" />

    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 89, Column 67: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … 	  <div align='right' style=" margin-right:10px;  border:0px;"></script></div>

    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 89, Column 76: end tag for element "script" which is not open
    … 	  <div align='right' style=" margin-right:10px;  border:0px;"></script></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 99, Column 37: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div id="searchwrapper"><div  class=indexmenu2>
  • Error Line 109, Column 8: end tag for "br" omitted, but OMITTAG NO was specified
    	  <br><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 109, Column 4: start tag was here
    	  <br><br>
  • Error Line 109, Column 12: end tag for "br" omitted, but OMITTAG NO was specified
    	  <br><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 109, Column 8: start tag was here
    	  <br><br>
  • Error Line 115, Column 85: "if" is not a reserved name
    …ent_cat=Film"><span>FILMER +</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 115, Column 104: "endif" is not a reserved name
    …>FILMER +</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 117, Column 83: document type does not allow element "div" here; assuming missing "li" start-tag
    …ss="Meniui"><a href="torrents.php?cat=49">action</a></li><div class="hr"></div>
  • Error Line 118, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=55">komedi</a></li><div class="h…

    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 119, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=52">drama</a></li><div class="hr…

    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 120, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=54">fantasy</a></li><div class="…

    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 121, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=50">animerat</a></li><div class=…

    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 122, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=60">skräck</a></li><div class="h…

    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 123, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=58">romantik</a></li><div class=…

    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 124, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=61">sci-fi</a></li><div class="h…

    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 125, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=64">thriller</a></li><div class=…

    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 126, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=56">krig</a></li><div class="hr"…

    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 127, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=59">äventyr</a></li><div class="…

    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 128, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=65">western</a></li><div class="…

    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 129, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=62">sport</a></li><div class="hr…

    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 130, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=68">musikal</a></li><div class="…

    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 131, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=57">kriminal</a></li><div class=…

    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 132, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=53">familj</a></li><div class="h…

    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 133, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=51">dokumentär</a></li><div clas…

    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 134, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=67">dans</a></li><div class="hr"…

    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 135, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=104">3d</a></li><div class="hr">…

    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 136, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt…

    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 136, Column 66: cannot generate system identifier for general entity "cat"
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</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 136, Column 66: general entity "cat" not defined and no default entity
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</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 136, Column 69: reference not terminated by REFC delimiter
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</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 136, Column 69: reference to external entity in attribute value
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</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 136, Column 69: reference to entity "cat" for which no system identifier could be generated
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</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 136, Column 65: entity was defined here
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</a></li>
  • Error Line 138, 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 117, Column 68: start tag was here
    …ss="Meniui"><a href="torrents.php?cat=49">action</a></li><div class="hr"></div>
  • Error Line 140, Column 92: "if" is not a reserved name
    …=Tv-serie"><span>TV-SERIER +</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 140, Column 111: "endif" is not a reserved name
    …-SERIER +</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 142, Column 82: document type does not allow element "div" here; assuming missing "li" start-tag
    …ss="Meniui"><a href="torrents.php?cat=77">action</a></li><div class="hr"></div>
  • Error Line 143, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=69">komedi</a></li><div class="h…

    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 144, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=73">drama</a></li><div class="hr…

    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 145, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=80">fantasy</a></li><div class="…

    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 146, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=82">animerat</a></li><div class=…

    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 147, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=79">skräck</a></li><div class="h…

    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 148, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=75">sci-fi</a></li><div class="h…

    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 149, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=76">thriller</a></li><div class=…

    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 150, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=94">krig</a></li><div class="hr"…

    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 151, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=74">äventyr</a></li><div class="…

    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 152, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=81">kriminal</a></li><div class=…

    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 153, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=101">familj</a></li><div class="…

    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 154, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents.php?cat=103">dokumentär</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 155, 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 142, Column 67: start tag was here
    …ss="Meniui"><a href="torrents.php?cat=77">action</a></li><div class="hr"></div>
  • Error Line 157, Column 50: "if" is not a reserved name
    …"Meniui0"><a><span>kvalité +</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 157, Column 69: "endif" is not a reserved name
    …kvalité +</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Warning Line 159, Column 65: cannot generate system identifier for general entity "x"
    …ef="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr">…

    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 159, Column 65: general entity "x" not defined and no default entity
    …ef="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr">…

    This is usually a cascading error caused by 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 159, Column 66: reference not terminated by REFC delimiter
    …f="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"><…

    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 159, Column 66: reference to external entity in attribute value
    …f="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"><…

    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 159, Column 66: reference to entity "x" for which no system identifier could be generated
    …f="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"><…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 159, Column 69: cannot generate system identifier for general entity "y"
    …torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></di…

    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 159, Column 69: general entity "y" not defined and no default entity
    …torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></di…

    This is usually a cascading error caused by 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 159, Column 70: reference not terminated by REFC delimiter
    …orrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></div…

    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 159, Column 70: reference to external entity in attribute value
    …orrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></div…

    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 159, Column 70: reference to entity "y" for which no system identifier could be generated
    …orrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></div…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 159, Column 104: document type does not allow element "div" here; assuming missing "li" start-tag
    …orrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></div>
  • Error Line 160, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=brrip&x=0&y=0">BRRip</…

    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 160, Column 65: reference not terminated by REFC delimiter
    …ef="torrents-search.php?search=brrip&x=0&y=0">BRRip</a></li><div class="hr"></…

    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 160, Column 65: reference to external entity in attribute value
    …ef="torrents-search.php?search=brrip&x=0&y=0">BRRip</a></li><div class="hr"></…

    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 160, Column 65: reference to entity "x" for which no system identifier could be generated
    …ef="torrents-search.php?search=brrip&x=0&y=0">BRRip</a></li><div class="hr"></…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 160, Column 69: reference not terminated by REFC delimiter
    …"torrents-search.php?search=brrip&x=0&y=0">BRRip</a></li><div class="hr"></div>

    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 160, Column 69: reference to external entity in attribute value
    …"torrents-search.php?search=brrip&x=0&y=0">BRRip</a></li><div class="hr"></div>

    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 160, Column 69: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=brrip&x=0&y=0">BRRip</a></li><div class="hr"></div>

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 161, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=bdrip&x=0&y=0">BDRip</…

    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 161, Column 65: reference not terminated by REFC delimiter
    …ef="torrents-search.php?search=bdrip&x=0&y=0">BDRip</a></li><div class="hr"></…

    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 161, Column 65: reference to external entity in attribute value
    …ef="torrents-search.php?search=bdrip&x=0&y=0">BDRip</a></li><div class="hr"></…

    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 161, Column 65: reference to entity "x" for which no system identifier could be generated
    …ef="torrents-search.php?search=bdrip&x=0&y=0">BDRip</a></li><div class="hr"></…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 161, Column 69: reference not terminated by REFC delimiter
    …"torrents-search.php?search=bdrip&x=0&y=0">BDRip</a></li><div class="hr"></div>

    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 161, Column 69: reference to external entity in attribute value
    …"torrents-search.php?search=bdrip&x=0&y=0">BDRip</a></li><div class="hr"></div>

    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 161, Column 69: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=bdrip&x=0&y=0">BDRip</a></li><div class="hr"></div>

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 162, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=720p&cat=0">HD 720p</a…

    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 162, Column 66: reference not terminated by REFC delimiter
    …f="torrents-search.php?search=720p&cat=0">HD 720p</a></li><div class="hr"></di…

    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 162, Column 66: reference to external entity in attribute value
    …f="torrents-search.php?search=720p&cat=0">HD 720p</a></li><div class="hr"></di…

    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 162, Column 66: reference to entity "cat" for which no system identifier could be generated
    …f="torrents-search.php?search=720p&cat=0">HD 720p</a></li><div class="hr"></di…

    This is usually a cascading error caused by 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 136, Column 65: entity was defined here
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</a></li>
  • Error Line 163, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=1080p&cat=0">HD 1080p<…

    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 163, Column 67: reference not terminated by REFC delimiter
    …="torrents-search.php?search=1080p&cat=0">HD 1080p</a></li><div class="hr"></d…

    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 163, Column 67: reference to external entity in attribute value
    …="torrents-search.php?search=1080p&cat=0">HD 1080p</a></li><div class="hr"></d…

    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 163, Column 67: reference to entity "cat" for which no system identifier could be generated
    …="torrents-search.php?search=1080p&cat=0">HD 1080p</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 136, Column 65: entity was defined here
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</a></li>
  • Error Line 164, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=r5&cat=0">R5</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>").

  • Warning Line 164, Column 64: reference not terminated by REFC delimiter
    …<a href="torrents-search.php?search=r5&cat=0">R5</a></li><div class="hr"></div>

    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 164, Column 64: reference to external entity in attribute value
    …<a href="torrents-search.php?search=r5&cat=0">R5</a></li><div class="hr"></div>

    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 164, Column 64: reference to entity "cat" for which no system identifier could be generated
    …<a href="torrents-search.php?search=r5&cat=0">R5</a></li><div class="hr"></div>

    This is usually a cascading error caused by 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 136, Column 65: entity was defined here
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</a></li>
  • Error Line 165, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=dvdscr&cat=0">DVDscr</…

    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 165, Column 68: reference not terminated by REFC delimiter
    …"torrents-search.php?search=dvdscr&cat=0">DVDscr</a></li><div class="hr"></div…

    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 165, Column 68: reference to external entity in attribute value
    …"torrents-search.php?search=dvdscr&cat=0">DVDscr</a></li><div class="hr"></div…

    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 165, Column 68: reference to entity "cat" for which no system identifier could be generated
    …"torrents-search.php?search=dvdscr&cat=0">DVDscr</a></li><div class="hr"></div…

    This is usually a cascading error caused by 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 136, Column 65: entity was defined here
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</a></li>
  • Error Line 166, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="torrents-search.php?search=bluray&cat=0">Bluray</…

    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 166, Column 68: reference not terminated by REFC delimiter
    …"torrents-search.php?search=bluray&cat=0">Bluray</a></li><div class="hr"></div…

    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 166, Column 68: reference to external entity in attribute value
    …"torrents-search.php?search=bluray&cat=0">Bluray</a></li><div class="hr"></div…

    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 166, Column 68: reference to entity "cat" for which no system identifier could be generated
    …"torrents-search.php?search=bluray&cat=0">Bluray</a></li><div class="hr"></div…

    This is usually a cascading error caused by 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 136, Column 65: entity was defined here
    …Meniui"><a href="torrents-search.php?search=swedish&cat=0">svenskt tal</a></li>
  • Error Line 169, 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 159, Column 89: start tag was here
    …orrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></div>
  • Error Line 171, Column 55: "if" is not a reserved name
    …ui0"><a><span>utgivningsår +</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 171, Column 74: "endif" is not a reserved name
    …ningsår +</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 173, Column 54: document type does not allow element "table" here; assuming missing "li" start-tag
    		<table  border="0"  cellpadding="2" cellspacing="0">
  • Error Line 176, Column 21: 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=2013&x=0&y=0">2013</a>…

    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 176, Column 64: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2013&x=0&y=0">2013</a></li><div class="hr"></d…

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

  • Warning Line 176, Column 64: reference to external entity in attribute value
    …ref="torrents-search.php?search=2013&x=0&y=0">2013</a></li><div class="hr"></d…

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

  • Error Line 176, Column 64: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2013&x=0&y=0">2013</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 176, Column 68: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2013&x=0&y=0">2013</a></li><div class="hr"></div><…

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

  • Warning Line 176, Column 68: reference to external entity in attribute value
    …"torrents-search.php?search=2013&x=0&y=0">2013</a></li><div class="hr"></div><…

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

  • Error Line 176, Column 68: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2013&x=0&y=0">2013</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 177, 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 177, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2012&x=0&y=0">2012</a></li><div class="hr"></d…

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

  • Warning Line 177, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2012&x=0&y=0">2012</a></li><div class="hr"></d…

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

  • Error Line 177, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2012&x=0&y=0">2012</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 177, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2012&x=0&y=0">2012</a></li><div class="hr"></div><…

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

  • Warning Line 177, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2012&x=0&y=0">2012</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 178, 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 178, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2011&x=0&y=0">2011</a></li><div class="hr"></d…

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

  • Warning Line 178, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2011&x=0&y=0">2011</a></li><div class="hr"></d…

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

  • Error Line 178, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2011&x=0&y=0">2011</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 178, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2011&x=0&y=0">2011</a></li><div class="hr"></div><…

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

  • Warning Line 178, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2011&x=0&y=0">2011</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 179, 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 179, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2010&x=0&y=0">2010</a></li><div class="hr"></d…

    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 179, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2010&x=0&y=0">2010</a></li><div class="hr"></d…

    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 179, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2010&x=0&y=0">2010</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 179, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2010&x=0&y=0">2010</a></li><div class="hr"></div><…

    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 179, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2010&x=0&y=0">2010</a></li><div class="hr"></div><…

    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 179, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2010&x=0&y=0">2010</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 180, 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 180, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2009&x=0&y=0">2009</a></li><div class="hr"></d…

    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 180, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2009&x=0&y=0">2009</a></li><div class="hr"></d…

    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 180, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2009&x=0&y=0">2009</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 180, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2009&x=0&y=0">2009</a></li><div class="hr"></div><…

    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 180, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2009&x=0&y=0">2009</a></li><div class="hr"></div><…

    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 180, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2009&x=0&y=0">2009</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 184, 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 184, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2008&x=0&y=0">2008</a></li><div class="hr"></d…

    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 184, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2008&x=0&y=0">2008</a></li><div class="hr"></d…

    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 184, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2008&x=0&y=0">2008</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 184, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2008&x=0&y=0">2008</a></li><div class="hr"></div><…

    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 184, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2008&x=0&y=0">2008</a></li><div class="hr"></div><…

    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 184, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2008&x=0&y=0">2008</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 185, 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 185, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2007&x=0&y=0">2007</a></li><div class="hr"></d…

    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 185, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2007&x=0&y=0">2007</a></li><div class="hr"></d…

    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 185, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2007&x=0&y=0">2007</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 185, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2007&x=0&y=0">2007</a></li><div class="hr"></div><…

    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 185, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2007&x=0&y=0">2007</a></li><div class="hr"></div><…

    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 185, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2007&x=0&y=0">2007</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 186, 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 186, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2006&x=0&y=0">2006</a></li><div class="hr"></d…

    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 186, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2006&x=0&y=0">2006</a></li><div class="hr"></d…

    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 186, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2006&x=0&y=0">2006</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 186, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2006&x=0&y=0">2006</a></li><div class="hr"></div><…

    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 186, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2006&x=0&y=0">2006</a></li><div class="hr"></div><…

    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 186, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2006&x=0&y=0">2006</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 187, 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 187, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2005&x=0&y=0">2005</a></li><div class="hr"></d…

    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 187, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2005&x=0&y=0">2005</a></li><div class="hr"></d…

    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 187, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2005&x=0&y=0">2005</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 187, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2005&x=0&y=0">2005</a></li><div class="hr"></div><…

    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 187, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2005&x=0&y=0">2005</a></li><div class="hr"></div><…

    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 187, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=2005&x=0&y=0">2005</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 188, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 188, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2004&x=0&y=0">2004</a></li><div class="hr"></d…

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

  • Warning Line 188, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2004&x=0&y=0">2004</a></li><div class="hr"></d…

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

  • Error Line 188, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2004&x=0&y=0">2004</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 188, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2004&x=0&y=0">2004</a></li><div class="hr"></div><…

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

  • Warning Line 188, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2004&x=0&y=0">2004</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 193, 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 196, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 196, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2003&x=0&y=0">2003</a></li><div class="hr"></d…

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

  • Warning Line 196, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2003&x=0&y=0">2003</a></li><div class="hr"></d…

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

  • Error Line 196, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2003&x=0&y=0">2003</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 196, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2003&x=0&y=0">2003</a></li><div class="hr"></div><…

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

  • Warning Line 196, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2003&x=0&y=0">2003</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 197, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 197, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2002&x=0&y=0">2002</a></li><div class="hr"></d…

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

  • Warning Line 197, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2002&x=0&y=0">2002</a></li><div class="hr"></d…

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

  • Error Line 197, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2002&x=0&y=0">2002</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 197, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2002&x=0&y=0">2002</a></li><div class="hr"></div><…

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

  • Warning Line 197, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2002&x=0&y=0">2002</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 198, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 198, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2001&x=0&y=0">2001</a></li><div class="hr"></d…

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

  • Warning Line 198, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2001&x=0&y=0">2001</a></li><div class="hr"></d…

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

  • Error Line 198, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2001&x=0&y=0">2001</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 198, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2001&x=0&y=0">2001</a></li><div class="hr"></div><…

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

  • Warning Line 198, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2001&x=0&y=0">2001</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 199, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 199, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=2000&x=0&y=0">2000</a></li><div class="hr"></d…

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

  • Warning Line 199, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=2000&x=0&y=0">2000</a></li><div class="hr"></d…

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

  • Error Line 199, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=2000&x=0&y=0">2000</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 199, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=2000&x=0&y=0">2000</a></li><div class="hr"></div><…

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

  • Warning Line 199, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=2000&x=0&y=0">2000</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 200, Column 17: 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">1999</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>").

  • Warning Line 200, Column 60: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1999&x=0&y=0">1999</a></li><div class="hr"></d…

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

  • Warning Line 200, Column 60: reference to external entity in attribute value
    …ref="torrents-search.php?search=1999&x=0&y=0">1999</a></li><div class="hr"></d…

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

  • Error Line 200, Column 60: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1999&x=0&y=0">1999</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 200, Column 64: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1999&x=0&y=0">1999</a></li><div class="hr"></div><…

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

  • Warning Line 200, Column 64: reference to external entity in attribute value
    …"torrents-search.php?search=1999&x=0&y=0">1999</a></li><div class="hr"></div><…

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

  • Error Line 200, Column 64: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=1999&x=0&y=0">1999</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 205, 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 205, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1998&x=0&y=0">1998</a></li><div class="hr"></d…

    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 205, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1998&x=0&y=0">1998</a></li><div class="hr"></d…

    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 205, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1998&x=0&y=0">1998</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 205, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1998&x=0&y=0">1998</a></li><div class="hr"></div><…

    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 205, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=1998&x=0&y=0">1998</a></li><div class="hr"></div><…

    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 205, Column 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=1998&x=0&y=0">1998</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 206, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 206, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1997&x=0&y=0">1997</a></li><div class="hr"></d…

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

  • Warning Line 206, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1997&x=0&y=0">1997</a></li><div class="hr"></d…

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

  • Error Line 206, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1997&x=0&y=0">1997</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 206, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1997&x=0&y=0">1997</a></li><div class="hr"></div><…

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

  • Warning Line 206, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=1997&x=0&y=0">1997</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 207, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 207, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1996&x=0&y=0">1996</a></li><div class="hr"></d…

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

  • Warning Line 207, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1996&x=0&y=0">1996</a></li><div class="hr"></d…

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

  • Error Line 207, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1996&x=0&y=0">1996</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 207, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1996&x=0&y=0">1996</a></li><div class="hr"></div><…

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

  • Warning Line 207, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=1996&x=0&y=0">1996</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 208, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 208, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1995&x=0&y=0">1995</a></li><div class="hr"></d…

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

  • Warning Line 208, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1995&x=0&y=0">1995</a></li><div class="hr"></d…

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

  • Error Line 208, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1995&x=0&y=0">1995</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 208, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1995&x=0&y=0">1995</a></li><div class="hr"></div><…

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

  • Warning Line 208, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=1995&x=0&y=0">1995</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 209, Column 17: 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">1994</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>").

  • Warning Line 209, Column 60: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1994&x=0&y=0">1994</a></li><div class="hr"></d…

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

  • Warning Line 209, Column 60: reference to external entity in attribute value
    …ref="torrents-search.php?search=1994&x=0&y=0">1994</a></li><div class="hr"></d…

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

  • Error Line 209, Column 60: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1994&x=0&y=0">1994</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 209, Column 64: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1994&x=0&y=0">1994</a></li><div class="hr"></div><…

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

  • Warning Line 209, Column 64: reference to external entity in attribute value
    …"torrents-search.php?search=1994&x=0&y=0">1994</a></li><div class="hr"></div><…

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

  • Error Line 209, Column 64: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=1994&x=0&y=0">1994</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 214, 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 217, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 217, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1993&x=0&y=0">1993</a></li><div class="hr"></d…

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

  • Warning Line 217, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1993&x=0&y=0">1993</a></li><div class="hr"></d…

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

  • Error Line 217, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1993&x=0&y=0">1993</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 217, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1993&x=0&y=0">1993</a></li><div class="hr"></div><…

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

  • Warning Line 217, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=1993&x=0&y=0">1993</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 218, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                <td>&nbsp;<li><a href="torrents-search.php?search=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 218, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1992&x=0&y=0">1992</a></li><div class="hr"></d…

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

  • Warning Line 218, Column 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1992&x=0&y=0">1992</a></li><div class="hr"></d…

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

  • Error Line 218, Column 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1992&x=0&y=0">1992</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 218, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1992&x=0&y=0">1992</a></li><div class="hr"></div><…

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

  • Warning Line 218, Column 73: reference to external entity in attribute value
    …"torrents-search.php?search=1992&x=0&y=0">1992</a></li><div class="hr"></div><…

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

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

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 219, 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 219, Column 69: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1991&x=0&y=0">1991</a></li><div class="hr"></d…

    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 69: reference to external entity in attribute value
    …ref="torrents-search.php?search=1991&x=0&y=0">1991</a></li><div class="hr"></d…

    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 69: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1991&x=0&y=0">1991</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 219, Column 73: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1991&x=0&y=0">1991</a></li><div class="hr"></div><…

    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 73: reference to external entity in attribute value
    …"torrents-search.php?search=1991&x=0&y=0">1991</a></li><div class="hr"></div><…

    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 73: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=1991&x=0&y=0">1991</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 220, Column 17: 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">1990</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>").

  • Warning Line 220, Column 60: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1994&x=0&y=0">1990</a></li><div class="hr"></d…

    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 60: reference to external entity in attribute value
    …ref="torrents-search.php?search=1994&x=0&y=0">1990</a></li><div class="hr"></d…

    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 60: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1994&x=0&y=0">1990</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 220, Column 64: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1994&x=0&y=0">1990</a></li><div class="hr"></div><…

    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 64: reference to external entity in attribute value
    …"torrents-search.php?search=1994&x=0&y=0">1990</a></li><div class="hr"></div><…

    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 64: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=1994&x=0&y=0">1990</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 221, Column 17: 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=1989&x=0&y=0">1989</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>").

  • Warning Line 221, Column 60: reference not terminated by REFC delimiter
    …ref="torrents-search.php?search=1989&x=0&y=0">1989</a></li><div class="hr"></d…

    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 60: reference to external entity in attribute value
    …ref="torrents-search.php?search=1989&x=0&y=0">1989</a></li><div class="hr"></d…

    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 60: reference to entity "x" for which no system identifier could be generated
    …ref="torrents-search.php?search=1989&x=0&y=0">1989</a></li><div class="hr"></d…

    This is usually a cascading error caused by 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 159, Column 64: entity was defined here
    …ref="torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"…
  • Warning Line 221, Column 64: reference not terminated by REFC delimiter
    …"torrents-search.php?search=1989&x=0&y=0">1989</a></li><div class="hr"></div><…

    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 64: reference to external entity in attribute value
    …"torrents-search.php?search=1989&x=0&y=0">1989</a></li><div class="hr"></div><…

    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 64: reference to entity "y" for which no system identifier could be generated
    …"torrents-search.php?search=1989&x=0&y=0">1989</a></li><div class="hr"></div><…

    This is usually a cascading error caused by 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 159, Column 68: entity was defined here
    …"torrents-search.php?search=dvdrip&x=0&y=0">DVDRip</a></li><div class="hr"></d…
  • Error Line 227, 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 232, 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">Skriv in övriga årtal i sökrutan</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 233, 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 173, Column 3: start tag was here
    		<table  border="0"  cellpadding="2" cellspacing="0">
  • Error Line 238, Column 49: "if" is not a reserved name
    …"Meniui0"><a><span>sortera +</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 238, Column 68: "endif" is not a reserved name
    …sortera +</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 240, Column 95: document type does not allow element "div" here; assuming missing "li" start-tag
    …a href="torrents-today.php">dagens uppladdningar</a></li><div class="hr"></div>
  • Error Line 241, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="new.php">premiär</a></li><div class="hr"></div>

    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 242, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li class="Meniui"><a href="most.php">mest populära</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 244, 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 240, Column 80: start tag was here
    …a href="torrents-today.php">dagens uppladdningar</a></li><div class="hr"></div>
  • Error Line 249, Column 70: "if" is not a reserved name
    …rrents-search.php"><span>SÖK</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 249, Column 89: "endif" is not a reserved name
    …<span>SÖK</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 255, Column 77: "if" is not a reserved name
    …nkafilm.com"><span>tankafilm</span><![if gt IE 6]></a><![endif]><!--[if lte IE…
  • Error Line 255, Column 96: "endif" is not a reserved name
    …tankafilm</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…
  • Error Line 262, Column 6: end tag for element "li" which is not open
    	</li>	

    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 266, Column 129: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …lor:#FFFFFF; line-height:5px;"><center>Slumpa</center></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 266, Column 155: "if" is not a reserved name
    …; line-height:5px;"><center>Slumpa</center></span><![if gt IE 6]></a><![endif]>
  • Error Line 266, Column 174: "endif" is not a reserved name
    …; line-height:5px;"><center>Slumpa</center></span><![if gt IE 6]></a><![endif]>
  • Error Line 287, 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 284, Column 11: start tag was here
              <td valign="top">
  • Error Line 287, 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 282, Column 6: start tag was here
         <tr>
  • Error Line 287, 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 281, Column 5: start tag was here
        <table cellspacing="0" cellpadding="7" width="100%" border="0">
  • Error Line 292, 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).

  • Warning Line 308, Column 82: cannot generate system identifier for general entity "lim"
    …propellerpops.com/apu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC "…

    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 308, Column 82: general entity "lim" not defined and no default entity
    …propellerpops.com/apu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC "…

    This is usually a cascading error caused by 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 308, Column 85: reference not terminated by REFC delimiter
    …pellerpops.com/apu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC "-//…

    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 308, Column 85: reference to external entity in attribute value
    …pellerpops.com/apu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC "-//…

    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 308, Column 85: reference to entity "lim" for which no system identifier could be generated
    …pellerpops.com/apu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC "-//…

    This is usually a cascading error caused by 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 308, Column 81: entity was defined here
    …/propellerpops.com/apu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC …
  • Error Line 308, Column 101: "DOCTYPE" declaration not allowed in instance
    …pu.php?zoneid=2091&lim=24'></script><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1…
  • Error Line 309, Column 43: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml">

    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 344, Column 42: document type does not allow element "th" here; assuming missing "tr" start-tag
    …         <th align="left" width="130" ><strong>Användarnamn: <img src="http://…
  • Error Line 354, Column 12: 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 344, Column 13: start tag was here
                <th align="left" width="130" ><strong>Användarnamn: <img src="http:…
  • Error Line 402, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<div class=titles></div>
  • Error Line 403, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div  class=indexmenu><b>Senaste Uppladdningarna</b>
  • Error Line 404, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class=fler><a href=torrents.php><b>Visa Fler</b><img src='/images/nextarro…
  • Error Line 404, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class=fler><a href=torrents.php><b>Visa Fler</b><img src='/images/nextarro…
  • Error Line 404, Column 113: there is no attribute "valign"
    …tarrow.gif' class='favicons'   valign='middle'  /> </a></div></div><br><table …

    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 404, Column 124: required attribute "alt" not specified
    … class='favicons'   valign='middle'  /> </a></div></div><br><table  align=left…

    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 146: end tag for "br" omitted, but OMITTAG NO was specified
    …lign='middle'  /> </a></div></div><br><table  align=left cellpadding=0 class=p…

    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 404, Column 142: start tag was here
    …  valign='middle'  /> </a></div></div><br><table  align=left cellpadding=0 cla…
  • Error Line 404, Column 160: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … /> </a></div></div><br><table  align=left cellpadding=0 class=premier cellspa…
  • Error Line 404, Column 177: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/a></div></div><br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 404, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/a></div></div><br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 404, Column 205: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/a></div></div><br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 405, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		border=0><tr><td align=center><a href='http://swesub.tv/torrents-details.php?…
  • Error Line 405, Column 26: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		border=0><tr><td align=center><a href='http://swesub.tv/torrents-details.php?…
  • Error Line 406, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ustom.Swesub-Mr KeFF / Äventyr" width=100 height=140 class=index_posters title…
  • Error Line 406, Column 132: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …b-Mr KeFF / Äventyr" width=100 height=140 class=index_posters title='SUR.LA.PI…
  • Error Line 406, Column 142: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Äventyr" width=100 height=140 class=index_posters title='SUR.LA.PISTE.DU.MAR…
  • Error Line 406, Column 234: end tag for "img" omitted, but OMITTAG NO was specified
    …BRrip.720p.Custom.Swesub-Mr KeFF' ></a></td><td>&nbsp;</td><td align=center><a…

    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 405, Column 100: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11899&amp;hit=1'><img border='0'  
  • Error Line 406, Column 265: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …F' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 407, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ip.XviD.AC3-Graniten / Äventyr" width=100 height=140 class=index_posters title…
  • Error Line 407, Column 126: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-Graniten / Äventyr" width=100 height=140 class=index_posters title='Indian.In…
  • Error Line 407, Column 136: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Äventyr" width=100 height=140 class=index_posters title='Indian.In.The.Cupbo…
  • Error Line 407, Column 222: end tag for "img" omitted, but OMITTAG NO was specified
    ….SWESUB.DVDRip.XviD.AC3-Graniten' ></a></td><td>&nbsp;</td><td align=center><a…

    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 406, Column 339: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11898&amp;hit=1'><img border='0'  
  • Error Line 407, Column 253: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 408, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DRip.XviD.AC3-Graniten / Drama" width=100 height=140 class=index_posters title…
  • Error Line 408, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …C3-Graniten / Drama" width=100 height=140 class=index_posters title='Soldier.O…
  • Error Line 408, Column 126: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n / Drama" width=100 height=140 class=index_posters title='Soldier.Of.God.2005…
  • Error Line 408, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    ….SWESUB.DVDRip.XviD.AC3-Graniten' ></a></td><td>&nbsp;</td><td align=center><a…

    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 407, Column 327: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11897&amp;hit=1'><img border='0'  
  • Error Line 408, Column 235: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 409, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ESUB.DVDRip.xviD-SC666 / Drama" width=100 height=140 class=index_posters title…
  • Error Line 409, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….xviD-SC666 / Drama" width=100 height=140 class=index_posters title='Hello.I.M…
  • Error Line 409, Column 126: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6 / Drama" width=100 height=140 class=index_posters title='Hello.I.Must.Be.Goi…
  • Error Line 409, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …ng.2012.SWESUB.DVDRip.xviD-SC666' ></a></td><td>&nbsp;</td><td align=center><a…

    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 408, Column 309: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11896&amp;hit=1'><img border='0'  
  • Error Line 409, Column 235: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 410, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p.XviD.AC3-Haggebulle / Action" width=100 height=140 class=index_posters title…
  • Error Line 410, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Haggebulle / Action" width=100 height=140 class=index_posters title='Red.Dawn.…
  • Error Line 410, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Action" width=100 height=140 class=index_posters title='Red.Dawn.2012.SWESU…
  • Error Line 410, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …SWESUB.BRRip.XviD.AC3-Haggebulle' ></a></td><td>&nbsp;</td><td align=center><a…

    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 409, Column 309: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11895&amp;hit=1'><img border='0'  
  • Error Line 410, Column 226: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 411, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Swesub.XviD-Mr KeFF / Thriller" width=100 height=140 class=index_posters title…
  • Error Line 411, Column 118: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-Mr KeFF / Thriller" width=100 height=140 class=index_posters title='PERSON.OF…
  • Error Line 411, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Thriller" width=100 height=140 class=index_posters title='PERSON.OF.INTEREST.…
  • Error Line 411, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    ….S02E13.HDTV.Swesub.XviD-Mr KeFF' ></a></td><td>&nbsp;</td><td align=center><a…

    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 410, Column 300: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11894&amp;hit=1'><img border='0'  
  • Error Line 411, Column 236: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …F' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 412, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….XviD-snuttebullen.avi / Drama" width=100 height=140 class=index_posters title…
  • Error Line 412, Column 118: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ebullen.avi / Drama" width=100 height=140 class=index_posters title='Suits.201…
  • Error Line 412, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i / Drama" width=100 height=140 class=index_posters title='Suits.2012.S02E04.S…
  • Error Line 412, Column 208: end tag for "img" omitted, but OMITTAG NO was specified
    …2012.S02E04.SWESUB.WEBRiP.XviD-snuttebullen.avi' ></a></td><td>&nbsp;</td></tr>

    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 411, Column 310: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11893&amp;hit=1'><img border='0'  
  • Error Line 414, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=center><a href='http://swesub.tv/torrents-details.php?id=11892&amp;hi…
  • Error Line 415, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….HDTV.x264-Justiso.avi / Drama" width=100 height=140 class=index_posters title…
  • Error Line 415, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Justiso.avi / Drama" width=100 height=140 class=index_posters title='Zero.Hour…
  • Error Line 415, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i / Drama" width=100 height=140 class=index_posters title='Zero.Hour.S01E02.Sw…
  • Error Line 415, Column 192: end tag for "img" omitted, but OMITTAG NO was specified
    …E02.Swesub.HDTV.x264-Justiso.avi' ></a></td><td>&nbsp;</td><td align=center><a…

    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 85: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11892&amp;hit=1'><img border='0'  
  • Error Line 415, Column 223: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 416, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …XviD.AC3-Haggebulle / Thriller" width=100 height=140 class=index_posters title…
  • Error Line 416, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ggebulle / Thriller" width=100 height=140 class=index_posters title='Girls.Aga…
  • Error Line 416, Column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Thriller" width=100 height=140 class=index_posters title='Girls.Against.Boys.…
  • Error Line 416, Column 217: end tag for "img" omitted, but OMITTAG NO was specified
    …SWESUB.BRRip.XviD.AC3-Haggebulle' ></a></td><td>&nbsp;</td><td align=center><a…

    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 415, Column 297: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11891&amp;hit=1'><img border='0'  
  • Error Line 416, Column 248: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 417, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ESUB.dvdrip.Xvid.ac3 / Äventyr" width=100 height=140 class=index_posters title…
  • Error Line 417, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….Xvid.ac3 / Äventyr" width=100 height=140 class=index_posters title='Stone.Of.…
  • Error Line 417, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Äventyr" width=100 height=140 class=index_posters title='Stone.Of.Destiny.20…
  • Error Line 417, Column 192: end tag for "img" omitted, but OMITTAG NO was specified
    …tiny.2008.SWESUB.dvdrip.Xvid.ac3' ></a></td><td>&nbsp;</td><td align=center><a…

    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 416, Column 322: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11890&amp;hit=1'><img border='0'  
  • Error Line 417, Column 223: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 418, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …SUB HDTV XviD-SD.avi / Fantasy" width=100 height=140 class=index_posters title…
  • Error Line 418, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …iD-SD.avi / Fantasy" width=100 height=140 class=index_posters title='Supernatu…
  • Error Line 418, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Fantasy" width=100 height=140 class=index_posters title='Supernatural S08E15…
  • Error Line 418, Column 190: end tag for "img" omitted, but OMITTAG NO was specified
    …l S08E15 SWESUB HDTV XviD-SD.avi' ></a></td><td>&nbsp;</td><td align=center><a…

    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 417, Column 297: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11889&amp;hit=1'><img border='0'  
  • Error Line 418, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 419, Column 93: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …B.DVDrip.xvid-SC666 / Kriminal" width=100 height=140 class=index_posters title…
  • Error Line 419, Column 104: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id-SC666 / Kriminal" width=100 height=140 class=index_posters title='Grupo7.20…
  • Error Line 419, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Kriminal" width=100 height=140 class=index_posters title='Grupo7.2012.SWESUB.…
  • Error Line 419, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …o7.2012.SWESUB.DVDrip.xvid-SC666' ></a></td><td>&nbsp;</td><td align=center><a…

    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 418, Column 295: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11888&amp;hit=1'><img border='0'  
  • Error Line 419, Column 208: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 420, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….WEB-DL.x264-Mr.Stiffy / Drama" width=100 height=140 class=index_posters title…
  • Error Line 420, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4-Mr.Stiffy / Drama" width=100 height=140 class=index_posters title='Hitchcock…
  • Error Line 420, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …y / Drama" width=100 height=140 class=index_posters title='Hitchcock.2012.SWES…
  • Error Line 420, Column 198: end tag for "img" omitted, but OMITTAG NO was specified
    …WESUB.720p.WEB-DL.x264-Mr.Stiffy' ></a></td><td>&nbsp;</td><td align=center><a…

    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 419, Column 282: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11885&amp;hit=1'><img border='0'  
  • Error Line 420, Column 229: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …y' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 421, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …iD.AC3-Haggebulle / Dokumentär" width=100 height=140 class=index_posters title…
  • Error Line 421, Column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ebulle / Dokumentär" width=100 height=140 class=index_posters title='Inside.Th…
  • Error Line 421, Column 135: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …okumentär" width=100 height=140 class=index_posters title='Inside.The.Mafia.20…
  • Error Line 421, Column 217: end tag for "img" omitted, but OMITTAG NO was specified
    …SWESUB.DVDRip.XviD.AC3-Haggebulle' ></a></td><td>&nbsp;</td></tr></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 420, Column 303: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11884&amp;hit=1'><img border='0'  
  • Error Line 433, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<div class=titles></div>
  • Error Line 434, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div  class=indexmenu><b>Nya Filmer<b/>
  • Error Line 435, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class=fler><a href=new.php>Visa Fler<img src='/images/nextarrow.gif' class…
  • Error Line 435, Column 16: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div class=fler><a href=new.php>Visa Fler<img src='/images/nextarrow.gif' class…

    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 435, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class=fler><a href=new.php>Visa Fler<img src='/images/nextarrow.gif' class…
  • Error Line 435, Column 112: required attribute "alt" not specified
    … class='favicons'   valign='middle'  /></a></div></div><br><table  align=left …

    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 435, Column 128: end tag for "b" omitted, but OMITTAG NO was specified
    …'   valign='middle'  /></a></div></div><br><table  align=left cellpadding=0 cl…

    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 434, Column 23: start tag was here
    <div  class=indexmenu><b>Nya Filmer<b/>
  • Error Line 435, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    …align='middle'  /></a></div></div><br><table  align=left cellpadding=0 class=p…

    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 435, Column 129: start tag was here
    …   valign='middle'  /></a></div></div><br><table  align=left cellpadding=0 cla…
  • Error Line 435, Column 147: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …  /></a></div></div><br><table  align=left cellpadding=0 class=premier cellspa…
  • Error Line 435, Column 164: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/a></div></div><br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 435, Column 172: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/a></div></div><br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 435, Column 192: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/a></div></div><br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 436, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		border=0><tr></tr>
  • Error Line 436, Column 20: end tag for "tr" which is not finished
    		border=0><tr></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 438, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=center><a href='http://swesub.tv/torrents-details.php?id=11895&amp;hi…
  • Error Line 439, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p.XviD.AC3-Haggebulle / Action" width=100 height=140 class=index_posters title…
  • Error Line 439, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Haggebulle / Action" width=100 height=140 class=index_posters title='Red.Dawn.…
  • Error Line 439, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Action" width=100 height=140 class=index_posters title='Red.Dawn.2012.SWESU…
  • Error Line 439, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …SWESUB.BRRip.XviD.AC3-Haggebulle' ></a></td><td>&nbsp;</td><td align=center><a…

    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 438, Column 85: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11895&amp;hit=1'><img border='0'  
  • Error Line 439, Column 226: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 440, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …SWESUB.BDRip.XviDSC666 / Drama" width=100 height=140 class=index_posters title…
  • Error Line 440, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p.XviDSC666 / Drama" width=100 height=140 class=index_posters title='The.Sapph…
  • Error Line 440, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6 / Drama" width=100 height=140 class=index_posters title='The.Sapphires.2012.…
  • Error Line 440, Column 184: end tag for "img" omitted, but OMITTAG NO was specified
    …ires.2012.SWESUB.BDRip.XviDSC666' ></a></td><td>&nbsp;</td><td align=center><a…

    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 439, Column 300: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11876&amp;hit=1'><img border='0'  
  • Error Line 440, Column 215: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 441, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….XViD.AC3-little devil / Drama" width=100 height=140 class=index_posters title…
  • Error Line 441, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ittle devil / Drama" width=100 height=140 class=index_posters title='Lincoln.2…
  • Error Line 441, Column 130: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …l / Drama" width=100 height=140 class=index_posters title='Lincoln.2012.CUSTOM…
  • Error Line 441, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …SUB.DVDSCR.XViD.AC3-little devil' ></a></td><td>&nbsp;</td><td align=center><a…

    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 289: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11866&amp;hit=1'><img border='0'  
  • Error Line 441, Column 243: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …l' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 442, Column 129: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ip.XviD.MP3-Graniten / Äventyr" width=100 height=140 class=index_posters title…
  • Error Line 442, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-Graniten / Äventyr" width=100 height=140 class=index_posters title='Asterix.a…
  • Error Line 442, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Äventyr" width=100 height=140 class=index_posters title='Asterix.and.Obelix.…
  • Error Line 442, Column 250: end tag for "img" omitted, but OMITTAG NO was specified
    …2.SWESUB.BRRip.XviD.MP3-Graniten' ></a></td><td>&nbsp;</td><td align=center><a…

    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 441, Column 317: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11865&amp;hit=1'><img border='0'  
  • Error Line 442, Column 281: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 443, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ESUB.DVDRip.XviD.avi / Fantasy" width=100 height=140 class=index_posters title…
  • Error Line 443, Column 133: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….XviD.avi / Fantasy" width=100 height=140 class=index_posters title='The.Twili…
  • Error Line 443, Column 143: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Fantasy" width=100 height=140 class=index_posters title='The.Twilight.Saga.B…
  • Error Line 443, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …rt.2.2012.SWESUB.DVDRip.XviD.avi' ></a></td><td>&nbsp;</td><td align=center><a…

    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 442, Column 355: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11845&amp;hit=1'><img border='0'  
  • Error Line 443, Column 267: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 444, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ESUB.BDrip.xvid-SC666 / Komedi" width=100 height=140 class=index_posters title…
  • Error Line 444, Column 103: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …xvid-SC666 / Komedi" width=100 height=140 class=index_posters title='Fun.Size.…
  • Error Line 444, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Komedi" width=100 height=140 class=index_posters title='Fun.Size.2012.SWESU…
  • Error Line 444, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …ize.2012.SWESUB.BDrip.xvid-SC666' ></a></td><td>&nbsp;</td><td align=center><a…

    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 443, Column 341: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11839&amp;hit=1'><img border='0'  
  • Error Line 444, Column 208: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 445, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …SUB.DVDrip.xvid-SC666 / Action" width=100 height=140 class=index_posters title…
  • Error Line 445, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …xvid-SC666 / Action" width=100 height=140 class=index_posters title='Alex.Cros…
  • Error Line 445, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Action" width=100 height=140 class=index_posters title='Alex.Cross.2012.SWE…
  • Error Line 445, Column 183: end tag for "img" omitted, but OMITTAG NO was specified
    …ex.Cross.2012.SWESUB.DVDrip.xvid-SC666' ></a></td><td>&nbsp;</td></tr></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 444, Column 282: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11834&amp;hit=1'><img border='0'  
  • Error Line 457, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<div class=indexmenu><b>Mest Populära<b/>&nbsp;
  • Error Line 459, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class=fler><a href=most.php>Visa Fler<img src='/images/nextarrow.gif' clas…
  • Error Line 459, Column 16: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div class=fler><a href=most.php>Visa Fler<img src='/images/nextarrow.gif' clas…

    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 459, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class=fler><a href=most.php>Visa Fler<img src='/images/nextarrow.gif' clas…
  • Error Line 459, Column 113: required attribute "alt" not specified
    … class='favicons'   valign='middle'  /></a></div></div></br><table  align=left…

    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 459, Column 129: end tag for "b" omitted, but OMITTAG NO was specified
    …'   valign='middle'  /></a></div></div></br><table  align=left cellpadding=0 c…

    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 457, Column 25: start tag was here
    			<div class=indexmenu><b>Mest Populära<b/>&nbsp;
  • Error Line 459, Column 134: end tag for element "br" which is not open
    …align='middle'  /></a></div></div></br><table  align=left cellpadding=0 class=…

    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 459, Column 149: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … /></a></div></div></br><table  align=left cellpadding=0 class=premier cellspa…
  • Error Line 459, Column 166: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a></div></div></br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 459, Column 174: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a></div></div></br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 459, Column 194: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a></div></div></br><table  align=left cellpadding=0 class=premier cellspacing=0
  • Error Line 460, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		border=0><tr></tr>
  • Error Line 460, Column 20: end tag for "tr" which is not finished
    		border=0><tr></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 462, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=center><a href='http://swesub.tv/torrents-details.php?id=11028&amp;hi…
  • Error Line 463, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …UB.BDRip.XviD-Fuvisa / Äventyr" width=100 height=140 class=index_posters title…
  • Error Line 463, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …iD-Fuvisa / Äventyr" width=100 height=140 class=index_posters title='The.Hunge…
  • Error Line 463, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/ Äventyr" width=100 height=140 class=index_posters title='The.Hunger.Games.20…
  • Error Line 463, Column 196: end tag for "img" omitted, but OMITTAG NO was specified
    …es.2012.SWESUB.BDRip.XviD-Fuvisa' ></a></td><td>&nbsp;</td><td align=center><a…

    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 462, Column 85: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11028&amp;hit=1'><img border='0'  
  • Error Line 463, Column 227: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 464, Column 104: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….BluRay.x264-Olizzz / Animerat" width=100 height=140 class=index_posters title…
  • Error Line 464, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4-Olizzz / Animerat" width=100 height=140 class=index_posters title='Brave.201…
  • Error Line 464, Column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Animerat" width=100 height=140 class=index_posters title='Brave.2012.SWEDiSH.…
  • Error Line 464, Column 199: end tag for "img" omitted, but OMITTAG NO was specified
    …iSH.AC3.1080p.BluRay.x264-Olizzz' ></a></td><td>&nbsp;</td><td align=center><a…

    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 463, Column 301: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11505&amp;hit=1'><img border='0'  
  • Error Line 464, Column 230: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …z' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 465, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …B.BRRip.XviD.MovieCom / Action" width=100 height=140 class=index_posters title…
  • Error Line 465, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …D.MovieCom / Action" width=100 height=140 class=index_posters title='Real.Stee…
  • Error Line 465, Column 119: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Action" width=100 height=140 class=index_posters title='Real.Steel.(2011).S…
  • Error Line 465, Column 190: end tag for "img" omitted, but OMITTAG NO was specified
    …2011).SWESUB.BRRip.XviD.MovieCom' ></a></td><td>&nbsp;</td><td align=center><a…

    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 464, Column 303: start tag was here
    …ref='http://swesub.tv/torrents-details.php?id=9796&amp;hit=1'><img border='0'  
  • Error Line 465, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 466, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DvDRip.XviD-SWAXXON / Kriminal" width=100 height=140 class=index_posters title…
  • Error Line 466, Column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-SWAXXON / Kriminal" width=100 height=140 class=index_posters title='Johan.Fal…
  • Error Line 466, Column 135: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Kriminal" width=100 height=140 class=index_posters title='Johan.Falk.107.Patr…
  • Error Line 466, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …2012.SWEDiSH.DvDRip.XviD-SWAXXON' ></a></td><td>&nbsp;</td><td align=center><a…

    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 465, Column 295: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11229&amp;hit=1'><img border='0'  
  • Error Line 466, Column 250: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …N' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 467, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DRip.XviD.MovieCom.se / Komedi" width=100 height=140 class=index_posters title…
  • Error Line 467, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ovieCom.se / Komedi" width=100 height=140 class=index_posters title='Paul.(201…
  • Error Line 467, Column 117: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Komedi" width=100 height=140 class=index_posters title='Paul.(2011).SWESUB.…
  • Error Line 467, Column 186: end tag for "img" omitted, but OMITTAG NO was specified
    …).SWESUB.DVDRip.XviD.MovieCom.se' ></a></td><td>&nbsp;</td><td align=center><a…

    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 466, Column 323: start tag was here
    …ref='http://swesub.tv/torrents-details.php?id=8266&amp;hit=1'><img border='0'  
  • Error Line 467, Column 217: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 468, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …sa.2012.SWEDiSH.BDRip / Action" width=100 height=140 class=index_posters title…
  • Error Line 468, Column 108: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …DiSH.BDRip / Action" width=100 height=140 class=index_posters title='Johan.Fal…
  • Error Line 468, Column 118: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Action" width=100 height=140 class=index_posters title='Johan.Falk.Kodnamn.…
  • Error Line 468, Column 187: end tag for "img" omitted, but OMITTAG NO was specified
    ….Kodnamn.Lisa.2012.SWEDiSH.BDRip' ></a></td><td>&nbsp;</td><td align=center><a…

    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 467, Column 291: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11376&amp;hit=1'><img border='0'  
  • Error Line 468, Column 218: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p' ></a></td><td>&nbsp;</td><td align=center><a href='http://swesub.tv/torrent…
  • Error Line 469, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …VDRip.XviD.AC3-Fuvisa / Action" width=100 height=140 class=index_posters title…
  • Error Line 469, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AC3-Fuvisa / Action" width=100 height=140 class=index_posters title='The.Aveng…
  • Error Line 469, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … / Action" width=100 height=140 class=index_posters title='The.Avengers.2012.S…
  • Error Line 469, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …12.SWESUB.DVDRip.XviD.AC3-Fuvisa' ></a></td><td>&nbsp;</td></tr></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 468, Column 292: start tag was here
    …ef='http://swesub.tv/torrents-details.php?id=11087&amp;hit=1'><img border='0'  
  • Error Line 477, Column 19: end tag for element "td" which is not open
    		            </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 479, 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 481, 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 490, 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 497, Column 42: there is no attribute "height"
    <table align="center" width="940" height="150" 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 503, Column 6: element "left" undefined
    <left><span>&nbsp;<b>Community</b></span>

    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 505, Column 9: end tag for element "center" which is not open
    </center>

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

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

  • Warning Line 509, Column 68: 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 509, Column 68: 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 509, Column 76: 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 509, Column 76: 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 509, Column 76: 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 509, Column 67: entity was defined here
    …ontact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='C…
  • Warning Line 509, Column 97: 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 509, Column 97: 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 509, Column 97: 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 509, Column 67: entity was defined here
    …ontact/contact.php?lightbox[width]=500&lightbox[height]=500&lightbox' title='C…
  • Error Line 509, Column 244: required attribute "alt" not specified
    …ontact.png'  class='favicons' width='13' height='13'   />&nbsp;Kontakta oss</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 511, Column 194: required attribute "alt" not specified
    …ebook.png' class='favicons' width='13' height='13' />&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 513, Column 142: required attribute "alt" not specified
    …tv/images/rss.png' class='favicons' width='13' height='13' />&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 515, Column 6: end tag for "left" omitted, but OMITTAG NO was specified
    </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 503, Column 1: start tag was here
    <left><span>&nbsp;<b>Community</b></span>
  • Error Line 517, 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 500, Column 13: start tag was here
                <td>&nbsp;<div class="our_friends">
  • Error Line 517, 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 499, Column 9: start tag was here
            <tr>
  • Error Line 517, 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 498, Column 5: start tag was here
        <tbody>
  • Error Line 517, 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 497, Column 1: start tag was here
    <table align="center" width="940" height="150" border="0">
  • Error Line 517, 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 518, 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 521, Column 6: element "left" undefined
    <left><span>&nbsp;<b>Vänner</b></span></center>

    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 521, Column 47: end tag for element "center" which is not open
    <left><span>&nbsp;<b>Vänner</b></span></center>

    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 524, Column 172: required attribute "alt" not specified
    …ss='favicons'  width='14' height='8' valign='middle'  />&nbsp;Tankafilm.com</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 526, Column 158: required attribute "alt" not specified
    …s/torrentz.png' class='favicons' width='13' height='13' />&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 528, Column 170: required attribute "alt" not specified
    …artiet.png' class='favicons' width='13' height='13' />&nbsp;Piratpartiet.se</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 531, Column 168: 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 534, Column 6: end tag for "left" omitted, but OMITTAG NO was specified
    </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 521, Column 1: start tag was here
    <left><span>&nbsp;<b>Vänner</b></span></center>
  • Error Line 537, Column 16: document type does not allow element "td" here
                <td>

    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 539, Column 48: there is no attribute "data-href"
    …bg-box" class="fb-like-box" data-href="http://www.facebook.com/pages/SwesubTv/…

    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 539, Column 116: there is no attribute "data-width"
    …/SwesubTv/128621930486255" data-width="260" data-height= "180" data-colorschem…

    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 539, Column 135: there is no attribute "data-height"
    …486255" data-width="260" data-height= "180" data-colorscheme="light" data-show…

    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 539, Column 158: there is no attribute "data-colorscheme"
    …" data-height= "180" data-colorscheme="light" data-show-faces="true"  data-bor…

    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 539, Column 182: there is no attribute "data-show-faces"
    …a-colorscheme="light" data-show-faces="true"  data-border-color="F1F1F1" data-…

    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 539, Column 208: there is no attribute "data-border-color"
    …-show-faces="true"  data-border-color="F1F1F1" 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 539, Column 229: there is no attribute "data-stream"
    …rue"  data-border-color="F1F1F1" data-stream="false" data-header="false"></div>

    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 539, Column 249: there is no attribute "data-header"
    …rue"  data-border-color="F1F1F1" data-stream="false" data-header="false"></div>

    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 543, Column 11: 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 544, 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 551, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 538, Column 1: start tag was here
    <div class="fb-container">
  • Error Line 551, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
    </body>

    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 537, Column 13: start tag was here
                <td>
  • Error Line 551, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 1: start tag was here
    <div class="wrap">
  • Error Line 552, Column 8: 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 43, Column 1: start tag was here
    <body>
  • Error Line 552, Column 8: end tag for "html" 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 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 5.133 visits