Afla totul despre moda, tendinte, coafuri, tunsori, frumusete, cuplu, vedete, shopping si horoscop. Sfaturi utile pentru femei oferite de specialisti in make up si hairstyling. Saloane de coafura si de infrumusetare de top ...

divahair.ro
  • Domain Name
    divahair.ro
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #49504
  • Page Size
    123.6 KB
  • Ip Address
    89.36.26.43
  • Heading
    H1: 0, H2: 19, H3: 16, H4: 1, H5: 0, H6: 0
  • Images
    1 GIF, 85 JPG, 5 PNG

Website Meta Analysis

  • Title
    Diva Hair - Coafuri, frizuri, tunsori, saloane de coafura si saloane de infrumusetare
  • Meta Keyword
  • Meta Description
    Afla totul despre moda, tendinte, coafuri, tunsori, frumusete, cuplu, vedete, shopping si horoscop. Sfaturi utile pentru femei oferite de specialisti in make up si hairstyling. Saloane de coafura si de infrumusetare de top din Bucuresti si din tara.

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from divahair.ro.

HTML Analysis

  • date: Wed, 27 Feb 2013 04:39:23 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.16
  • pragma: no-cache
  • cache-control: private, max-age=3600, s-maxage=3600, must-revalidate
  • expires: Tue, 25 Apr 2056 10:18:46 GMT
  • vary: Host,Accept-Encoding,User-Agent
  • connection: keep-alive, close
  • last-modified: Wed, 27 Feb 2013 04:39:23 GMT
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for divahair.ro

DNS Analysis


DNS servers
ns2.divahair.ro [89.36.26.43]
ns1.divahair.ro [89.36.26.43]


DNS Records

Answer records
divahair.ro MX
preference: 0
exchange: divahair.ro
14400s
divahair.ro SOA
server: ns1.divahair.ro
email: servers@hostway.ro
serial: 2011020705
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
divahair.ro NS  ns1.divahair.ro 86400s
divahair.ro NS  ns2.divahair.ro 86400s
divahair.ro A 89.36.26.43 14400s

Authority records

Additional records
divahair.ro A 89.36.26.43 14400s
ns1.divahair.ro A 89.36.26.43 14400s
ns2.divahair.ro A 89.36.26.43 14400s

