Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 8, Column 17:
there is no attribute "LANGUAGE".<script language=javascript><!--You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 8, Column 27:
required attribute "TYPE" not specified.<script language=javascript><!--The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 214, Column 27:
required attribute "TYPE" not specified.<script language=javascript>var YLH='_ylh=X3oDMTFkcXA5Zzg1BF9TAzI3MTYxNDkEcGlkAzThe 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>.
Line 214, Column 361:
there is no attribute "TARGET".…GVzdAMwBHRtcGwDaW5kZXgtbA--/" target=_top></noscript>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.
Line 214, Column 365:
document type does not allow element "BASE" here.…AMwBHRtcGwDaW5kZXgtbA--/" target=_top></noscript>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).
Line 214, Column 376:
end tag for "NOSCRIPT" which is not finished.…aW5kZXgtbA--/" target=_top></noscript>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 225, Column 22:
document type does not allow element "STYLE" here.<style type="text/css">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).
Line 2605, Column 6:
end tag for element "HEAD" which is not open.</head>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 2606, Column 19:
document type does not allow element "BODY" here.<body class="ywide">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).
Line 2610, Column 6:
required attribute "TYPE" not specified.<style>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>.
Line 2610, Column 6:
document type does not allow element "STYLE" here.<style>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).
Line 2633, Column 364:
required attribute "TYPE" not specified.…opping</A><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 2636, Column 18:
document type does not allow element "NOSCRIPT" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.</script><noscript><img width=1 height=1 alt="" src="http://us.bc.yahoo.com/b?P=The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2636, Column 121:
cannot generate system identifier for general entity "T".…hES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d27161An 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 "&" (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 æ 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.
Line 2636, Column 121:
general entity "T" not defined and no default entity.…hES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d27161This 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.
Line 2636, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…9934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d385An 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 "&" (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 æ 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.
Line 2636, Column 266:
general entity "U" not defined and no default entity.…9934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d385This 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.
Line 2636, Column 267:
reference to entity "U" for which no system identifier could be generated.…934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d3858This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…452.9641268%2fD%3dHDLN%2fB%3d4995222"></noscript></span>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2636, Column 372:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dHDLN%2fB%3d4995222"></noscript></span>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 2637, Column 22:
document type does not allow element "STYLE" here.<style type="text/css">#ws_hp{display:block};</style>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).
Line 2659, Column 132:
end tag for element "A" which is not open.…tba" href=\'r\/1m\'>Get Yahoo! DSL</a>';}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.
Line 2724, Column 3:
"IF" is not a reserved name.<![if !IE]>…HTML='<div class=bd><div id=pnt></div><a title="Yahoo!" class=shp href="http:
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 2725, Column 0:
start tag was here.<script language="javascript" type="text/javascript">…e detailed instructions <a href=http://www.yahoo.com/r/hs>click here</a>.</p>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2742, Column 418:
end tag for element "A" which is not open.…tp://www.yahoo.com/r/hs>click here</a>.</p></div>';The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 2751, Column 8:
end tag for element "SCRIPT" which is not open.</script>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.
Line 2752, Column 3:
"ENDIF" is not a reserved name.<![endif]>…us.yimg.com/i/ww/beta/y3.gif" border=0 width=232 height=44 alt="Yahoo!" id="yYou 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.
Line 2758, Column 7:
required attribute "TYPE" not specified.<script>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>.
Line 2786, Column 264:
end tag for element "MAP" which is not open.…ick="callYodel();return false;"></map><div id=l_fl style="position:absolute">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.
Line 2786, Column 309:
end tag for "SCRIPT" omitted, but its declaration does not permit this.…=l_fl style="position:absolute"></div>');
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 2758, Column 0:
start tag was here.<script>…=l_fl style="position:absolute"></div>');
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 2757, Column 0:
start tag was here.<h1><img src="http://us.i1.yimg.com/us.yimg.com/i/ww/beta/y3.gif" border=0 width</script><script language=javascript>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.
Line 2789, Column 36:
required attribute "TYPE" not specified.</script><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 2792, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142d7bft8%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…233%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13b6n2c7t%2fN%3dT2zcUtGDJGM-%2fC%3d2895This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…57.5322130%2fD%3dHEADR%2fB%3d4040821"></noscript></h1>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2792, Column 373:
end tag for "NOSCRIPT" which is not finished.…2fD%3dHEADR%2fB%3d4040821"></noscript></h1>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 2792, Column 378:
end tag for element "H1" which is not open.…dHEADR%2fB%3d4040821"></noscript></h1>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.
Line 2819, Column 6:
required attribute "TYPE" not specified.<style>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>.
Line 2819, Column 6:
document type does not allow element "STYLE" here.<style>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).
Line 2825, Column 183:
required attribute "TYPE" not specified.…88/R=0 --><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 2828, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142848gs3%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…123%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bis81h9%2fN%3dUmzcUtGDJGM-%2fC%3d5927This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…693.11125467%2fD%3dNAM%2fB%3d4925688"></noscript><noscript><input name="u" tyThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2828, Column 373:
end tag for "NOSCRIPT" which is not finished.…7%2fD%3dNAM%2fB%3d4925688"></noscript><noscript><input name="u" type="hidden"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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 2828, Column 461:
cannot generate system identifier for general entity "p".…p://search.yahoo.com/search?fr=yfp-t&p="></noscript>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 "&" (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 æ 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.
Line 2828, Column 461:
general entity "p" not defined and no default entity.…p://search.yahoo.com/search?fr=yfp-t&p="></noscript>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.
Line 2828, Column 462:
reference to entity "p" for which no system identifier could be generated.…://search.yahoo.com/search?fr=yfp-t&p="></noscript>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.
Line 2828, Column 460:
entity was defined here.…tp://search.yahoo.com/search?fr=yfp-t&p="></noscript>…/search.yahoo.com/search?fr=yfp-t&p="></noscript>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2828, Column 475:
end tag for "NOSCRIPT" which is not finished.…oo.com/search?fr=yfp-t&p="></noscript>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 2833, Column 29:
required attribute "TYPE" not specified.<script language="javascript">The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 2865, Column 17:
document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<div class="iemw"></div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2866, Column 18:
document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<div id="pscolors">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2886, Column 5:
end tag for element "DIV" which is not open.</div>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 2888, Column 5:
end tag for element "DIV" which is not open.</div>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 2918, Column 120:
NET-enabling start-tag requires SHORTTAG YES.…und-position: -400px -1205px;" href=r/io>Bix<small class="new" style="backgroThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2948, Column 281:
required attribute "TYPE" not specified.…ebsite</a><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 2951, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142vscu0v%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…361%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13ctmpvdn%2fN%3dYGzcUtGDJGM-%2fC%3d2613This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…35.10391589%2fD%3dFPC1%2fB%3d1798789"></noscript></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2951, Column 374:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dFPC1%2fB%3d1798789"></noscript></li>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 2966, Column 17:
there is no attribute "HIDEFOCUS".<em><a hidefocus="true" id="featured1" href="r/tj">Featured</a></em>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.
Line 2989, Column 9:
NET-enabling start-tag requires SHORTTAG YES.<a href=s/720538><img src="http://us.i1.yimg.com/us.yimg.com/i/ww/news/2007/10/2The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2991, Column 3:
document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<h3><a href=s/720538>NFL's winners and losers</a></h3>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2991, Column 13:
NET-enabling start-tag requires SHORTTAG YES.<h3><a href=s/720538>NFL's winners and losers</a></h3>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2992, Column 2:
document type does not allow element "P" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<p>Not everyone is perfect, unless you are the Indianapolis Colts and New EnglanThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2992, Column 112:
NET-enabling start-tag requires SHORTTAG YES.…ngland Patriots. <a class=more href=s/720538>» Week 8 list</a></p>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2994, Column 3:
document type does not allow element "UL" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<ul>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 2995, Column 26:
NET-enabling start-tag requires SHORTTAG YES.<li><a class=bullet href=s/720539>Most hyped game ever</a></li>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2996, Column 26:
NET-enabling start-tag requires SHORTTAG YES.<li><a class=bullet href=s/720540>Scores</a></li>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2997, Column 26:
NET-enabling start-tag requires SHORTTAG YES.<li><a class=bullet href=s/720541>Moss' mind</a></li>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2998, Column 26:
NET-enabling start-tag requires SHORTTAG YES.<li><a class=bullet href=s/720542>Rowdy game</a></li>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 2999, Column 26:
NET-enabling start-tag requires SHORTTAG YES.<li><a class=bullet href=s/720543>Silver</a></li>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3038, Column 22:
document type does not allow element "UL" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<ul id="todaystories1">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3039, Column 17:
character "|" is not allowed in the value of attribute "ID".<li id="featured1|854" class="on"><a href=s/720544><img src="http://us.i1.yimg.c
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 3039, Column 43:
NET-enabling start-tag requires SHORTTAG YES.…="featured1|854" class="on"><a href=s/720544><img src="http://us.i1.yimg.com/The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3040, Column 17:
character "|" is not allowed in the value of attribute "ID".<li id="featured2|851"><a href=s/720404><img src="http://us.i1.yimg.com/us.yimg.
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 3040, Column 32:
NET-enabling start-tag requires SHORTTAG YES.<li id="featured2|851"><a href=s/720404><img src="http://us.i1.yimg.com/us.yimg.The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3042, Column 17:
character "|" is not allowed in the value of attribute "ID".<li id="featured3|856"><a href=s/720554><img src="http://us.i1.yimg.com/us.yimg.
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 3042, Column 32:
NET-enabling start-tag requires SHORTTAG YES.<li id="featured3|856"><a href=s/720554><img src="http://us.i1.yimg.com/us.yimg.The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3043, Column 17:
character "|" is not allowed in the value of attribute "ID".<li id="featured4|835"><a href=s/720472>
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 3043, Column 32:
NET-enabling start-tag requires SHORTTAG YES.<li id="featured4|835"><a href=s/720472>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3046, Column 40:
document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<div id="more-featured" class="btn-more">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3088, Column 16:
document type does not allow element "H2" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<h2 class="a11y">In the News</h2>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3089, Column 17:
document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<div id="newstop">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3091, Column 5:
reference to non-SGML character.• <a href=s/720335>Suicide bomber kills 27 at Iraqi police station</a>You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 21:
NET-enabling start-tag requires SHORTTAG YES.• <a href=s/720335>Suicide bomber kills 27 at Iraqi police station</a>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 124:
NET-enabling start-tag requires SHORTTAG YES.…ss="inline"><dt><a class=video href=s/720499 onclick="window.open('s/720499',The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 243:
end tag for element "A" which is not open.…lbars=no');return false;">Security</a></dt></dl><br>• <a href=s/720The 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.
Line 3091, Column 263:
reference to non-SGML character.…lse;">Security</a></dt></dl><br>• <a href=s/720529>Turkey targets KYou've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 279:
NET-enabling start-tag requires SHORTTAG YES.…a></dt></dl><br>• <a href=s/720529>Turkey targets Kurdish rebels asThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 381:
NET-enabling start-tag requires SHORTTAG YES.…ss="inline"><dt><a class=video href=s/720534 onclick="window.open('s/720534',The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 499:
end tag for element "A" which is not open.…llbars=no');return false;">Clashes</a></dt></dl><br>• <a href=s/720The 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.
Line 3091, Column 519:
reference to non-SGML character.…alse;">Clashes</a></dt></dl><br>• <a href=s/720580>Darfur rebels saYou've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 535:
NET-enabling start-tag requires SHORTTAG YES.…a></dt></dl><br>• <a href=s/720580>Darfur rebels say attacks continThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 643:
NET-enabling start-tag requires SHORTTAG YES.…ss="inline"><dt><a class=video href=s/720581 onclick="window.open('s/720581',The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 759:
end tag for element "A" which is not open.…rollbars=no');return false;">Talks</a></dt></dl><br>• <a href=s/720The 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.
Line 3091, Column 779:
reference to non-SGML character.… false;">Talks</a></dt></dl><br>• <a href=s/720523>Campus mourns seYou've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 795:
NET-enabling start-tag requires SHORTTAG YES.…a></dt></dl><br>• <a href=s/720523>Campus mourns seven killed in NoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 900:
NET-enabling start-tag requires SHORTTAG YES.…ss="inline"><dt><a class=video href=s/720524 onclick="window.open('s/720524',The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 1021:
end tag for element "A" which is not open.…ars=no');return false;">Beach trip</a></dt></dl><br>• <a href=s/720The 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.
Line 3091, Column 1041:
reference to non-SGML character.…e;">Beach trip</a></dt></dl><br>• <a href=s/720563>Slaying suspect You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 1057:
NET-enabling start-tag requires SHORTTAG YES.…a></dt></dl><br>• <a href=s/720563>Slaying suspect escapes jail by The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 1139:
reference to non-SGML character.…ing identity of cellmate</a><br>• <a href=s/720537>Ghost tourism boYou've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 1155:
NET-enabling start-tag requires SHORTTAG YES.…cellmate</a><br>• <a href=s/720537>Ghost tourism booming on U.S. inThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 1230:
reference to non-SGML character.…interest in supernatural</a><br>• <a href=s/720589>French presidentYou've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.
The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.
Line 3091, Column 1246:
NET-enabling start-tag requires SHORTTAG YES.…rnatural</a><br>• <a href=s/720589>French president cuts off 'stupiThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 1350:
NET-enabling start-tag requires SHORTTAG YES.…ss="inline"><dt><a class=video href=s/720590 onclick="window.open('s/720590',The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3091, Column 1468:
end tag for element "A" which is not open.…llbars=no');return false;">Sarkozy</a></dt></dl><br>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.
Line 3093, Column 91:
NET-enabling start-tag requires SHORTTAG YES.…<b>»</b> More:</li><li><a href=r/xn>News</a></li><li><a href=r/me>PopulaThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3093, Column 121:
NET-enabling start-tag requires SHORTTAG YES.… href=r/xn>News</a></li><li><a href=r/me>Popular</a></li><li class="last"><a The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3093, Column 167:
NET-enabling start-tag requires SHORTTAG YES.…ar</a></li><li class="last"><a href=r/z0>Election '08</a></li></ul>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3095, Column 16:
document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag.<div id="newsft">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3098, Column 496:
NET-enabling start-tag requires SHORTTAG YES.…size="5" title="Enter ticker symbol" /><input type="submit" class="submit" vaThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3098, Column 545:
NET-enabling start-tag requires SHORTTAG YES.…e="submit" class="submit" value="Go" /></fieldset></form></div></div>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3101, Column 22:
document type does not allow element "STYLE" here.<style type="text/css">#news-sponsor img{position:relative;display:block;margin: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).
Line 3101, Column 581:
required attribute "ALT" not specified.…height=15 title="Switch to Scottrade"></a><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3101, Column 613:
required attribute "TYPE" not specified.…rade"></a><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3104, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142uii5d3%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…557%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bjjg8k5%2fN%3dYWzcUtGDJGM-%2fC%3d5797This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…704.9498165%2fD%3dSTCK%2fB%3d4876291"></noscript></div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3104, Column 373:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dSTCK%2fB%3d4876291"></noscript></div>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3123, Column 328:
cannot generate system identifier for general entity "hmpgID".…report.com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="hAn 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 "&" (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 æ 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.
Line 3123, Column 328:
general entity "hmpgID" not defined and no default entity.…report.com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="hThis 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.
Line 3123, Column 334:
reference to entity "hmpgID" for which no system identifier could be generated.….com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://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.
Line 3123, Column 327:
entity was defined here.…treport.com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="…m/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://us.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 "&" (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 æ 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.
Line 3123, Column 337:
general entity "bcd" not defined and no default entity.…m/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://us.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.
Line 3123, Column 340:
reference to entity "bcd" for which no system identifier could be generated.…m/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://us.i1.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.
Line 3123, Column 336:
entity was defined here.…om/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://us…ltlA.gif" width=70 height=50 border=0></a></td><td width=8> </td><td valThe 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>.
Line 3123, Column 506:
there is no attribute "WIDTH".…eight=50 border=0></a></td><td width=8> </td><td valign=top><font face=aYou 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.
Line 3123, Column 545:
there is no attribute "FACE".… </td><td valign=top><font face=arial size=-1><a href="http://us.ard.yahYou 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.
Line 3123, Column 556:
there is no attribute "SIZE".…<td valign=top><font face=arial size=-1><a href="http://us.ard.yahoo.com/SIG=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.
Line 3123, Column 558:
element "FONT" undefined.…d valign=top><font face=arial size=-1><a href="http://us.ard.yahoo.com/SIG=12You 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:
Line 3123, Column 817:
reference to entity "hmpgID" for which no system identifier could be generated.….com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY">What's your crediThis 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.
Line 3123, Column 327:
entity was defined here.…treport.com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="…m/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY">What's your credit scorThis 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.
Line 3123, Column 336:
entity was defined here.…om/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://us….com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY">See yours for $0.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.
Line 3123, Column 327:
entity was defined here.…treport.com/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="…m/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY">See yours for $0. By ExThis 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.
Line 3123, Column 336:
entity was defined here.…om/pm/default.aspx?sc=658900&hmpgID=2&bcd=YFPMON1029ARMY"><img src="http://us…r></table><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3126, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141opbrc2%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…196%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13akvmu95%2fN%3dYmzcUtGDJGM-%2fC%3d5999This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…3182.9413987%2fD%3dMKP%2fB%3d4995695"></noscript><hr size=1 noshade><a href="The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3126, Column 371:
end tag for "NOSCRIPT" which is not finished.…7%2fD%3dMKP%2fB%3d4995695"></noscript><hr size=1 noshade><a href="http://us.aMost 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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3126, Column 381:
there is no attribute "SIZE".…P%2fB%3d4995695"></noscript><hr size=1 noshade><a href="http://us.ard.yahoo.cYou 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.
Line 3126, Column 390:
"NOSHADE" is not a member of a group specified for any attribute.…995695"></noscript><hr size=1 noshade><a href="http://us.ard.yahoo.com/SIG=12…e/index.jsp?sourceid=lmb-11622-22067&moid=20015">Think the Fed will lower ratAn 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 "&" (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 æ 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.
Line 3126, Column 653:
general entity "moid" not defined and no default entity.…e/index.jsp?sourceid=lmb-11622-22067&moid=20015">Think the Fed will lower ratThis 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.
Line 3126, Column 657:
reference to entity "moid" for which no system identifier could be generated.…dex.jsp?sourceid=lmb-11622-22067&moid=20015">Think the Fed will lower rates oThis 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.
Line 3126, Column 652:
entity was defined here.…re/index.jsp?sourceid=lmb-11622-22067&moid=20015">Think the Fed will lower ra…dex.jsp?sourceid=lmb-11622-22067&moid=20015">LowerMyBills: Estimate payment</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.
Line 3126, Column 652:
entity was defined here.…re/index.jsp?sourceid=lmb-11622-22067&moid=20015">Think the Fed will lower ra…yment</a>.<script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3130, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=14100kvt2%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…855%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bjke66o%2fN%3dY2zcUtGDJGM-%2fC%3d5716This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…655.9413843%2fD%3dMKP1%2fB%3d4995368"></noscript><hr size=1 noshade><a href="The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3130, Column 372:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dMKP1%2fB%3d4995368"></noscript><hr size=1 noshade><a href="http://us.aMost 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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3130, Column 391:
"NOSHADE" is not a member of a group specified for any attribute.…995368"></noscript><hr size=1 noshade><a href="http://us.ard.yahoo.com/SIG=12…w.sharebuilder.com/affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2FwelcomeAn 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 "&" (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 æ 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.
Line 3130, Column 633:
general entity "SID" not defined and no default entity.…w.sharebuilder.com/affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2FwelcomeThis 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.
Line 3130, Column 636:
reference to entity "SID" for which no system identifier could be generated.…harebuilder.com/affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2FThis 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.
Line 3130, Column 632:
entity was defined here.…ww.sharebuilder.com/affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcom…ffiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2F25offer%2Findex.hAn 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 "&" (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 æ 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.
Line 3130, Column 653:
general entity "MGDURL" not defined and no default entity.…ffiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2F25offer%2Findex.hThis 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.
Line 3130, Column 659:
reference to entity "MGDURL" for which no system identifier could be generated.…tes/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2F25offer%2Findex.htm&cm_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.
Line 3130, Column 652:
entity was defined here.…affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2F25offer%2Findex.…=Web%2Fwelcome%2F25offer%2Findex.htm&cm_mmc=WebPortal-_-YHOO-_-CPM-_-TXTHP">BAn 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 "&" (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 æ 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.
Line 3130, Column 696:
general entity "cm_mmc" not defined and no default entity.…=Web%2Fwelcome%2F25offer%2Findex.htm&cm_mmc=WebPortal-_-YHOO-_-CPM-_-TXTHP">BThis 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.
Line 3130, Column 702:
reference to entity "cm_mmc" for which no system identifier could be generated.…Fwelcome%2F25offer%2Findex.htm&cm_mmc=WebPortal-_-YHOO-_-CPM-_-TXTHP">Buy stoThis 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.
Line 3130, Column 695:
entity was defined here.…L=Web%2Fwelcome%2F25offer%2Findex.htm&cm_mmc=WebPortal-_-YHOO-_-CPM-_-TXTHP">…harebuilder.com/affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2FThis 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.
Line 3130, Column 632:
entity was defined here.…ww.sharebuilder.com/affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcom…tes/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2F25offer%2Findex.htm&cm_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.
Line 3130, Column 652:
entity was defined here.…affiliates/?PC=sb&SID=480035263015003&MGDURL=Web%2Fwelcome%2F25offer%2Findex.…Fwelcome%2F25offer%2Findex.htm&cm_mmc=WebPortal-_-YHOO-_-CPM-_-TXTHP">Start iThis 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.
Line 3130, Column 695:
entity was defined here.…L=Web%2Fwelcome%2F25offer%2Findex.htm&cm_mmc=WebPortal-_-YHOO-_-CPM-_-TXTHP">…today</a>.<script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3133, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142abrm5s%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…499%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13b1oime5%2fN%3dZGzcUtGDJGM-%2fC%3d6159This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…271.9413843%2fD%3dMKP1%2fB%3d4936625"></noscript><hr size=1 noshade><a href="The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3133, Column 373:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dMKP1%2fB%3d4936625"></noscript><hr size=1 noshade><a href="http://us.aMost 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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3133, Column 392:
"NOSHADE" is not a member of a group specified for any attribute.…936625"></noscript><hr size=1 noshade><a href="http://us.ard.yahoo.com/SIG=12…erica</a>.<script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3136, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142bcf3cq%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…774%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13b990f9g%2fN%3dZWzcUtGDJGM-%2fC%3d5768This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…297.9413843%2fD%3dMKP1%2fB%3d4987139"></noscript>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3136, Column 373:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dMKP1%2fB%3d4987139"></noscript>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3138, Column 27:
required attribute "TYPE" not specified.<script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3141, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=1425288cr%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…798%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=128ch22on%2fN%3dZmzcUtGDJGM-%2fC%3d-2%2This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…tGDJGM-%2fC%3d-2%2fD%3dMKP4%2fB%3d-2"></noscript></div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3141, Column 338:
end tag for "NOSCRIPT" which is not finished.…%3d-2%2fD%3dMKP4%2fB%3d-2"></noscript></div>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3217, Column 7:
required attribute "TYPE" not specified.<script>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>.
Line 3232, Column 110:
end tag for element "A" which is not open.…EIGHT=200 BORDER=0 alt="'+text+'"></A>';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.
Line 3238, Column 144:
character "\" not allowed in end tag.…sh.ShockwaveFlash."&nfv)))\n\</script\>\n');…ign=center><font face=verdana size=-2><b><a href="'+red+'R=3/id=txt/*'+tred+'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:
Line 3250, Column 184:
there is no attribute "TARGET".…d+'R=2/id=survey/*'+survey+'" target="_blank">Ad Feedback</a></font></td></trYou 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.
Line 3251, Column 8:
end tag for element "SCRIPT" which is not open.</script><script language=javascript>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.
Line 3251, Column 36:
required attribute "TYPE" not specified.</script><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3254, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142ema5ih%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…031%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bnconph%2fN%3dZ2zcUtGDJGM-%2fC%3d5845This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…568.7674020%2fD%3dFPAD%2fB%3d4987841"></noscript></div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3254, Column 373:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dFPAD%2fB%3d4987841"></noscript></div>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3262, Column 6:
required attribute "TYPE" not specified.<style>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>.
Line 3262, Column 6:
document type does not allow element "STYLE" here.<style>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).
Line 3278, Column 33:
required attribute "TYPE" not specified.</div><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3281, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142svm87h%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…320%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13c6eeb62%2fN%3daGzcUtGDJGM-%2fC%3d3888This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…33.10360830%2fD%3dMNTL%2fB%3d4958782"></noscript></div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3281, Column 374:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dMNTL%2fB%3d4958782"></noscript></div>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3283, Column 23:
document type does not allow element "STYLE" here. <style type="text/css">#pulse h3{font:bold 114% arial;text-align:left;color:#55The 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).
Line 3283, Column 705:
NET-enabling start-tag requires SHORTTAG YES.…n's Halloween Costumes </h3><a href=s/717861/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 1160:
end tag for element "A" which is not open.…stumes " width="139" height="119"></a><ol><li class="tt1"><a href=s/717924/*-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.
Line 3283, Column 1190:
NET-enabling start-tag requires SHORTTAG YES.…19"></a><ol><li class="tt1"><a href=s/717924/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 1508:
end tag for element "A" which is not open.…uIENvc3R1bWVz> Supergirl Costumes </a></li><li class="tt2"><a href=s/717863/*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.
Line 3283, Column 1539:
NET-enabling start-tag requires SHORTTAG YES.…es </a></li><li class="tt2"><a href=s/717863/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 1828:
end tag for element "A" which is not open.…Vz?keyword=adult> Maiden Costumes </a></li><li class="tt3"><a href=s/717864/*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.
Line 3283, Column 1859:
NET-enabling start-tag requires SHORTTAG YES.…es </a></li><li class="tt3"><a href=s/717864/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 2179:
end tag for element "A" which is not open.…rden+-child+-cute> Fairy Costumes </a></li><li class="tt4"><a href=s/717865/*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.
Line 3283, Column 2210:
NET-enabling start-tag requires SHORTTAG YES.…es </a></li><li class="tt4"><a href=s/717865/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 2667:
end tag for element "A" which is not open.…+-toddler> Princess Leia Costumes </a></li><li class="tt5"><a href=s/717866/*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.
Line 3283, Column 2698:
NET-enabling start-tag requires SHORTTAG YES.…es </a></li><li class="tt5"><a href=s/717866/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 3001:
end tag for element "A" which is not open.…rd=-child+adult> Dorothy Costumes </a></li><li class="tt6"><a href=s/717867/*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.
Line 3283, Column 3032:
NET-enabling start-tag requires SHORTTAG YES.…es </a></li><li class="tt6"><a href=s/717867/*-http://shopping.yahoo.com/s:CoThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 3321:
end tag for element "A" which is not open.…Vz?keyword=adult> Pirate Costumes </a></li></ol></div><a class=btn-more href=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.
Line 3283, Column 3362:
NET-enabling start-tag requires SHORTTAG YES.…i></ol></div><a class=btn-more href=s/717868/*-http://shopping.yahoo.com/b:HaThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 3283, Column 3632:
end tag for element "A" which is not open.…N0dW1lcw-->» More Halloween </a></div> <div id="popsearch" class="md">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.
Line 3287, Column 94:
cannot generate system identifier for general entity "cs".…oo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California WAn 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 "&" (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 æ 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.
Line 3287, Column 94:
general entity "cs" not defined and no default entity.…oo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California WThis 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.
Line 3287, Column 96:
reference to entity "cs" for which no system identifier could be generated.….com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California WilThis 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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California WildfirAn 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 "&" (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 æ 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.
Line 3287, Column 100:
general entity "sado" not defined and no default entity.…/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California WildfirThis 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.
Line 3287, Column 104:
reference to entity "sado" for which no system identifier could be generated.…rch?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a><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 "&" (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 æ 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.
Line 3287, Column 107:
general entity "fr" not defined and no default entity.…?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a><This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3287, Column 109:
reference to entity "fr" for which no system identifier could be generated.…=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a></…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…h.yahoo.com/search?p=Gabriel+Aubry&cs=bz&sado=1&fr=fp-buzzmod">Gabriel Aubry<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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …com/search?p=Gabriel+Aubry&cs=bz&sado=1&fr=fp-buzzmod">Gabriel Aubry</a></li>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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…earch?p=Gabriel+Aubry&cs=bz&sado=1&fr=fp-buzzmod">Gabriel Aubry</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…search.yahoo.com/search?p=Bullying&cs=bz&sado=1&fr=fp-buzzmod">Bullying</a></This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …ahoo.com/search?p=Bullying&cs=bz&sado=1&fr=fp-buzzmod">Bullying</a></li>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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…com/search?p=Bullying&cs=bz&sado=1&fr=fp-buzzmod">Bullying</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…://search.yahoo.com/search?p=Rambo&cs=bz&sado=1&fr=fp-buzzmod">Rambo</a></li>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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …h.yahoo.com/search?p=Rambo&cs=bz&sado=1&fr=fp-buzzmod">Rambo</a></li>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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…oo.com/search?p=Rambo&cs=bz&sado=1&fr=fp-buzzmod">Rambo</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>….yahoo.com/search?p=Curt+Schilling&cs=bz&sado=1&fr=fp-buzzmod">Curt SchillingThis 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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …om/search?p=Curt+Schilling&cs=bz&sado=1&fr=fp-buzzmod">Curt Schilling</a></…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…arch?p=Curt+Schilling&cs=bz&sado=1&fr=fp-buzzmod">Curt Schilling</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…yahoo.com/search?p=Charlize+Theron&cs=bz&sado=1&fr=fp-buzzmod">Charlize TheroThis 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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …m/search?p=Charlize+Theron&cs=bz&sado=1&fr=fp-buzzmod">Charlize Theron</a></…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…rch?p=Charlize+Theron&cs=bz&sado=1&fr=fp-buzzmod">Charlize Theron</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…rch.yahoo.com/search?p=Joey+Logano&cs=bz&sado=1&fr=fp-buzzmod">Joey Logano</aThis 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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …o.com/search?p=Joey+Logano&cs=bz&sado=1&fr=fp-buzzmod">Joey Logano</a></li>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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…/search?p=Joey+Logano&cs=bz&sado=1&fr=fp-buzzmod">Joey Logano</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…ch.yahoo.com/search?p=Holiday+Jobs&cs=bz&sado=1&fr=fp-buzzmod">Holiday Jobs</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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California ….com/search?p=Holiday+Jobs&cs=bz&sado=1&fr=fp-buzzmod">Holiday Jobs</a></li>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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…search?p=Holiday+Jobs&cs=bz&sado=1&fr=fp-buzzmod">Holiday Jobs</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…o.com/search?p=Sugar+Cookie+Recipe&cs=bz&sado=1&fr=fp-buzzmod">Sugar Cookie RThis 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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California …arch?p=Sugar+Cookie+Recipe&cs=bz&sado=1&fr=fp-buzzmod">Sugar Cookie Recipe</aThis 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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…p=Sugar+Cookie+Recipe&cs=bz&sado=1&fr=fp-buzzmod">Sugar Cookie Recipe</a></…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a>…ch.yahoo.com/search?p=James+Taylor&cs=bz&sado=1&fr=fp-buzzmod">James Taylor</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.
Line 3287, Column 93:
entity was defined here.…hoo.com/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California ….com/search?p=James+Taylor&cs=bz&sado=1&fr=fp-buzzmod">James Taylor</a></li>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.
Line 3287, Column 99:
entity was defined here.…m/search?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfi…search?p=James+Taylor&cs=bz&sado=1&fr=fp-buzzmod">James Taylor</a></li>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.
Line 3287, Column 106:
entity was defined here.…h?p=California+Wildfires&cs=bz&sado=1&fr=fp-buzzmod">California Wildfires</a></div>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 3341, Column 27:
required attribute "TYPE" not specified.<script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3344, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142j8u8gj%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…364%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=127frmc3o%2fN%3dbGzcUtGDJGM-%2fC%3d-1%2This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…UtGDJGM-%2fC%3d-1%2fD%3dSIP%2fB%3d-1"></noscript><script language=javascript>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3344, Column 337:
end tag for "NOSCRIPT" which is not finished.…C%3d-1%2fD%3dSIP%2fB%3d-1"></noscript><script language=javascript>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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3344, Column 365:
required attribute "TYPE" not specified.…/noscript><script language=javascript>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 3347, Column 122:
reference to entity "T" for which no system identifier could be generated.…ES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=142vfolsi%2fX%3d1193669459%2fE%3d271614This 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.
Line 2636, Column 120:
entity was defined here.…hhES0zpKO_cf_RvwJeCZfRyEEfkcl81MACCnl&T=141bn7bbs%2fX%3d1193669459%2fE%3d2716…905%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=139gs4fc6%2fN%3daWzcUtGDJGM-%2fC%3d2240This 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.
Line 2636, Column 265:
entity was defined here.…79934%2fQ%3d-1%2fS%3d1%2fJ%3d92CEB444&U=13bhme6iu%2fN%3dTGzcUtGDJGM-%2fC%3d38…622.2012076%2fD%3dFOOT%2fB%3d1088125"></noscript><noscript><img src="r/dw" stThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3347, Column 371:
end tag for "NOSCRIPT" which is not finished.…%2fD%3dFOOT%2fB%3d1088125"></noscript><noscript><img src="r/dw" style="positiMost 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 (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3347, Column 464:
required attribute "ALT" not specified.…:-2000px;top:0;" height="1" width="1"></noscript>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>.
Line 3347, Column 464:
document type does not allow element "IMG" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "DIV", "ADDRESS" start-tag.…:-2000px;top:0;" height="1" width="1"></noscript>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 3347, Column 475:
end tag for "NOSCRIPT" which is not finished.…p:0;" height="1" width="1"></noscript>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 3525, Column 151:
end tag for element "A" which is not open.…result" class="vs_answers">Answers</a></li><li><a href="r/aw/*-http://audio.sThe 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.
Line 3525, Column 156:
end tag for element "LI" which is not open.…t" class="vs_answers">Answers</a></li><li><a href="r/aw/*-http://audio.searchThe 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.
Line 3525, Column 246:
end tag for element "A" which is not open.…arch/audio" class="vs_audio">Audio</a></li><li><a href="r/b0/*-http://search.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.
Line 3525, Column 251:
end tag for element "LI" which is not open.…audio" class="vs_audio">Audio</a></li><li><a href="r/b0/*-http://search.yahooThe 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.
Line 3525, Column 341:
end tag for element "A" which is not open.…ir" class="vs_directory">Directory</a></li><li><a href="r/b4/*-http://hotjobsThe 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.
Line 3525, Column 346:
end tag for element "LI" which is not open.…lass="vs_directory">Directory</a></li><li><a href="r/b4/*-http://hotjobs.yahoThe 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.
Line 3525, Column 456:
end tag for element "A" which is not open.…results.html" class="vs_jobs">Jobs</a></li><li><a href="r/b1/*-http://news.seThe 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.
Line 3525, Column 461:
end tag for element "LI" which is not open.…ts.html" class="vs_jobs">Jobs</a></li><li><a href="r/b1/*-http://news.search.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.
Line 3525, Column 547:
end tag for element "A" which is not open.…/search/news" class="vs_news">News</a></li><li class="last"><a href="r/cq">AlThe 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.
Line 3525, Column 552:
end tag for element "LI" which is not open.…ch/news" class="vs_news">News</a></li><li class="last"><a href="r/cq">All SeaThe 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.
Line 3525, Column 607:
end tag for element "A" which is not open.…<a href="r/cq">All Search Services</a></li></ul><span></span><ul class="vslisThe 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.
Line 3525, Column 612:
end tag for element "LI" which is not open.…ef="r/cq">All Search Services</a></li></ul><span></span><ul class="vslist"><lThe 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.
Line 3525, Column 617:
end tag for element "UL" which is not open.…/cq">All Search Services</a></li></ul><span></span><ul class="vslist"><li claThe 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.
Line 3525, Column 630:
end tag for element "SPAN" which is not open.…ch Services</a></li></ul><span></span><ul class="vslist"><li class="first"><aThe 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.
Line 3525, Column 706:
end tag for element "A" which is not open.…a href="r/bt">Advertising Programs</a></li></ul></div>';The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 3525, Column 711:
end tag for element "LI" which is not open.…f="r/bt">Advertising Programs</a></li></ul></div>';The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 3525, Column 716:
end tag for element "UL" which is not open.…bt">Advertising Programs</a></li></ul></div>';The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 3525, Column 722:
end tag for element "DIV" which is not open.…vertising Programs</a></li></ul></div>';The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 3526, Column 157:
end tag for element "SPAN" which is not open.…<span>Businesses & Services</span></label><label for="scsz" class="cszlabThe 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.
Line 3526, Column 165:
end tag for element "LABEL" which is not open.…sinesses & Services</span></label><label for="scsz" class="cszlabel1">in<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.
Line 3526, Column 211:
end tag for element "LABEL" which is not open.…or="scsz" class="cszlabel1">in</label><label for="scsz" class="cszlabel2"><inThe 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.
Line 3526, Column 346:
end tag for element "SPAN" which is not open.…an>Address, City, State, or Zip</span></label>';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.
Line 3526, Column 354:
end tag for element "LABEL" which is not open.…ss, City, State, or Zip</span></label>';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.
Line 3530, Column 43:
end tag for element "A" which is not open.… "go to <a href='r/lm'>Yahoo! Mail</a> to get your mail.</li><li class='last'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.
Line 3530, Column 66:
end tag for element "LI" which is not open.…Yahoo! Mail</a> to get your mail.</li><li class='last'><a href='r/ll'>» 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.
Line 3539, Column 48:
end tag for element "A" which is not open.…to <a href='r/p4'>Yahoo! Messenger</a> to see your online contacts.</li><li cThe 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.
Line 3539, Column 82:
end tag for element "LI" which is not open.…</a> to see your online contacts.</li><li class='last'><a href='ymsgr:SendIM'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.
Line 3548, Column 46:
end tag for element "A" which is not open.…o to <a href='r/wf'>Yahoo! Weather</a> to get the local weather.</li><li clasThe 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.
Line 3548, Column 77:
end tag for element "LI" which is not open.…her</a> to get the local weather.</li><li class='last'><a href='r/wf'>» 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.
Line 3556, Column 44:
end tag for element "A" which is not open.…"go to <a href='r/kf'>Yahoo! Local</a> to get the local traffic.</li><li clasThe 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.
Line 3556, Column 75:
end tag for element "LI" which is not open.…cal</a> to get the local traffic.</li><li class='last'><a href='r/kf'>» 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.
Line 3564, Column 44:
end tag for element "A" which is not open.…"go to <a href='r/kf'>Yahoo! Local</a> to get the local events.</li><li classThe 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.
Line 3564, Column 74:
end tag for element "LI" which is not open.…ocal</a> to get the local events.</li><li class='last'><a href='r/kf'>» 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.
Line 3572, Column 47:
end tag for element "A" which is not open.…3><a href='r/uc'>LAUNCHcast Radio:</a> <em><a href='r/ud'>Featured stations</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.
Line 3572, Column 88:
end tag for element "A" which is not open.…m><a href='r/ud'>Featured stations</a></em></h3><div class='station'><div claThe 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.
Line 3572, Column 93:
end tag for element "EM" which is not open.…href='r/ud'>Featured stations</a></em></h3><div class='station'><div class='sThe 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.
Line 3572, Column 98:
end tag for element "H3" which is not open.…'r/ud'>Featured stations</a></em></h3><div class='station'><div class='statioThe 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.
Line 3572, Column 149:
end tag for element "DIV" which is not open.…tation'><div class='station-hd'></div><div class='station-bd' class='fixfloatThe 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.
Line 3572, Column 397:
end tag for element "A" which is not open.…hoo.com/000/025/969/25969265.jpg'></a><h4><a class='station-name' href='r/ut/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.
Line 3572, Column 520:
end tag for element "A" which is not open.…tation.asp?i=341'>Today's Big Hits</a></h4><p class='artists'><a href='r/ut/*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.
Line 3572, Column 525:
end tag for element "H4" which is not open.…n.asp?i=341'>Today's Big Hits</a></h4><p class='artists'><a href='r/ut/*-httpThe 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.
Line 3572, Column 675:
end tag for element "A" which is not open.…Kelly Clarkson, Sean Paul, Beyonce</a></p><a class='listen' href='r/ul/*-httpThe 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.
Line 3572, Column 679:
end tag for element "P" which is not open.…y Clarkson, Sean Paul, Beyonce</a></p><a class='listen' href='r/ul/*-http://mThe 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.
Line 3572, Column 976:
end tag for element "A" which is not open.…341&rp2=0');return false;\">Listen</a></div><div class='station-ft'></div></dThe 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.
Line 3572, Column 982:
end tag for element "DIV" which is not open.…2=0');return false;\">Listen</a></div><div class='station-ft'></div></div><a 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.
Line 3572, Column 1012:
end tag for element "DIV" which is not open.…a></div><div class='station-ft'></div></div><a class='btn-more' href='r/ua'>&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.
Line 3572, Column 1018:
end tag for element "DIV" which is not open.…v><div class='station-ft'></div></div><a class='btn-more' href='r/ua'>» 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.
Line 3572, Column 1078:
end tag for element "A" which is not open.…ef='r/ua'>» View All Stations</a><div class='nav'><a class='back' onclicThe 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.
Line 3572, Column 1221:
end tag for element "A" which is not open.…urr_stn:1})\" href='r/um'>Previous</a><a class='frwd' onclick=\"return YAHOO.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.
Line 3572, Column 1342:
end tag for element "A" which is not open.…t',curr_stn:1})\" href='r/um'>Next</a></div>",The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.