hayleybr.com

Seu site de informações sobre a banda Paramore e a vocalista Hayley Williams, Fonte oficial sobre Hayley Williams e o Paramore ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    hayleybr.com
  • Favicon
  • Alexa Rank
    #10849765
  • Google Page Rank
    PR 4
  • Ip Address
    46.105.114.41
  • Page Size
    67.8 KB
  • Images
    0 GIF, 30 JPG, 13 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 0 0 0 0 0

Website Meta Analysis



  • Title
    Hayley Williams Brasil - HayleyBR.com - Sua fonte de informações sobre a banda Paramore no Brasil.
  • Meta Keyword
    Hayley Williams, Paramore, Taylor York, Jeremy Davis, Paramore 2013, Paramore tuor 2013, Parawhore, Paramore Brasil, Paramore Brazil, Paramore no brasil, Josh Farro, Zac Farro, Chad Gilbert, paramore notícias, paramore fotos, hayley williams fotos, hayley williams notícias, riot!, paramore albums, paramore discografia, all we know is falling, Brand New Eyes, Hayley Williams Brasil, hayley williams namorado, hayley williams estilo, hayley williams fansite, hayley williams fã site
  • Meta Description
    Seu site de informações sobre a banda Paramore e a vocalista Hayley Williams, Fonte oficial sobre Hayley Williams e o Paramore

Technical Analysis



  • Webserver
    nginx admin
  • Ip Address
    46.105.114.41
  • Domain Age
    3 Years, 5 Months, 9 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from hayleybr.com.

HTML Analysis

  • server: nginx admin
  • date: Fri, 13 Sep 2013 19:38:33 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-pingback: http://hayleybr.com/xmlrpc.php
  • x-mobilized-by: WordPress Mobile Pack 1.2.5
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for hayleybr.com

DNS Analysis


DNS servers
us1.flauntmedia.net [87.98.238.48]
us2.flauntmedia.net [46.105.114.41]


DNS Records

Answer records
hayleybr.com MX
preference: 0
exchange: hayleybr.com
14400s
hayleybr.com SOA
server: us1.flauntmedia.net
email: admin@flaunt.nu
serial: 2013031200
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
hayleybr.com NS  us1.flauntmedia.net 86400s
hayleybr.com NS  us2.flauntmedia.net 86400s
hayleybr.com A 46.105.114.41 14400s

Authority records

Additional records
hayleybr.com A 46.105.114.41 14400s
us1.flauntmedia.net A 87.98.238.48 100s
us2.flauntmedia.net A 46.105.114.41 100s

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 148 Errors
  • 25 Warnings
Ratio Text/Html
  • 0.546077739533678
