Slando.ua - крупнейшая доска бесплатных объявлений Украины. Огромная база предложений по темам: недвижимость, работа, транспорт, купля/продажа товаров, услуги, знакомства и многое другое! ...

emarket.ua
  • Domain Name
    emarket.ua
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #476757
  • Page Size
    54.4 KB
  • Ip Address
    178.21.158.74
  • Heading
    H1: 1, H2: 3, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    Доска объявлений Slando: сайт бесплатных частных объявлений Украины - купля/продажа б/у товаров на Slando.ua
  • Meta Keyword
    бесплатные объявления, объявления, сайт бесплатных объявлений, доска объявлений, частные объявления, сландо, slando, сландо.уа, slando.ua, сландоуа, slandoua, сландо Украина, slando.ua, slando.com.ua, сландо юа, slando ua, ckfylj, ыдфтвщ
  • Meta Description
    Slando.ua - крупнейшая доска бесплатных объявлений Украины. Огромная база предложений по темам: недвижимость, работа, транспорт, купля/продажа товаров, услуги, знакомства и многое другое!

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from emarket.ua.

HTML Analysis

  • date: Fri, 16 Aug 2013 15:39:41 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
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 14074
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% request from 65.75.128.151
% This is the Ukrainian Whois query server #B.
% The Whois is subject to Terms of use
% See https://hostmaster.ua/services/
%


% % .UA whois
% Domain Record:
% =============
domain: emarket.ua
admin-c: HL66-UANIC
tech-c: HL66-UANIC
status: OK-UNTIL 20130629172313
dom-public: NO
license: 77922
nserver: ns.dns.com.ua
nserver: ns2.dns.com.ua
mnt-by: DNSU-UANIC (ua.dns)
remark: Emarket.ua - Private free classifieds of Ukraine
created: 0-UANIC 20070629172314
changed: EVA-UANIC 20120531173004
source: UANIC


% Administrative Contact:
% ======================
nic-handle: HL66-UANIC
organization: Hotcat Ltd
address: 525, Shevchenko Str, 53
address: 49044 DNEPROPETROVSK
address: UA
phone: +380 (56) 7324410
fax-no: +380 (56) 7324410
e-mail: email
org-id: 34716896
mnt-by: NONE
changed: HL66-UANIC 20120730141400
source: UANIC

% Technical Contact:
% =================
nic-handle: HL66-UANIC
organization: Hotcat Ltd
address: 525, Shevchenko Str, 53
address: 49044 DNEPROPETROVSK
address: UA
phone: +380 (56) 7324410
fax-no: +380 (56) 7324410
e-mail: email
org-id: 34716896
mnt-by: NONE
changed: HL66-UANIC 20120730141400
source: UANIC


% % .UA whois


% Query time: 12 msec

IP 178.21.158.74 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.74

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 88 Errors
  • 23 Warnings
Ratio Text/Html
  • 0.7348086145887593
