¡Corazón de Melón, juego de citas! ¡Conquista a los personajes que más te gusten y vive una auténtica historia de amor! ¡¡Descubre un nuevo capítulo regularmente y conviértete en la chica más cautivadora!! ...

corazondemelon.es
  • Domain Name
    corazondemelon.es
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #67950
  • Page Size
    15.4 KB
  • Ip Address
    178.33.132.180
  • Heading
    H1: 1, H2: 2, H3: 2, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    Corazón de Melón, juego de amor y ligue para las chicas!
  • Meta Keyword
  • Meta Description
    ¡Corazón de Melón, juego de citas! ¡Conquista a los personajes que más te gusten y vive una auténtica historia de amor! ¡¡Descubre un nuevo capítulo regularmente y conviértete en la chica más cautivadora!!

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    178.33.132.180
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from corazondemelon.es.

HTML Analysis

  • server: nginx
  • date: Wed, 07 Aug 2013 13:25:57 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • 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
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for corazondemelon.es

DNS Analysis


DNS servers
dns19.ovh.net [213.251.188.139]
ns19.ovh.net [213.251.128.139]


DNS Records

Answer records
corazondemelon.es SOA
server: dns19.ovh.net
email: tech@ovh.net
serial: 2012120300
refresh: 86400
retry: 3600
expire: 3600000
minimum ttl: 86400
3600s
corazondemelon.es NS  dns19.ovh.net 3600s
corazondemelon.es NS  ns19.ovh.net 3600s
corazondemelon.es MX
preference: 1
exchange: titan.beemoov.com
3600s
corazondemelon.es A 178.33.132.180 3600s
corazondemelon.es TXT v=spf1 mx ip4:94.23.233.207 -all 3600s
corazondemelon.es TXT spf2.0/pra mx ip4:94.23.233.207 mx:titan.beemoov.com -all 3600s

Authority records

Additional records

