aprod.hu

Ingyenes apróhirdetések, hirdetések . Add fel hirdetésed egyszerűen és ingyenesen pár kattintással és a vevők találnak meg téged, vagy vásárolj a lakóhelyedhez közel! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 30-06-2013 09:47:38  (update).

Overview Info

  • Domain Name
    aprod.hu
  • Favicon
  • Alexa Rank
    #4213
  • Google Page Rank
    PR 5
  • Ip Address
    178.21.158.49
  • Page Size
    50.7 KB
  • Images
    0 GIF, 0 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 0 0

Website Meta Analysis



  • Title
    apród.hu: Ingyenes apróhirdetések - Adj el vagy vásárolj az apród.hu-n!
  • Meta Keyword
  • Meta Description
    Ingyenes apróhirdetések, hirdetések . Add fel hirdetésed egyszerűen és ingyenesen pár kattintással és a vevők találnak meg téged, vagy vásárolj a lakóhelyedhez közel!

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from aprod.hu.

HTML Analysis

  • date: Sun, 30 Jun 2013 09:47:33 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: 12602
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for aprod.hu

DNS Analysis


DNS servers
pdns1.cscdns.net
pdns2.cscdns.net


DNS Records

Answer records
aprod.hu SOA
server: pdns1.cscdns.net
email: hostmaster@cscdns.net
serial: 2012030910
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 14400
14400s
aprod.hu NS  pdns1.cscdns.net 14400s
aprod.hu NS  pdns2.cscdns.net 14400s
aprod.hu A 178.21.158.49 14400s
aprod.hu MX
preference: 30
exchange: aspmx2.googlemail.com
14400s
aprod.hu MX
preference: 20
exchange: alt1.aspmx.l.google.com
14400s
aprod.hu MX
preference: 10
exchange: aspmx.l.google.com
14400s
aprod.hu TXT v=spf1 a mx ptr ip4:178.21.153.64/26 include:aspmx.googlemail.com -all 14400s

Authority records

Additional records

