tablica.pl

Darmowe ogłoszenia w Twoim mieście. Znajdziesz tutaj pokój, pracę, samochód i psa, sprzedasz meble, ubrania i telefon. Sprzedawaj po sąsiedzku na Tablica.pl ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 03:25:21  (update).

Overview Info

  • Domain Name
    tablica.pl
  • Favicon
  • Alexa Rank
    #2822
  • Google Page Rank
    PR 4
  • Ip Address
    178.21.158.73
  • Page Size
    47.3 KB
  • Images
    0 GIF, 0 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 0 0

Website Meta Analysis



  • Title
    Ogłoszenia - Sprzedam, kupię na Tablica.pl
  • Meta Keyword
  • Meta Description
    Darmowe ogłoszenia w Twoim mieście. Znajdziesz tutaj pokój, pracę, samochód i psa, sprzedasz meble, ubrania i telefon. Sprzedawaj po sąsiedzku na Tablica.pl

Technical Analysis



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

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

HTML Analysis

  • date: Tue, 09 Jul 2013 15:25:14 GMT
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-ocache: 1
  • x-utime: 1
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 12394
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: tablica.pl
registrant type: organization
nameservers: gtmdc3.allegro.pl. [91.207.14.244]
gtmdc2.allegro.pl. [91.194.188.132]
created: 2005.09.09 13:27:02
last modified: 2012.03.05 14:13:27
renewal date: 2013.09.09 13:27:02

option created: 2011.05.04 12:59:01
option expiration date: 2014.05.04 12:59:01

dnssec: Unsigned

TECHNICAL CONTACT:
company: Domain Administrator
MIH Allegro B.V.
street: Taurusavenue 105
city: 2132LS Hoofddorp
location: NL
handle: cscyrudcd3095303
phone: +31.235562636
fax: +31.235562880
last modified: 2012.03.05


REGISTRAR:
Corporation Service Company
2711 Centerville Road
Suite 400
Wilmington, DE 19808
United States
tel: +1.302.636.5400
fax: +1.302.636.5454
email: 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
gtmdc3.allegro.pl [91.207.14.244]
gtmdc2.allegro.pl [91.194.188.132]

DNS Records

Answer records
tablica.pl SOA
server: ns1.allegro.pl
email: hostmaster@allegro.pl
serial: 2012103101
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
tablica.pl NS  gtmdc2.allegro.pl 86400s
tablica.pl NS  gtmdc3.allegro.pl 86400s
tablica.pl A 178.21.158.73 300s
tablica.pl MX
preference: 20
exchange: alt1.aspmx.l.google.com
14400s
tablica.pl MX
preference: 30
exchange: aspmx2.googlemail.com
14400s
tablica.pl MX
preference: 10
exchange: aspmx.l.google.com
14400s
tablica.pl TXT v=spf1 a mx ptr ip4:178.21.153.64/26 include:aspmx.googlemail.com -all 14400s

Authority records

Additional records
gtmdc2.allegro.pl A 91.194.188.132 1800s
gtmdc3.allegro.pl A 91.207.14.244 1800s

