No co Ty - informacje z życia polskich i zagranicznych gwiazd i gwiazdeczek. Pikantne fotki, relacje i filmy. Plotki i skandale! ...

nocoty.pl
  • Domain Name
    nocoty.pl
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #3539
  • Page Size
    138.5 KB
  • Ip Address
    212.77.100.98
  • Heading
    H1: 0, H2: 13, H3: 2, H4: 3, H5: 0, H6: 0
  • Images
    34 GIF, 36 JPG, 4 PNG

Website Meta Analysis

  • Title
    No co Ty!? - pikantne życie gwiazd, plotki i skandale
  • Meta Keyword
    plotki, afery, skandale, no co ty, gwiazdy, galerie, fotki, zdjęcia, filmy, fotorelacje, życie, afery
  • Meta Description
    No co Ty - informacje z życia polskich i zagranicznych gwiazd i gwiazdeczek. Pikantne fotki, relacje i filmy. Plotki i skandale!

Technical Analysis

  • Webserver
    aris
  • Ip Address
    212.77.100.98
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: aris
  • content-type: text/html; charset=iso-8859-2
  • pragma: no-cache
  • x-ua-compatible: IE=10
  • content-encoding: gzip
  • content-length: 26323
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: nocoty.pl
registrant type: organization
nameservers: ns2.wp.pl. [153.19.102.182]
ns1.wp.pl. [212.77.102.200]
created: 2007.10.16 18:52:51
last modified: 2011.10.12 11:38:58
renewal date: 2012.10.16 18:52:51

no option

dnssec: Unsigned

TECHNICAL CONTACT:
company: Albert Jerka, Andrzej Kostrzewa
AZ.pl Sp. z o.o.
street: Sosnowa 6a
city: 71-468 Szczecin
location: PL
handle: tdc7174981189648
phone: +48.914243780
fax: +48.914243799
last modified: 2010.08.26


REGISTRAR:
AZ.pl Sp. z o.o.
ul. Niedzialkowskiego 24(IX p.)
71-410 Szczecin
Polska/Poland
+48.422999111
email

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

DNS Analysis


DNS servers
ns2.wp.pl [153.19.102.182]
ns1.wp.pl [212.77.102.200]

DNS Records

Answer records
nocoty.pl SOA
server: ns1.wp.pl
email: dnsmaster@wp-sa.pl
serial: 2012040201
refresh: 21600
retry: 7200
expire: 1814400
minimum ttl: 172800
172800s
nocoty.pl NS  ns1.wp.pl 172800s
nocoty.pl NS  ns2.wp.pl 172800s
nocoty.pl MX
preference: 0
exchange: mx.wp-sa.pl
172800s
nocoty.pl TXT v=spf1 include:wp.pl -all 172800s
nocoty.pl A 212.77.100.98 172800s

Authority records

Additional records

IP 212.77.100.98 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 100 Errors
  • 125 Warnings
Ratio Text/Html
  • 0.7191409831440863
