Serwis internetowy tygodnika POLITYKA. Analizy, komentarze, blogi, recenzje. ...

polityka.pl
  • Domain Name
    polityka.pl
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #29595
  • Page Size
    213.7 KB
  • Ip Address
    217.17.45.162
  • Heading
    H1: 1, H2: 4, H3: 7, H4: 50, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 12 PNG

Website Meta Analysis

  • Title
    Polityka.pl - serwis internetowy tygodnika Polityka
  • Meta Keyword
    tygodnik Polityka, polityka, Polityka
  • Meta Description
    Serwis internetowy tygodnika POLITYKA. Analizy, komentarze, blogi, recenzje.

Technical Analysis

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

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

HTML Analysis

  • date: Fri, 28 Jun 2013 15:32:16 GMT
  • server: Apache
  • p3p: CP="NOI DSP COR NID PSAo OUR IND"
  • cache-control: max-age=1
  • expires: Fri, 28 Jun 2013 15:32:17 GMT
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html;charset=UTF-8
  • x-cache: MISS from kvm191
  • x-cache-lookup: MISS from kvm191:80
  • via: 1.0 kvm191 (squid)
  • connection: close
  • x-google-cache-control: remote-fetch

DOMAIN NAME: polityka.pl
registrant type: organization
nameservers: ns3.eo.pl. [217.17.46.218]
dns1.polityka.com.pl. [83.238.13.194]
created: 1999.12.27 12:00:00
last modified: 2011.12.19 16:04:43
renewal date: 2012.12.26 13:00:00

option created: 2011.11.29 14:47:18
option expiration date: 2014.11.29 14:47:18

dnssec: Unsigned


REGISTRAR:
Domainmaker sp. z o.o.
ul. Gdanska 107
85-022 Bydgoszcz
Polska/Poland
+48.525524220
www.domainmaker.pl

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

DNS Analysis


DNS servers
ns3.eo.pl [217.17.46.218]
dns1.polityka.com.pl


DNS Records

Answer records
polityka.pl A 217.17.45.162 86400s
polityka.pl NS  ns3.eo.pl 600s
polityka.pl NS  wexch1.wydawnictwo.local 600s
polityka.pl NS  dns2.polityka.com.pl 600s
polityka.pl NS  ns2.eo.pl 600s
polityka.pl NS  wexch2.wydawnictwo.local 600s
polityka.pl NS  dns1.polityka.com.pl 600s
polityka.pl SOA
server: dns1.polityka.com.pl
email: administrator@polityka.com.pl
serial: 660
refresh: 10800
retry: 3600
expire: 1209600
minimum ttl: 600
600s
polityka.pl MX
preference: 10
exchange: mail.polityka.com.pl
600s
polityka.pl MX
preference: 10
exchange: upc74.polityka.com.pl
600s
polityka.pl MX
preference: 10
exchange: upc218.polityka.com.pl
600s
polityka.pl TXT v=spf1 include:polityka.com.pl include:amazonses.com -all 86400s
polityka.pl TXT v=spf2.0/pra include:polityka.com.pl include:amazonses.com -all 600s
polityka.pl RP
email: administrator@polityka.com.pl
txt domain:
600s

Authority records

Additional records
ns3.eo.pl A 217.17.46.218 600s
wexch1.wydawnictwo.local A 192.168.2.126 600s

IP 217.17.45.162 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    EU
  • Continent Code
    52° North
  • Latitude
    20.
  • Longitude
  • No whois ip data for 217.17.45.162

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 931 Errors
  • 71 Warnings
Ratio Text/Html
  • 0.7851019885948238
