Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 1, Column 204:
document type does not allow element "NOSCRIPT" here
…"text/html; charset=UTF-8"><noscript> <img src="mail?cmd=cookie.setnonjs&.ranThe 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 1, Column 258:
cannot generate system identifier for general entity "mcrumb"
…md=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1">An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (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 1, Column 258:
general entity "mcrumb" not defined and no default entity
…md=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1">This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 1, Column 264:
reference to entity "mcrumb" for which no system identifier could be generated
…kie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1"><META 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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…mb=x5JBU0JDwpA" height="1" width="1"><META HTTP-EQUIV=Refresh CONTENT="0; URLThe 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 2, Column 1288:
document type does not allow element "NOSCRIPT" here
…le.start('RT_TP');</script><noscript><style type="text/css">* { visibility: hThe 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 2, Column 1422:
cannot generate system identifier for general entity "c"
…mail?cmd=css.check&.rand=1562226557&c=x5JBU0JDwpA" type="text/css" media="allAn 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 2, Column 1422:
general entity "c" not defined and no default entity
…mail?cmd=css.check&.rand=1562226557&c=x5JBU0JDwpA" type="text/css" media="allThis 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 2, Column 1423:
reference to entity "c" for which no system identifier could be generated
…ail?cmd=css.check&.rand=1562226557&c=x5JBU0JDwpA" type="text/css" media="all"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 2, Column 1420:
entity was defined here
…="mail?cmd=css.check&.rand=1562226557&c=x5JBU0JDwpA" type="text/css" media="a…1/aro_eb.gif" style="display:none;" ><img src="http://mail.yimg.com/a/i/us/piThe 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 2, Column 1558:
document type does not allow element "IMG" here
…1/aro_eb.gif" style="display:none;" ><img src="http://mail.yimg.com/a/i/us/piThe 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 2, Column 1640:
required attribute "ALT" not specified
…strip_22.png" style="display:none;" ><script type='text/javascript'>gLaunchPrThe 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 2, Column 1640:
document type does not allow element "IMG" here
…strip_22.png" style="display:none;" ><script type='text/javascript'>gLaunchPrThe 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 2, Column 3213:
cannot generate system identifier for general entity "bc"
…s/yui_utils.js&/mg/6_1_1/js/core.js&bc/bc_2.0.4.js&/mg/6_1_1/js/darla.js&/uh/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 2, Column 3213:
general entity "bc" not defined and no default entity
…s/yui_utils.js&/mg/6_1_1/js/core.js&bc/bc_2.0.4.js&/mg/6_1_1/js/darla.js&/uh/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 2, Column 3215:
reference to entity "bc" for which no system identifier could be generated
…yui_utils.js&/mg/6_1_1/js/core.js&bc/bc_2.0.4.js&/mg/6_1_1/js/darla.js&/uh/15This 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 2, Column 3211:
entity was defined here
…/js/yui_utils.js&/mg/6_1_1/js/core.js&bc/bc_2.0.4.js&/mg/6_1_1/js/darla.js&/u…rla.js&/uh/15/js/uh_mail-1.0.11.js&"></script><script type="text/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 7, Column 230:
Attribute "HSPACE" is not a valid attribute. Did you mean "hspace"?
…inwidth="0" marginheight="0" hspace="0" vspace="0" allowTransparency="true" tYou 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 7, Column 241:
Attribute "VSPACE" is not a valid attribute. Did you mean "vspace"?
… marginheight="0" hspace="0" vspace="0" allowTransparency="true" title=""></iYou 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 7, Column 263:
Attribute "ALLOWTRANSPARENCY" is not a valid attribute
…ce="0" vspace="0" allowTransparency="true" title=""></iframe><div id="networkYou 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 7, Column 317:
Attribute "ROLE" is not a valid attribute. Did you mean "frameborder" or "scrolling"?
…iframe><div id="networkHeader" role="banner"><div id="HEAD"><style type="textYou 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 7, Column 363:
document type does not allow element "STYLE" here
…div id="HEAD"><style type="text/css">/*Fix for IE5*/#ygmabt #ygmabt-search{ _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 7, Column 3871:
end tag for element "SPAN" which is not open
…id + "'>" + h.shortaliasid + "</span>",title:h.aliasid,className:"last-child"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 7, Column 7243:
duplicate specification of attribute "CHARSET"
…="" type="text/javascript" charset="utf-8">(function(){var A=document.getEle
You have specified an attribute more than once. Example: Using
the "height" attribute twice on the same
"img" tag.
Line 7, Column 7250:
document type does not allow element "SCRIPT" here; assuming missing "LI" start-tag
…pe="text/javascript" charset="utf-8">(function(){var A=document.getElementByI… class="ygmabt-search-wrapper" role="application"><input type="text" class="sYou 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 7, Column 10974:
start tag for "LEGEND" omitted, but its declaration does not permit this
…t-search-wrapper" role="application"><input type="text" class="sp ygmabtnorma…ld';}" maxlength="100" autocomplete="off" /><input type="hidden" id="fr" nameYou 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 7, Column 11315:
NET-enabling start-tag requires SHORTTAG YES
… maxlength="100" autocomplete="off" /><input type="hidden" id="fr" name="fr" The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 7, Column 11373:
NET-enabling start-tag requires SHORTTAG YES
… id="fr" name="fr" value="ush-mail" /><div id="sat"></div></span><span class=The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 7, Column 11388:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…fr" value="ush-mail" /><div id="sat"></div></span><span class="ygmabt-search-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 7, Column 11617:
end tag for "LEGEND" omitted, but its declaration does not permit this
…tton></span></span></span></fieldset></form></div></div></div></div></div><sc
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 7, Column 10919:
start tag was here
…thod="GET" target="_blank"><fieldset><span class="ygmabt-search-wrapper" role…ript charset="" 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 10, Column 122:
cannot generate system identifier for general entity "T"
…dG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d398301An 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 10, Column 122:
general entity "T" not defined and no default entity
…dG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d398301This 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 10, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d6500An 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 10, Column 265:
general entity "U" not defined and no default entity
…826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d6500This 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 10, Column 266:
reference to entity "U" for which no system identifier could be generated
…26%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65000This 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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…ript charset="" 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 13, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vdq3r8j%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…63%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13hnrd2v7%2fN%3danukCtG_fzw-%2fC%3d65000This 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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65… title="Advertisement" onload="parent.gLaunchProfile.stop('RT_AD_N', 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 20, Column 35:
Attribute "ROLE" is not a valid attribute. Did you mean "frameborder" or "scrolling"?
<ul id="pimtabs" role="navigation">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 32, Column 21:
Attribute "URL" is not a valid attribute. Did you mean "clear" or "onmouseover"?
url="options?mailop=1&noFlush&.rand=668838503">Mail Options</optYou 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 32, Column 39:
cannot generate system identifier for general entity "noFlush"
url="options?mailop=1&noFlush&.rand=668838503">Mail Options</optAn 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 32, Column 39:
general entity "noFlush" not defined and no default entity
url="options?mailop=1&noFlush&.rand=668838503">Mail Options</optThis 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 32, Column 46:
reference to entity "noFlush" for which no system identifier could be generated
… url="options?mailop=1&noFlush&.rand=668838503">Mail Options</option><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 32, Column 37:
entity was defined here
url="options?mailop=1&noFlush&.rand=668838503">Mail Options</opt… title="Select one of the options from dropdown" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 38, Column 52:
document type does not allow element "SCRIPT" here; assuming missing "LI" start-tag
… </li><script type="text/javascript">YAHOO.mc.optionsMenu = new Menu("mOption…den" id="crumb" value="x5JBU0JDwpA" /></div><script type="text/javascript">gLThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 38, Column 821:
cannot generate system identifier for general entity "order"
…AzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><pAn 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 38, Column 821:
general entity "order" not defined and no default entity
…AzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><pThis 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 38, Column 826:
reference to entity "order" for which no system identifier could be generated
…hYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><inpThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…GtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input tyAn 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 38, Column 832:
general entity "pSize" not defined and no default entity
…GtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input tyThis 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 38, Column 837:
reference to entity "pSize" for which no system identifier could be generated
…ls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sThis 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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input ….rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="submiAn 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 38, Column 841:
general entity "tt" not defined and no default entity
….rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="submiThis 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 38, Column 843:
reference to entity "tt" for which no system identifier could be generated
…and=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="submit"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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…ck for new mail" value="Check Mail" /><input type="hidden" name=".rand" valueThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 38, Column 1033:
NET-enabling start-tag requires SHORTTAG YES
…den" name=".rand" value="668838503" /></p></form><form action="compose?&.randThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 38, Column 1215:
NET-enabling start-tag requires SHORTTAG YES
…pose a new message" value="Compose" /><input type="hidden" name=".rand" valueThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 38, Column 1269:
NET-enabling start-tag requires SHORTTAG YES
…den" name=".rand" value="668838503" /></p></form></div><div id="searchtestfieThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 39, Column 215:
Attribute "ROLE" is not a valid attribute. Did you mean "frameborder" or "scrolling"?
…3" method="post" target="_top" role="search">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 43, Column 42:
NET-enabling start-tag requires SHORTTAG YES
id="msqtop" value="" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 46, Column 41:
NET-enabling start-tag requires SHORTTAG YES
title="Search Mail" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 53, Column 41:
NET-enabling start-tag requires SHORTTAG YES
id="wsqtop" value=""/></noscript>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 54, Column 61:
NET-enabling start-tag requires SHORTTAG YES
… <input type="hidden" name="fr" value="ush_mailm"/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 55, Column 57:
NET-enabling start-tag requires SHORTTAG YES
<input type="hidden" name="ei" value="UTF-8"/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 57, Column 40:
NET-enabling start-tag requires SHORTTAG YES
title="Search the Web" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 58, Column 16:
end tag for element "P" which is not open
</p> 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 62, Column 22:
required attribute "TYPE" not specified
</div><script>YAHOO.util.Event.on(["searchTheWebtop", "searchTheWebbottoThe 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 62, Column 323:
required attribute "TYPE" not specified
…d="navigation" class="yui-b"><script>if (!asyncMode) {YAHOO.util.Event.on("leThe 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 67, Column 212:
end tag for "SPAN" omitted, but its declaration does not permit this
…reen"> a new folder</span></a>]</div><script type="text/javascript">YAHOO.uti
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 67, Column 55:
start tag was here
…lders</h2><div style="float:right;">[<span id="addfoldercontrol"><a href="fol…><a href="showFolder?fid=Inbox&order=down&tt=3&pSize=25&.rand=668838503" ><emThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…="showFolder?fid=Inbox&order=down&tt=3&pSize=25&.rand=668838503" ><em>Inbox <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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…lder?fid=Inbox&order=down&tt=3&pSize=25&.rand=668838503" ><em>Inbox <b>(2)</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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input …><a href="showFolder?fid=Draft&order=down&tt=0&pSize=25&.rand=668838503" >DraThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…="showFolder?fid=Draft&order=down&tt=0&pSize=25&.rand=668838503" >Drafts</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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…lder?fid=Draft&order=down&tt=0&pSize=25&.rand=668838503" >Drafts</a></li><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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input … ><a href="showFolder?fid=Sent&order=down&tt=0&pSize=25&.rand=668838503" >SenThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…f="showFolder?fid=Sent&order=down&tt=0&pSize=25&.rand=668838503" >Sent</a></lThis 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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…older?fid=Sent&order=down&tt=0&pSize=25&.rand=668838503" >Sent</a></li><li idThis 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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input …showFolder?fid=%2540B%2540Bulk&order=down&tt=0&pSize=25&.rand=668838503" claThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…er?fid=%2540B%2540Bulk&order=down&tt=0&pSize=25&.rand=668838503" class="firsThis 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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…2540B%2540Bulk&order=down&tt=0&pSize=25&.rand=668838503" class="first">Spam<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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input …ref="showFolder?fid=%2540B%2540Bulk&cmd=fmgt.emptybulk&mcrumb=x5JBU0JDwpA&.raAn 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 67, Column 991:
general entity "cmd" not defined and no default entity
…ref="showFolder?fid=%2540B%2540Bulk&cmd=fmgt.emptybulk&mcrumb=x5JBU0JDwpA&.raThis 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 67, Column 994:
reference to entity "cmd" for which no system identifier could be generated
…="showFolder?fid=%2540B%2540Bulk&cmd=fmgt.emptybulk&mcrumb=x5JBU0JDwpA&.rand=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 67, Column 989:
entity was defined here
… href="showFolder?fid=%2540B%2540Bulk&cmd=fmgt.emptybulk&mcrumb=x5JBU0JDwpA&.…B%2540Bulk&cmd=fmgt.emptybulk&mcrumb=x5JBU0JDwpA&.rand=668838503"title="EmptyThis 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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…><a href="showFolder?fid=Trash&order=down&tt=0&pSize=25&.rand=668838503" claThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…="showFolder?fid=Trash&order=down&tt=0&pSize=25&.rand=668838503" class="firsThis 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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…lder?fid=Trash&order=down&tt=0&pSize=25&.rand=668838503" class="first">TrashThis 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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input …rash" href="showFolder?fid=Trash&cmd=fmgt.emptytrash&mcrumb=x5JBU0JDwpA&.randThis 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 67, Column 989:
entity was defined here
… href="showFolder?fid=%2540B%2540Bulk&cmd=fmgt.emptybulk&mcrumb=x5JBU0JDwpA&.…fid=Trash&cmd=fmgt.emptytrash&mcrumb=x5JBU0JDwpA&.rand=668838503"title="EmptyThis 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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…DMwMTAzNARhYwNzcmNoUGh0?show=photos&extraargs=%26.rand%3D668838503"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 72, Column 130:
general entity "extraargs" not defined and no default entity
…DMwMTAzNARhYwNzcmNoUGh0?show=photos&extraargs=%26.rand%3D668838503"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 72, Column 139:
reference to entity "extraargs" for which no system identifier could be generated
…RhYwNzcmNoUGh0?show=photos&extraargs=%26.rand%3D668838503"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 72, Column 128:
entity was defined here
…5ODMwMTAzNARhYwNzcmNoUGh0?show=photos&extraargs=%26.rand%3D668838503"…zcmNoQXR0?show=attachments&extraargs=%26.rand%3D668838503"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 72, Column 128:
entity was defined here
…5ODMwMTAzNARhYwNzcmNoUGh0?show=photos&extraargs=%26.rand%3D668838503" <ol><li><nobr><strong><a href="showFolder?fid=Inbox&.rand=668838You 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 85, Column 82:
required attribute "TYPE" not specified
…v id="MWA1"> </div></div><style> #yui-main #pageContent { min-width:785pThe 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 85, Column 82:
document type does not allow element "STYLE" here
…v id="MWA1"> </div></div><style> #yui-main #pageContent { min-width:785pThe 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 86, Column 117:
cannot generate system identifier for general entity "nsc"
…ome?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>ToAn 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 86, Column 117:
general entity "nsc" not defined and no default entity
…ome?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>ToThis 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 86, Column 120:
reference to entity "nsc" for which no system identifier could be generated
…?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>Top SThis 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 86, Column 115:
entity was defined here
…lcome?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>…stories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>Top Stories</sThis 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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…38503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>Top Stories</strong></div></a></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 86, Column 263:
reference to entity "nsc" for which no system identifier could be generated
…lcome?news=world&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div>World</div></This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 86, Column 115:
entity was defined here
…lcome?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>…s=world&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div>World</div></a></li><lThis 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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…38503&nsc=1&mcrumb=x5JBU0JDwpA"><div>World</div></a></li><li style="width:115The 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 86, Column 391:
reference to entity "nsc" for which no system identifier could be generated
…ws=entertainment&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div>EntertainmentThis 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 86, Column 115:
entity was defined here
…lcome?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>…ainment&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div>Entertainment</div></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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…38503&nsc=1&mcrumb=x5JBU0JDwpA"><div>Entertainment</div></a></li><li style="wThe 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 86, Column 533:
reference to entity "nsc" for which no system identifier could be generated
…come?news=sports&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div>Sports</div><This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 86, Column 115:
entity was defined here
…lcome?news=topstories&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div><strong>…=sports&.rand=668838503&nsc=1&mcrumb=x5JBU0JDwpA"><div>Sports</div></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 1, Column 256:
entity was defined here
…?cmd=cookie.setnonjs&.rand=1562226557&mcrumb=x5JBU0JDwpA" height="1" width="1…38503&nsc=1&mcrumb=x5JBU0JDwpA"><div>Sports</div></a></li></ul><div id="newscThe 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 88, Column 285:
cannot generate system identifier for general entity "y"
…pt_11_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" aAn 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 88, Column 285:
general entity "y" not defined and no default entity
…pt_11_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" 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 88, Column 286:
reference to entity "y" for which no system identifier could be generated
…t_11_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" alThis 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 88, Column 283:
entity was defined here
…sept_11_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--"…_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align=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 88, Column 290:
general entity "q" not defined and no default entity
…_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align=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 88, Column 291:
reference to entity "q" for which no system identifier could be generated
…anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align="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 88, Column 288:
entity was defined here
…11_anniversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" alig…versary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align="leftAn 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 88, Column 295:
general entity "sig" not defined and no default entity
…versary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align="leftThis 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 88, Column 298:
reference to entity "sig" for which no system identifier could be generated
…sary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align="left" 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 88, Column 293:
entity was defined here
…niversary_whcd112.jpg?x=130&y=86&q=85&sig=JWsTH2WwUJpAZnSKOXKEdQ--" align="le…Photo/Charles Dharapak)" border="0" /></a>AP - On his first 9/11 anniversary The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 88, Column 809:
NET-enabling start-tag requires SHORTTAG YES
… eight years ago.</p><br clear="all"/></p><div><ul> <style>#newsmodule img {wThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 88, Column 814:
end tag for element "P" which is not open
…t years ago.</p><br clear="all"/></p><div><ul> <style>#newsmodule img {width: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 88, Column 831:
required attribute "TYPE" not specified
…br clear="all"/></p><div><ul> <style>#newsmodule img {width:113.37209302326pxThe 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 88, Column 831:
document type does not allow element "STYLE" here
…br clear="all"/></p><div><ul> <style>#newsmodule img {width:113.37209302326pxThe 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 102, Column 137:
required attribute "ALT" not specified
…rc="stampNonJs" height="1" width="1"> </noscript></div></div><div id="lrecad"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 107, Column 399:
reference to entity "order" for which no system identifier could be generated
…hYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><inpThis 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 38, Column 819:
entity was defined here
…MTAzNARhYwNjaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET">…ls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sThis 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 38, Column 830:
entity was defined here
…jaGtNYWls?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input …and=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="submit"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 38, Column 839:
entity was defined here
…?&.rand=668838503&order=down&pSize=25&tt=3" method="GET"><p><input type="sub…ck for new mail" value="Check Mail" /><input type="hidden" name=".rand" valueThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 107, Column 609:
NET-enabling start-tag requires SHORTTAG YES
…den" name=".rand" value="668838503" /></p></form><form action="compose?&.randThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 107, Column 794:
NET-enabling start-tag requires SHORTTAG YES
…pose a new message" value="Compose" /><input type="hidden" name=".rand" valueThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 107, Column 848:
NET-enabling start-tag requires SHORTTAG YES
…den" name=".rand" value="668838503" /></p></form></div><div id="searchtestfieThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 112, Column 45:
NET-enabling start-tag requires SHORTTAG YES
id="msqbottom" value="" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 113, Column 62:
ID "MAILSEARCH" already defined
… <input class="inputbutton" type="submit" id="mailsearch" name="MailSearch"An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 44, Column 61:
ID "MAILSEARCH" first defined here
… <input class="inputbutton" type="submit" id="mailsearch" name="MailSearch" title="Search Mail" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 122, Column 44:
NET-enabling start-tag requires SHORTTAG YES
id="wsqbottom" value=""/></noscript>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 123, Column 61:
NET-enabling start-tag requires SHORTTAG YES
… <input type="hidden" name="fr" value="ush_mailm"/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 124, Column 57:
NET-enabling start-tag requires SHORTTAG YES
<input type="hidden" name="ei" value="UTF-8"/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 126, Column 40:
NET-enabling start-tag requires SHORTTAG YES
title="Search the Web" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 127, Column 16:
end tag for element "P" which is not open
</p> 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 131, Column 129:
document type does not allow element "STYLE" here
…div><noscript><style type="text/css">#yui-main { background-color:#D6DEEC }</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 131, Column 1392:
reference to entity "noFlush" for which no system identifier could be generated
…ions" href="options?mailop=1&noFlush&.rand=668838503"></a><script type="text/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 32, Column 37:
entity was defined here
url="options?mailop=1&noFlush&.rand=668838503">Mail Options</opt…bsp;</div><br> <small><div id="FOOT"><center><small><br>Copyright © 1994The 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 131, Column 2360:
NET-enabling start-tag requires SHORTTAG YES
…Terms of Service</a> - <a href=http://us.ard.yahoo.com/SIG=15onu9r86/M=289534The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 131, Column 2694:
end tag for element "A" which is not open
…target="_top">Copyright/IP Policy</a> - <a href="http://us.ard.yahoo.com/SIG=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 133, Column 55:
cannot generate system identifier for general entity "t"
…ad.yieldmanager.com/pixel?id=117310&t=2" width="1" height="1" /><img width="0An 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 133, Column 55:
general entity "t" not defined and no default entity
…ad.yieldmanager.com/pixel?id=117310&t=2" width="1" height="1" /><img width="0This 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 133, Column 56:
reference to entity "t" for which no system identifier could be generated
…d.yieldmanager.com/pixel?id=117310&t=2" width="1" height="1" /><img width="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 133, Column 53:
entity was defined here
…//ad.yieldmanager.com/pixel?id=117310&t=2" width="1" height="1" /><img width=…id=117310&t=2" width="1" height="1" /><img width="0" height="0" border="0" srThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 133, Column 81:
required attribute "ALT" not specified
…id=117310&t=2" width="1" height="1" /><img width="0" height="0" border="0" srThe 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 133, Column 168:
cannot generate system identifier for general entity "code"
…ad.yieldmanager.com/pixel?adv=23351&code=&t=2"><script charset="" language=jAn 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 133, Column 168:
general entity "code" not defined and no default entity
…ad.yieldmanager.com/pixel?adv=23351&code=&t=2"><script charset="" language=jThis 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 133, Column 172:
reference to entity "code" for which no system identifier could be generated
…ieldmanager.com/pixel?adv=23351&code=&t=2"><script charset="" language=javasThis 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 133, Column 166:
entity was defined here
…//ad.yieldmanager.com/pixel?adv=23351&code=&t=2"><script charset="" language…dmanager.com/pixel?adv=23351&code=&t=2"><script charset="" language=javascriThis 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 133, Column 53:
entity was defined here
…//ad.yieldmanager.com/pixel?id=117310&t=2" width="1" height="1" /><img width=…nager.com/pixel?adv=23351&code=&t=2"><script charset="" 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 133, Column 218:
required attribute "TYPE" not specified
…ript charset="" 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 136, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vt26n3t%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…72%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13fvnnct5%2fN%3daHukCtG_fzw-%2fC%3d28953This 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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…ript charset="" 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 139, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13upp5c89%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…25%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13ft45rr9%2fN%3da3ukCtG_fzw-%2fC%3d62432This 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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…ript charset="" 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 142, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vgjpi3n%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…94%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=12dnnht7m%2fN%3dbXukCtG_fzw-%2fC%3d-1%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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…ript charset="" 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 145, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vslaigc%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…61%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f1toq08%2fN%3dbnukCtG_fzw-%2fC%3d71548This 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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…target='_blank' /><!--STYLE--></head><body style='overflow:hidden;background-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 146, Column 110:
end tag for element "TD" which is not open
…<tr><td valign=top><!--ADHTML--></td></tr></table>" +The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 146, Column 115:
end tag for element "TR" which is not open
…td valign=top><!--ADHTML--></td></tr></table>" +The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 146, Column 123:
end tag for element "TABLE" which is not open
…n=top><!--ADHTML--></td></tr></table>" +The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 147, Column 28:
end tag for "SCRIPT" omitted, but its declaration does not permit this
"</body></html>",templates: {"N":"<html><head><!--ENCODING--
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 145, Column 435:
start tag was here
…d be replaced by the RT code later--><script type="text/javascript">YAHOO["a" "</body></html>",templates: {"N":"<html><head><!--ENCODING--
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 131, Column 1608:
start tag was here
…div id="RS2"> </div><br> <small><div id="FOOT"><center><small><br>Copyri "</body></html>",templates: {"N":"<html><head><!--ENCODING--
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 131, Column 1601:
start tag was here
…</div><div id="RS2"> </div><br> <small><div id="FOOT"><center><small><br "</body></html>",templates: {"N":"<html><head><!--ENCODING--
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 131, Column 1026:
start tag was here
…ile.stop('LD_JS_BP', false);</script><div id="mg_footer"><a accesskey="1" tit "</body></html>",templates: {"N":"<html><head><!--ENCODING--You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 147, Column 60:
document type does not allow element "HTML" here
…body></html>",templates: {"N":"<html><head><!--ENCODING--><base target='_blanThe 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 147, Column 104:
NET-enabling start-tag requires SHORTTAG YES
…!--ENCODING--><base target='_blank' /><!--STYLE--></head><body style='overfloThe sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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 147, Column 105:
character data is not allowed here
…--ENCODING--><base target='_blank' /><!--STYLE--></head><body style='overflowYou have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 147, Column 124:
end tag for "HEAD" which is not finished
…target='_blank' /><!--STYLE--></head><body style='overflow: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 149, Column 40:
character data is not allowed here
"</body></html>"You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 151, Column 278:
end tag for element "SCRIPT" which is not open
…tyle.display = "none";}})();</script><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 151, Column 286:
required attribute "TYPE" not specified
…play = "none";}})();</script><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 151, Column 286:
document type does not allow element "SCRIPT" here
…play = "none";}})();</script><script>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 155, Column 8:
required attribute "TYPE" not specified
<script>YAHOO["a"+"d"+"s"].renderer.ComplexScriptRenderer._setupRender();</scripThe 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 155, Column 8:
document type does not allow element "SCRIPT" here
<script>YAHOO["a"+"d"+"s"].renderer.ComplexScriptRenderer._setupRender();</scripThe 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 155, Column 110:
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 155, Column 110:
document type does not allow element "SCRIPT" here
…</script><script language=javascript>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 158, Column 19:
document type does not allow element "NOSCRIPT" here
</script><noscript><img width=1 height=1 alt="" src="http://us.bc.yahoo.com/b?P=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 158, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vcrppse%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…76%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=12cn1henp%2fN%3dWnukCtG_fzw-%2fC%3d-1%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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…2fB%3d-1%2fV%3d0"></noscript><script>isAdPrefetched = true;</script><script tThe 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 158, Column 352:
document type does not allow element "SCRIPT" here
…2fB%3d-1%2fV%3d0"></noscript><script>isAdPrefetched = true;</script><script tThe 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 158, Column 414:
document type does not allow element "SCRIPT" here
…cript><script type="text/javascript">if ((typeof parent.isBookmark === "undefThe 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 158, Column 722:
end tag for element "FONT" which is not open
…\"ad_slug_font\">ADVERTISEMENT</font><br /></span>\r<IFRAME FRAMEBORDER=0 MARThe 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 158, Column 735:
end tag for element "SPAN" which is not open
…t\">ADVERTISEMENT</font><br /></span>\r<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MAThe 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 158, Column 1299:
end tag for element "IFRAME" which is not open
…cbSR4UqbQ/A=5761135/R=0/*\"></IFRAME>\r</td></tr></table>", "<scr"+"ipt languThe 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 158, Column 1306:
end tag for element "TD" which is not open
…bQ/A=5761135/R=0/*\"></IFRAME>\r</td></tr></table>", "<scr"+"ipt language=javThe 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 158, Column 1311:
end tag for element "TR" which is not open
…5761135/R=0/*\"></IFRAME>\r</td></tr></table>", "<scr"+"ipt language=javascr"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 158, Column 1319:
end tag for element "TABLE" which is not open
…R=0/*\"></IFRAME>\r</td></tr></table>", "<scr"+"ipt language=javascr"+"ipt>\nThe 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 158, Column 1553:
delimiter """ invalid: only S separators and TAGC allowed here
…dLREC%2fB%3d5761135%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1…dLREC%2fB%3d5761135%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1The 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 158, Column 1933:
delimiter """ invalid: only S separators and TAGC allowed here
…LREC%2fB%3d5761135%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script type=…LREC%2fB%3d5761135%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script type=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 158, Column 1991:
document type does not allow element "SCRIPT" here
…cript><script type="text/javascript">if ((typeof parent.isBookmark === "undefThe 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 158, Column 2741:
end tag for element "A" which is not open
…le=margin-right:.5em;float:left;></a> <a href=\"http://us.ard.yahoo.com/SIG=1The 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 158, Column 3254:
end tag for element "P" which is not open
…5m2\" target=\"_blank\"> <p>Free</p> <p>Phones</p> </a>\r<img src=\"http://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 158, Column 3269:
end tag for element "P" which is not open
…_blank\"> <p>Free</p> <p>Phones</p> </a>\r<img src=\"http://ad.doubleclick.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 158, Column 3274:
end tag for element "A" which is not open
…k\"> <p>Free</p> <p>Phones</p> </a>\r<img src=\"http://ad.doubleclick.net/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 158, Column 3630:
delimiter """ invalid: only S separators and TAGC allowed here
…3dMNW%2fB%3d5776625%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1…3dMNW%2fB%3d5776625%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1The 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 158, Column 4010:
delimiter """ invalid: only S separators and TAGC allowed here
…dMNW%2fB%3d5776625%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script type=…dMNW%2fB%3d5776625%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script type=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 158, Column 4068:
document type does not allow element "SCRIPT" here
…cript><script type="text/javascript">if ((typeof parent.isBookmark === "undefThe 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 158, Column 4533:
end tag for element "DIV" which is not open
…5\" style=\"border:0px none;\"></div>\r<p style=\"padding:11px 5px 3px 0;margThe 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 158, Column 4753:
end tag for element "P" which is not open
…nect and share like never before.</p>\r<p style=\"padding:0 10px 0 0;margin:0The 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 158, Column 5240:
end tag for element "A" which is not open
…yle=\"color:#0c00ff;\">Learn more</a>.</p>\r</div>", "<scr"+"ipt language=javThe 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 158, Column 5245:
end tag for element "P" which is not open
…"color:#0c00ff;\">Learn more</a>.</p>\r</div>", "<scr"+"ipt language=javascr"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 158, Column 5253:
end tag for element "DIV" which is not open
…0c00ff;\">Learn more</a>.</p>\r</div>", "<scr"+"ipt language=javascr"+"ipt>\nThe 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 158, Column 5487:
delimiter """ invalid: only S separators and TAGC allowed here
…dMWA2%2fB%3d5823345%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1…dMWA2%2fB%3d5823345%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1The 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 158, Column 5868:
delimiter """ invalid: only S separators and TAGC allowed here
…MWA2%2fB%3d5823345%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script type=…MWA2%2fB%3d5823345%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script type=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 158, Column 5926:
document type does not allow element "SCRIPT" here
…cript><script type="text/javascript">if ((typeof parent.isBookmark === "undefThe 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 158, Column 7111:
end tag for element "IFRAME" which is not open
…0\" title=\"Advertisement\"></iframe>';\rvar rt_ad_id = \"rt_id_\"+(ran);\rvaThe 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 158, Column 7296:
delimiter """ invalid: only S separators and TAGC allowed here
…ontent, rt_ad_url, rt_ad_id);\r</scr"+"ipt>\r", "<scr"+"ipt language=javascr"…ontent, rt_ad_url, rt_ad_id);\r</scr"+"ipt>\r", "<scr"+"ipt language=javascr"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 158, Column 7536:
delimiter """ invalid: only S separators and TAGC allowed here
…3dREC%2fB%3d5742174%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1…3dREC%2fB%3d5742174%2fV%3d1';\n</scr"+"ipt><noscr"+"ipt><img width=1 height=1The 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 158, Column 7914:
delimiter """ invalid: only S separators and TAGC allowed here
…dREC%2fB%3d5742174%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script>YAHOO…dREC%2fB%3d5742174%2fV%3d1\"></noscr"+"ipt>", "true");}</script><script>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 158, Column 7949:
required attribute "TYPE" not specified
…r"+"ipt>", "true");}</script><script>YAHOO["a"+"d"+"s"].renderer.ComplexScripThe 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 158, Column 7949:
document type does not allow element "SCRIPT" here
…r"+"ipt>", "true");}</script><script>YAHOO["a"+"d"+"s"].renderer.ComplexScripThe 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 158, Column 8051:
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 158, Column 8051:
document type does not allow element "SCRIPT" here
…</script><script language=javascript>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 161, Column 19:
document type does not allow element "NOSCRIPT" here
</script><noscript><img width=1 height=1 alt="" src="http://us.bc.yahoo.com/b?P=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 161, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vdc6kgv%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…44%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=12ap6vp81%2fN%3dZXukCtG_fzw-%2fC%3d-1%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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…2fB%3d-1%2fV%3d0"></noscript><script>YAHOO["a"+"d"+"s"].renderer.ComplexScripThe 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 161, Column 350:
document type does not allow element "SCRIPT" here
…2fB%3d-1%2fV%3d0"></noscript><script>YAHOO["a"+"d"+"s"].renderer.ComplexScripThe 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 161, Column 452:
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 161, Column 452:
document type does not allow element "SCRIPT" here
…</script><script language=javascript>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 164, Column 19:
document type does not allow element "NOSCRIPT" here
</script><noscript><img width=1 height=1 alt="" src="http://us.bc.yahoo.com/b?P=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 164, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13vqop1k8%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…81%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=12b7n8u74%2fN%3dZnukCtG_fzw-%2fC%3d-1%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 10, Column 263:
entity was defined here
…43826%2fQ%3d-1%2fS%3d1%2fJ%3d9D4FBFD1&U=13f85sadq%2fN%3dZ3ukCtG_fzw-%2fC%3d65…2fB%3d-1%2fV%3d0"></noscript><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 164, Column 351:
document type does not allow element "SCRIPT" here
…2fB%3d-1%2fV%3d0"></noscript><script>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 177, Column 8:
required attribute "TYPE" not specified
<script>YAHOO["a"+"d"+"s"].renderer.ComplexScriptRenderer._setupRender();</scripThe 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 177, Column 8:
document type does not allow element "SCRIPT" here
<script>YAHOO["a"+"d"+"s"].renderer.ComplexScriptRenderer._setupRender();</scripThe 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 177, Column 110:
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 177, Column 110:
document type does not allow element "SCRIPT" here
…</script><script language=javascript>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 178, Column 118:
delimiter """ invalid: only S separators and TAGC allowed here
….yimg.com/d/lib/bc/bc_2.0.4.js></scr"+"ipt>");….yimg.com/d/lib/bc/bc_2.0.4.js></scr"+"ipt>");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 179, Column 37:
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 179, Column 37:
document type does not allow element "SCRIPT" here
</script><script language=javascript>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 182, Column 19:
document type does not allow element "NOSCRIPT" here
</script><noscript><img width=1 height=1 alt="" src="http://us.bc.yahoo.com/b?P=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 182, Column 123:
reference to entity "T" for which no system identifier could be generated
…G_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13uhg3c6g%2fX%3d1252708109%2fE%3d3983010This 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 10, Column 120:
entity was defined here
…jtdG_T4kHco8iSqrDtAJBxpDAKkqqzw0ABngM&T=13v6o0307%2fX%3d1252708109%2fE%3d3983…1%2fJ%3d9D4FBFD1"></noscript><script> YAHOO.mc.AdIdLog = "MWA1/&LREC/M=715481The 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 182, Column 283:
document type does not allow element "SCRIPT" here
…1%2fJ%3d9D4FBFD1"></noscript><script> YAHOO.mc.AdIdLog = "MWA1/&LREC/M=715481The 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 182, Column 537:
end tag for element "DIV" which is not open
…/A=5742174&RS/&RS2/&";</script></div></small> </div><script type="text/javascThe 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 182, Column 545:
end tag for element "SMALL" which is not open
…74&RS/&RS2/&";</script></div></small> </div><script type="text/javascript">gLThe 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 182, Column 552:
end tag for element "DIV" which is not open
…RS2/&";</script></div></small> </div><script type="text/javascript">gLaunchPrThe 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 182, Column 583:
document type does not allow element "SCRIPT" here
…</div><script type="text/javascript">gLaunchProfile.stop('RT_AD_FOOT', true);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 182, Column 675:
end tag for element "BODY" which is not open
…stop('RT_BP', false);</script></body></html><!-- mc1030.mail.mud.yahoo.com FrThe 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 182, Column 682:
end tag for element "HTML" which is not open
…T_BP', false);</script></body></html><!-- mc1030.mail.mud.yahoo.com Fri, 11 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 182, Column 780:
document type does not allow element "SCRIPT" here
…0 --> <script type="text/javascript">document.cookie ="YM.MGC=yNtzqKp9hS_CDa.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 182, Column 919:
document type does not allow element "SCRIPT" here
…cript><script type="text/javascript">mgProfiler.CT = "175.864";mgProfiler.CL 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 192, Column 64:
document type does not allow element "DIV" here
…mc.SpaceID = "398301034";</script><div id="debugLog">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 29, Column 40:
reference to non-existent ID "MOPTIONSLIST"
<label id="optLb" for="mOptionsList" class="offscreen">Options</This error can be triggered by:
Try to check the spelling and case of the id you are referring to.
