naprzerwie.pl

Na Przerwie.pl... i po szkole - codzienne nowe gry online. Gry logiczne, ubieranki, gry dla dziewczyn, gry dla dzieci, mahjong, kulki, zuma i wiele innych. ...

This data was last updated from 17-03-2015 11:56:37  (update).

Overview Info



  • Domain Name
    naprzerwie.pl
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    6
  • Ip Address
    80.252.0.135
  • Page Size
    98.9 KB
  • Images
    1 GIF, 55 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 60 0 0 0

Website Meta Analysis



  • Title
    Gry Online - Darmowe Gry Dla Dziewczyn, Gry Dla Chłopców, Gry dla Dzieci
  • Meta Keyword
    gry online, gry dla dziewczyn, gry dla dzieci, fajne gry, darmowe gry online, gry logiczne, fajne gierki online, gry za darmo, gry on line, gry strategiczne, gry samochodowe, gry wyścigowe, gry przygodowe, gry karciane, gry oline, gry platformowe, gry zręcznościowe, gry akcji, gierki flash
  • Meta Description
    Na Przerwie.pl... i po szkole - codzienne nowe gry online. Gry logiczne, ubieranki, gry dla dziewczyn, gry dla dzieci, mahjong, kulki, zuma i wiele innych.

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    80.252.0.135
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 17 Mar 2015 11:56:27 GMT
  • server: Apache
  • x-powered-by: Servlet/2.5 JSP/2.1
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • p3p: CP="NOI DSP COR NID PSAo OUR IND"
  • content-type: text/html; charset=iso-8859-2
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for naprzerwie.pl

IP 80.252.0.135 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 124 Errors
  • 44 Warnings
Ratio Text/Html
  • 0.7050695795597081