Message Error
  • Error Line 17, Column 36: there is no attribute "sizes"
    <link rel="apple-touch-icon" sizes="72x72" href="http://www.polityka.pl/_resour…

    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 45, Column 132: end tag for "link" omitted, but OMITTAG NO was specified
    … title="Strona główna" href="http://www.polityka.pl/rss/articles.xml?list=519">

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

  • Info Line 45, Column 5: start tag was here
        <link rel="alternate" type="application/rss+xml" title="Strona główna" href…
  • Warning Line 76, Column 191: cannot generate system identifier for general entity "keywords"
    …lease/showit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' styl…

    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 76, Column 191: general entity "keywords" not defined and no default entity
    …lease/showit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' styl…

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

  • Warning Line 76, Column 199: reference not terminated by REFC delimiter
    …owit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' style='borde…

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

  • Warning Line 76, Column 199: reference to external entity in attribute value
    …owit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' style='borde…

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

  • Error Line 76, Column 199: reference to entity "keywords" for which no system identifier could be generated
    …owit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' style='borde…

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

  • Info Line 76, Column 190: entity was defined here
    …please/showit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' sty…
  • Warning Line 200, Column 132: cannot generate system identifier for general entity "login_error"
    …ccess=http%3A%2F%2Fwww.polityka.pl%2F&login_error=http%3A%2F%2Fwww.polityka.pl…

    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 200, Column 132: general entity "login_error" not defined and no default entity
    …ccess=http%3A%2F%2Fwww.polityka.pl%2F&login_error=http%3A%2F%2Fwww.polityka.pl…

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

  • Warning Line 200, Column 143: reference not terminated by REFC delimiter
    …3A%2F%2Fwww.polityka.pl%2F&login_error=http%3A%2F%2Fwww.polityka.pl%2F%3FshowL…

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

  • Warning Line 200, Column 143: reference to external entity in attribute value
    …3A%2F%2Fwww.polityka.pl%2F&login_error=http%3A%2F%2Fwww.polityka.pl%2F%3FshowL…

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

  • Error Line 200, Column 143: reference to entity "login_error" for which no system identifier could be generated
    …3A%2F%2Fwww.polityka.pl%2F&login_error=http%3A%2F%2Fwww.polityka.pl%2F%3FshowL…

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

  • Info Line 200, Column 131: entity was defined here
    …uccess=http%3A%2F%2Fwww.polityka.pl%2F&login_error=http%3A%2F%2Fwww.polityka.p…
  • Error Line 496, Column 16: ID "worth_reading_header_img" already defined
          <img id="worth_reading_header_img" src="http://www.polityka.pl/_resource/…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 483, Column 16: ID "worth_reading_header_img" first defined here
          <img id="worth_reading_header_img" src="http://www.polityka.pl/_resource/…
  • Error Line 497, Column 15: ID "worth_reading_header" already defined
        <span id="worth_reading_header"></span>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 484, Column 15: ID "worth_reading_header" first defined here
        <span id="worth_reading_header"></span>
  • Warning Line 914, Column 199: reference not terminated by REFC delimiter
    …owit/4057/1/6/36/?typkodu=img&keywords=' width='300' height='250' style='borde…

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

  • Warning Line 914, Column 199: reference to external entity in attribute value
    …owit/4057/1/6/36/?typkodu=img&keywords=' width='300' height='250' style='borde…

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

  • Error Line 914, Column 199: reference to entity "keywords" for which no system identifier could be generated
    …owit/4057/1/6/36/?typkodu=img&keywords=' width='300' height='250' style='borde…

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

  • Info Line 76, Column 190: entity was defined here
    …please/showit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' sty…
  • Error Line 936, Column 77: required attribute "alt" not specified
    	<img class="pc_box300_logo" src="_resource/fs/images/naglowki/PC_logo.png"/>

    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 941, Column 130: required attribute "alt" not specified
    …yka.pl:80/_resource/res/path/d2/ab/d2abb227-24c7-4491-b208-493c3bc7aab3_150x"/>

    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 963, Column 252: end tag for "img" omitted, but OMITTAG NO was specified
    … i gorsi od nas, a Hobbes tłumaczył, że bez ośmieszania innych nie ma frajdy.">

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

  • Info Line 963, Column 7: start tag was here
    						<img src="http://static.polityka.pl:80/_resource/res/path/2a/2c/2a2cd161-…
  • Error Line 984, Column 174: end tag for "img" omitted, but OMITTAG NO was specified
    …aa86eadd420b_f268x101" alt="Andrzej z żoną Mariolą i synem Andrzejem, 2010 r.">

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

  • Info Line 984, Column 7: start tag was here
    						<img src="http://static.polityka.pl:80/_resource/res/path/58/49/5849b962-…
  • Error Line 1005, Column 168: end tag for "img" omitted, but OMITTAG NO was specified
    …-bc5c-4da4da626d2d_f268x101" alt="Histopatologiczny obraz szpiczaka mnogiego.">

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

  • Info Line 1005, Column 7: start tag was here
    						<img src="http://static.polityka.pl:80/_resource/res/path/44/88/448837d4-…
  • Error Line 1022, Column 329: there is no attribute "align"
    …version=8,0,0,0" width="300" height="190" id="trasy_02_300x190" align="middle">

    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 1025, Column 188: there is no attribute "src"
    …bgcolor" value="#9f0200" /><embed src="http://www.polityka.pl/download/szwajca…

    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 1025, Column 266: there is no attribute "quality"
    …ria2012/trasy_03_300x190.swf" quality="best" bgcolor="#9f0200" width="300" hei…

    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 1025, Column 281: there is no attribute "bgcolor"
    …3_300x190.swf" quality="best" bgcolor="#9f0200" width="300" height="190" name=…

    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 1025, Column 297: there is no attribute "width"
    …uality="best" bgcolor="#9f0200" width="300" height="190" name="trasy_04_300x19…

    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 1025, Column 310: there is no attribute "height"
    … bgcolor="#9f0200" width="300" height="190" name="trasy_04_300x190" align="mid…

    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 1025, Column 321: there is no attribute "name"
    …9f0200" width="300" height="190" name="trasy_04_300x190" align="middle" allowS…

    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 1025, Column 346: there is no attribute "align"
    …t="190" name="trasy_04_300x190" align="middle" allowScriptAccess="sameDomain" …

    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 1025, Column 373: there is no attribute "allowScriptAccess"
    …190" align="middle" allowScriptAccess="sameDomain" allowFullScreen="false" typ…

    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 1025, Column 402: there is no attribute "allowFullScreen"
    …ptAccess="sameDomain" allowFullScreen="false" type="application/x-shockwave-fl…

    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 1025, Column 415: there is no attribute "type"
    …eDomain" allowFullScreen="false" type="application/x-shockwave-flash" pluginsp…

    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 1025, Column 459: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.adobe.com/go/getflashplayer_…

    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 1025, Column 504: element "embed" undefined
    …n/x-shockwave-flash" pluginspage="http://www.adobe.com/go/getflashplayer_pl" />

    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 1186, Column 299: there is no attribute "profile_id"
    …7642e37");</script><fb:fan profile_id="255100403945" stream="0" connections="1…

    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 1186, Column 321: there is no attribute "stream"
    …:fan profile_id="255100403945" stream="0" connections="10" logobar="1" width="…

    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 1186, Column 337: there is no attribute "connections"
    …"255100403945" stream="0" connections="10" logobar="1" width="300"></fb:fan><d…

    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 1186, Column 350: there is no attribute "logobar"
    …" stream="0" connections="10" logobar="1" width="300"></fb:fan><div style="fon…

    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 1186, Column 360: there is no attribute "width"
    …0" connections="10" logobar="1" width="300"></fb:fan><div style="font-size:8px…

    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 1186, Column 365: element "fb:fan" undefined
    …nnections="10" logobar="1" width="300"></fb:fan><div style="font-size:8px; pad…

    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 2644, Column 24: character "<" is the first character of a delimiter but occurred as data
    	   for ( var i = 0; i < images.length; i++ )

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2778, Column 29: character "<" is the first character of a delimiter but occurred as data
    		for (var index = 0; index < (5 + 1); index++) {

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 2877, Column 5: document type does not allow element "br" here; assuming missing "li" start-tag
    <br/>
  • Error Line 2878, Column 20: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
      <li class="first">

    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 2881, Column 6: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
      <li>

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

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

  • Error Line 2884, Column 6: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
      <li>

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

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

  • Error Line 2887, Column 19: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
      <li class="last">

    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 2890, Column 21: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
       <li class="clear">

    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 2892, Column 22: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
        <li class="first">

    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 2893, Column 51: there is no attribute "target"
    …="http://www.presseurop.eu/pl" target="_blank"><img src="_resource/fs/img/pres…

    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 2893, Column 127: there is no attribute "border"
    …k"><img src="_resource/fs/img/presseurop.png" alt="presseurop" border="0"/></a>

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

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

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

  • Error Line 2895, Column 22: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
        <li class="first">

    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 2896, Column 71: cannot generate system identifier for general entity "news_cat_id"
    …forum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM<…

    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 2896, Column 71: general entity "news_cat_id" not defined and no default entity
    …forum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM<…

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

  • Warning Line 2896, Column 82: reference not terminated by REFC delimiter
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</a>

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

  • Warning Line 2896, Column 82: reference to external entity in attribute value
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</a>

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

  • Error Line 2896, Column 82: reference to entity "news_cat_id" for which no system identifier could be generated
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</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 2896, Column 70: entity was defined here
    …kforum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM…
  • Warning Line 2896, Column 86: cannot generate system identifier for general entity "layout"
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</a>

    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 2896, Column 86: general entity "layout" not defined and no default entity
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</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.

  • Warning Line 2896, Column 92: reference not terminated by REFC delimiter
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</a>

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

  • Warning Line 2896, Column 92: reference to external entity in attribute value
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</a>

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

  • Error Line 2896, Column 92: reference to entity "layout" for which no system identifier could be generated
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</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 2896, Column 85: entity was defined here
    …rum.pl/forum/index.jsp?place=Menu01&news_cat_id=-1&layout=0">Tygodnik FORUM</a>
  • Error Line 2898, Column 19: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
      <li class="last">

    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 2901, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
     </ul> 

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

  • Info Line 2877, Column 1: start tag was here
    <br/>
  • Error Line 2908, Column 92: there is no attribute "align"
    …fs/img/polityka_logo_small.png" align="right" alt="polityka" title="polityka" …

    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 2919, Column 199: reference not terminated by REFC delimiter
    …owit/4057/1/1/33/?typkodu=img&keywords=' width='1' height='1' style='border-wi…

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

  • Warning Line 2919, Column 199: reference to external entity in attribute value
    …owit/4057/1/1/33/?typkodu=img&keywords=' width='1' height='1' style='border-wi…

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

  • Error Line 2919, Column 199: reference to entity "keywords" for which no system identifier could be generated
    …owit/4057/1/1/33/?typkodu=img&keywords=' width='1' height='1' style='border-wi…

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

  • Info Line 76, Column 190: entity was defined here
    …please/showit/4057/1/2/30/?typkodu=img&keywords=' width='750' height='100' sty…
  • Error Line 2953, Column 73: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <a id="noCookiesPopupTrigger" style="display:none;" href="#cookiesPopup"></a>

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

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

Visitor Analysis

Daily Visitor
  • 5.483 visits
Daily Visitor