IP 178.21.158.49 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.49

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 79 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.7187005976479661
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 49: NET-enabling start-tag requires SHORTTAG YES
    …l="canonical" href="http://aprod.hu/" />					<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 50: character data is not allowed here
    …="canonical" href="http://aprod.hu/" />					<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="apród.hu: Ingyenes apróhirdetések -…

    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 117: NET-enabling start-tag requires SHORTTAG YES
    …ent="apród.hu: Ingyenes apróhirdetések - Adj el vagy vásárolj az apród.hu-n!"/>

    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 214: NET-enabling start-tag requires SHORTTAG YES
    …intással és a vevők találnak meg téged, vagy vásárolj a lakóhelyedhez közel!"/>

    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="158710884185828"/>

    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 136: NET-enabling start-tag requires SHORTTAG YES
    …/static/aprodhu/external/sites/aprodhu/img/fb/fb-image200x200.png?t=13-01-12"/>

    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 55: NET-enabling start-tag requires SHORTTAG YES
    					<meta property="og:url" content="http://aprod.hu"/>

    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 54: NET-enabling start-tag requires SHORTTAG YES
    					<meta property="og:site_name" content="apród.hu"/>

    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 97: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="hMyIgXfrUcbf5mV_nvBpKmNjlRcoMbBonHVCQj8SHy0" />

    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 76: NET-enabling start-tag requires SHORTTAG YES
    <link rel="publisher" href="https://plus.google.com/103383629692910164638" />

    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 76, Column 319: required attribute "ALT" not specified
    …rodhu/img/headerLogo.png" class="vtop"></a></h1>												<span class="icon …

    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 106, 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 111, Column 30: there is no attribute "AUTOCOMPLETE"
    									<input autocomplete="off" type="text" defaultval="Keresés..." class="w…

    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 111, Column 59: there is no attribute "DEFAULTVAL"
    …complete="off" type="text" defaultval="Keresés..." class="with-x-clear-button …

    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 121, 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 136, 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 503, Column 120: there is no attribute "BORDER"
    ….png" width="397" height="245" 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 503, Column 187: required attribute "ALT" not specified
    …45" border="0" ismap usemap="#map.png" class="mapper noborder iopacity30 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 505, Column 126: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region1'}" shape="polygon" coords="31,97,49,102,55,98,55,102,62,1…

    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 505, Column 324: required attribute "ALT" not specified
    …24,148,12,159,12,149,9,145,3,145,0,147,4,141,8,138,9,136,22,135,24,123,21,101">

    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 506, Column 159: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region2'}" shape="polygon" coords="351,13,348,20,332,30,320,29,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 506, Column 326: required attribute "ALT" not specified
    …3,73,256,52,256,35,243,41,233,34,247,26,259,4,272,0,293,6,312,0,330,18,351,13">

    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 507, Column 133: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region3'}" shape="polygon" coords="132,199,134,200,135,206,139,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 507, Column 368: required attribute "ALT" not specified
    …3,89,229,89,225,88,221,94,205,106,205,108,198,122,196,122,190,129,189,132,199">

    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 508, Column 135: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region4'}" shape="polygon" coords="265,158,267,176,264,193,272,19…

    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 508, Column 369: required attribute "ALT" not specified
    …4,175,228,177,231,164,229,161,233,155,240,159,245,155,250,158,256,154,265,158">

    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 509, Column 129: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region5'}" shape="polygon" coords="165,151,168,159,170,164,168,16…

    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 509, Column 459: required attribute "ALT" not specified
    …5,178,118,161,129,154,138,161,143,158,149,165,155,162,154,159,163,151,165,151">

    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 510, Column 131: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region6'}" shape="polygon" coords="121,142,122,157,117,161,113,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 510, Column 379: required attribute "ALT" not specified
    …196,46,199,53,196,53,188,62,186,68,160,82,159,105,148,106,145,115,141,121,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 511, Column 127: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region7'}" shape="polygon" coords="168,106,173,105,175,103,179,10…

    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 511, Column 602: required attribute "ALT" not specified
    …6,126,201,127,198,132,190,135,190,127,186,125,174,133,165,131,164,123,166,114">

    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 512, Column 127: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …mainpage_map_region8'}" shape="polygon" coords="57,133,63,136,65,143,70,146,75…

    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 512, Column 305: required attribute "ALT" not specified
    …,23,173,15,160,13,160,25,150,30,143,37,143,41,139,50,140,53,134,56,135,57,133">

    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 513, Column 142: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region9'}"  shape="polygon" coords="189,128,189,137,199,133,201,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 513, Column 584: required attribute "ALT" not specified
    …2,172,164,170,168,169,172,164,169,159,167,150,169,133,174,135,185,127,189,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 514, Column 130: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region10'}" shape="polygon" coords="290,116,306,123,306,128,302,13…

    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 404: required attribute "ALT" not specified
    …7,157,256,153,256,149,263,145,269,146,273,142,273,134,279,134,281,125,290,116">

    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 136: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region11'}" shape="polygon" coords="80,101,83,97,95,97,98,101,94,1…

    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 363: required attribute "ALT" not specified
    …58,71,145,66,143,64,135,57,132,62,131,65,129,66,110,69,108,64,100,74,99,76,96">

    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 130: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region12'}" shape="polygon" coords="152,88,151,92,157,98,155,102,1…

    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 366: required attribute "ALT" not specified
    …,126,136,124,131,125,129,125,118,115,112,114,108,123,97,129,103,143,94,141,90">

    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 136: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region13'}" shape="polygon" coords="177,84,186,94,188,94,190,97,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 517, Column 235: required attribute "ALT" not specified
    …94,188,94,190,97,185,102,179,106,175,102,173,103,169,104,169,97,167,94,167,88">

    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 160: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region14'}" shape="polygon" coords="277,79,279,85,286,86,290,104,2…

    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 487: required attribute "ALT" not specified
    …228,79,231,88,238,89,237,86,241,85,246,92,246,95,253,102,272,86,274,78,277,79">

    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 154: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region15'}" shape="polygon" coords="164,68,166,74,161,75,161,80,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 519, Column 314: required attribute "ALT" not specified
    …23,95,113,107,105,103,108,84,105,81,107,72,129,74,145,72,151,72,156,67,164,68">

    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 142: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region16'}" shape="polygon" coords="296,51,305,57,320,54,319,66,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 520, Column 346: required attribute "ALT" not specified
    …34,304,131,308,128,308,122,290,115,291,105,288,85,280,84,279,79,291,72,296,51">

    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 154: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region17'}" shape="polygon" coords="68,49,74,51,79,60,83,64,87,67,…

    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 367: required attribute "ALT" not specified
    …6,95,49,100,32,95,36,88,32,80,20,77,26,74,27,71,35,72,37,77,58,75,60,52,67,48">

    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 130: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region18'}" shape="polygon" coords="262,75,273,78,271,85,253,100,2…

    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 316: required attribute "ALT" not specified
    …,206,72,216,62,220,61,218,57,230,50,228,43,235,38,243,43,254,37,255,52,262,75">

    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 132: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region19'}" shape="polygon" coords="234,37,226,42,229,49,217,57,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 523, Column 282: required attribute "ALT" not specified
    …,169,55,172,52,172,48,168,46,184,46,199,42,203,33,207,30,222,39,232,35,234,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 524, Column 164: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ainpage_map_region20'}" shape="polygon" coords="359,12,367,26,373,25,380,37,39…

    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 391: required attribute "ALT" not specified
    …,294,49,295,46,312,46,313,35,321,31,332,31,337,28,349,21,353,13,356,10,359,12">

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

    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 537, Column 77: there is no attribute "DATA-SEND"
    …/www.facebook.com/aprod.hu" 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 537, Column 97: there is no attribute "DATA-LAYOUT"
    …rod.hu" 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 537, Column 123: 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 537, Column 145: 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 553, Column 11: required attribute "TYPE" not specified
    			<script>(function(d, s, id) {

    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 560, Column 10: ID "FB-ROOT" already defined
    <div id="fb-root"></div>

    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 528, Column 11: ID "FB-ROOT" first defined here
    	<div id="fb-root"></div>
  • Error Line 562, Column 153: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …lse" data-layout="button_count" data-width="160" data-show-faces="false"></div>

    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 566, Column 39: there is no attribute "SIZE"
    			<span class="vtop"><g:plusone size="medium"></g:plusone></span>

    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 566, Column 47: element "G:PLUSONE" undefined
    			<span class="vtop"><g:plusone size="medium"></g:plusone></span>

    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 615, Column 51: there is no attribute "TARGET"
    … href="http://prodavalnik.com" target="_blank" class="link gray clicker {click…

    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 651, Column 75: 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 651, Column 75: 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 651, Column 78: 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 651, Column 74: entity was defined here
    …isable/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofo…
  • Error Line 654, Column 78: 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 651, Column 74: entity was defined here
    …isable/m/?ref%5B0%5D%5Baction%5D=index&ref%5B0%5D%5Bmethod%5D=index" rel="nofo…
  • Error Line 679, 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 680, 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 680, 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 690, 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 696, 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.

  • Error Line 710, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT language="JavaScript">

    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 710, Column 30: required attribute "TYPE" not specified
    <SCRIPT language="JavaScript">

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

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

  • Warning Line 714, Column 120: cannot generate system identifier for general entity "dc"
    …audit.median.hu/cgi-bin/track.cgi?uc=12990551687782&dc=1" width="1" height="1">

    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 714, Column 120: general entity "dc" not defined and no default entity
    …audit.median.hu/cgi-bin/track.cgi?uc=12990551687782&dc=1" width="1" height="1">

    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 714, Column 122: reference to entity "dc" for which no system identifier could be generated
    …audit.median.hu/cgi-bin/track.cgi?uc=12990551687782&dc=1" width="1" height="1">

    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 714, Column 119: entity was defined here
    …audit.median.hu/cgi-bin/track.cgi?uc=12990551687782&dc=1" width="1" height="1">
  • Error Line 714, Column 146: required attribute "ALT" not specified
    …audit.median.hu/cgi-bin/track.cgi?uc=12990551687782&dc=1" width="1" height="1">

    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 714, Column 146: document type does not allow element "IMG" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "DIV", "ADDRESS" start-tag
    …audit.median.hu/cgi-bin/track.cgi?uc=12990551687782&dc=1" width="1" height="1">

    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 715, Column 11: end tag for "NOSCRIPT" which is not finished
    </NOSCRIPT>

    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 755, Column 200: NET-enabling start-tag requires SHORTTAG YES
    …on/980119973/?value=0&amp;label=rYpfCIvOxQMQpeOt0wM&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 774, Column 200: NET-enabling start-tag requires SHORTTAG YES
    …on/980119973/?value=0&amp;label=1kUPCIPPxQMQpeOt0wM&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
  • 33.833 visits

In Page Analysis