Message Error
  • Error Line 87, Column 16: there is no attribute "PROPERTY"
    <meta property="og:image" content="http://bi.gazeta.pl/im/8/14837/m14837798,ZAS…

    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 87, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …ge" content="http://bi.gazeta.pl/im/8/14837/m14837798,ZASLEPKA-STRZALKA.jpg" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 92, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <meta property="og:site_name" content="naprzerwie.pl"/> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 92, Column 54: document type does not allow element "META" here
    <meta property="og:site_name" content="naprzerwie.pl"/> 

    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 95, Column 54: NET-enabling start-tag requires SHORTTAG YES
    	<meta property="fb:app_id" content="177459862392178"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 95, Column 54: document type does not allow element "META" here
    	<meta property="fb:app_id" content="177459862392178"/>

    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 106, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="t-YMabN-d0KzIeRQ83mNPDar6jifzrEIexSpzNc8h2Q" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 106, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="t-YMabN-d0KzIeRQ83mNPDar6jifzrEIexSpzNc8h2Q" />

    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 107, Column 191: document type does not allow element "META" here
    …anki, gry dla dziewczyn, gry dla dzieci, mahjong, kulki, zuma i wiele innych.">

    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 108, Column 323: document type does not allow element "META" here
    …ciane, gry oline, gry platformowe, gry zręcznościowe, gry akcji, gierki flash">

    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 123, Column 275: NET-enabling start-tag requires SHORTTAG YES
    …6593396404" style="display: block !important; margin:0 auto; "/></a></noscript>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 123, Column 275: required attribute "ALT" not specified
    …6593396404" style="display: block !important; margin:0 auto; "/></a></noscript>

    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 124, Column 132: document type does not allow element "LINK" here
    …e="param.rss_tytul uuuummm" href="http://rss.gazeta.pl/pub/rss/naprzerwie.xml">

    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 125, Column 87: document type does not allow element "LINK" here
    …l="stylesheet" href="http://bi.gazeta.pl/css/globalshared.css" type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 126, Column 91: document type does not allow element "LINK" here
    …stylesheet" href="http://bi.gazeta.pl/css/globalshared_bs.css" type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 127, Column 91: document type does not allow element "LINK" here
    …stylesheet" href="http://bi.gazeta.pl/css/naprzerwie/lay0.css" type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 129, Column 94: document type does not allow element "LINK" here
    …naprzerwie/style0.css" type="text/css"><script language="javascript">var now =…

    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 129, Column 124: required attribute "TYPE" not specified
    …ext/css"><script language="javascript">var now = new Date(2015, 2, 17, 12, 56,…

    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 131, Column 76: document type does not allow element "LINK" here
    <link rel="shortcut icon" href="http://bi.gazeta.pl/im/5/5121/m5121405.png">

    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 192, Column 192: required attribute "TYPE" not specified
    …y:hidden"></iframe></noscript> <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l]…

    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 197, Column 64: document type does not allow element "LINK" here
    <link rel="stylesheet" type="text/css" href="/info/404/404.css"> 

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

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

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

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

  • Error Line 213, Column 10: document type does not allow element "BODY" here
        <body>    

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 218, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Error Line 281, Column 22: there is no attribute "ID"
    		       <section id="page-hat" data-position="czapeczka">	        

    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 281, Column 47: there is no attribute "DATA-POSITION"
    		       <section id="page-hat" data-position="czapeczka">	        

    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 281, Column 58: element "SECTION" undefined
    		       <section id="page-hat" data-position="czapeczka">	        

    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 282, Column 21: there is no attribute "CLASS"
    		    	  <nav class="hat-body">

    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 282, Column 31: element "NAV" undefined
    		    	  <nav class="hat-body">

    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).
  • Warning Line 364, Column 84: cannot generate system identifier for general entity "back"
    …0,97382,5461177.html?utm_nooverride=1&back=http%3A%2F%2Fwww.naprzerwie.pl%2Fna…

    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 364, Column 84: general entity "back" not defined and no default entity
    …0,97382,5461177.html?utm_nooverride=1&back=http%3A%2F%2Fwww.naprzerwie.pl%2Fna…

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

  • Error Line 364, Column 88: reference to entity "back" for which no system identifier could be generated
    …382,5461177.html?utm_nooverride=1&back=http%3A%2F%2Fwww.naprzerwie.pl%2Fnaprze…

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

  • Info Line 364, Column 83: entity was defined here
    …/0,97382,5461177.html?utm_nooverride=1&back=http%3A%2F%2Fwww.naprzerwie.pl%2Fn…
  • Error Line 386, Column 137: required attribute "ALT" not specified
    …rect" href="http://www.naprzerwie.pl/"></map><img class="Wimg3" src="http://bi…

    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 386, Column 322: an attribute value must be a literal unless it contains only name characters
    …ute;w, Dzieci - NaPrzerwie.pl" usemap=#winieta /></div></div><!--winieta /zaj/…

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

  • Warning Line 386, Column 331: NET-enabling start-tag requires SHORTTAG YES
    …ieci - NaPrzerwie.pl" usemap=#winieta /></div></div><!--winieta /zaj/5089/n508…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 403, Column 74: required attribute "ACTION" not specified
    …pageSearch"><div class="visible"><form><fieldset><input id="pageSearchQ"><div …

    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 403, Column 108: start tag for "LEGEND" omitted, but its declaration does not permit this
    …form><fieldset><input id="pageSearchQ"><div class="folded"><ul><li data-target…
  • Error Line 403, Column 128: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …t id="pageSearchQ"><div class="folded"><ul><li data-target="serwis">w serwisie…

    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 403, Column 149: there is no attribute "DATA-TARGET"
    …iv class="folded"><ul><li data-target="serwis">w serwisie</li><li data-target=…

    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 403, Column 271: end tag for "LEGEND" omitted, but its declaration does not permit this
    …alue="Szukaj" type="submit"></fieldset></form></div><div class="hidden"><form …
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 403, Column 85: start tag was here
    …><div class="visible"><form><fieldset><input id="pageSearchQ"><div class="fold…
  • Error Line 403, Column 323: there is no attribute "DATA-TARGET"
    …<div class="hidden"><form data-target="serwis" data-default method="get" actio…

    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 403, Column 345: "DATA-DEFAULT" is not a member of a group specified for any attribute
    …orm data-target="serwis" data-default method="get" action="http://szukaj.gazet…
  • Error Line 403, Column 443: "DATA-QUERY" is not a member of a group specified for any attribute
    …l"><p><input type="hidden" data-query name="query"/><input value="Gry" name="n…
  • Warning Line 403, Column 455: NET-enabling start-tag requires SHORTTAG YES
    … type="hidden" data-query name="query"/><input value="Gry" name="navservice" t…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 403, Column 645: "DATA-QUERY" is not a member of a group specified for any attribute
    …tykul"><p><input type="hidden" data-query name="query"/></p></form></div></div>
  • Warning Line 403, Column 657: NET-enabling start-tag requires SHORTTAG YES
    …tykul"><p><input type="hidden" data-query name="query"/></p></form></div></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 416, Column 29: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		       <span class="kL"><p>

    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 558, Column 121: NET-enabling start-tag requires SHORTTAG YES
    …c="http://bi.gazeta.pl/im/4a/af/10/z17497674C,Ubieranka--prawdziwy-aniol.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 558, Column 121: required attribute "ALT" not specified
    …c="http://bi.gazeta.pl/im/4a/af/10/z17497674C,Ubieranka--prawdziwy-aniol.jpg"/>

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

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

  • Warning Line 858, Column 119: NET-enabling start-tag requires SHORTTAG YES
    …src="http://bi.gazeta.pl/im/44/af/10/z17497668C,Ubieranka--przyszla-mama.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 858, Column 119: required attribute "ALT" not specified
    …src="http://bi.gazeta.pl/im/44/af/10/z17497668C,Ubieranka--przyszla-mama.jpg"/>

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

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

  • Warning Line 1158, Column 99: NET-enabling start-tag requires SHORTTAG YES
    …               <img src="http://bi.gazeta.pl/im/3d/af/10/z17497661C,GOL-.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1158, Column 99: required attribute "ALT" not specified
    …               <img src="http://bi.gazeta.pl/im/3d/af/10/z17497661C,GOL-.jpg"/>

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

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

  • Warning Line 1460, Column 121: NET-enabling start-tag requires SHORTTAG YES
    …c="http://bi.gazeta.pl/im/37/af/10/z17497655C,Co-dwie-glowy-to-nie-jedna.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1460, Column 121: required attribute "ALT" not specified
    …c="http://bi.gazeta.pl/im/37/af/10/z17497655C,Co-dwie-glowy-to-nie-jedna.jpg"/>

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

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

  • Warning Line 1760, Column 112: NET-enabling start-tag requires SHORTTAG YES
    …  <img src="http://bi.gazeta.pl/im/0e/af/10/z17497614C,Wojna-na-papierze.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1760, Column 112: required attribute "ALT" not specified
    …  <img src="http://bi.gazeta.pl/im/0e/af/10/z17497614C,Wojna-na-papierze.jpg"/>

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

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

  • Warning Line 2060, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …http://bi.gazeta.pl/im/84/aa/10/z17475204C,Ubieranka--czapka-dla-kazdego.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2060, Column 124: required attribute "ALT" not specified
    …http://bi.gazeta.pl/im/84/aa/10/z17475204C,Ubieranka--czapka-dla-kazdego.jpg"/>

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

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

  • Warning Line 2360, Column 112: NET-enabling start-tag requires SHORTTAG YES
    …  <img src="http://bi.gazeta.pl/im/7d/aa/10/z17475197C,Hakerska-ucieczka.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2360, Column 112: required attribute "ALT" not specified
    …  <img src="http://bi.gazeta.pl/im/7d/aa/10/z17475197C,Hakerska-ucieczka.jpg"/>

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

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

  • Warning Line 2660, Column 114: NET-enabling start-tag requires SHORTTAG YES
    …<img src="http://bi.gazeta.pl/im/67/aa/10/z17475175C,Ekran-pelen-przygod.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2660, Column 114: required attribute "ALT" not specified
    …<img src="http://bi.gazeta.pl/im/67/aa/10/z17475175C,Ekran-pelen-przygod.jpg"/>

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

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

  • Warning Line 2960, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …   <img src="http://bi.gazeta.pl/im/64/aa/10/z17475172C,Obronca-ze-stali.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2960, Column 111: required attribute "ALT" not specified
    …   <img src="http://bi.gazeta.pl/im/64/aa/10/z17475172C,Obronca-ze-stali.jpg"/>

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

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

  • Warning Line 3267, Column 121: cannot generate system identifier for general entity "utm_medium"
    …-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&ut…

    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 3267, Column 121: general entity "utm_medium" not defined and no default entity
    …-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&ut…

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

  • Error Line 3267, Column 131: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Warning Line 3267, Column 138: cannot generate system identifier for general entity "utm_content"
    …ce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes…

    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 3267, Column 138: general entity "utm_content" not defined and no default entity
    …ce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes…

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

  • Error Line 3267, Column 149: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><i…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Warning Line 3267, Column 159: cannot generate system identifier for general entity "utm_campaign"
    …utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title="…

    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 3267, Column 159: general entity "utm_campaign" not defined and no default entity
    …utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title="…

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

  • Error Line 3267, Column 171: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title="" alt="" 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 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3267, Column 405: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3267, Column 423: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online">GR…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3267, Column 445: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Heroes_Online">GRAJ</a></p></div></div>…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3267, Column 1094: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3267, Column 1112: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online">GR…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3267, Column 1134: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Heroes_Online">GRAJ</a></p></div></div>…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3269, Column 109: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3269, Column 127: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Bigfarm"><img tit…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3269, Column 149: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Bigfarm"><img title="" alt="" 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 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3269, Column 355: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3269, Column 373: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Bigfarm">GRAJ</a>…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3269, Column 395: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Bigfarm">GRAJ</a></p></div></div><div c…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3277, Column 153: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3277, Column 171: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Bigfarm">GRAJ</a>…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3277, Column 193: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Bigfarm">GRAJ</a></p></div></div></div>…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3393, Column 117: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3393, Column 135: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Goodgame_Empire">…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3393, Column 157: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Goodgame_Empire"><img title="" alt="" s…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3393, Column 379: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3393, Column 397: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Goodgame_Empire">…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3393, Column 419: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Goodgame_Empire">GRAJ</a></p></div></di…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 3399, Column 161: reference to entity "utm_medium" for which no system identifier could be generated
    …tm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 3399, Column 179: reference to entity "utm_content" for which no system identifier could be generated
    …ie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Goodgame_Empire">…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 3399, Column 201: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=Goodgame_Empire">GRAJ</a></p></div></di…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Warning Line 3512, Column 108: NET-enabling start-tag requires SHORTTAG YES
    …      <img src="http://bi.gazeta.pl/im/35/81/10/z17308981C,Lamacz-barier.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 3512, Column 108: required attribute "ALT" not specified
    …      <img src="http://bi.gazeta.pl/im/35/81/10/z17308981C,Lamacz-barier.jpg"/>

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

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

  • Warning Line 3812, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …     <img src="http://bi.gazeta.pl/im/7f/81/10/z17308799C,Szybki-diament.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 3812, Column 109: required attribute "ALT" not specified
    …     <img src="http://bi.gazeta.pl/im/7f/81/10/z17308799C,Szybki-diament.jpg"/>

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

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

  • Warning Line 4112, Column 117: NET-enabling start-tag requires SHORTTAG YES
    …g src="http://bi.gazeta.pl/im/8d/5d/10/z17159821C,Dom-szalonego-naukowca.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 4112, Column 117: required attribute "ALT" not specified
    …g src="http://bi.gazeta.pl/im/8d/5d/10/z17159821C,Dom-szalonego-naukowca.jpg"/>

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

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

  • Warning Line 4412, Column 113: NET-enabling start-tag requires SHORTTAG YES
    … <img src="http://bi.gazeta.pl/im/99/5b/10/z17152409C,Swiateczne-babelki.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 4412, Column 113: required attribute "ALT" not specified
    … <img src="http://bi.gazeta.pl/im/99/5b/10/z17152409C,Swiateczne-babelki.jpg"/>

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

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

  • Warning Line 4712, Column 112: NET-enabling start-tag requires SHORTTAG YES
    …  <img src="http://bi.gazeta.pl/im/bd/5b/10/z17152701C,Ogrodowy-minigolf.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 4712, Column 112: required attribute "ALT" not specified
    …  <img src="http://bi.gazeta.pl/im/bd/5b/10/z17152701C,Ogrodowy-minigolf.jpg"/>

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

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

  • Warning Line 5012, Column 106: NET-enabling start-tag requires SHORTTAG YES
    …        <img src="http://bi.gazeta.pl/im/a2/5b/10/z17152674C,Do-tablicy-.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5012, Column 106: required attribute "ALT" not specified
    …        <img src="http://bi.gazeta.pl/im/a2/5b/10/z17152674C,Do-tablicy-.jpg"/>

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

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

  • Warning Line 5312, Column 106: NET-enabling start-tag requires SHORTTAG YES
    …        <img src="http://bi.gazeta.pl/im/9b/5a/10/z17149851C,Scal-dzialo.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5312, Column 106: required attribute "ALT" not specified
    …        <img src="http://bi.gazeta.pl/im/9b/5a/10/z17149851C,Scal-dzialo.jpg"/>

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

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

  • Warning Line 5612, Column 135: NET-enabling start-tag requires SHORTTAG YES
    …azeta.pl/im/9f/5a/10/z17149855C,Szkolna-zagadka--pracownia-informatyczna.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5612, Column 135: required attribute "ALT" not specified
    …azeta.pl/im/9f/5a/10/z17149855C,Szkolna-zagadka--pracownia-informatyczna.jpg"/>

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

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

  • Warning Line 5912, Column 112: NET-enabling start-tag requires SHORTTAG YES
    …  <img src="http://bi.gazeta.pl/im/eb/b3/fc/z16561131C,Ceglana-ukladanka.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5912, Column 112: required attribute "ALT" not specified
    …  <img src="http://bi.gazeta.pl/im/eb/b3/fc/z16561131C,Ceglana-ukladanka.jpg"/>

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

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

  • Warning Line 6212, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …//bi.gazeta.pl/im/fa/b8/fc/z16562426C,Pandemia--gra-w-jezyku-angielskim-.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 6212, Column 129: required attribute "ALT" not specified
    …//bi.gazeta.pl/im/fa/b8/fc/z16562426C,Pandemia--gra-w-jezyku-angielskim-.jpg"/>

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

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

  • Warning Line 6512, Column 113: NET-enabling start-tag requires SHORTTAG YES
    … <img src="http://bi.gazeta.pl/im/b7/b9/fc/z16562615C,Ahoj---lamiglowko-.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 6512, Column 113: required attribute "ALT" not specified
    … <img src="http://bi.gazeta.pl/im/b7/b9/fc/z16562615C,Ahoj---lamiglowko-.jpg"/>

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

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

  • Warning Line 6812, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …    <img src="http://bi.gazeta.pl/im/0a/bb/fc/z16562954C,Skoczny-diament.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 6812, Column 110: required attribute "ALT" not specified
    …    <img src="http://bi.gazeta.pl/im/0a/bb/fc/z16562954C,Skoczny-diament.jpg"/>

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

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

  • Warning Line 7112, Column 113: NET-enabling start-tag requires SHORTTAG YES
    … <img src="http://bi.gazeta.pl/im/c9/d4/fc/z16569545C,Zlodziejskie-drony.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 7112, Column 113: required attribute "ALT" not specified
    … <img src="http://bi.gazeta.pl/im/c9/d4/fc/z16569545C,Zlodziejskie-drony.jpg"/>

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

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

  • Warning Line 7412, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …    <img src="http://bi.gazeta.pl/im/38/b3/fc/z16560952C,Azteckie-kulki-.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 7412, Column 110: required attribute "ALT" not specified
    …    <img src="http://bi.gazeta.pl/im/38/b3/fc/z16560952C,Azteckie-kulki-.jpg"/>

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

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

  • Warning Line 7712, Column 107: NET-enabling start-tag requires SHORTTAG YES
    …       <img src="http://bi.gazeta.pl/im/c4/77/fd/z16611268C,Wladca-kulki.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 7712, Column 107: required attribute "ALT" not specified
    …       <img src="http://bi.gazeta.pl/im/c4/77/fd/z16611268C,Wladca-kulki.jpg"/>

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

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

  • Warning Line 8012, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …   <img src="http://bi.gazeta.pl/im/6b/b3/fc/z16561003C,Wielozadaniowiec.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 8012, Column 111: required attribute "ALT" not specified
    …   <img src="http://bi.gazeta.pl/im/6b/b3/fc/z16561003C,Wielozadaniowiec.jpg"/>

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

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

  • Warning Line 8312, Column 113: NET-enabling start-tag requires SHORTTAG YES
    … <img src="http://bi.gazeta.pl/im/9d/b8/fc/z16562333C,Drogocenny-diament.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 8312, Column 113: required attribute "ALT" not specified
    … <img src="http://bi.gazeta.pl/im/9d/b8/fc/z16562333C,Drogocenny-diament.jpg"/>

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

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

  • Warning Line 8612, Column 107: NET-enabling start-tag requires SHORTTAG YES
    …       <img src="http://bi.gazeta.pl/im/a8/b3/fc/z16561064C,Zlota-raczka.jpg"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 8612, Column 107: required attribute "ALT" not specified
    …       <img src="http://bi.gazeta.pl/im/a8/b3/fc/z16561064C,Zlota-raczka.jpg"/>

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

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

  • Warning Line 9345, Column 1081: unclosed start-tag requires SHORTTAG YES
    …epsze gry Mahjong według serwisu <a...</span></li><li class="even"><div class=…

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 9345, Column 1081: element "A..." undefined
    …epsze gry Mahjong według serwisu <a...</span></li><li class="even"><div class=…

    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 9363, Column 172: reference to entity "utm_medium" for which no system identifier could be generated
    …utm_source=Naprzerwie_Prawa&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 9363, Column 190: reference to entity "utm_content" for which no system identifier could be generated
    …wie_Prawa&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=gry.naprzerwie"><…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 9363, Column 212: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=gry.naprzerwie"><img alt="" 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 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 9363, Column 463: reference to entity "utm_medium" for which no system identifier could be generated
    …utm_source=Naprzerwie_Prawa&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 9363, Column 481: reference to entity "utm_content" for which no system identifier could be generated
    …wie_Prawa&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=gry.naprzerwie"><…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 9363, Column 503: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=gry.naprzerwie"><img alt="" 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 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 9363, Column 754: reference to entity "utm_medium" for which no system identifier could be generated
    …utm_source=Naprzerwie_Prawa&utm_medium=Kafle&utm_content=Kampanie&utm_campaign…

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

  • Info Line 3267, Column 120: entity was defined here
    …s-online/?utm_source=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&u…
  • Error Line 9363, Column 772: reference to entity "utm_content" for which no system identifier could be generated
    …wie_Prawa&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=gry.naprzerwie"><…

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

  • Info Line 3267, Column 137: entity was defined here
    …rce=Naprzerwie_Srodek&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroe…
  • Error Line 9363, Column 794: reference to entity "utm_campaign" for which no system identifier could be generated
    …afle&utm_content=Kampanie&utm_campaign=gry.naprzerwie"><img alt="" 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 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Error Line 9363, Column 1229: there is no attribute "CLASS"
    …tm/5400/n5400290.htm--><article class="mod mod_cpCommerce small" data-ga="&amp…

    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 9363, Column 1264: there is no attribute "DATA-GA"
    …ss="mod mod_cpCommerce small" data-ga="&amp;utm_content=naprzerwie"  data-limi…

    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 9363, Column 1306: there is no attribute "DATA-LIMIT"
    …" data-ga="&amp;utm_content=naprzerwie"  data-limit="4"   data-source="okazje">

    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 9363, Column 1324: there is no attribute "DATA-SOURCE"
    …" data-ga="&amp;utm_content=naprzerwie"  data-limit="4"   data-source="okazje">

    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 9363, Column 1332: element "ARTICLE" undefined
    …" data-ga="&amp;utm_content=naprzerwie"  data-limit="4"   data-source="okazje">

    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 9364, Column 8: element "HEADER" undefined
    <header>

    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).
  • Warning Line 9365, Column 52: cannot generate system identifier for general entity "utm_source"
    …://www.okazje.info.pl/?utm_medium=cpc&utm_source=gazeta&utm_campaign=gazeta"><…

    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 9365, Column 52: general entity "utm_source" not defined and no default entity
    …://www.okazje.info.pl/?utm_medium=cpc&utm_source=gazeta&utm_campaign=gazeta"><…

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

  • Error Line 9365, Column 62: reference to entity "utm_source" for which no system identifier could be generated
    …zje.info.pl/?utm_medium=cpc&utm_source=gazeta&utm_campaign=gazeta"><img src="h…

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

  • Info Line 9365, Column 51: entity was defined here
    …p://www.okazje.info.pl/?utm_medium=cpc&utm_source=gazeta&utm_campaign=gazeta">…
  • Error Line 9365, Column 82: reference to entity "utm_campaign" for which no system identifier could be generated
    …ium=cpc&utm_source=gazeta&utm_campaign=gazeta"><img src="http://bi.gazeta.pl/i…

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

  • Info Line 3267, Column 158: entity was defined here
    …&utm_medium=Kafle&utm_content=Kampanie&utm_campaign=Heroes_Online"><img title=…
  • Warning Line 9365, Column 146: NET-enabling start-tag requires SHORTTAG YES
    …_campaign=gazeta"><img src="http://bi.gazeta.pl/im/1/11872/m11872411.png"/></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 9365, Column 146: required attribute "ALT" not specified
    …_campaign=gazeta"><img src="http://bi.gazeta.pl/im/1/11872/m11872411.png"/></a>

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

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

  • Error Line 9368, Column 16: there is no attribute "CLASS"
    <section class="search">

    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 9368, Column 24: element "SECTION" undefined
    <section class="search">

    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 9369, Column 33: there is no attribute "AUTOCOMPLETE"
    <input type="text" autocomplete="off" name="searched" id="oi_search" placeholde…

    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 9369, Column 82: there is no attribute "PLACEHOLDER"
    …te="off" name="searched" id="oi_search" placeholder="Wpisz co chcesz kupić...">

    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 9372, Column 44: element "SECTION" undefined
    <section class="body pricein imgB  border ">

    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).
  • Warning Line 9375, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …15aQcmLQN5TOGT5C3w3O2pZz.tNFSXuWK.k7ujY8ALL..7/stparam=nffnbuqguj" border="0"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 9375, Column 129: required attribute "ALT" not specified
    …15aQcmLQN5TOGT5C3w3O2pZz.tNFSXuWK.k7ujY8ALL..7/stparam=nffnbuqguj" border="0"/>

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

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

  • Error Line 9376, Column 8: element "FOOTER" undefined
    <footer>

    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).
  • Warning Line 9443, Column 94: cannot generate system identifier for general entity "refnlt"
    …l/newslettery/0,0.html?fromnlt=stopka&refnlt=http://www.naprzerwie.pl/naprzerw…

    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 9443, Column 94: general entity "refnlt" not defined and no default entity
    …l/newslettery/0,0.html?fromnlt=stopka&refnlt=http://www.naprzerwie.pl/naprzerw…

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

  • Error Line 9443, Column 100: reference to entity "refnlt" for which no system identifier could be generated
    …lettery/0,0.html?fromnlt=stopka&refnlt=http://www.naprzerwie.pl/naprzerwie/" c…

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

  • Info Line 9443, Column 93: entity was defined here
    …pl/newslettery/0,0.html?fromnlt=stopka&refnlt=http://www.naprzerwie.pl/naprzer…

Visitor Analysis

Daily Visitor
  • 607 visits

In Page Analysis