Message Error
  • Warning Line 116, Column 111: character "<" is the first character of a delimiter but occurred as data
    … with everything changing colors."] //<--no trailing comma after very last ima…

    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 127, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  • Error Line 129, Column 67: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 131, Column 101: document type does not allow element "script" here; assuming missing "head" start-tag
    …src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
  • Warning Line 164, Column 37: character "&" is the first character of a delimiter but occurred as data
    (function(s,o,l,v,e,d){if(s[o]==null&&s[l+e]){s[o]="loading";s[l+e](d,l=functio…

    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.
  • Warning Line 164, Column 39: cannot generate system identifier for general entity "s"
    (function(s,o,l,v,e,d){if(s[o]==null&&s[l+e]){s[o]="loading";s[l+e](d,l=functio…

    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 164, Column 39: general entity "s" not defined and no default entity
    (function(s,o,l,v,e,d){if(s[o]==null&&s[l+e]){s[o]="loading";s[l+e](d,l=functio…

    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 164, Column 40: reference not terminated by REFC delimiter
    …function(s,o,l,v,e,d){if(s[o]==null&&s[l+e]){s[o]="loading";s[l+e](d,l=functio…

    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 164, Column 40: reference to entity "s" for which no system identifier could be generated
    …function(s,o,l,v,e,d){if(s[o]==null&&s[l+e]){s[o]="loading";s[l+e](d,l=functio…

    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 164, Column 38: entity was defined here
    (function(s,o,l,v,e,d){if(s[o]==null&&s[l+e]){s[o]="loading";s[l+e](d,l=functio…
  • Error Line 188, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 195, Column 15: there is no attribute "BORDER"
    <TABLE BORDER="0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" cla…

    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 195, Column 25: there is no attribute "WIDTH"
    <TABLE BORDER="0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" cla…

    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 195, Column 44: there is no attribute "CELLPADDING"
    …E BORDER="0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" class="…

    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 195, Column 60: there is no attribute "CELLSPACING"
    …"0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" class="menutopo">

    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 195, Column 71: there is no attribute "HEIGHT"
    …"0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" class="menutopo">

    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 195, Column 83: there is no attribute "class"
    …"0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" class="menutopo">

    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 195, Column 93: element "TABLE" undefined
    …"0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" class="menutopo">

    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 197, Column 79: there is no attribute "ALIGN"
    …RDER="0" WIDTH="519" CELLPADDING="0" CELLSPACING="0" ALIGN="LEFT" HEIGHT="180">

    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 197, Column 98: element "TABLE" undefined
    …RDER="0" WIDTH="519" CELLPADDING="0" CELLSPACING="0" ALIGN="LEFT" HEIGHT="180">

    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 198, Column 4: element "TR" undefined
    <TR>

    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 199, Column 5: element "TD" undefined
    	<TD><IMG SRC="http://jbieberlovers.com/web/wp-content/themes/hayleybr/images/l…

    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 199, Column 15: there is no attribute "SRC"
    	<TD><IMG SRC="http://jbieberlovers.com/web/wp-content/themes/hayleybr/images/l…

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

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

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

  • Error Line 199, Column 97: there is no attribute "ALT"
    …mes/hayleybr/images/logotipo.png" ALT="HAYLEYBR.COM ~ SUA FONTE PARAMORE." ></…

    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 199, Column 134: element "IMG" undefined
    …s/hayleybr/images/logotipo.png" ALT="HAYLEYBR.COM ~ SUA FONTE PARAMORE." ></TD>

    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 199, Column 139: end tag for "IMG" omitted, but OMITTAG NO was specified
    …s/hayleybr/images/logotipo.png" ALT="HAYLEYBR.COM ~ SUA FONTE PARAMORE." ></TD>

    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 199, Column 6: start tag was here
    	<TD><IMG SRC="http://jbieberlovers.com/web/wp-content/themes/hayleybr/images/l…
  • Error Line 202, Column 88: element "TABLE" undefined
    …RDER="0" WIDTH="495" CELLPADDING="0" CELLSPACING="0" ALIGN="LEFT" HEIGHT="180">

    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 203, Column 4: element "TR" undefined
    <TR>

    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 204, Column 5: element "TD" undefined
    	<TD><center><form method="get" action="http://hayleybr.com/">

    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 204, Column 13: element "center" undefined
    	<TD><center><form method="get" action="http://hayleybr.com/">

    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 210, Column 4: element "TR" undefined
    <TR>

    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 211, Column 5: element "TD" undefined
    	<TD><center><div id="menu-sprite">

    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 211, Column 13: element "center" undefined
    	<TD><center><div id="menu-sprite">

    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 223, Column 10: end tag for element "table" which is not open
      </table>

    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 224, Column 70: there is no attribute "VALIGN"
    …ELLPADDING="5" CELLSPACING="0" VALIGN="BOTTOM" ALIGN="LEFT" style="margin-top:…

    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 224, Column 98: there is no attribute "style"
    …"0" VALIGN="BOTTOM" ALIGN="LEFT" style="margin-top: 320px; margin-left: 70px;">

    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 224, Column 137: element "TABLE" undefined
    …"0" VALIGN="BOTTOM" ALIGN="LEFT" style="margin-top: 320px; margin-left: 70px;">

    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 225, Column 4: element "TR" undefined
    <TR>

    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 226, Column 5: element "TD" undefined
    	<TD><center><a href="http://paramore-music.com/" target=_blank><IMG alt="" src…

    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 226, Column 13: element "center" undefined
    	<TD><center><a href="http://paramore-music.com/" target=_blank><IMG alt="" src…

    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 226, Column 58: there is no attribute "target"
    …f="http://paramore-music.com/" target=_blank><IMG alt="" src="http://i47.tinyp…

    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 226, Column 58: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …f="http://paramore-music.com/" target=_blank><IMG alt="" src="http://i47.tinyp…
  • Error Line 226, Column 74: there is no attribute "alt"
    …re-music.com/" target=_blank><IMG alt="" src="http://i47.tinypic.com/w9gtvn.pn…

    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 226, Column 81: there is no attribute "src"
    …c.com/" target=_blank><IMG alt="" src="http://i47.tinypic.com/w9gtvn.png" clas…

    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 226, Column 123: there is no attribute "class"
    …p://i47.tinypic.com/w9gtvn.png" class="flags"></a> <a href="http://paramore.co…

    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 226, Column 130: element "IMG" undefined
    ….tinypic.com/w9gtvn.png" class="flags"></a> <a href="http://paramore.com.ar/" …

    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 226, Column 134: end tag for "IMG" omitted, but OMITTAG NO was specified
    …ypic.com/w9gtvn.png" class="flags"></a> <a href="http://paramore.com.ar/" targ…

    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 226, Column 65: start tag was here
    …://paramore-music.com/" target=_blank><IMG alt="" src="http://i47.tinypic.com/…
  • Error Line 226, Column 177: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …href="http://paramore.com.ar/" target=_blank><IMG alt="" src="http://i49.tinyp…
  • Error Line 226, Column 250: element "IMG" undefined
    …tinypic.com/2yttffr.png" class="flags"></a> <a href="http://#" target=_blank><…

    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 226, Column 254: end tag for "IMG" omitted, but OMITTAG NO was specified
    …pic.com/2yttffr.png" class="flags"></a> <a href="http://#" target=_blank><IMG …

    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 226, Column 184: start tag was here
    …ttp://paramore.com.ar/" target=_blank><IMG alt="" src="http://i49.tinypic.com/…
  • Error Line 226, Column 282: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …flags"></a> <a href="http://#" target=_blank><IMG alt="" src="http://i48.tinyp…
  • Error Line 226, Column 354: element "IMG" undefined
    …alt="" src="http://i48.tinypic.com/5p3aeo.png" class="flags"></a></center></TD>

    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 226, Column 358: end tag for "IMG" omitted, but OMITTAG NO was specified
    …alt="" src="http://i48.tinypic.com/5p3aeo.png" class="flags"></a></center></TD>

    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 226, Column 289: start tag was here
    …</a> <a href="http://#" target=_blank><IMG alt="" src="http://i48.tinypic.com/…
  • Error Line 229, Column 6: end tag for "TABLE" omitted, but OMITTAG NO was specified
    </div>

    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 195, Column 1: start tag was here
    <TABLE BORDER="0" WIDTH="1024" CELLPADDING="0" CELLSPACING="0" HEIGHT="180" cla…
  • Error Line 232, Column 8: element "center" undefined
    <center><iframe src="//www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fw…

    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 232, Column 21: there is no attribute "src"
    <center><iframe src="//www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fw…

    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 232, Column 243: there is no attribute "scrolling"
    …eam=false&amp;header=false" scrolling="no" frameborder="0" style="border:none;…

    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 232, Column 260: there is no attribute "frameborder"
    …der=false" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 232, Column 270: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:260…

    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 232, Column 347: there is no attribute "allowTransparency"
    …h:260px; height:258px;" allowTransparency="true"></iframe></center></div><br />

    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 232, Column 353: element "iframe" undefined
    …h:260px; height:258px;" allowTransparency="true"></iframe></center></div><br />

    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 235, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Nome:</b> Hayley Williams Brasil<br>

    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 235, Column 36: start tag was here
    <b>Nome:</b> Hayley Williams Brasil<br>
  • Error Line 236, Column 29: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Desde:</b> 26/04/2010<br>

    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 236, Column 25: start tag was here
    <b>Desde:</b> 26/04/2010<br>
  • Error Line 237, Column 78: end tag for "br" omitted, but OMITTAG NO was specified
    <b>WebMasters:</b> Lucas Amariz, Ana Carla Fernandes e Thomas Chwalensky.<br>

    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 237, Column 74: start tag was here
    <b>WebMasters:</b> Lucas Amariz, Ana Carla Fernandes e Thomas Chwalensky.<br>
  • Error Line 238, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Host:</b> <a href="http://www.flaunt.nu/" target="_blanck">Flaunt.nu</a><br>

    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 238, Column 76: start tag was here
    <b>Host:</b> <a href="http://www.flaunt.nu/" target="_blanck">Flaunt.nu</a><br>
  • Error Line 239, Column 41: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Contato:</b> contato@hayleybr.com<br>

    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 239, Column 37: start tag was here
    <b>Contato:</b> contato@hayleybr.com<br>
  • Error Line 240, Column 33: there is no attribute "language"
    <b>Online:</b> <script language='JavaScript' src='http://blogutils.net/olct/onl…

    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 240, Column 110: cannot generate system identifier for general entity "interval"
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />

    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 240, Column 110: general entity "interval" not defined and no default entity
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />

    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 240, Column 118: reference not terminated by REFC delimiter
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />

    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 240, Column 118: reference to external entity in attribute value
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />

    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 240, Column 118: reference to entity "interval" for which no system identifier could be generated
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />

    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 240, Column 109: entity was defined here
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />
  • Error Line 240, Column 123: required attribute "type" not specified
    …s.net/olct/online.php?site=www.hayleybr.com&interval=600'></script></div><br />

    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 243, Column 8: element "center" undefined
    <center><div class="family">

    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 257, Column 8: element "center" undefined
    <center><a href="http://www.alavigne.com.br/" target=_blank><IMG src="http://i4…

    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 257, Column 54: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …="http://www.alavigne.com.br/" target=_blank><IMG src="http://i46.tinypic.com/…
  • Error Line 257, Column 113: there is no attribute "CLASS"
    …://i46.tinypic.com/2h5uq1i.png" CLASS="afiliados"></a> <a href="http://www.dem…

    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 257, Column 124: element "IMG" undefined
    …pic.com/2h5uq1i.png" CLASS="afiliados"></a> <a href="http://www.demilovato.com…

    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 257, Column 128: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/2h5uq1i.png" CLASS="afiliados"></a> <a href="http://www.demilovato.com.br/…

    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 257, Column 61: start tag was here
    …//www.alavigne.com.br/" target=_blank><IMG src="http://i46.tinypic.com/2h5uq1i…
  • Error Line 257, Column 177: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …http://www.demilovato.com.br/" target=_blank><IMG src="http://i48.tinypic.com/…
  • Error Line 257, Column 246: element "IMG" undefined
    …ypic.com/mkcd1w.png" CLASS="afiliados"></a> <a href="http://www.haydenbrasil.c…

    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 257, Column 250: end tag for "IMG" omitted, but OMITTAG NO was specified
    ….com/mkcd1w.png" CLASS="afiliados"></a> <a href="http://www.haydenbrasil.com/"…

    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 257, Column 184: start tag was here
    …www.demilovato.com.br/" target=_blank><IMG src="http://i48.tinypic.com/mkcd1w.…
  • Error Line 257, Column 298: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …"http://www.haydenbrasil.com/" target=_blank><IMG src="http://i46.tinypic.com/…
  • Error Line 257, Column 367: element "IMG" undefined
    …ypic.com/ztgggh.png" CLASS="afiliados"></a> <a href="http://leamichele.com.br/…

    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 257, Column 371: end tag for "IMG" omitted, but OMITTAG NO was specified
    ….com/ztgggh.png" CLASS="afiliados"></a> <a href="http://leamichele.com.br/" ta…

    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 257, Column 305: start tag was here
    …/www.haydenbrasil.com/" target=_blank><IMG src="http://i46.tinypic.com/ztgggh.…
  • Error Line 257, Column 416: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ef="http://leamichele.com.br/" target=_blank><IMG src="http://i47.tinypic.com/…
  • Error Line 257, Column 485: element "IMG" undefined
    …ypic.com/51o56e.png" CLASS="afiliados"></a> <a href="http://leightonmeester.co…

    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 257, Column 489: end tag for "IMG" omitted, but OMITTAG NO was specified
    ….com/51o56e.png" CLASS="afiliados"></a> <a href="http://leightonmeester.com.br…

    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 257, Column 423: start tag was here
    …p://leamichele.com.br/" target=_blank><IMG src="http://i47.tinypic.com/51o56e.…
  • Error Line 257, Column 539: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ttp://leightonmeester.com.br/" target=_blank><IMG src="http://i46.tinypic.com/…
  • Error Line 257, Column 609: element "IMG" undefined
    …pic.com/11twysi.png" CLASS="afiliados"></a> <a href="http://www.marjorieonline…

    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 257, Column 613: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/11twysi.png" CLASS="afiliados"></a> <a href="http://www.marjorieonline.kit…

    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 257, Column 546: start tag was here
    …eightonmeester.com.br/" target=_blank><IMG src="http://i46.tinypic.com/11twysi…
  • Error Line 257, Column 667: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …//www.marjorieonline.kit.net/" target=_blank><IMG src="http://i49.tinypic.com/…
  • Error Line 257, Column 736: element "IMG" undefined
    …ypic.com/jhv6vm.png" CLASS="afiliados"></a> <a href="http://mcyrus.com/" targe…

    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 257, Column 740: end tag for "IMG" omitted, but OMITTAG NO was specified
    ….com/jhv6vm.png" CLASS="afiliados"></a> <a href="http://mcyrus.com/" target=_b…

    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 257, Column 674: start tag was here
    …arjorieonline.kit.net/" target=_blank><IMG src="http://i49.tinypic.com/jhv6vm.…
  • Error Line 257, Column 778: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …> <a href="http://mcyrus.com/" target=_blank><IMG src="http://i47.tinypic.com/…
  • Error Line 257, Column 848: element "IMG" undefined
    …pic.com/2rfrccj.png" CLASS="afiliados"></a> <a href="http://www.pixielottbrasi…

    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 257, Column 852: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/2rfrccj.png" CLASS="afiliados"></a> <a href="http://www.pixielottbrasil.co…

    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 257, Column 785: start tag was here
    …ef="http://mcyrus.com/" target=_blank><IMG src="http://i47.tinypic.com/2rfrccj…
  • Error Line 257, Column 903: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tp://www.pixielottbrasil.com/" target=_blank><IMG src="http://i46.tinypic.com/…
  • Error Line 257, Column 973: element "IMG" undefined
    …pic.com/28i9n9v.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src…

    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 257, Column 977: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/28i9n9v.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src="ht…

    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 257, Column 910: start tag was here
    …w.pixielottbrasil.com/" target=_blank><IMG src="http://i46.tinypic.com/28i9n9v…
  • Error Line 257, Column 998: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …S="afiliados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/…
  • Error Line 257, Column 1068: element "IMG" undefined
    …pic.com/2gtdqvk.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src…

    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 257, Column 1072: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/2gtdqvk.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src="ht…

    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 257, Column 1005: start tag was here
    …iados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/2gtdqvk…
  • Error Line 257, Column 1093: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …S="afiliados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/…
  • Error Line 257, Column 1163: element "IMG" undefined
    …pic.com/2gtdqvk.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src…

    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 257, Column 1167: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/2gtdqvk.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src="ht…

    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 257, Column 1100: start tag was here
    …iados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/2gtdqvk…
  • Error Line 257, Column 1188: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …S="afiliados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/…
  • Error Line 257, Column 1258: element "IMG" undefined
    …pic.com/2gtdqvk.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src…

    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 257, Column 1262: end tag for "IMG" omitted, but OMITTAG NO was specified
    …com/2gtdqvk.png" CLASS="afiliados"></a> <a href="#" target=_blank><IMG src="ht…

    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 257, Column 1195: start tag was here
    …iados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/2gtdqvk…
  • Error Line 257, Column 1283: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …S="afiliados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/…
  • Error Line 257, Column 1353: element "IMG" undefined
    …_blank><IMG src="http://i49.tinypic.com/2gtdqvk.png" CLASS="afiliados"></a><br>

    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 257, Column 1357: end tag for "IMG" omitted, but OMITTAG NO was specified
    …_blank><IMG src="http://i49.tinypic.com/2gtdqvk.png" CLASS="afiliados"></a><br>

    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 257, Column 1290: start tag was here
    …iados"></a> <a href="#" target=_blank><IMG src="http://i49.tinypic.com/2gtdqvk…
  • Error Line 257, Column 1362: end tag for "br" omitted, but OMITTAG NO was specified
    …_blank><IMG src="http://i49.tinypic.com/2gtdqvk.png" CLASS="afiliados"></a><br>

    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 257, Column 1358: start tag was here
    …_blank><IMG src="http://i49.tinypic.com/2gtdqvk.png" CLASS="afiliados"></a><br>
  • Error Line 264, Column 8: element "center" undefined
    <center><SCRIPT src="http://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <…

    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 264, Column 21: there is no attribute "src"
    <center><SCRIPT src="http://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <…

    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 264, Column 61: element "SCRIPT" undefined
    …ttp://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widg…

    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 264, Column 86: element "SCRIPT" undefined
    …/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widget({  version: 2,  type: …

    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 264, Column 553: element "center" undefined
    …start();</SCRIPT></center><hr/><center><SCRIPT src="http://widgets.twimg.com/j…

    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 264, Column 606: element "SCRIPT" undefined
    …ttp://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widg…

    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 264, Column 631: element "SCRIPT" undefined
    …/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widget({  version: 2,  type: …

    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 264, Column 1098: element "center" undefined
    …start();</SCRIPT></center><hr/><center><SCRIPT src="http://widgets.twimg.com/j…

    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 264, Column 1151: element "SCRIPT" undefined
    …ttp://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widg…

    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 264, Column 1176: element "SCRIPT" undefined
    …/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widget({  version: 2,  type: …

    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 267, Column 8: element "center" undefined
    <center><SCRIPT src="http://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <…

    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 267, Column 61: element "SCRIPT" undefined
    …ttp://widgets.twimg.com/j/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widg…

    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 267, Column 86: element "SCRIPT" undefined
    …/2/widget.js"></SCRIPT>        <SCRIPT> new TWTR.Widget({  version: 2,  type: …

    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 270, Column 65: end tag for "br" omitted, but OMITTAG NO was specified
    <b>23/02/2013</b> - Soundwave Festival @ Brisbane, Austrália<br><hr />

    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 270, Column 61: start tag was here
    <b>23/02/2013</b> - Soundwave Festival @ Brisbane, Austrália<br><hr />
  • Error Line 271, Column 63: end tag for "br" omitted, but OMITTAG NO was specified
    <b>24/02/2013</b> - Soundwave Festival @ Sydney, Austrália<br><hr />

    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 271, Column 59: start tag was here
    <b>24/02/2013</b> - Soundwave Festival @ Sydney, Austrália<br><hr />
  • Error Line 272, Column 66: end tag for "br" omitted, but OMITTAG NO was specified
    <b>01/03/2013</b> - Soundwave Festival @ Melbourne, Austrália<br><hr />

    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 272, Column 62: start tag was here
    <b>01/03/2013</b> - Soundwave Festival @ Melbourne, Austrália<br><hr />
  • Error Line 273, Column 65: end tag for "br" omitted, but OMITTAG NO was specified
    <b>02/03/2013</b> - Soundwave Festival @ Adelaide, Austrália<br><hr />

    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 273, Column 61: start tag was here
    <b>02/03/2013</b> - Soundwave Festival @ Adelaide, Austrália<br><hr />
  • Error Line 274, Column 67: end tag for "br" omitted, but OMITTAG NO was specified
    <b>04/03/2013</b> - Soundwave Festival @ Perth, Austrália<br></div><br />

    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 274, Column 58: start tag was here
    <b>04/03/2013</b> - Soundwave Festival @ Perth, Austrália<br></div><br />
  • Error Line 277, Column 148: element "u" undefined
    … <b>Paramore</b>. Não temos nenhuma <u>ligação</u> com a Hayley ou com a banda…

    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 277, Column 485: element "u" undefined
    …tence ao site, não o <b>utilize</b> sem os devidos <u>créditos</u>.</div><br />

    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 279, Column 8: element "center" undefined
    <center><a href="http://www.fueledbyramen.com" target="_blank"><img src="http:/…

    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 279, Column 143: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ia.tumblr.com/tumblr_kzftfvzqoW1qamjkgo1_500.jpg" width=150 height=146></a><br>
  • Error Line 279, Column 154: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ia.tumblr.com/tumblr_kzftfvzqoW1qamjkgo1_500.jpg" width=150 height=146></a><br>
  • Error Line 279, Column 157: required attribute "alt" not specified
    …ia.tumblr.com/tumblr_kzftfvzqoW1qamjkgo1_500.jpg" width=150 height=146></a><br>

    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 279, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …ia.tumblr.com/tumblr_kzftfvzqoW1qamjkgo1_500.jpg" width=150 height=146></a><br>

    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 279, Column 64: start tag was here
    …ww.fueledbyramen.com" target="_blank"><img src="http://24.media.tumblr.com/tum…
  • Error Line 279, Column 166: end tag for "br" omitted, but OMITTAG NO was specified
    …ia.tumblr.com/tumblr_kzftfvzqoW1qamjkgo1_500.jpg" width=150 height=146></a><br>

    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 279, Column 162: start tag was here
    …ia.tumblr.com/tumblr_kzftfvzqoW1qamjkgo1_500.jpg" width=150 height=146></a><br>
  • Error Line 281, Column 101: required attribute "alt" not specified
    …"_blank"><img src="http://i48.tinypic.com/s1os9c.png"></a></center></div><br />

    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 281, Column 105: end tag for "img" omitted, but OMITTAG NO was specified
    …"_blank"><img src="http://i48.tinypic.com/s1os9c.png"></a></center></div><br />

    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 281, Column 57: start tag was here
    …w.warnermusic.com.br" target="_blank"><img src="http://i48.tinypic.com/s1os9c.…
  • Error Line 284, Column 8: element "center" undefined
    <center><!-- PUT THIS TAG IN DESIRED LOCATION OF SLOT FlauntLightSky

    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 306, Column 547: end tag for "br" omitted, but OMITTAG NO was specified
    …s em Paramore (álbum)" rel="category tag">Paramore (álbum)</a> </div></div><br>

    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 306, Column 543: start tag was here
    …s em Paramore (álbum)" rel="category tag">Paramore (álbum)</a> </div></div><br>
  • Error Line 320, Column 1497: end tag for "br" omitted, but OMITTAG NO was specified
    …e="Ver todos os posts em Taylor" rel="category tag">Taylor</a> </div></div><br>

    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 320, Column 1493: start tag was here
    …e="Ver todos os posts em Taylor" rel="category tag">Taylor</a> </div></div><br>
  • Error Line 339, Column 13: end tag for "p" omitted, but OMITTAG NO was specified
    </blockquote>

    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 338, Column 1: start tag was here
    <p style="text-align: center;">
  • Error Line 343, Column 1057: end tag for "br" omitted, but OMITTAG NO was specified
    …e="Ver todos os posts em Taylor" rel="category tag">Taylor</a> </div></div><br>

    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 343, Column 1053: start tag was here
    …e="Ver todos os posts em Taylor" rel="category tag">Taylor</a> </div></div><br>
  • Error Line 356, Column 679: end tag for "br" omitted, but OMITTAG NO was specified
    …s em Paramore (álbum)" rel="category tag">Paramore (álbum)</a> </div></div><br>

    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 356, Column 675: start tag was here
    …s em Paramore (álbum)" rel="category tag">Paramore (álbum)</a> </div></div><br>
  • Error Line 384, Column 691: end tag for "br" omitted, but OMITTAG NO was specified
    …s em Paramore (álbum)" rel="category tag">Paramore (álbum)</a> </div></div><br>

    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 384, Column 687: start tag was here
    …s em Paramore (álbum)" rel="category tag">Paramore (álbum)</a> </div></div><br>
  • Error Line 388, Column 33: element "center" undefined
    <div class="caixa"><br /><center><div class='wp-pagenavi'>

    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 396, Column 123: there is no attribute "align"
    …ELLPADDING="0" CELLSPACING="0" HEIGHT="231" class="footerstyle" align="center">

    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 396, Column 131: element "TABLE" undefined
    …ELLPADDING="0" CELLSPACING="0" HEIGHT="231" class="footerstyle" align="center">

    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 397, Column 8: element "TR" undefined
        <TR>

    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 398, Column 10: element "TD" undefined
          <TD><div class="footer1"><div class="navlinktext">HayleyBR.com</div><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 409, Column 82: ID "menu" already defined
    …div><div class="footer2"><div class="navlinktext">Paramore</div><div id="menu">

    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 398, Column 84: ID "menu" first defined here
    …<div class="footer1"><div class="navlinktext">HayleyBR.com</div><div id="menu">
  • Error Line 420, Column 81: ID "menu" already defined
    …/div><div class="footer3"><div class="navlinktext">Galeria</div><div id="menu">

    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 398, Column 84: ID "menu" first defined here
    …<div class="footer1"><div class="navlinktext">HayleyBR.com</div><div id="menu">
  • Error Line 442, Column 8: end tag for "head" omitted, but OMITTAG NO was specified
    </html>

    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 3, Column 1: start tag was here
    <head profile="http://gmpg.org/xfn/11">
  • Error Line 442, Column 8: "html" not finished but document ended
    </html>
  • Error Line 442, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

    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 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 4 visits