Message Error
  • Error Line 33, Column 16: there is no attribute "property"
    <meta property="og:title" content="No co Ty!? - pikantne życie gwiazd, plotki i…

    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 43, Column 72: there is no attribute "ttitle"
    …nate" type="application/rss+xml" ttitle="Najnowsze plotki z serwisu NoCoTy!" />

    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 100, Column 20: there is no attribute "href"
    	<fb:like-box href="http://www.facebook.com/nocotypl" width="292" height="320" …

    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 100, Column 61: there is no attribute "width"
    …tp://www.facebook.com/nocotypl" width="292" height="320" colorscheme="light" s…

    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 100, Column 74: there is no attribute "height"
    …book.com/nocotypl" width="292" height="320" colorscheme="light" show_faces="tr…

    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 100, Column 92: there is no attribute "colorscheme"
    … width="292" height="320" colorscheme="light" show_faces="true" stream="false"…

    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 100, Column 111: there is no attribute "show_faces"
    …="320" colorscheme="light" show_faces="true" stream="false" header="false" for…

    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 100, Column 125: there is no attribute "stream"
    …heme="light" show_faces="true" stream="false" header="false" force_wall="false…

    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 100, Column 140: there is no attribute "header"
    …ow_faces="true" stream="false" header="false" force_wall="false" style="backgr…

    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 100, Column 159: there is no attribute "force_wall"
    …eam="false" header="false" force_wall="false" style="background: white"></fb:l…

    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 100, Column 173: there is no attribute "style"
    …ader="false" force_wall="false" style="background: white"></fb:like-box><scrip…

    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 100, Column 192: element "fb:like-box" undefined
    …wall="false" style="background: white"></fb:like-box><script type="text/javasc…

    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 102, Column 34: an attribute value must be a literal unless it contains only name characters
    				WP.$("body").append("<div id=\"fb-root\"></div>");

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

  • Error Line 102, Column 34: character "\" is not allowed in the value of attribute "id"
    				WP.$("body").append("<div id=\"fb-root\"></div>");

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 102, Column 45: document type does not allow element "div" here
    				WP.$("body").append("<div id=\"fb-root\"></div>");

    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 142, Column 78: required attribute "alt" not specified
    	<img class="gwiazdki" src="http://i.wp.pl/a/i/nocoty/gwiazdki_blaski2.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 222, Column 91: document type does not allow element "link" here
    …="/fb/socialreader/pasek-aktywnosci.css?v=7" rel="stylesheet" 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 223, Column 83: document type does not allow element "link" here
    …ink href="/fb/socialreader/s_popup.css?v=7" rel="stylesheet" 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 240, Column 120: document type does not allow element "h2" here
    …0%;').addClass('friendBx').append('<h2>Aktywno&#347;ci Twoich znajomych</h2>')…

    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 245, Column 104: document type does not allow element "h2" here
    …ss('cnt').append('<h2 class="hd panel">Twoje<span> Informacje WP.PL</span></h2…

    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 265, Column 139: document type does not allow element "img" here
    …src="http://i.wp.pl/a/i/wiadomosci/fb/no-avatar.jpg" />').appendTo(leftColCnt);

    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 267, Column 32: document type does not allow element "h2" here
    					friendActivity.append('<h2>Zobacz, co zainteresowa&#322;o Twoich znajomych…

    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 269, Column 36: document type does not allow element "p" here
    					friendActivityInner.append('<p>Dowiedz si&#281;, co przegl&#261;daj&#261; …

    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 270, Column 141: document type does not allow element "a" here
    …onclick="wiadPopOpen(); return false;">wi&#281;cej na ten temat</a>').appendTo…

    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 274, Column 173: document type does not allow element "img" here
    …rc="http://a.wpimg.pl/a/i/nocoty/fb/fb_login-big.png">').appendTo(rightColCnt);

    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 274, Column 174: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="http://a.wpimg.pl/a/i/nocoty/fb/fb_login-big.png">').appendTo(rightColCnt);

    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 274, Column 107: start tag was here
    …blogin').addClass('btnBegin').append('<img alt="" src="http://a.wpimg.pl/a/i/n…
  • Error Line 393, Column 118: invalid comment declaration: found digit outside comment but inside comment declaration
    …rch.adkontekst.pl/_/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' +…
  • Info Line 388, Column 5: comment declaration started here
    				<!--
  • Warning Line 393, Column 135: cannot generate system identifier for general entity "noChache"
    …/_/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' + '></' + 'script>…

    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 393, Column 135: general entity "noChache" not defined and no default entity
    …/_/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' + '></' + 'script>…

    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 393, Column 143: reference not terminated by REFC delimiter
    …/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' + '></' + 'script>');

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

  • Error Line 393, Column 143: reference to entity "noChache" for which no system identifier could be generated
    …/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' + '></' + 'script>');

    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 393, Column 134: entity was defined here
    …l/_/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' + '></' + 'script…
  • Warning Line 393, Column 161: character "<" is the first character of a delimiter but occurred as data
    …/ads0/?QAPS_AKPL=--3-95318-#14412--&noChache=false' + '"' + '></' + 'script>');

    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 739, Column 177: cannot generate system identifier for general entity "title"
    …tion.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-ta…

    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 739, Column 177: general entity "title" not defined and no default entity
    …tion.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-ta…

    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 739, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-tam-rob…

    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 739, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-tam-rob…

    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 739, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-tam-rob…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 739, Column 226: cannot generate system identifier for general entity "kat"
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">

    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 739, Column 226: general entity "kat" not defined and no default entity
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">

    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 739, Column 229: reference not terminated by REFC delimiter
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">

    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 739, Column 229: reference to external entity in attribute value
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">

    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 739, Column 229: reference to entity "kat" for which no system identifier could be generated
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 748, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15359024&title=Joanna-Krupa-Zjawiskowo-piekna&kat=1013…

    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 748, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15359024&title=Joanna-Krupa-Zjawiskowo-piekna&kat=1013…

    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 748, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15359024&title=Joanna-Krupa-Zjawiskowo-piekna&kat=1013…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 748, Column 217: reference not terminated by REFC delimiter
    …024&title=Joanna-Krupa-Zjawiskowo-piekna&kat=1013703'" style="cursor:pointer;">

    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 748, Column 217: reference to external entity in attribute value
    …024&title=Joanna-Krupa-Zjawiskowo-piekna&kat=1013703'" style="cursor:pointer;">

    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 748, Column 217: reference to entity "kat" for which no system identifier could be generated
    …024&title=Joanna-Krupa-Zjawiskowo-piekna&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Error Line 756, Column 14: required attribute "type" not specified
    							<style>

    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 756, Column 14: document type does not allow element "style" here
    							<style>

    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 767, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15358898&title=Jak-mieszka-Marta-Wierzbicka&kat=101354…

    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 767, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15358898&title=Jak-mieszka-Marta-Wierzbicka&kat=101354…

    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 767, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15358898&title=Jak-mieszka-Marta-Wierzbicka&kat=101354…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 767, Column 215: reference not terminated by REFC delimiter
    …58898&title=Jak-mieszka-Marta-Wierzbicka&kat=1013543'" style="cursor:pointer;">

    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 767, Column 215: reference to external entity in attribute value
    …58898&title=Jak-mieszka-Marta-Wierzbicka&kat=1013543'" style="cursor:pointer;">

    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 767, Column 215: reference to entity "kat" for which no system identifier could be generated
    …58898&title=Jak-mieszka-Marta-Wierzbicka&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 776, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15358873&title=Ups-Kolejna-wpadka-na-salonach&kat=1013…

    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 776, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15358873&title=Ups-Kolejna-wpadka-na-salonach&kat=1013…

    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 776, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15358873&title=Ups-Kolejna-wpadka-na-salonach&kat=1013…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 776, Column 217: reference not terminated by REFC delimiter
    …873&title=Ups-Kolejna-wpadka-na-salonach&kat=1013701'" style="cursor:pointer;">

    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 776, Column 217: reference to external entity in attribute value
    …873&title=Ups-Kolejna-wpadka-na-salonach&kat=1013701'" style="cursor:pointer;">

    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 776, Column 217: reference to entity "kat" for which no system identifier could be generated
    …873&title=Ups-Kolejna-wpadka-na-salonach&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 785, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15358732&title=Aldona-Jankowska-Wyglupy-na-czerwonym-d…

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

  • Warning Line 785, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15358732&title=Aldona-Jankowska-Wyglupy-na-czerwonym-d…

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

  • Error Line 785, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15358732&title=Aldona-Jankowska-Wyglupy-na-czerwonym-d…

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

  • Info Line 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 785, Column 244: reference not terminated by REFC delimiter
    …Wyglupy-na-czerwonym-dywanie-Ponioslo-ja&kat=1013701'" style="cursor:pointer;">

    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 785, Column 244: reference to external entity in attribute value
    …Wyglupy-na-czerwonym-dywanie-Ponioslo-ja&kat=1013701'" style="cursor:pointer;">

    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 785, Column 244: reference to entity "kat" for which no system identifier could be generated
    …Wyglupy-na-czerwonym-dywanie-Ponioslo-ja&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 794, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15357147&title=Magda-Modra-moglaby-zachwycic-kazdego-D…

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

  • Warning Line 794, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15357147&title=Magda-Modra-moglaby-zachwycic-kazdego-D…

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

  • Error Line 794, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15357147&title=Magda-Modra-moglaby-zachwycic-kazdego-D…

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

  • Info Line 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 794, Column 249: reference not terminated by REFC delimiter
    …chwycic-kazdego-Dlaczego-sie-nie-postara&kat=1013701'" style="cursor:pointer;">

    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 794, Column 249: reference to external entity in attribute value
    …chwycic-kazdego-Dlaczego-sie-nie-postara&kat=1013701'" style="cursor:pointer;">

    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 794, Column 249: reference to entity "kat" for which no system identifier could be generated
    …chwycic-kazdego-Dlaczego-sie-nie-postara&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 803, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15355883&title=Olga-Boladz-dwa-tygodnie-po-porodzie&ka…

    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 803, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15355883&title=Olga-Boladz-dwa-tygodnie-po-porodzie&ka…

    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 803, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15355883&title=Olga-Boladz-dwa-tygodnie-po-porodzie&ka…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 803, Column 223: reference not terminated by REFC delimiter
    …tle=Olga-Boladz-dwa-tygodnie-po-porodzie&kat=1013703'" style="cursor:pointer;">

    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 803, Column 223: reference to external entity in attribute value
    …tle=Olga-Boladz-dwa-tygodnie-po-porodzie&kat=1013703'" style="cursor:pointer;">

    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 803, Column 223: reference to entity "kat" for which no system identifier could be generated
    …tle=Olga-Boladz-dwa-tygodnie-po-porodzie&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 812, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15355940&title=Aleksandra-Szwed-Co-za-przemiana&kat=10…

    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 812, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15355940&title=Aleksandra-Szwed-Co-za-przemiana&kat=10…

    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 812, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15355940&title=Aleksandra-Szwed-Co-za-przemiana&kat=10…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 812, Column 219: reference not terminated by REFC delimiter
    …0&title=Aleksandra-Szwed-Co-za-przemiana&kat=1013703'" style="cursor:pointer;">

    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 812, Column 219: reference to external entity in attribute value
    …0&title=Aleksandra-Szwed-Co-za-przemiana&kat=1013703'" style="cursor:pointer;">

    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 812, Column 219: reference to entity "kat" for which no system identifier could be generated
    …0&title=Aleksandra-Szwed-Co-za-przemiana&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 821, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15355463&title=Ranking-najpiekniejszych-biustow-show-b…

    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 821, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15355463&title=Ranking-najpiekniejszych-biustow-show-b…

    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 821, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15355463&title=Ranking-najpiekniejszych-biustow-show-b…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 821, Column 232: reference not terminated by REFC delimiter
    …ng-najpiekniejszych-biustow-show-biznesu&kat=1013543'" style="cursor:pointer;">

    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 821, Column 232: reference to external entity in attribute value
    …ng-najpiekniejszych-biustow-show-biznesu&kat=1013543'" style="cursor:pointer;">

    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 821, Column 232: reference to entity "kat" for which no system identifier could be generated
    …ng-najpiekniejszych-biustow-show-biznesu&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 830, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15355492&title=Joanna-Liszowska-Znowu-przybrala-na-wad…

    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 830, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15355492&title=Joanna-Liszowska-Znowu-przybrala-na-wad…

    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 830, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15355492&title=Joanna-Liszowska-Znowu-przybrala-na-wad…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 830, Column 228: reference not terminated by REFC delimiter
    …oanna-Liszowska-Znowu-przybrala-na-wadze&kat=1013701'" style="cursor:pointer;">

    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 830, Column 228: reference to external entity in attribute value
    …oanna-Liszowska-Znowu-przybrala-na-wadze&kat=1013701'" style="cursor:pointer;">

    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 830, Column 228: reference to entity "kat" for which no system identifier could be generated
    …oanna-Liszowska-Znowu-przybrala-na-wadze&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 839, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15355319&title=Klaudia-Halejcio-Pokazala-chlopaka&kat=…

    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 839, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15355319&title=Klaudia-Halejcio-Pokazala-chlopaka&kat=…

    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 839, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15355319&title=Klaudia-Halejcio-Pokazala-chlopaka&kat=…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 839, Column 221: reference not terminated by REFC delimiter
    …title=Klaudia-Halejcio-Pokazala-chlopaka&kat=1013703'" style="cursor:pointer;">

    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 839, Column 221: reference to external entity in attribute value
    …title=Klaudia-Halejcio-Pokazala-chlopaka&kat=1013703'" style="cursor:pointer;">

    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 839, Column 221: reference to entity "kat" for which no system identifier could be generated
    …title=Klaudia-Halejcio-Pokazala-chlopaka&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 848, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15353643&title=Fajcht-i-Wodzianka-wija-sie-na-barze&ka…

    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 848, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15353643&title=Fajcht-i-Wodzianka-wija-sie-na-barze&ka…

    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 848, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15353643&title=Fajcht-i-Wodzianka-wija-sie-na-barze&ka…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 848, Column 223: reference not terminated by REFC delimiter
    …tle=Fajcht-i-Wodzianka-wija-sie-na-barze&kat=1013701'" style="cursor:pointer;">

    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 848, Column 223: reference to external entity in attribute value
    …tle=Fajcht-i-Wodzianka-wija-sie-na-barze&kat=1013701'" style="cursor:pointer;">

    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 848, Column 223: reference to entity "kat" for which no system identifier could be generated
    …tle=Fajcht-i-Wodzianka-wija-sie-na-barze&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 857, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15352680&title=Klaudia-Halejcio-dlaczego-pieknosc-ukry…

    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 857, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15352680&title=Klaudia-Halejcio-dlaczego-pieknosc-ukry…

    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 857, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15352680&title=Klaudia-Halejcio-dlaczego-pieknosc-ukry…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 857, Column 251: reference not terminated by REFC delimiter
    …o-pieknosc-ukrywa-sie-pod-grubym-swetrem&kat=1013703'" style="cursor:pointer;">

    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 857, Column 251: reference to external entity in attribute value
    …o-pieknosc-ukrywa-sie-pod-grubym-swetrem&kat=1013703'" style="cursor:pointer;">

    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 857, Column 251: reference to entity "kat" for which no system identifier could be generated
    …o-pieknosc-ukrywa-sie-pod-grubym-swetrem&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 866, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15352593&title=Joanna-Kulig-Wreszcie-wyglada-dobrze&ka…

    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 866, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15352593&title=Joanna-Kulig-Wreszcie-wyglada-dobrze&ka…

    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 866, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15352593&title=Joanna-Kulig-Wreszcie-wyglada-dobrze&ka…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 866, Column 223: reference not terminated by REFC delimiter
    …tle=Joanna-Kulig-Wreszcie-wyglada-dobrze&kat=1013703'" style="cursor:pointer;">

    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 866, Column 223: reference to external entity in attribute value
    …tle=Joanna-Kulig-Wreszcie-wyglada-dobrze&kat=1013703'" style="cursor:pointer;">

    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 866, Column 223: reference to entity "kat" for which no system identifier could be generated
    …tle=Joanna-Kulig-Wreszcie-wyglada-dobrze&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 875, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15351871&title=Sonia-Bohosiewicz-kupuje-bielizne-na-wy…

    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 875, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15351871&title=Sonia-Bohosiewicz-kupuje-bielizne-na-wy…

    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 875, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15351871&title=Sonia-Bohosiewicz-kupuje-bielizne-na-wy…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 875, Column 236: reference not terminated by REFC delimiter
    …osiewicz-kupuje-bielizne-na-wyprzedazach&kat=1013543'" style="cursor:pointer;">

    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 875, Column 236: reference to external entity in attribute value
    …osiewicz-kupuje-bielizne-na-wyprzedazach&kat=1013543'" style="cursor:pointer;">

    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 875, Column 236: reference to entity "kat" for which no system identifier could be generated
    …osiewicz-kupuje-bielizne-na-wyprzedazach&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 884, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15351847&title=Anna-Popek-Co-za-figura&kat=1013703'" s…

    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 884, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15351847&title=Anna-Popek-Co-za-figura&kat=1013703'" s…

    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 884, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15351847&title=Anna-Popek-Co-za-figura&kat=1013703'" 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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 884, Column 210: reference not terminated by REFC delimiter
    …d=15351847&title=Anna-Popek-Co-za-figura&kat=1013703'" style="cursor:pointer;">

    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 884, Column 210: reference to external entity in attribute value
    …d=15351847&title=Anna-Popek-Co-za-figura&kat=1013703'" style="cursor:pointer;">

    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 884, Column 210: reference to entity "kat" for which no system identifier could be generated
    …d=15351847&title=Anna-Popek-Co-za-figura&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 893, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15351629&title=Niezapomniane-kreacje-oscarowe&kat=1013…

    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 893, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15351629&title=Niezapomniane-kreacje-oscarowe&kat=1013…

    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 893, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15351629&title=Niezapomniane-kreacje-oscarowe&kat=1013…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 893, Column 217: reference not terminated by REFC delimiter
    …629&title=Niezapomniane-kreacje-oscarowe&kat=1013543'" style="cursor:pointer;">

    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 893, Column 217: reference to external entity in attribute value
    …629&title=Niezapomniane-kreacje-oscarowe&kat=1013543'" style="cursor:pointer;">

    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 893, Column 217: reference to entity "kat" for which no system identifier could be generated
    …629&title=Niezapomniane-kreacje-oscarowe&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 902, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15350318&title=Katarzyna-Zielinska-Jaka-ona-piekna&kat…

    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 902, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15350318&title=Katarzyna-Zielinska-Jaka-ona-piekna&kat…

    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 902, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15350318&title=Katarzyna-Zielinska-Jaka-ona-piekna&kat…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 902, Column 222: reference not terminated by REFC delimiter
    …itle=Katarzyna-Zielinska-Jaka-ona-piekna&kat=1013703'" style="cursor:pointer;">

    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 902, Column 222: reference to external entity in attribute value
    …itle=Katarzyna-Zielinska-Jaka-ona-piekna&kat=1013703'" style="cursor:pointer;">

    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 902, Column 222: reference to entity "kat" for which no system identifier could be generated
    …itle=Katarzyna-Zielinska-Jaka-ona-piekna&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 911, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15350006&title=Manuela-Michalak-Czy-dzis-wstydzi-sie-t…

    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 911, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15350006&title=Manuela-Michalak-Czy-dzis-wstydzi-sie-t…

    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 911, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15350006&title=Manuela-Michalak-Czy-dzis-wstydzi-sie-t…

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

  • Info Line 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 911, Column 235: reference not terminated by REFC delimiter
    …Michalak-Czy-dzis-wstydzi-sie-tych-zdjec&kat=1013703'" style="cursor:pointer;">

    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 911, Column 235: reference to external entity in attribute value
    …Michalak-Czy-dzis-wstydzi-sie-tych-zdjec&kat=1013703'" style="cursor:pointer;">

    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 911, Column 235: reference to entity "kat" for which no system identifier could be generated
    …Michalak-Czy-dzis-wstydzi-sie-tych-zdjec&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 920, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15348712&title=Piotr-Machalica-znalazl-pocieszenie-po-…

    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 920, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15348712&title=Piotr-Machalica-znalazl-pocieszenie-po-…

    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 920, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15348712&title=Piotr-Machalica-znalazl-pocieszenie-po-…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 920, Column 252: reference not terminated by REFC delimiter
    …ocieszenie-po-rozstaniu-z-Edyta-Olszowka&kat=1013543'" style="cursor:pointer;">

    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 920, Column 252: reference to external entity in attribute value
    …ocieszenie-po-rozstaniu-z-Edyta-Olszowka&kat=1013543'" style="cursor:pointer;">

    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 920, Column 252: reference to entity "kat" for which no system identifier could be generated
    …ocieszenie-po-rozstaniu-z-Edyta-Olszowka&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 929, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15348656&title=To-dzieki-niej-Nowicki-zapomnial-o-Mlyn…

    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 929, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15348656&title=To-dzieki-niej-Nowicki-zapomnial-o-Mlyn…

    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 929, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15348656&title=To-dzieki-niej-Nowicki-zapomnial-o-Mlyn…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 929, Column 231: reference not terminated by REFC delimiter
    …zieki-niej-Nowicki-zapomnial-o-Mlynkovej&kat=1013543'" style="cursor:pointer;">

    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 929, Column 231: reference to external entity in attribute value
    …zieki-niej-Nowicki-zapomnial-o-Mlynkovej&kat=1013543'" style="cursor:pointer;">

    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 929, Column 231: reference to entity "kat" for which no system identifier could be generated
    …zieki-niej-Nowicki-zapomnial-o-Mlynkovej&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 938, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15347004&title=Kasia-Bosacka-zachwyca-w-ciazy&kat=1013…

    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 938, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15347004&title=Kasia-Bosacka-zachwyca-w-ciazy&kat=1013…

    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 938, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15347004&title=Kasia-Bosacka-zachwyca-w-ciazy&kat=1013…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 938, Column 217: reference not terminated by REFC delimiter
    …004&title=Kasia-Bosacka-zachwyca-w-ciazy&kat=1013543'" style="cursor:pointer;">

    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 938, Column 217: reference to external entity in attribute value
    …004&title=Kasia-Bosacka-zachwyca-w-ciazy&kat=1013543'" style="cursor:pointer;">

    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 938, Column 217: reference to entity "kat" for which no system identifier could be generated
    …004&title=Kasia-Bosacka-zachwyca-w-ciazy&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 947, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15345175&title=Sonia-Bohosiewicz-wyglada-jak-caryca&ka…

    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 947, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15345175&title=Sonia-Bohosiewicz-wyglada-jak-caryca&ka…

    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 947, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15345175&title=Sonia-Bohosiewicz-wyglada-jak-caryca&ka…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 947, Column 223: reference not terminated by REFC delimiter
    …tle=Sonia-Bohosiewicz-wyglada-jak-caryca&kat=1013703'" style="cursor:pointer;">

    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 947, Column 223: reference to external entity in attribute value
    …tle=Sonia-Bohosiewicz-wyglada-jak-caryca&kat=1013703'" style="cursor:pointer;">

    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 947, Column 223: reference to entity "kat" for which no system identifier could be generated
    …tle=Sonia-Bohosiewicz-wyglada-jak-caryca&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 956, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15344952&title=Niezgoda-w-stroju-kroliczka-Playboya&ka…

    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 956, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15344952&title=Niezgoda-w-stroju-kroliczka-Playboya&ka…

    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 956, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15344952&title=Niezgoda-w-stroju-kroliczka-Playboya&ka…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 956, Column 223: reference not terminated by REFC delimiter
    …tle=Niezgoda-w-stroju-kroliczka-Playboya&kat=1013543'" style="cursor:pointer;">

    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 956, Column 223: reference to external entity in attribute value
    …tle=Niezgoda-w-stroju-kroliczka-Playboya&kat=1013543'" style="cursor:pointer;">

    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 956, Column 223: reference to entity "kat" for which no system identifier could be generated
    …tle=Niezgoda-w-stroju-kroliczka-Playboya&kat=1013543'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 965, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15342475&title=Przypominaja-zywe-manekiny-Oto-najbardz…

    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 965, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15342475&title=Przypominaja-zywe-manekiny-Oto-najbardz…

    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 965, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15342475&title=Przypominaja-zywe-manekiny-Oto-najbardz…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 965, Column 245: reference not terminated by REFC delimiter
    …manekiny-Oto-najbardziej-woskowe-gwiazdy&kat=1013701'" style="cursor:pointer;">

    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 965, Column 245: reference to external entity in attribute value
    …manekiny-Oto-najbardziej-woskowe-gwiazdy&kat=1013701'" style="cursor:pointer;">

    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 965, Column 245: reference to entity "kat" for which no system identifier could be generated
    …manekiny-Oto-najbardziej-woskowe-gwiazdy&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 974, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15341676&title=Malgorzata-Rozenek-zabrala-miejsce-inwa…

    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 974, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15341676&title=Malgorzata-Rozenek-zabrala-miejsce-inwa…

    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 974, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15341676&title=Malgorzata-Rozenek-zabrala-miejsce-inwa…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 974, Column 232: reference not terminated by REFC delimiter
    …rzata-Rozenek-zabrala-miejsce-inwalidzie&kat=1013703'" style="cursor:pointer;">

    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 974, Column 232: reference to external entity in attribute value
    …rzata-Rozenek-zabrala-miejsce-inwalidzie&kat=1013703'" style="cursor:pointer;">

    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 974, Column 232: reference to entity "kat" for which no system identifier could be generated
    …rzata-Rozenek-zabrala-miejsce-inwalidzie&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 983, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15340195&title=Kasia-Tusk-w-pizamie-na-ulicy&kat=10137…

    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 983, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15340195&title=Kasia-Tusk-w-pizamie-na-ulicy&kat=10137…

    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 983, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15340195&title=Kasia-Tusk-w-pizamie-na-ulicy&kat=10137…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 983, Column 216: reference not terminated by REFC delimiter
    …0195&title=Kasia-Tusk-w-pizamie-na-ulicy&kat=1013701'" style="cursor:pointer;">

    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 983, Column 216: reference to external entity in attribute value
    …0195&title=Kasia-Tusk-w-pizamie-na-ulicy&kat=1013701'" style="cursor:pointer;">

    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 983, Column 216: reference to entity "kat" for which no system identifier could be generated
    …0195&title=Kasia-Tusk-w-pizamie-na-ulicy&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 992, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15337843&title=U-nas-zima-a-one-wyleguja-sie-na-goracy…

    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 992, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15337843&title=U-nas-zima-a-one-wyleguja-sie-na-goracy…

    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 992, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15337843&title=U-nas-zima-a-one-wyleguja-sie-na-goracy…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 992, Column 236: reference not terminated by REFC delimiter
    …a-a-one-wyleguja-sie-na-goracych-plazach&kat=1013703'" style="cursor:pointer;">

    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 992, Column 236: reference to external entity in attribute value
    …a-a-one-wyleguja-sie-na-goracych-plazach&kat=1013703'" style="cursor:pointer;">

    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 992, Column 236: reference to entity "kat" for which no system identifier could be generated
    …a-a-one-wyleguja-sie-na-goracych-plazach&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 1001, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15336826&title=Agata-Nizinska-Pozuje-z-ukochanym-dziad…

    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 1001, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15336826&title=Agata-Nizinska-Pozuje-z-ukochanym-dziad…

    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 1001, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15336826&title=Agata-Nizinska-Pozuje-z-ukochanym-dziad…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 1001, Column 230: reference not terminated by REFC delimiter
    …ta-Nizinska-Pozuje-z-ukochanym-dziadkiem&kat=1013703'" style="cursor:pointer;">

    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 1001, Column 230: reference to external entity in attribute value
    …ta-Nizinska-Pozuje-z-ukochanym-dziadkiem&kat=1013703'" style="cursor:pointer;">

    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 1001, Column 230: reference to entity "kat" for which no system identifier could be generated
    …ta-Nizinska-Pozuje-z-ukochanym-dziadkiem&kat=1013703'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Warning Line 1010, Column 182: reference not terminated by REFC delimiter
    …href='/galeria.html?gid=15336605&title=Lidia-Kopania-prawie-jak-Joanna-Przetak…

    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 1010, Column 182: reference to external entity in attribute value
    …href='/galeria.html?gid=15336605&title=Lidia-Kopania-prawie-jak-Joanna-Przetak…

    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 1010, Column 182: reference to entity "title" for which no system identifier could be generated
    …href='/galeria.html?gid=15336605&title=Lidia-Kopania-prawie-jak-Joanna-Przetak…

    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 739, Column 176: entity was defined here
    …ation.href='/galeria.html?gid=15360005&title=Agnieszka-Wlodarczyk-w-cyrku-Co-t…
  • Warning Line 1010, Column 232: reference not terminated by REFC delimiter
    …-Kopania-prawie-jak-Joanna-Przetakiewicz&kat=1013701'" style="cursor:pointer;">

    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 1010, Column 232: reference to external entity in attribute value
    …-Kopania-prawie-jak-Joanna-Przetakiewicz&kat=1013701'" style="cursor:pointer;">

    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 1010, Column 232: reference to entity "kat" for which no system identifier could be generated
    …-Kopania-prawie-jak-Joanna-Przetakiewicz&kat=1013701'" style="cursor:pointer;">

    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 739, Column 225: entity was defined here
    …nieszka-Wlodarczyk-w-cyrku-Co-tam-robila&kat=1013703'" style="cursor:pointer;">
  • Error Line 1038, Column 22: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<h3 class="hdCS"><img src="http://i.wp.pl/a/i/nocoty/conceptshop/hd_concep…

    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 1077, Column 206: there is no attribute "rel"
    …jpeg/30677/nago185.jpeg" alt="Jabłczyńska o nagiej sesji!" rel="nofollow"/></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 1420, Column 12: ID "zdjNaTopie" already defined
    		<div id="zdjNaTopie" class="bxRight bxRoz ST-BX-Najpopularniejsze_gwiazdy">

    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 1069, Column 10: ID "zdjNaTopie" first defined here
    <div id="zdjNaTopie" class="bxRight bxRoz ST-BX-Zdjecia-na-topie">
  • Error Line 1524, Column 29: "Na" is not a member of a group specified for any attribute
    					        	<a title=""Na Wspólnej": Anna Guzik nie chciała się rozebrać" hre…
  • Error Line 1524, Column 37: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    					        	<a title=""Na Wspólnej": Anna Guzik nie chciała się rozebrać" hre…

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

  • Error Line 1561, Column 279: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …iustów telewizji! 					<div class="rt"><a class="wiecejOrange" href="/gid,1443…

    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 1562, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
    				</div>

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

  • Info Line 1561, Column 6: start tag was here
    					<p>Sztuczne czy naturalne? Większe czy mniejsze? To kwestia indywidualnych…

Visitor Analysis

Daily Visitor
  • 43.167 visits
Daily Visitor