IP 89.36.26.43 Analysis

  • Country Code
    RO
  • Country Code3
    ROU
  • Country Name
    Romania
  • City
    Bucharest
  • Continent Code
    EU
  • Latitude
    44.4333
  • Longitude
    26.1.
  • No whois ip data for 89.36.26.43

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 122 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.7350412491702754
Message Error
  • Error Line 2, Column 120: "itemscope" is not a member of a group specified for any attribute
    …ns:fb="http://ogp.me/ns/fb#" dir="ltr" itemscope itemtype="http://schema.org/">
  • Error Line 2, Column 129: there is no attribute "itemtype"
    …ns:fb="http://ogp.me/ns/fb#" dir="ltr" itemscope itemtype="http://schema.org/">

    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 8, Column 91: end tag for "link" omitted, but OMITTAG NO was specified
    …"shortcut icon" type="image/x-icon" href="http://www.divahair.ro/favicon7.ico">

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

  • Info Line 8, Column 2: start tag was here
    	<link rel="shortcut icon" type="image/x-icon" href="http://www.divahair.ro/fav…
  • Error Line 18, Column 24: there is no attribute "property"
            <meta property="fb:app_id" content="364168041693" />

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

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

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

  • Error Line 43, Column 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 43, Column 30: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript">

    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 47, Column 26: there is no attribute "SRC"
    document.write("<IMG SRC=\""+IVW+"?r="+escape(document.referrer)+"&d="+(Math.ra…

    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 47, Column 26: an attribute value must be a literal unless it contains only name characters
    document.write("<IMG SRC=\""+IVW+"?r="+escape(document.referrer)+"&d="+(Math.ra…

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

  • Error Line 47, Column 142: there is no attribute "WIDTH"
    …)*100000)+"&x="+screen.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\">");

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

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

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

  • Error Line 47, Column 142: an attribute value must be a literal unless it contains only name characters
    …)*100000)+"&x="+screen.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\">");

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

  • Error Line 47, Column 155: there is no attribute "HEIGHT"
    …)*100000)+"&x="+screen.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\">");

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

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

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

  • Error Line 47, Column 155: an attribute value must be a literal unless it contains only name characters
    …)*100000)+"&x="+screen.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\">");

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

  • Error Line 47, Column 160: element "IMG" undefined
    …)*100000)+"&x="+screen.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\">");

    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 48, Column 9: end tag for "IMG" omitted, but OMITTAG NO was specified
    </SCRIPT>

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

  • Info Line 47, Column 17: start tag was here
    document.write("<IMG SRC=\""+IVW+"?r="+escape(document.referrer)+"&d="+(Math.ra…
  • Error Line 49, Column 10: element "NOSCRIPT" undefined
    <NOSCRIPT>

    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 50, Column 97: element "IMG" undefined
    …://divahair.count.brat-online.ro/cgi-bin/cnt/CP/homepage" WIDTH="1" HEIGHT="1">

    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 51, Column 11: end tag for "IMG" omitted, but OMITTAG NO was specified
    </NOSCRIPT>

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

  • Info Line 50, Column 5: start tag was here
        <IMG SRC="http://divahair.count.brat-online.ro/cgi-bin/cnt/CP/homepage" WID…
  • Error Line 119, Column 29: there is no attribute "size"
    						<fb:login-button size="medium" max-rows="1" v="2" show-faces="false" scop…

    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 119, Column 47: there is no attribute "max-rows"
    …b:login-button size="medium" max-rows="1" v="2" show-faces="false" scope="publ…

    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 119, Column 53: there is no attribute "v"
    …n-button size="medium" max-rows="1" v="2" show-faces="false" scope="publish_ac…

    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 119, Column 68: there is no attribute "show-faces"
    …medium" max-rows="1" v="2" show-faces="false" scope="publish_actions,publish_s…

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

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

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

  • Error Line 119, Column 82: there is no attribute "scope"
    …ws="1" v="2" show-faces="false" scope="publish_actions,publish_stream" onlogin…

    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 119, Column 123: there is no attribute "onlogin"
    …blish_actions,publish_stream" onlogin="refresh_page()">Conecteaza-te cu Facebo…

    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 119, Column 139: element "fb:login-button" undefined
    …blish_stream" onlogin="refresh_page()">Conecteaza-te cu Facebook</fb:login-but…

    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 187, 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 197, Column 19: character "<" is the first character of a delimiter but occurred as data
            for(i=1; i<=4; i++)        

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 256, Column 162: value of attribute "id" invalid: "5" cannot start a name
    …ass="box_shopping_categs"><ul><li id="5"><a href="javascript:void(0)" class="c…

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

  • Error Line 256, Column 1475: value of attribute "id" invalid: "6" cannot start a name
    …">Accesorii par</a></div></li><li id="6"><a href="javascript:void(0)" class="c…

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

  • Error Line 256, Column 2521: value of attribute "id" invalid: "7" cannot start a name
    …u">Seturi cadou</a></div></li><li id="7"><a href="javascript:void(0)" class="c…

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

  • Error Line 256, Column 2920: value of attribute "id" invalid: "8" cannot start a name
    …s">Home-Fitness</a></div></li><li id="8"><a href="javascript:void(0)" class="c…

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

  • Error Line 256, Column 3345: value of attribute "id" invalid: "1" cannot start a name
    …smetice barbati</a></div></li><li id="10"><a href="javascript:void(0)" class="…

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

  • Error Line 256, Column 3670: value of attribute "id" invalid: "1" cannot start a name
    … pentru barbati</a></div></li><li id="11"><a href="javascript:void(0)" class="…

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

  • Error Line 256, Column 4066: value of attribute "id" invalid: "1" cannot start a name
    …jire">Ingrijire</a></div></li><li id="12"><a href="javascript:void(0)" class="…

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

  • Error Line 256, Column 4282: value of attribute "id" invalid: "1" cannot start a name
    …Ceasuri de mana</a></div></li><li id="13"><a href="javascript:void(0)" class="…

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

  • Error Line 256, Column 5278: value of attribute "id" invalid: "5" cannot start a name
    …578px;"><div class="product_item" id="57744"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 5724: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58393"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 6187: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58386"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 6740: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58027"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 7225: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57693"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 7832: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58520"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 8621: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58046"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 9130: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58050"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 9633: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58146"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 10144: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57697"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 10655: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58340"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 11172: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57738"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 11714: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58481"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 12291: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57730"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 12778: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57735"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 13307: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57725"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 13764: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57703"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 14323: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58544"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 14972: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58111"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 15614: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57982"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 16098: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58339"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 16591: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57971"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 17086: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57732"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 17591: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57712"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 18079: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58176"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 18591: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58526"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 19198: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58178"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 19649: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58110"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 20122: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58250"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 20561: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57699"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 21096: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57705"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 21637: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58398"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 22130: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57513"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 22600: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58057"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 23000: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57946"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 23472: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58100"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 23945: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58511"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 24704: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58522"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 25377: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58142"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 26104: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58082"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 26660: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="57704"><div class="imagine"><a href="htt…

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

  • Error Line 256, Column 27201: value of attribute "id" invalid: "5" cannot start a name
    …v></div><div class="product_item" id="58039"><div class="imagine"><a href="htt…

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

  • Error Line 629, Column 94: there is no attribute "align"
    …ormal" align="left"><span class="error" id="ghid_err" align="left"></span></td>

    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 633, Column 26: value of attribute "id" must be a single token
    				<td><input id="custom Nume" name="custom Nume" class="input_style" type="te…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 637, Column 26: value of attribute "id" must be a single token
    				<td><input id="custom Prenume" name="custom Prenume" class="input_style" ty…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 793, Column 150: end tag for "input" omitted, but OMITTAG NO was specified
    … class="buton" style="width: 235px;float:none" onclick="return submit_ghid();">

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

  • Info Line 793, Column 6: start tag was here
    					<input type="submit" value="Da, vreau sa primesc ghidul divahair" class="b…
  • Error Line 803, 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>.

  • Error Line 817, Column 40: document type does not allow element "br" here
                err += 'Introdu numele.<br/>';

    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 819, Column 43: document type does not allow element "br" here
                err += 'Introdu prenumele.<br/>';

    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 821, Column 50: document type does not allow element "br" here
                err += 'Introdu adresa de e-mail.<br/>';

    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 826, Column 63: document type does not allow element "br" here
                    err += 'Introdu o adresa de e-mail valida.<br/>';

    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 845, Column 102: there is no attribute "autocomplete"
    …s" value="Cauta aici..." autocomplete="off" spellcheck="false" onclick="if($(t…

    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 845, Column 119: there is no attribute "spellcheck"
    …ici..." autocomplete="off" spellcheck="false" onclick="if($(this).val()=='Caut…

    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 931, Column 695: cannot generate system identifier for general entity "clickTAG"
    …re/original/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirect…

    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 931, Column 695: general entity "clickTAG" not defined and no default entity
    …re/original/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirect…

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

  • Warning Line 931, Column 703: reference not terminated by REFC delimiter
    …nal/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

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

  • Error Line 931, Column 703: reference to entity "clickTAG" for which no system identifier could be generated
    …nal/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

    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 931, Column 694: entity was defined here
    …ere/original/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirec…
  • Warning Line 931, Column 1441: reference not terminated by REFC delimiter
    …ashVars" value="id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

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

  • Warning Line 931, Column 1441: reference to external entity in attribute value
    …ashVars" value="id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

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

  • Error Line 931, Column 1441: reference to entity "clickTAG" for which no system identifier could be generated
    …ashVars" value="id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

    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 931, Column 694: entity was defined here
    …ere/original/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirec…
  • Error Line 931, Column 1528: there is no attribute "src"
    …391daabe3de1d76a6739ccd" /><embed src="http://www.divahair.ro/uploads/bannere/…

    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 931, Column 1604: there is no attribute "FlashVars"
    …e/original/bannere_554.swf" FlashVars="id_banner=554&clickTAG=http://www.divah…

    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 931, Column 1627: reference not terminated by REFC delimiter
    …swf" FlashVars="id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

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

  • Warning Line 931, Column 1627: reference to external entity in attribute value
    …swf" FlashVars="id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

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

  • Error Line 931, Column 1627: reference to entity "clickTAG" for which no system identifier could be generated
    …swf" FlashVars="id_banner=554&clickTAG=http://www.divahair.ro/redirect/banner/…

    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 931, Column 694: entity was defined here
    …ere/original/bannere_554?id_banner=554&clickTAG=http://www.divahair.ro/redirec…
  • Error Line 931, Column 1707: there is no attribute "wmode"
    …388103a391daabe3de1d76a6739ccd" wmode="transparent" scale="showall" quality="h…

    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 931, Column 1727: there is no attribute "scale"
    …76a6739ccd" wmode="transparent" scale="showall" quality="high" bgcolor="#FFFFF…

    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 931, Column 1745: there is no attribute "quality"
    …"transparent" scale="showall" quality="high" bgcolor="#FFFFFF" width="300" hei…

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

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

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

  • Error Line 931, Column 1760: there is no attribute "bgcolor"
    …cale="showall" quality="high" bgcolor="#FFFFFF" width="300" height="170" align…

    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 931, Column 1776: there is no attribute "width"
    …uality="high" bgcolor="#FFFFFF" width="300" height="170" align="middle" allows…

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

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

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

  • Error Line 931, Column 1789: there is no attribute "height"
    … bgcolor="#FFFFFF" width="300" height="170" align="middle" allowscriptaccess="…

    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 931, Column 1801: there is no attribute "align"
    …FFFFF" width="300" height="170" align="middle" allowscriptaccess="sameDomain" …

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

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

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

  • Error Line 931, Column 1828: there is no attribute "allowscriptaccess"
    …170" align="middle" allowscriptaccess="sameDomain" allowFullScreen="false" typ…

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

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

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

  • Error Line 931, Column 1857: there is no attribute "allowFullScreen"
    …ptaccess="sameDomain" allowFullScreen="false" type="application/x-shockwave-fl…

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

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

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

  • Error Line 931, Column 1870: there is no attribute "type"
    …eDomain" allowFullScreen="false" type="application/x-shockwave-flash" pluginsp…

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

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

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

  • Error Line 931, Column 1914: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 931, Column 1963: there is no attribute "id"
    ….macromedia.com/go/getflashplayer" id="banner554" name="banner554" /></embed><…

    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 931, Column 1980: there is no attribute "name"
    …o/getflashplayer" id="banner554" name="banner554" /></embed></object></noscrip…

    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 931, Column 1993: element "embed" undefined
    …ashplayer" id="banner554" name="banner554" /></embed></object></noscript></div>

    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 931, Column 2001: end tag for element "embed" which is not open
    …ashplayer" id="banner554" name="banner554" /></embed></object></noscript></div>

    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 1003, Column 20: an attribute specification must start with a name or name token
    document.write('<sc'+'ript type="text/javascript" src="'+uri+'" charset="ISO-88…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1003, Column 20: element "sc" undefined
    document.write('<sc'+'ript type="text/javascript" src="'+uri+'" charset="ISO-88…

    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 1003, Column 90: delimiter "'" invalid: only S separators and TAGC allowed here
    …'ript type="text/javascript" src="'+uri+'" charset="ISO-8859-1"></sc'+'ript>');
  • Error Line 1009, Column 32: there is no attribute "href"
                	<fb:like-box href="https://www.facebook.com/DivaHair.ro" width="29…

    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 1009, Column 77: there is no attribute "width"
    …//www.facebook.com/DivaHair.ro" width="298" show_faces="true" stream="false" h…

    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 1009, Column 94: there is no attribute "show_faces"
    …m/DivaHair.ro" width="298" show_faces="true" stream="false" header="false"></f…

    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 1009, Column 108: there is no attribute "stream"
    ….ro" width="298" show_faces="true" stream="false" header="false"></fb:like-box>

    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 1009, Column 123: there is no attribute "header"
    ….ro" width="298" show_faces="true" stream="false" header="false"></fb:like-box>

    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 1009, Column 130: element "fb:like-box" undefined
    ….ro" width="298" show_faces="true" stream="false" header="false"></fb:like-box>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1012, Column 77: cannot generate system identifier for general entity "set"
    …ok.com/photo.php?fbid=494277060628027&set=a.352751648113903.91494.352452944810…

    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 1012, Column 77: general entity "set" not defined and no default entity
    …ok.com/photo.php?fbid=494277060628027&set=a.352751648113903.91494.352452944810…

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

  • Warning Line 1012, Column 80: reference not terminated by REFC delimiter
    …com/photo.php?fbid=494277060628027&set=a.352751648113903.91494.352452944810440…

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

  • Warning Line 1012, Column 80: reference to external entity in attribute value
    …com/photo.php?fbid=494277060628027&set=a.352751648113903.91494.352452944810440…

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

  • Error Line 1012, Column 80: reference to entity "set" for which no system identifier could be generated
    …com/photo.php?fbid=494277060628027&set=a.352751648113903.91494.352452944810440…

    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 1012, Column 76: entity was defined here
    …ook.com/photo.php?fbid=494277060628027&set=a.352751648113903.91494.35245294481…
  • Error Line 1014, Column 27: there is no attribute "href"
                	<g:plus href="https://plus.google.com/109222668446973613296" rel="…

    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 1014, Column 79: there is no attribute "rel"
    … href="https://plus.google.com/109222668446973613296" rel="publisher"></g:plus>

    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 1014, Column 90: element "g:plus" undefined
    … href="https://plus.google.com/109222668446973613296" rel="publisher"></g:plus>

    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 1190, Column 93: value of attribute "id" invalid: "6" cannot start a name
    …d-11cf-96b8-444553540000" width="600" height="500" id="600x500" align="middle">

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

Visitor Analysis

Daily Visitor
  • 5.717 visits
Daily Visitor