IP 178.21.158.73 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 77 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.7007293237743022
Message Error
  • Error Line 2, Column 16: there is no attribute "XMLNS:OG"
    <html xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml">

    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 2, Column 45: there is no attribute "XMLNS:FB"
    <html xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml">

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

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

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

  • Warning Line 6, Column 51: NET-enabling start-tag requires SHORTTAG YES
    …"canonical" href="http://tablica.pl/" />					<meta name="robots" content="inde…

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

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

  • Error Line 6, Column 52: character data is not allowed here
    …canonical" href="http://tablica.pl/" />					<meta name="robots" content="index…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 9, Column 25: there is no attribute "PROPERTY"
    									<meta property="og:title" content="Ogłoszenia - Sprzedam, kupię na Tab…

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

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

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

  • Warning Line 9, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …meta property="og:title" content="Ogłoszenia - Sprzedam, kupię na Tablica.pl"/>

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

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

  • Warning Line 10, Column 204: NET-enabling start-tag requires SHORTTAG YES
    …a, sprzedasz meble, ubrania i telefon. Sprzedawaj po sąsiedzku na Tablica.pl"/>

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

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

  • Warning Line 11, Column 58: NET-enabling start-tag requires SHORTTAG YES
    					<meta property="fb:app_id" content="121167521293285"/>

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

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

  • Warning Line 12, Column 142: NET-enabling start-tag requires SHORTTAG YES
    …tic/tablicapl/external/sites/tablicapl/img/fb/fb-image200x200.png?t=13-01-10"/>

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

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

  • Warning Line 13, Column 48: NET-enabling start-tag requires SHORTTAG YES
    					<meta property="og:type" content="website"/>

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

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

  • Warning Line 14, Column 57: NET-enabling start-tag requires SHORTTAG YES
    					<meta property="og:url" content="http://tablica.pl"/>

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

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

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

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

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

  • Warning Line 18, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …		<link href="https://plus.google.com/113406265199615974663" rel="publisher" />

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

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

  • Warning Line 19, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …TZIV57Re1Erk7ewz1ntSu7GuZWM0gG5v-CO0" />																				<link rel="stylesh…

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

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

  • Error Line 126, Column 33: document type does not allow element "DIV" here
    					<div class="fblock clr rel">

    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 131, Column 30: there is no attribute "AUTOCOMPLETE"
    									<input autocomplete="off" type="text" defaultval="Szukaj..." class="wi…

    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 131, Column 59: there is no attribute "DEFAULTVAL"
    …complete="off" type="text" defaultval="Szukaj..." class="with-x-clear-button 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 141, Column 15: end tag for "FIELDSET" which is not finished
    				</fieldset>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 154, Column 41: there is no attribute "WIDTH"
    														<td class="tcenter" width="25%">

    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 512, Column 126: there is no attribute "BORDER"
    ….png" width="349" height="333" border="0" ismap usemap="#map.png" class="mappe…

    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 512, Column 207: required attribute "ALT" not specified
    … ismap usemap="#map.png" class="mapper noborder iopacity100 icolor3074B9 vtop">

    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 514, Column 161: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region11'}" shape="polygon" coords="92,20,95,35,90,38,98,59,96,71,…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 514, Column 366: required attribute "ALT" not specified
    …,111,5,105,10,100,14,92,15,87,12,68,11,65,12,62,21,66,30,46,60,36,72,35,86,21">

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

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

  • Error Line 515, Column 163: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region14'}" shape="polygon" coords="190,27,186,33,184,32,177,38,17…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 515, Column 376: required attribute "ALT" not specified
    …,235,84,264,79,287,53,278,35,287,30,286,29,252,32,236,32,210,30,196,28,192,27">

    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 516, Column 140: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region9'}" shape="polygon" coords="17,122,25,122,30,111,37,112,51…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 516, Column 414: required attribute "ALT" not specified
    …,16,166,20,162,21,153,19,151,19,144,15,140,15,134,18,131,18,127,18,125,17,123">

    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 517, Column 149: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region1'}" shape="polygon" coords="96,72,100,78,112,79,108,87,114…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 517, Column 431: required attribute "ALT" not specified
    …,168,74,164,69,164,60,154,58,121,64,118,66,102,72,105,82,97,92,87,84,80,94,74">

    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 518, Column 161: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region15'}" shape="polygon" coords="135,65,170,75,173,82,179,86,18…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 518, Column 322: required attribute "ALT" not specified
    …2,176,142,168,144,141,134,115,123,116,113,110,106,116,92,110,86,114,78,133,66">

    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 519, Column 146: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region2'}" shape="polygon" coords="194,98,197,101,212,101,216,94,…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 519, Column 583: required attribute "ALT" not specified
    …09,157,196,145,188,149,177,142,184,122,182,112,188,110,188,101,191,100,194,97">

    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 520, Column 138: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region7'}" shape="polygon" coords="177,144,188,151,197,148,208,15…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 520, Column 396: required attribute "ALT" not specified
    …5,215,138,210,134,198,138,194,142,197,144,195,148,174,155,174,160,166,169,146">

    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 521, Column 138: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region6'}" shape="polygon" coords="163,214,193,230,188,237,194,23…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 521, Column 404: required attribute "ALT" not specified
    …0,289,150,282,134,276,132,268,145,263,145,246,153,246,152,242,149,236,155,216">

    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 522, Column 147: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region4'}"  shape="polygon" coords="183,254,170,279,170,281,176,29…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 522, Column 469: required attribute "ALT" not specified
    …2,287,241,285,240,283,246,280,242,276,243,256,214,266,208,249,198,250,197,252">

    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 523, Column 149: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region17'}" shape="polygon" coords="266,230,269,231,275,229,278,23…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 523, Column 447: required attribute "ALT" not specified
    …4,308,250,288,243,286,244,283,248,279,244,275,246,255,260,242,264,238,266,234">

    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 524, Column 148: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region3'}" shape="polygon" coords="79,173,94,188,106,189,106,184,…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 524, Column 468: required attribute "ALT" not specified
    …,30,215,27,214,26,216,24,215,29,201,29,199,27,196,41,186,48,191,65,171,73,181">

    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 525, Column 141: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region12'}" shape="polygon" coords="93,249,105,257,109,260,116,260…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 525, Column 342: required attribute "ALT" not specified
    …4,262,144,244,151,244,147,236,154,216,136,211,128,215,124,210,116,211,103,242">

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

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

  • Error Line 526, Column 153: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region13'}" shape="polygon" coords="216,202,225,211,234,211,240,21…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 526, Column 363: required attribute "ALT" not specified
    …2,236,190,236,196,229,193,229,196,220,203,220,202,216,201,210,207,210,214,204">

    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 527, Column 142: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region8'}" shape="polygon" coords="306,146,307,146,309,148,312,14…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 527, Column 544: required attribute "ALT" not specified
    …8,184,263,184,264,183,269,172,266,165,270,161,290,160,290,156,298,158,303,150">

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

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

  • Error Line 528, Column 143: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region18'}" shape="polygon" coords="288,27,290,30,280,36,290,52,26…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 528, Column 356: required attribute "ALT" not specified
    …,126,331,121,332,118,331,112,322,86,311,48,313,44,309,36,303,33,296,30,294,27">

    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 529, Column 142: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region5'}" shape="polygon" coords="94,20,98,36,92,39,100,59,98,70…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 529, Column 379: required attribute "ALT" not specified
    …165,17,165,16,161,13,157,10,152,7,146,4,136,5,124,7,113,10,109,11,98,18,94,19">

    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 542, Column 32: there is no attribute "DATA-HREF"
    <div class="fb-like" data-href="http://www.facebook.com/tablica" data-send="fal…

    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 542, Column 76: there is no attribute "DATA-SEND"
    …//www.facebook.com/tablica" data-send="false" data-layout="button_count" data-…

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

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

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

  • Error Line 542, Column 96: there is no attribute "DATA-LAYOUT"
    …ablica" data-send="false" data-layout="button_count" data-width="120" data-sho…

    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 542, Column 122: there is no attribute "DATA-WIDTH"
    …alse" data-layout="button_count" data-width="120" data-show-faces="true"></div>

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

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

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

  • Error Line 542, Column 144: there is no attribute "DATA-SHOW-FACES"
    …alse" data-layout="button_count" data-width="120" data-show-faces="true"></div>

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

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

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

  • Error Line 584, Column 43: there is no attribute "TARGET"
    …									<li class="inline"><a target="_blank" class="clicker {clickerID:'foot…

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

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

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

  • Warning Line 628, Column 73: cannot generate system identifier for general entity "ls"
    …e.com/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="…

    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 628, Column 73: general entity "ls" not defined and no default entity
    …e.com/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="…

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

  • Error Line 628, Column 75: reference to entity "ls" for which no system identifier could be generated
    …com/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="_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 628, Column 72: entity was defined here
    …le.com/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target=…
  • Warning Line 628, Column 78: cannot generate system identifier for general entity "mt"
    …/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="_blan…

    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 628, Column 78: general entity "mt" not defined and no default entity
    …/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="_blan…

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

  • Error Line 628, Column 80: reference to entity "mt" for which no system identifier could be generated
    …s/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="_blank"…

    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 628, Column 77: entity was defined here
    …m/us/app/tablica/id531717763?l=pl&ls=1&mt=8" id="footerAppIphone" target="_bla…
  • Warning Line 645, Column 188: NET-enabling start-tag requires SHORTTAG YES
    …n/1035062597/?value=0&amp;label=uyNSCIvxkAIQxZrH7QM&amp;guid=ON&amp;script=0"/>

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

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

  • Warning Line 649, Column 77: cannot generate system identifier for general entity "ref"
    …sable/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofol…

    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 649, Column 77: general entity "ref" not defined and no default entity
    …sable/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofol…

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

  • Error Line 649, Column 80: reference to entity "ref" for which no system identifier could be generated
    …le/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofollow…

    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 649, Column 76: entity was defined here
    …isable/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofo…
  • Error Line 652, Column 80: reference to entity "ref" for which no system identifier could be generated
    …le/i/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofollow…

    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 649, Column 76: entity was defined here
    …isable/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofo…
  • Error Line 677, Column 29: document type does not allow element "DIV" here
    				<div class="fblock main">

    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 678, Column 89: required attribute "ROWS" not specified
    …feedback-content" id="feedback-textarea" class="br3 light x-normal"></textarea>

    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 678, Column 89: required attribute "COLS" not specified
    …feedback-content" id="feedback-textarea" class="br3 light x-normal"></textarea>

    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 688, Column 40: document type does not allow element "DIV" here
    				<div class="fblock clr margintop20">

    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 694, Column 14: end tag for "FIELDSET" which is not finished
    			</fieldset>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 767, Column 82: cannot generate system identifier for general entity "stc"
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 

    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 767, Column 82: general entity "stc" not defined and no default entity
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 

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

  • Error Line 767, Column 85: reference to entity "stc" for which no system identifier could be generated
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 

    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 767, Column 81: entity was defined here
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 
  • Error Line 767, Column 97: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 

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

  • Error Line 767, Column 97: document type does not allow element "IMG" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "DIV", "ADDRESS" start-tag
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 

    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 767, Column 98: character data is not allowed here
    …"" src="http://LOGC269.xiti.com/hit.xiti?s=507462&stc={"page_name":"home"}&" > 

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 768, Column 11: end tag for "NOSCRIPT" which is not finished
    </noscript>	    								<script type="text/javascript" src="http://s1.tablica.p…

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 75.833 visits

In Page Analysis