IP 178.33.132.180 Analysis

  • Country Code
    ES
  • Country Code3
    ESP
  • Country Name
    Spain
  • City
    EU
  • Continent Code
    40° North
  • Latitude
    4.
  • Longitude
  • No whois ip data for 178.33.132.180

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 24 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.5687167805618831
Message Error
  • Error Line 17, Column 91: there is no attribute "sizes"
    …e/common/img/favicon/apple-favicon-114.png" sizes="114x114" type="image/png" />

    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 76, Column 31: 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 223, Column 36: there is no attribute "rel"
    									<span id="picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resol…

    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 223, Column 75: cannot generate system identifier for general entity "resolution"
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>

    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 223, Column 75: general entity "resolution" not defined and no default entity
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>

    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 223, Column 85: reference not terminated by REFC delimiter
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>

    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 223, Column 85: reference to external entity in attribute value
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>

    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 223, Column 85: reference to entity "resolution" for which no system identifier could be generated
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>

    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 223, Column 74: entity was defined here
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>
  • Warning Line 224, Column 88: reference not terminated by REFC delimiter
    …"picture_15" rel="assets/episode.kiss!normal%C2%BFid=15&resolution=web"></span>

    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 224, Column 88: reference to external entity in attribute value
    …"picture_15" rel="assets/episode.kiss!normal%C2%BFid=15&resolution=web"></span>

    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 224, Column 88: reference to entity "resolution" for which no system identifier could be generated
    …"picture_15" rel="assets/episode.kiss!normal%C2%BFid=15&resolution=web"></span>

    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 223, Column 74: entity was defined here
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>
  • Warning Line 225, Column 87: reference not terminated by REFC delimiter
    …g id="picture_16" src="assets/episode.kiss!normal%C2%BFid=16&resolution=web" />

    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 225, Column 87: reference to external entity in attribute value
    …g id="picture_16" src="assets/episode.kiss!normal%C2%BFid=16&resolution=web" />

    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 225, Column 87: reference to entity "resolution" for which no system identifier could be generated
    …g id="picture_16" src="assets/episode.kiss!normal%C2%BFid=16&resolution=web" />

    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 223, Column 74: entity was defined here
    …"picture_14" rel="assets/episode.kiss!normal%C2%BFid=14&resolution=web"></span>
  • Error Line 225, Column 94: required attribute "alt" not specified
    …g id="picture_16" src="assets/episode.kiss!normal%C2%BFid=16&resolution=web" />

    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 233, Column 66: cannot generate system identifier for general entity "autoplay"
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 66: general entity "autoplay" not defined and no default entity
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 74: reference not terminated by REFC delimiter
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 74: reference to entity "autoplay" for which no system identifier could be generated
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 65: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 233, Column 77: cannot generate system identifier for general entity "hd"
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 77: general entity "hd" not defined and no default entity
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 79: reference not terminated by REFC delimiter
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 79: reference to entity "hd" for which no system identifier could be generated
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>

    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 233, Column 76: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 240, Column 74: reference not terminated by REFC delimiter
    …v class="video">http://www.youtube.com/embed/uyBWNLo50J0?&autoplay=1&hd=1</div>

    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 240, Column 74: reference to entity "autoplay" for which no system identifier could be generated
    …v class="video">http://www.youtube.com/embed/uyBWNLo50J0?&autoplay=1&hd=1</div>

    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 233, Column 65: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 240, Column 79: reference not terminated by REFC delimiter
    …v class="video">http://www.youtube.com/embed/uyBWNLo50J0?&autoplay=1&hd=1</div>

    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 240, Column 79: reference to entity "hd" for which no system identifier could be generated
    …v class="video">http://www.youtube.com/embed/uyBWNLo50J0?&autoplay=1&hd=1</div>

    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 233, Column 76: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 245, Column 74: reference not terminated by REFC delimiter
    …v class="video">http://www.youtube.com/embed/wP6cTJr29FI?&autoplay=1&hd=1</div>

    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 245, Column 74: reference to entity "autoplay" for which no system identifier could be generated
    …v class="video">http://www.youtube.com/embed/wP6cTJr29FI?&autoplay=1&hd=1</div>

    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 233, Column 65: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 245, Column 79: reference not terminated by REFC delimiter
    …v class="video">http://www.youtube.com/embed/wP6cTJr29FI?&autoplay=1&hd=1</div>

    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 245, Column 79: reference to entity "hd" for which no system identifier could be generated
    …v class="video">http://www.youtube.com/embed/wP6cTJr29FI?&autoplay=1&hd=1</div>

    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 233, Column 76: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 252, Column 97: reference not terminated by REFC delimiter
    …_enabled" href="http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1"></a>

    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 252, Column 97: reference to external entity in attribute value
    …_enabled" href="http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1"></a>

    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 252, Column 97: reference to entity "autoplay" for which no system identifier could be generated
    …_enabled" href="http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1"></a>

    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 233, Column 65: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Warning Line 252, Column 102: reference not terminated by REFC delimiter
    …_enabled" href="http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1"></a>

    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 252, Column 102: reference to external entity in attribute value
    …_enabled" href="http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1"></a>

    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 252, Column 102: reference to entity "hd" for which no system identifier could be generated
    …_enabled" href="http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1"></a>

    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 233, Column 76: entity was defined here
    …v class="video">http://www.youtube.com/embed/zosZVlDL1lk?&autoplay=1&hd=1</div>
  • Error Line 259, Column 29: there is no attribute "rel"
    					<div class="actif" rel="16">

    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 282, Column 21: there is no attribute "profile_id"
    	<fb:fan profile_id="101050723326137" stream="0" connections="8" logobar="1" wi…

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

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

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

  • Error Line 282, Column 46: there is no attribute "stream"
    …n profile_id="101050723326137" stream="0" connections="8" logobar="1" width="7…

    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 282, Column 62: there is no attribute "connections"
    …101050723326137" stream="0" connections="8" logobar="1" width="703" height="98"

    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 282, Column 74: there is no attribute "logobar"
    …101050723326137" stream="0" connections="8" logobar="1" width="703" height="98"

    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 282, Column 84: there is no attribute "width"
    …101050723326137" stream="0" connections="8" logobar="1" width="703" height="98"

    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 282, Column 97: there is no attribute "height"
    …101050723326137" stream="0" connections="8" logobar="1" width="703" height="98"

    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 283, Column 7: there is no attribute "css"
    		css="http://www.amoursucre.com/theme/client/css/facebook.css?BADCOFFEE"></fb:…

    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 283, Column 74: element "fb:fan" undefined
    …s="http://www.amoursucre.com/theme/client/css/facebook.css?BADCOFFEE"></fb:fan>

    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 285, 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 150, Column 10: ID "fb-root" first defined here
    <div id="fb-root"></div>
  • Error Line 294, Column 33: there is no attribute "size"
    <div id="gplus"><g:plusone size="tall" annotation="inline"></g:plusone></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 294, Column 51: there is no attribute "annotation"
    <div id="gplus"><g:plusone size="tall" annotation="inline"></g:plusone></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 294, Column 59: element "g:plusone" undefined
    <div id="gplus"><g:plusone size="tall" annotation="inline"></g:plusone></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 314, 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 150, Column 10: ID "fb-root" first defined here
    <div id="fb-root"></div>

Visitor Analysis

Daily Visitor
  • 2.917 visits