Message Error
  • Error Line 2, Column 17: 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 46: there is no attribute "XMLNS:FB"
    …ml  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 10, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …<meta name="verify-v1" content="dTY-PQBuxkvi5W-pwLFpue-Ko5AFUdLqDCHTIGQYIHA" />

    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 10, Column 81: character data is not allowed here
    …<meta name="verify-v1" content="dTY-PQBuxkvi5W-pwLFpue-Ko5AFUdLqDCHTIGQYIHA" />

    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.
  • Warning Line 11, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="dTY-PQBuxkvi5W-pwLFpue-Ko5AFUdLqDCHTIGQYIHA" />

    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 59: NET-enabling start-tag requires SHORTTAG YES
    …-verification" content="108987997609" />		<link rel="icon" href="http://emarke…

    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 108, Column 200: NET-enabling start-tag requires SHORTTAG YES
    …n/1013008327/?value=0&amp;label=nhalCLnlxAMQx4-F4wM&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.

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

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

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

  • Error Line 112, Column 17: document type does not allow element "BODY" here
    	<body class=" ">

    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 162, Column 21: there is no attribute "HREF"
    		    <fb:like href="" layout="button_count" width="120" show_faces="false" fon…

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

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

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

  • Error Line 162, Column 31: there is no attribute "LAYOUT"
    		    <fb:like href="" layout="button_count" width="120" show_faces="false" fon…

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

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

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

  • Error Line 162, Column 52: there is no attribute "WIDTH"
    …e href="" layout="button_count" width="120" show_faces="false" font=""></fb:li…

    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 162, Column 69: there is no attribute "SHOW_FACES"
    …href="" layout="button_count" width="120" show_faces="false" font=""></fb:like>

    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 162, Column 82: there is no attribute "FONT"
    …href="" layout="button_count" width="120" show_faces="false" font=""></fb:like>

    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 162, Column 84: element "FB:LIKE" undefined
    …href="" layout="button_count" width="120" show_faces="false" font=""></fb:like>

    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 190, Column 125: there is no attribute "BORDER"
    …gif"  width="496" height="349" border=0 ismap usemap="#pl-map.png" class="mapp…

    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 190, Column 206: required attribute "ALT" not specified
    …smap usemap="#pl-map.png" class="mapper noborder iopacity30 icolorffffff 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 192, Column 98: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …volynskaya.emarket.ua/" SHAPE="POLYGON" COORDS="59,27,56,34,56,35,56,40,63,60,…

    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 192, Column 294: required attribute "ALT" not specified
    …14,50,111,45,109,42,104,42,103,40,104,26,105,17,91,15,74,15,74,25,71,28,66,28">

    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 193, Column 114: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ankovskaya.emarket.ua/" SHAPE="POLYGON" COORDS="44,145,44,137,50,133,56,129,68…

    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 193, Column 285: required attribute "ALT" not specified
    …,70,184,70,182,66,178,66,176,68,175,68,165,60,164,60,162,60,155,54,154,49,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 194, Column 103: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …tomirskaya.emarket.ua/" SHAPE="POLYGON" COORDS="158,37,150,45,147,52,145,57,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 194, Column 328: required attribute "ALT" not specified
    …205,101,208,98,203,83,204,74,206,64,200,56,200,40,194,34,185,38,181,35,161,37">

    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 195, Column 103: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …elnitskaya.emarket.ua/" SHAPE="POLYGON" COORDS="114,99,143,75,143,84,151,96,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 195, Column 213: required attribute "ALT" not specified
    …51,96,149,107,154,114,154,137,144,137,139,144,139,147,143,158,115,156,115,105">

    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 196, Column 106: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …novitskaya.emarket.ua/" SHAPE="POLYGON" COORDS="96,145,114,158,142,159,148,167…

    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 196, Column 271: required attribute "ALT" not specified
    …,88,185,81,193,76,193,76,189,72,184,76,183,76,176,84,169,89,164,95,164,96,154">

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

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

  • Error Line 197, Column 106: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …nopolskaya.emarket.ua/" SHAPE="POLYGON" COORDS="98,88,107,88,110,85,116,85,119…

    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 197, Column 214: required attribute "ALT" not specified
    …116,85,119,93,113,98,114,108,114,156,68,125,68,117,76,117,87,105,95,105,96,94">

    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 198, Column 97: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …/kievskaya.emarket.ua/" SHAPE="POLYGON" COORDS="201,43,201,56,207,64,204,82,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 198, Column 390: required attribute "ALT" not specified
    …,257,83,247,83,246,82,246,74,239,74,227,62,227,54,228,48,222,40,207,40,204,43">

    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 199, Column 106: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …nigovskaya.emarket.ua/" SHAPE="POLYGON" COORDS="304,4,303,17,295,24,295,42,289…

    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 199, Column 309: required attribute "ALT" not specified
    …73,239,73,229,62,229,48,232,35,246,14,270,18,277,12,276,11,275,7,285,10,296,4">

    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 200, Column 95: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …//sumskaya.emarket.ua/" SHAPE="POLYGON" COORDS="305,4,304,17,296,25,296,42,290…

    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 200, Column 313: required attribute "ALT" not specified
    …3,356,78,356,59,351,56,348,54,348,50,326,47,323,33,328,33,328,25,322,22,315,4">

    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 201, Column 99: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …innitskaya.emarket.ua/" SHAPE="POLYGON" COORDS="155,113,155,138,145,138,140,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 201, Column 413: required attribute "ALT" not specified
    …2,144,205,136,198,129,203,124,199,120,195,120,186,121,186,110,180,113,159,113">

    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 202, Column 102: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …erkasskaya.emarket.ua/" SHAPE="POLYGON" COORDS="206,137,203,145,203,147,207,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 202, Column 374: required attribute "ALT" not specified
    …68,98,264,110,252,110,248,114,248,121,237,132,234,133,219,133,214,137,207,137">

    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 203, Column 97: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …donetskaya.emarket.ua/" SHAPE="POLYGON" COORDS="422,126,434,140,434,157,458,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 203, Column 315: required attribute "ALT" not specified
    …2,195,394,193,393,190,391,185,399,178,400,168,393,164,393,147,404,147,416,128">

    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 204, Column 112: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …etrovskaya.emarket.ua/" SHAPE="POLYGON" COORDS="343,135,352,134,359,142,372,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 204, Column 362: required attribute "ALT" not specified
    …3,178,309,172,310,170,310,168,307,163,315,155,322,148,326,150,330,150,330,140">

    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 205, Column 109: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ogradskaya.emarket.ua/" SHAPE="POLYGON" COORDS="291,137,301,137,304,140,310,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 205, Column 375: required attribute "ALT" not specified
    …1,167,230,157,252,157,261,146,271,146,274,141,276,140,279,141,280,142,291,142">

    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 206, Column 97: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …/odesskaya.emarket.ua/" SHAPE="POLYGON" COORDS="186,172,184,182,184,185,190,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 206, Column 587: required attribute "ALT" not specified
    …6,214,236,204,233,200,223,200,223,186,219,181,215,181,208,174,204,181,195,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 207, Column 101: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ersonskaya.emarket.ua/" SHAPE="POLYGON" COORDS="296,202,296,218,291,224,295,22…

    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 207, Column 503: required attribute "ALT" not specified
    …4,238,340,238,338,236,344,229,337,224,332,212,322,210,322,209,325,202,300,202">

    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 208, Column 103: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …orozhskaya.emarket.ua/" SHAPE="POLYGON" COORDS="326,202,323,209,334,212,338,22…

    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 208, Column 425: required attribute "ALT" not specified
    …8,203,400,196,393,194,390,186,379,186,376,177,354,177,347,185,350,200,349,202">

    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 209, Column 82: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ttp://krym.emarket.ua/" SHAPE="POLYGON" COORDS="315,261,320,258,323,264,326,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 209, Column 580: required attribute "ALT" not specified
    …6,294,288,297,284,291,287,288,309,272,318,272,319,270,320,268,318,266,315,266">

    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 210, Column 105: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …olaevskaya.emarket.ua/" SHAPE="POLYGON" COORDS="220,181,224,186,224,199,234,20…

    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 210, Column 419: required attribute "ALT" not specified
    …3,200,293,195,295,193,295,183,288,186,288,194,266,194,259,183,253,183,251,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 211, Column 101: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …oltavskaya.emarket.ua/" SHAPE="POLYGON" COORDS="270,95,279,85,286,87,293,83,31…

    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 211, Column 293: required attribute "ALT" not specified
    …4,127,344,129,343,134,329,140,329,149,318,145,306,140,302,136,291,136,276,100">

    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 212, Column 102: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …arkovskaya.emarket.ua/" SHAPE="POLYGON" COORDS="364,84,357,84,352,90,348,90,33…

    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 212, Column 397: required attribute "ALT" not specified
    …,413,88,410,76,403,83,394,83,390,88,386,88,376,82,372,80,368,84,366,85,365,85">

    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 213, Column 99: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …luganskaya.emarket.ua/" SHAPE="POLYGON" COORDS="426,107,426,116,422,118,422,12…

    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 213, Column 400: required attribute "ALT" not specified
    …04,472,110,464,102,458,102,456,100,451,102,445,97,433,97,430,95,428,95,426,98">

    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 214, Column 99: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …rovenskaya.emarket.ua/" SHAPE="POLYGON" COORDS="106,18,104,39,106,41,110,41,11…

    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 214, Column 355: required attribute "ALT" not specified
    …,144,58,145,54,146,51,149,46,151,42,154,38,156,36,149,33,140,28,125,22,116,18">

    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 215, Column 98: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …/lvovskaya.emarket.ua/" SHAPE="POLYGON" COORDS="63,65,68,66,71,73,77,84,87,84,…

    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 215, Column 279: required attribute "ALT" not specified
    …0,131,43,136,43,144,32,144,26,137,24,134,24,107,42,88,52,77,59,77,61,75,62,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 216, Column 104: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …arpatskaya.emarket.ua/" SHAPE="POLYGON" COORDS="20,126,23,127,23,136,31,145,42…

    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 216, Column 351: required attribute "ALT" not specified
    …4,18,173,21,172,22,169,19,167,16,166,12,154,10,148,6,144,10,144,18,129,20,126">

    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 223, Column 126: duplicate specification of attribute "ID"
    …/kyiv/" class="link {id:'10_161'}" id="level_link_10_161" title="Киев"><span><…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 223, Column 127: ID "LEVEL_LINK_10_161" already defined
    …kyiv/" class="link {id:'10_161'}" id="level_link_10_161" title="Киев"><span><s…

    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 223, Column 23: ID "LEVEL_LINK_10_161" first defined here
    				    			<li><a id="level_link_10_161" title="Киев" href="http://kievskaya.em…
  • Error Line 223, Column 152: duplicate specification of attribute "TITLE"
    …0_161'}" id="level_link_10_161" title="Киев"><span><strong>Киев</strong></span…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 224, Column 150: duplicate specification of attribute "ID"
    …etrovsk/" class="link {id:'4_55'}" id="level_link_4_55" title="Днепропетровск"…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 224, Column 151: ID "LEVEL_LINK_4_55" already defined
    …trovsk/" class="link {id:'4_55'}" id="level_link_4_55" title="Днепропетровск">…

    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 224, Column 23: ID "LEVEL_LINK_4_55" first defined here
    				    			<li><a id="level_link_4_55" title="Днепропетровск" href="http://dnep…
  • Error Line 224, Column 174: duplicate specification of attribute "TITLE"
    …d:'4_55'}" id="level_link_4_55" title="Днепропетровск"><span><strong>Днепропет…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 225, Column 128: duplicate specification of attribute "ID"
    …donetsk/" class="link {id:'5_71'}" id="level_link_5_71" title="Донецк"><span><…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 225, Column 129: ID "LEVEL_LINK_5_71" already defined
    …onetsk/" class="link {id:'5_71'}" id="level_link_5_71" title="Донецк"><span><s…

    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 225, Column 23: ID "LEVEL_LINK_5_71" first defined here
    				    			<li><a id="level_link_5_71" title="Донецк" href="http://donetskaya.e…
  • Error Line 225, Column 152: duplicate specification of attribute "TITLE"
    …d:'5_71'}" id="level_link_5_71" title="Донецк"><span><strong>Донецк</strong></…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 230, Column 127: duplicate specification of attribute "ID"
    …/lviv/" class="link {id:'13_220'}" id="level_link_13_220" title="Львов"><span>…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 230, Column 128: ID "LEVEL_LINK_13_220" already defined
    …lviv/" class="link {id:'13_220'}" id="level_link_13_220" title="Львов"><span><…

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

  • Info Line 230, Column 23: ID "LEVEL_LINK_13_220" first defined here
    				    			<li><a id="level_link_13_220" title="Львов" href="http://lvovskaya.e…
  • Error Line 230, Column 153: duplicate specification of attribute "TITLE"
    …3_220'}" id="level_link_13_220" title="Львов"><span><strong>Львов</strong></sp…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 231, Column 130: duplicate specification of attribute "ID"
    …dessa/" class="link {id:'15_259'}" id="level_link_15_259" title="Одесса"><span…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 231, Column 131: ID "LEVEL_LINK_15_259" already defined
    …essa/" class="link {id:'15_259'}" id="level_link_15_259" title="Одесса"><span>…

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

  • Info Line 231, Column 23: ID "LEVEL_LINK_15_259" first defined here
    				    			<li><a id="level_link_15_259" title="Одесса" href="http://odesskaya.…
  • Error Line 231, Column 156: duplicate specification of attribute "TITLE"
    …5_259'}" id="level_link_15_259" title="Одесса"><span><strong>Одесса</strong></…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 232, Column 134: duplicate specification of attribute "ID"
    …arkiv/" class="link {id:'20_352'}" id="level_link_20_352" title="Харьков"><spa…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 232, Column 135: ID "LEVEL_LINK_20_352" already defined
    …rkiv/" class="link {id:'20_352'}" id="level_link_20_352" title="Харьков"><span…

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

  • Info Line 232, Column 23: ID "LEVEL_LINK_20_352" first defined here
    				    			<li><a id="level_link_20_352" title="Харьков" href="http://harkovska…
  • Error Line 232, Column 160: duplicate specification of attribute "TITLE"
    …0_352'}" id="level_link_20_352" title="Харьков"><span><strong>Харьков</strong>…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 322, Column 57: cannot generate system identifier for general entity "aid"
    …kro.ua/listing/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_m…

    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 322, Column 57: general entity "aid" not defined and no default entity
    …kro.ua/listing/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_m…

    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 322, Column 60: reference to entity "aid" for which no system identifier could be generated
    ….ua/listing/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_medi…

    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 322, Column 56: entity was defined here
    …ukro.ua/listing/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_…
  • Warning Line 322, Column 70: cannot generate system identifier for general entity "utm_source"
    …g/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_medium=partner…

    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 322, Column 70: general entity "utm_source" not defined and no default entity
    …g/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_medium=partner…

    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 322, Column 80: reference to entity "utm_source" for which no system identifier could be generated
    …php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_medium=partner&utm_campa…

    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 322, Column 69: entity was defined here
    …ng/special.php/from1?ap=1&aid=17739992&utm_source=emarket.ua&utm_medium=partne…
  • Warning Line 322, Column 92: cannot generate system identifier for general entity "utm_medium"
    …=1&aid=17739992&utm_source=emarket.ua&utm_medium=partner&utm_campaign=ban_main…

    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 322, Column 92: general entity "utm_medium" not defined and no default entity
    …=1&aid=17739992&utm_source=emarket.ua&utm_medium=partner&utm_campaign=ban_main…

    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 322, Column 102: reference to entity "utm_medium" for which no system identifier could be generated
    …39992&utm_source=emarket.ua&utm_medium=partner&utm_campaign=ban_main" 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.

  • Info Line 322, Column 91: entity was defined here
    …p=1&aid=17739992&utm_source=emarket.ua&utm_medium=partner&utm_campaign=ban_mai…
  • Warning Line 322, Column 111: cannot generate system identifier for general entity "utm_campaign"
    …_source=emarket.ua&utm_medium=partner&utm_campaign=ban_main" target="_blank" c…

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

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

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

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

  • Error Line 322, Column 111: general entity "utm_campaign" not defined and no default entity
    …_source=emarket.ua&utm_medium=partner&utm_campaign=ban_main" target="_blank" c…

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

  • Error Line 322, Column 123: reference to entity "utm_campaign" for which no system identifier could be generated
    …ket.ua&utm_medium=partner&utm_campaign=ban_main" target="_blank" class="fleft …

    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 322, Column 110: entity was defined here
    …m_source=emarket.ua&utm_medium=partner&utm_campaign=ban_main" target="_blank" …
  • Error Line 322, Column 141: there is no attribute "TARGET"
    …partner&utm_campaign=ban_main" target="_blank" class="fleft tdnone" id="banner…

    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 322, Column 278: required attribute "ALT" not specified
    ….ua/static/emarketua/external/sites/emarketua/img/bannerAukro.jpg"></a>		</div>

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

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

  • Error Line 493, Column 29: ID "CONTACT" already defined
    		<li class="inline"><a id="contact" href="http://emarket.ua/help/contact/" tit…

    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 490, Column 29: ID "CONTACT" first defined here
    		<li class="inline"><a id="contact" href="http://emarket.ua/tv/advertising/" t…
  • Warning Line 569, Column 104: NET-enabling start-tag requires SHORTTAG YES
    …ch/1031599" style="position:absolute; left:-9999px;" alt="" /></div></noscript>

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

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

  • Warning Line 595, Column 200: NET-enabling start-tag requires SHORTTAG YES
    …n/1013894886/?value=0&amp;label=W-GICNqooAMQ5p274wM&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.

Visitor Analysis

Daily Visitor
  • 268 visits
Daily Visitor