Filmy i seriale online na megavideo, videobb, videozer. Oglądaj bez ściągania. To prawdopodobnie największy katalog linków do filmów online, sprawdź sam korzystanie jest darmowe. Filmy bez limitu za darmo, z lektorem, po polsku, ...

playtube.pl
  • Domain Name
    playtube.pl
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #19055
  • Page Size
    21.4 KB
  • Ip Address
    212.7.198.164
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 12 JPG, 3 PNG

Website Meta Analysis

  • Title
    Playtube.pl - Filmy online i seriale
  • Meta Keyword
    Filmy na online, films online free, filmy online, filmy, filmy on line, seriale online, darmowe filmy, seriale on line, filmy za darmo, filmy z lektorem, kino online, premiery kinowe, nowości filmowe, tv przez internet, efilmy,videobb.eu, videoweed.pl, videozer.pl
  • Meta Description
    Filmy i seriale online na megavideo, videobb, videozer. Oglądaj bez ściągania. To prawdopodobnie największy katalog linków do filmów online, sprawdź sam korzystanie jest darmowe. Filmy bez limitu za darmo, z lektorem, po polsku, z dubbingiem. U nas nie ma limitu na filmy.

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from playtube.pl.

HTML Analysis

  • server: nginx
  • date: Wed, 04 Sep 2013 18:17:30 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-frame-options: DENY
  • 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, 04 Sep 2013 10:17:30 +0200 GMT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: playtube.pl
registrant type: organization
nameservers: ns1.playtube.pl. [46.4.76.176]
ns2.playtube.pl. [46.4.76.176]
created: 2008.12.08 22:04:22
last modified: 2012.02.14 12:57:09
renewal date: 2012.12.08 22:04:22

no option

dnssec: Unsigned


REGISTRAR:
Home.pl S.A.
pl. Rodla 9
70-419 Szczecin
Polska/Poland
+48.914325555
+48.801445555
email

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

DNS Analysis


DNS servers
ns1.playtube.pl [46.4.76.176]
ns2.playtube.pl [46.4.76.176]


DNS Records

Answer records
playtube.pl MX
preference: 10
exchange: mail.playtube.pl
100s
playtube.pl TXT v=spf1 a mx ~all 100s
playtube.pl A 46.4.76.176 100s
playtube.pl SOA
server: ns1.playtube.pl
email: hostmaster@playtube.pl
serial: 2011039200
refresh: 100
retry: 3600
expire: 1209600
minimum ttl: 86400
100s
playtube.pl NS  ns2.playtube.pl 100s
playtube.pl NS  ns1.playtube.pl 100s

Authority records

Additional records
mail.playtube.pl A 46.4.76.176 100s
ns1.playtube.pl A 46.4.76.176 100s
ns2.playtube.pl A 46.4.76.176 100s

IP 212.7.198.164 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 86 Errors
  • 45 Warnings
Ratio Text/Html
  • 0.6707879009078881
Message Error
  • Error Line 18, Column 16: there is no attribute "property"
    <meta property="og:site_name" content="Playtube.pl" />

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

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

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

  • Warning Line 33, Column 83: cannot generate system identifier for general entity "bid"
    …tmmo.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src='…

    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 33, Column 83: general entity "bid" not defined and no default entity
    …tmmo.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src='…

    This is usually a cascading error caused by 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 33, Column 86: reference not terminated by REFC delimiter
    …o.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src='htt…

    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 33, Column 86: reference to external entity in attribute value
    …o.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src='htt…

    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 33, Column 86: reference to entity "bid" for which no system identifier could be generated
    …o.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src='htt…

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

  • Info Line 33, Column 82: entity was defined here
    …rtmmo.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src=…
  • Error Line 33, Column 112: document type does not allow element "a" here
    …d=allago&bid=492a1e20' target='_blank'><img src='http://panel.portmmo.com/acco…

    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 33, Column 320: reference not terminated by REFC delimiter
    …mmo.com/scripts/imp.php?aid=allago&bid=492a1e20' width='1' height='1' alt='' /…

    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 33, Column 320: reference to external entity in attribute value
    …mmo.com/scripts/imp.php?aid=allago&bid=492a1e20' width='1' height='1' alt='' /…

    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 33, Column 320: reference to entity "bid" for which no system identifier could be generated
    …mmo.com/scripts/imp.php?aid=allago&bid=492a1e20' width='1' height='1' alt='' /…

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

  • Info Line 33, Column 82: entity was defined here
    …rtmmo.com/scripts/click.php?aid=allago&bid=492a1e20' target='_blank'><img src=…
  • Error Line 33, Column 360: document type does not allow element "img" here
    …o.com/scripts/imp.php?aid=allago&bid=492a1e20' width='1' height='1' alt='' />";

    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 89, Column 68: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/www.playtube.pl/"><div  class="menu_item icon_home">G&#322;&#243;wna</div></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>").

  • Error Line 90, Column 86: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …aytube.pl/index.php?do=filmy"><div class="menu_item icon_filmy">Filmy</div></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>").

  • Error Line 91, Column 88: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ce24.pl/" target= "blank"><div class="menu_item icon_seriale">Seriale</div></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>").

  • Error Line 92, Column 76: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ww.playtube.pl/dzieci/"><div class="menu_item icon_dzieci">Dla dzieci</div></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>").

  • Error Line 93, Column 91: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tube.pl/index.php?do=play_tv_radio"><div class="menu_item icon_tv">TV</div></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>").

  • Error Line 94, Column 85: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …playtube.pl/index.php?do=mchat"><div class="menu_item icon_chat">Chat</div></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>").

  • Error Line 95, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <a href="http://www.playka.pl/"><div class="menu_item icon_games">Gry</div></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>").

  • Error Line 96, Column 83: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    ….playtube.pl/pomoc/index.php"><div class="menu_item icon_pomoc">Pomoc</div></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>").

  • Error Line 97, Column 91: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …pl/index.php?do=feedback"><div class="menu_item icon_contact">Kontakt</div></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>").

  • Error Line 98, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e.pl/free_bilety.html"><div class="menu_item icon_freepremium">Bilety</div></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>").

  • Error Line 99, Column 86: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e.pl/dodaj_film.html"><div class="menu_item icon_addmovie">Dodaj link</div></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>").

  • Error Line 115, Column 79: end tag for "br" omitted, but OMITTAG NO was specified
    …nie witamy w serwisie PlayTube.pl!<br>Oddajemy Wam do dyspozycji najwi&#281;ks…

    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 115, Column 75: start tag was here
    …decznie witamy w serwisie PlayTube.pl!<br>Oddajemy Wam do dyspozycji najwi&#28…
  • Error Line 118, Column 47: required attribute "action" not specified
              <form method="post" name="loginform">

    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 120, Column 120: there is no attribute "onKeyPress"
    …putbox" style="width:100px;" onKeyPress="return loginpres(this, event)"/></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 150, Column 132: end tag for "input" omitted, but OMITTAG NO was specified
    …gth="60" name="story" id="SearchTXT" onKeyPress="return keypress(this, event)">

    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 150, Column 1: start tag was here
    <input type="text" size="50" class="inputbox" maxlength="60" name="story" id="S…
  • Error Line 153, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" id="subaction" value="search" name="subaction">

    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 153, Column 1: start tag was here
    <input type="hidden" id="subaction" value="search" name="subaction">
  • Error Line 167, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="text" size="40" class="inputbox" name="mv_link">

    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 167, Column 1: start tag was here
    <input type="text" size="40" class="inputbox" name="mv_link">
  • Error Line 173, Column 11: element "blink" undefined
    <td><blink><a href="http://www.playtube.pl/nowe_serwery.html"><font color="red"…

    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 179, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="incat" id="incat" value="">

    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 179, Column 1: start tag was here
    <input type="hidden" name="incat" id="incat" value="">
  • Error Line 180, Column 22: required attribute "action" not specified
    <form id="qsort_Form">

    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 185, Column 12: end tag for "br" omitted, but OMITTAG NO was specified
    Rodzaj:<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 185, Column 8: start tag was here
    Rodzaj:<br><br>
  • Error Line 185, Column 16: end tag for "br" omitted, but OMITTAG NO was specified
    Rodzaj:<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 185, Column 12: start tag was here
    Rodzaj:<br><br>
  • Error Line 186, Column 315: ":" is not a member of a group specified for any attribute
    …cb5568625b3c0edd7b48d6182d0fbccc497d05aae3d1c3760ecd070f1ad650ae537e712b9');":>
  • Error Line 198, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
    Czas publikacji:<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 198, Column 17: start tag was here
    Czas publikacji:<br><br>
  • Error Line 198, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    Czas publikacji:<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 198, Column 21: start tag was here
    Czas publikacji:<br><br>
  • Error Line 199, Column 317: ":" is not a member of a group specified for any attribute
    …cb5568625b3c0edd7b48d6182d0fbccc497d05aae3d1c3760ecd070f1ad650ae537e712b9');":>
  • Error Line 209, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    Kolejno&#347;&#263;:<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 209, Column 21: start tag was here
    Kolejno&#347;&#263;:<br><br>
  • Error Line 209, Column 29: end tag for "br" omitted, but OMITTAG NO was specified
    Kolejno&#347;&#263;:<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 209, Column 25: start tag was here
    Kolejno&#347;&#263;:<br><br>
  • Error Line 210, Column 320: ":" is not a member of a group specified for any attribute
    …cb5568625b3c0edd7b48d6182d0fbccc497d05aae3d1c3760ecd070f1ad650ae537e712b9');":>
  • Error Line 242, Column 279: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …0b90b35216fd5.jpg" alt="Saga "Zmierzch": Przed świtem. Część 2 / The Twilight …

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 242, Column 280: end tag for "img" omitted, but OMITTAG NO was specified
    …b90b35216fd5.jpg" alt="Saga "Zmierzch": Przed świtem. Część 2 / The Twilight S…

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

  • Info Line 242, Column 138: start tag was here
    …zed-switem-czesc-2-the-twilight.html"><img style="border: 0px none;" src="http…
  • Error Line 290, Column 139: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ed-switem-czesc-2-the-twilight.html"><div class="short_button1">Linki</div></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>").

  • Error Line 311, Column 391: end tag for "img" omitted, but OMITTAG NO was specified
    …żsamości / Identity Thief (2013) BRRip ENG" width="150" height="200"></a></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 311, Column 141: start tag was here
    …i-identity-thief-2013-brrip-eng.html"><img style="border: 0px none;" src="http…
  • Error Line 344, Column 459: end tag for "br" omitted, but OMITTAG NO was specified
    …="white">SHARE</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" color="…

    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 455: start tag was here
    …olor="white">SHARE</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" col…
  • Error Line 359, Column 142: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …-identity-thief-2013-brrip-eng.html"><div class="short_button1">Linki</div></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>").

  • Error Line 380, Column 352: end tag for "img" omitted, but OMITTAG NO was specified
    …  title="Ucieczka / Flukt (2012) Napisy PL" width="150" height="200"></a></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 380, Column 119: start tag was here
    …5-ucieczka-flukt-2012-napisy-pl.html"><img style="border: 0px none;" src="http…
  • Error Line 428, Column 120: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …-ucieczka-flukt-2012-napisy-pl.html"><div class="short_button1">Linki</div></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>").

  • Error Line 449, Column 344: end tag for "img" omitted, but OMITTAG NO was specified
    …ie Żywy / Warm Bodies (2013) CAM Napisy PL" width="150" height="200"></a></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 449, Column 104: start tag was here
    …ilmy/dramat/54737-wiecznie-zywy.html"><img style="border: 0px none;" src="http…
  • Error Line 488, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
    …     <div class="font_silver_2lines font11">update link<br>Dzisiaj, 09:36</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 488, Column 64: start tag was here
    …     <div class="font_silver_2lines font11">update link<br>Dzisiaj, 09:36</div>
  • Error Line 502, Column 105: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …lmy/dramat/54737-wiecznie-zywy.html"><div class="short_button1">Linki</div></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>").

  • Error Line 523, Column 383: end tag for "img" omitted, but OMITTAG NO was specified
    …ycie Pi / The Life of Pi (2012) Dubbing PL" width="150" height="200"></a></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 523, Column 130: start tag was here
    …-the-life-of-pi-2012-dubbing-pl.html"><img style="border: 0px none;" src="http…
  • Error Line 556, Column 459: end tag for "br" omitted, but OMITTAG NO was specified
    …silver">LOCKER</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" color="…

    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 556, Column 455: start tag was here
    …or="silver">LOCKER</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" col…
  • Error Line 562, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
    … <div class="font_silver_2lines font11">mirror maxvideo<br>Dzisiaj, 18:01</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 562, Column 68: start tag was here
    … <div class="font_silver_2lines font11">mirror maxvideo<br>Dzisiaj, 18:01</div>
  • Error Line 576, Column 131: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …the-life-of-pi-2012-dubbing-pl.html"><div class="short_button1">Linki</div></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>").

  • Error Line 597, Column 427: end tag for "img" omitted, but OMITTAG NO was specified
    … / Trouble with the Curve (2012) Lektor PL" width="150" height="200"></a></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 597, Column 138: start tag was here
    …rze-trouble-with-the-curve-2012.html"><img style="border: 0px none;" src="http…
  • Error Line 645, Column 139: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ze-trouble-with-the-curve-2012.html"><div class="short_button1">Linki</div></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>").

  • Error Line 666, Column 388: end tag for "img" omitted, but OMITTAG NO was specified
    …o / Nono, het Zigzag Kind (2012) Napisy PL" width="150" height="200"></a></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 666, Column 131: start tag was here
    …-het-zigzag-kind-2012-napisy-pl.html"><img style="border: 0px none;" src="http…
  • Error Line 699, Column 459: end tag for "br" omitted, but OMITTAG NO was specified
    …="white">SHARE</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" color="…

    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 699, Column 455: start tag was here
    …olor="white">SHARE</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" col…
  • Error Line 705, Column 95: end tag for "br" omitted, but OMITTAG NO was specified
    …r_2lines font11">mirror putlocker,nextvideo i sockshare<br>Wczoraj, 11:37</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 705, Column 91: start tag was here
    …r_2lines font11">mirror putlocker,nextvideo i sockshare<br>Wczoraj, 11:37</div>
  • Error Line 719, Column 132: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …het-zigzag-kind-2012-napisy-pl.html"><div class="short_button1">Linki</div></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>").

  • Error Line 740, Column 295: end tag for "img" omitted, but OMITTAG NO was specified
    …13) CAM RUS"  title="Snitch (2013) CAM RUS" width="150" height="200"></a></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 740, Column 109: start tag was here
    …akcja/54741-snitch-2013-cam-rus.html"><img style="border: 0px none;" src="http…
  • Error Line 773, Column 463: end tag for "br" omitted, but OMITTAG NO was specified
    …r="green">WEED</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" color="…

    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 773, Column 459: start tag was here
    …color="green">WEED</font>&nbsp;&nbsp;|<br>|&nbsp;&nbsp;<font face="Tahoma" col…
  • Error Line 788, Column 110: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …kcja/54741-snitch-2013-cam-rus.html"><div class="short_button1">Linki</div></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>").

  • Error Line 809, Column 300: end tag for "img" omitted, but OMITTAG NO was specified
    … Lektor PL"  title="Jelly (2010) Lektor PL" width="150" height="200"></a></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 809, Column 112: start tag was here
    …edia/54626-jelly-2010-lektor-pl.html"><img style="border: 0px none;" src="http…
  • Error Line 848, Column 99: end tag for "br" omitted, but OMITTAG NO was specified
    …ines font11">mirror putlocker,nextvideo,nova i nowvideo<br>Dzisiaj, 22:25</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 848, Column 95: start tag was here
    …ines font11">mirror putlocker,nextvideo,nova i nowvideo<br>Dzisiaj, 22:25</div>
  • Error Line 862, Column 113: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …dia/54626-jelly-2010-lektor-pl.html"><div class="short_button1">Linki</div></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>").

  • Error Line 883, Column 393: end tag for "img" omitted, but OMITTAG NO was specified
    …sze życie / A Better Life (2011) Lektor PL" width="150" height="200"></a></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 883, Column 136: start tag was here
    …-better-life-2011-dvd-lektor-pl.html"><img style="border: 0px none;" src="http…
  • Error Line 922, Column 89: end tag for "br" omitted, but OMITTAG NO was specified
    …_silver_2lines font11">mirror nextvideo,nova i nowvideo<br>Dzisiaj, 22:23</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 922, Column 85: start tag was here
    …_silver_2lines font11">mirror nextvideo,nova i nowvideo<br>Dzisiaj, 22:23</div>
  • Error Line 936, Column 137: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …better-life-2011-dvd-lektor-pl.html"><div class="short_button1">Linki</div></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 981, Column 14: character "&" is the first character of a delimiter but occurred as data
    else if (dec && (keychar == "."))

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 981, Column 15: character "&" is the first character of a delimiter but occurred as data
    else if (dec && (keychar == "."))

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 994, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …span><div class="ptbackarrow leftside"></div></span><span class="numnavi"> <st…

    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 994, Column 680: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ytube.pl/page/2/"><strong><div class="ptnextarrow leftside"></div></strong></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>").

  • Error Line 997, Column 152: end tag for "input" omitted, but OMITTAG NO was specified
    … name="cstart" id="cstart" onKeyPress="return numbersonly(this, event)" ></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 997, Column 27: start tag was here
    <div class="jumpto_input"><input size="3" style="width:30px;" type="text" name=…
  • Error Line 1050, Column 109: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ouse-m-d.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1050, Column 302: end tag for "img" omitted, but OMITTAG NO was specified
    … Doktor House" height="93" width="70"><div class="miejsce">1</div></div></a>&n…

    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 1050, Column 110: start tag was here
    …use-m-d.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1052, Column 95: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …-diaries.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1052, Column 285: end tag for "img" omitted, but OMITTAG NO was specified
    …mpire Diaries" height="93" width="70"><div class="miejsce">2</div></div></a>&n…

    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 1052, Column 96: start tag was here
    …diaries.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1054, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="http://www.tasiemce24.pl/serial/86-dexter.html" ><div class="miejs…

    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 1054, Column 1: start tag was here
    <br><a href="http://www.tasiemce24.pl/serial/86-dexter.html" ><div class="miejs…
  • Error Line 1054, Column 85: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …6-dexter.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1054, Column 240: end tag for "img" omitted, but OMITTAG NO was specified
    …lt="3. Dexter" height="93" width="70"><div class="miejsce">3</div></div></a>&n…

    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 1054, Column 86: start tag was here
    …-dexter.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1056, Column 92: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ing-dead.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1056, Column 286: end tag for "img" omitted, but OMITTAG NO was specified
    … walking dead" height="93" width="70"><div class="miejsce">4</div></div></a>&n…

    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 1056, Column 93: start tag was here
    …ng-dead.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1058, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="http://www.tasiemce24.pl/serial/183-the-mentalist.html" ><div clas…

    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 1058, Column 1: start tag was here
    <br><a href="http://www.tasiemce24.pl/serial/183-the-mentalist.html" ><div clas…
  • Error Line 1058, Column 93: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …entalist.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1058, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …5. Mentalista" height="93" width="70"><div class="miejsce">5</div></div></a>&n…

    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 1058, Column 94: start tag was here
    …ntalist.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1060, Column 87: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …sip-girl.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1060, Column 258: end tag for "img" omitted, but OMITTAG NO was specified
    …/ Gossip Girl" height="93" width="70"><div class="miejsce">6</div></div></a>&n…

    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 1060, Column 88: start tag was here
    …ip-girl.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1062, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="http://www.tasiemce24.pl/serial/311-supernatural.html" ><div class…

    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 1062, Column 1: start tag was here
    <br><a href="http://www.tasiemce24.pl/serial/311-supernatural.html" ><div class…
  • Error Line 1062, Column 92: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rnatural.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1062, Column 241: end tag for "img" omitted, but OMITTAG NO was specified
    …ral / Rodzice" height="93" width="70"><div class="miejsce">7</div></div></a>&n…

    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 1062, Column 93: start tag was here
    …natural.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1064, Column 88: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …-anatomy.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1064, Column 223: end tag for "img" omitted, but OMITTAG NO was specified
    …"8. chirurdzy" height="93" width="70"><div class="miejsce">8</div></div></a>&n…

    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 1064, Column 89: start tag was here
    …anatomy.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1066, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="http://www.tasiemce24.pl/serial/118-glee.html" ><div class="miejsc…

    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 1066, Column 1: start tag was here
    <br><a href="http://www.tasiemce24.pl/serial/118-glee.html" ><div class="miejsc…
  • Error Line 1066, Column 84: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …118-glee.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1066, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
    … alt="9. Glee" height="93" width="70"><div class="miejsce">9</div></div></a>&n…

    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 1066, Column 85: start tag was here
    …18-glee.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1068, Column 80: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …26-90210.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src…

    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 1068, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …t="10. 90210 " height="93" width="70"><div class="miejsce">10</div></div></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 1068, Column 81: start tag was here
    …6-90210.html" ><div class="miejsce_1"><img class="playtube_serial_banner" src=…
  • Error Line 1068, Column 290: end tag for "br" omitted, but OMITTAG NO was specified
    … height="93" width="70"><div class="miejsce">10</div></div></a>&nbsp;<br></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 1068, Column 281: start tag was here
    … height="93" width="70"><div class="miejsce">10</div></div></a>&nbsp;<br></div>
  • Error Line 1141, Column 196: end tag for "img" omitted, but OMITTAG NO was specified
    …ów z Playtube.pl" title="recenzje i opisy filmów z Playtube.pl" border="0"></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 1141, Column 47: start tag was here
    …f="http://filmweb.pl" target="_blank"><img src="http://www.playtube.pl/images/…
  • Error Line 1146, Column 245: end tag for "img" omitted, but OMITTAG NO was specified
    …ne przez Norton" title="www.playtube.pl chronione przez Norton" border="0"></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 1146, Column 87: start tag was here
    …?url=www.playtube.pl" target="_blank"><img src="http://www.playtube.pl/images/…
  • Error Line 1148, Column 249: end tag for "img" omitted, but OMITTAG NO was specified
    … przez McAfee" title="www.playtube.pl chronione przez McAfee" border="0"></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 1148, Column 91: start tag was here
    …ites/www.playtube.pl" target="_blank"><img src="http://www.playtube.pl/images/…
  • Warning Line 1150, Column 68: cannot generate system identifier for general entity "hl"
    …gle.pl/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qd…

    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 1150, Column 68: general entity "hl" not defined and no default entity
    …gle.pl/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qd…

    This is usually a cascading error caused by 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 1150, Column 70: reference not terminated by REFC delimiter
    …e.pl/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:…

    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 1150, Column 70: reference to external entity in attribute value
    …e.pl/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:…

    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 1150, Column 70: reference to entity "hl" for which no system identifier could be generated
    …e.pl/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:…

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

  • Info Line 1150, Column 67: entity was defined here
    …ogle.pl/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=q…
  • Warning Line 1150, Column 74: cannot generate system identifier for general entity "tbo"
    …/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa…

    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 1150, Column 74: general entity "tbo" not defined and no default entity
    …/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa…

    This is usually a cascading error caused by 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 1150, Column 77: reference not terminated by REFC delimiter
    …bhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&…

    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 1150, Column 77: reference to external entity in attribute value
    …bhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&…

    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 1150, Column 77: reference to entity "tbo" for which no system identifier could be generated
    …bhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&…

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

  • Info Line 1150, Column 73: entity was defined here
    …l/webhp?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&s…
  • Warning Line 1150, Column 80: cannot generate system identifier for general entity "prmd"
    …?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=…

    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 1150, Column 80: general entity "prmd" not defined and no default entity
    …?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=…

    This is usually a cascading error caused by 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 1150, Column 84: reference not terminated by REFC delimiter
    …pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njA…

    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 1150, Column 84: reference to external entity in attribute value
    …pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njA…

    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 1150, Column 84: reference to entity "prmd" for which no system identifier could be generated
    …pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njA…

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

  • Info Line 1150, Column 79: entity was defined here
    …p?hl=pl#q=site:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei…
  • Warning Line 1150, Column 91: cannot generate system identifier for general entity "source"
    …te:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdC…

    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 1150, Column 91: general entity "source" not defined and no default entity
    …te:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdC…

    This is usually a cascading error caused by 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 1150, Column 97: reference not terminated by REFC delimiter
    …ytube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3…

    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 1150, Column 97: reference to external entity in attribute value
    …ytube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3…

    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 1150, Column 97: reference to entity "source" for which no system identifier could be generated
    …ytube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3…

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

  • Info Line 1150, Column 90: entity was defined here
    …ite:playtube.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROd…
  • Warning Line 1150, Column 102: cannot generate system identifier for general entity "tbs"
    ….pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA…

    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 1150, Column 102: general entity "tbs" not defined and no default entity
    ….pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA…

    This is usually a cascading error caused by 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 1150, Column 105: reference not terminated by REFC delimiter
    …&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ve…

    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 1150, Column 105: reference to external entity in attribute value
    …&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ve…

    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 1150, Column 105: reference to entity "tbs" for which no system identifier could be generated
    …&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ve…

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

  • Info Line 1150, Column 101: entity was defined here
    …e.pl&hl=pl&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6B…
  • Warning Line 1150, Column 112: cannot generate system identifier for general entity "sa"
    …tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8Q…

    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 1150, Column 112: general entity "sa" not defined and no default entity
    …tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8Q…

    This is usually a cascading error caused by 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 1150, Column 114: reference not terminated by REFC delimiter
    …o=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8Qpw…

    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 1150, Column 114: reference to external entity in attribute value
    …o=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8Qpw…

    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 1150, Column 114: reference to entity "sa" for which no system identifier could be generated
    …o=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8Qpw…

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

  • Info Line 1150, Column 111: entity was defined here
    …&tbo=1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8…
  • Warning Line 1150, Column 117: cannot generate system identifier for general entity "ei"
    …&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoA…

    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 1150, Column 117: general entity "ei" not defined and no default entity
    …&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoA…

    This is usually a cascading error caused by 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 1150, Column 119: reference not terminated by REFC delimiter
    …rmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&…

    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 1150, Column 119: reference to external entity in attribute value
    …rmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&…

    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 1150, Column 119: reference to entity "ei" for which no system identifier could be generated
    …rmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&…

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

  • Info Line 1150, Column 116: entity was defined here
    …1&prmd=imvns&source=lnt&tbs=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUo…
  • Warning Line 1150, Column 143: cannot generate system identifier for general entity "ved"
    …=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,c…

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

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1150, Column 143: general entity "ved" not defined and no default entity
    …=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,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.

  • Warning Line 1150, Column 146: reference not terminated by REFC delimiter
    …r:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.o…

    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 1150, Column 146: reference to external entity in attribute value
    …r:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.o…

    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 1150, Column 146: reference to entity "ved" for which no system identifier could be generated
    …r:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.o…

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

  • Info Line 1150, Column 142: entity was defined here
    …s=qdr:d&sa=X&ei=3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,…
  • Warning Line 1150, Column 159: cannot generate system identifier for general entity "bav"
    …njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d67…

    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 1150, Column 159: general entity "bav" not defined and no default entity
    …njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d67…

    This is usually a cascading error caused by 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 1150, Column 162: reference not terminated by REFC delimiter
    …TpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d67607…

    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 1150, Column 162: reference to external entity in attribute value
    …TpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d67607…

    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 1150, Column 162: reference to entity "bav" for which no system identifier could be generated
    …TpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d67607…

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

  • Info Line 1150, Column 158: entity was defined here
    …3njATpKROdCGhQfH3eC6BA&ved=0CA8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d6…
  • Warning Line 1150, Column 189: cannot generate system identifier for general entity "fp"
    …QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" t…

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

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1150, Column 189: general entity "fp" not defined and no default entity
    …QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" t…

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

  • Warning Line 1150, Column 191: reference not terminated by REFC delimiter
    …wUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" tar…

    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 1150, Column 191: reference to external entity in attribute value
    …wUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" tar…

    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 1150, Column 191: reference to entity "fp" for which no system identifier could be generated
    …wUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" tar…

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

  • Info Line 1150, Column 188: entity was defined here
    …8QpwUoAg&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" …
  • Warning Line 1150, Column 209: cannot generate system identifier for general entity "biw"
    …r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img …

    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 1150, Column 209: general entity "biw" not defined and no default entity
    …r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img …

    This is usually a cascading error caused by 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 1150, Column 212: reference not terminated by REFC delimiter
    …c.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src…

    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 1150, Column 212: reference to external entity in attribute value
    …c.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src…

    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 1150, Column 212: reference to entity "biw" for which no system identifier could be generated
    …c.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src…

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

  • Info Line 1150, Column 208: entity was defined here
    ….r_gc.r_pw.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img…
  • Warning Line 1150, Column 218: cannot generate system identifier for general entity "bih"
    ….,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src="http…

    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 1150, Column 218: general entity "bih" not defined and no default entity
    ….,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src="http…

    This is usually a cascading error caused by 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 1150, Column 221: reference not terminated by REFC delimiter
    …f.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src="http://…

    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 1150, Column 221: reference to external entity in attribute value
    …f.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src="http://…

    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 1150, Column 221: reference to entity "bih" for which no system identifier could be generated
    …f.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src="http://…

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

  • Info Line 1150, Column 217: entity was defined here
    …w.,cf.osb&fp=1048d676077cad14&biw=1920&bih=1096" target="_blank"><img src="htt…
  • Error Line 1150, Column 359: end tag for "img" omitted, but OMITTAG NO was specified
    …/google.png" alt="google" title="szukaj playtube.pl w google" border="0"></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 1150, Column 244: start tag was here
    …14&biw=1920&bih=1096" target="_blank"><img src="http://www.playtube.pl/images/…
  • Error Line 1153, Column 208: end tag for "img" omitted, but OMITTAG NO was specified
    …z profil na facebook" title="Odwiedź nasz profil na facebook" border="0"></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 1153, Column 65: start tag was here
    …cebook.com/playtubka" target="_blank"><img src="http://www.playtube.pl/images/…
  • Error Line 1193, Column 6: end tag for "center" 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 1162, Column 1: start tag was here
    <center>
  • Error Line 1197, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 1221, Column 9: character data is not allowed here
    </html> scrolling=

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

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

Visitor Analysis

Daily Visitor
  • 9.683 visits