Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 11,
Column 92:
cannot generate system identifier for general entity "ctrl"
…osoft.com/trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezo…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 11,
Column 92:
general entity "ctrl" not defined and no default entity
…osoft.com/trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezo…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 11,
Column 96:
reference not terminated by REFC delimiter
…t.com/trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOf…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 11,
Column 96:
reference to entity "ctrl" for which no system identifier could be generated
…t.com/trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOf…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 11,
Column 91:
entity was defined here
…rosoft.com/trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimez……trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOffset()…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 11,
Column 102:
general entity "tz" not defined and no default entity
…trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOffset()…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 11,
Column 104:
reference not terminated by REFC delimiter
…ans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOffset() /…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 11,
Column 104:
reference to entity "tz" for which no system identifier could be generated
…ans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOffset() /…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 11,
Column 101:
entity was defined here
…/trans_pixel.aspx?route=64DE&ctrl=9C5A&tz=' + ((new Date()).getTimezoneOffset(……z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;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 11,
Column 153:
general entity "cot" not defined and no default entity
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;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 11,
Column 156:
reference not terminated by REFC delimiter
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 11,
Column 156:
reference to entity "cot" for which no system identifier could be generated
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;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 11,
Column 152:
entity was defined here
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;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 11,
Column 159:
general entity "qos.uri" not defined and no default entity
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;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 11,
Column 166:
reference not terminated by REFC delimiter
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 11,
Column 166:
reference to entity "qos.uri" for which no system identifier could be generated
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;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 11,
Column 158:
entity was defined here
…z=' + ((new Date()).getTimezoneOffset() / 60) + '&cot=5&qos.uri=' + QosPageUri;…'<link rel="stylesheet" type="text/css" href="' + QosBuildUri('init') + '"/>');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 18,
Column 27:
cannot generate system identifier for general entity "cd"
return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time …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 18,
Column 27:
general entity "cd" not defined and no default entity
return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time …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 18,
Column 29:
reference not terminated by REFC delimiter
return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 18,
Column 29:
reference to entity "cd" for which no system identifier could be generated
return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time …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 18,
Column 26:
entity was defined here
return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time …… return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time +…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 18,
Column 41:
general entity "qos.ti" not defined and no default entity
… return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time +…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 18,
Column 47:
reference not terminated by REFC delimiter
…rn QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 18,
Column 47:
reference to entity "qos.ti" for which no system identifier could be generated
…rn QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos…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 18,
Column 40:
entity was defined here
… return QosBaseSrc + '&cd=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time ……' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime +…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 18,
Column 68:
general entity "ts" not defined and no default entity
…' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime +…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 18,
Column 70:
reference not terminated by REFC delimiter
…+ cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 18,
Column 70:
reference to entity "ts" for which no system identifier could be generated
…+ cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '…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 18,
Column 67:
entity was defined here
…=' + cd + '&qos.ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime …….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;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 18,
Column 84:
general entity "qos.tl" not defined and no default entity
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;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 18,
Column 90:
reference not terminated by REFC delimiter
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 18,
Column 90:
reference to entity "qos.tl" for which no system identifier could be generated
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;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 18,
Column 83:
entity was defined here
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;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 18,
Column 111:
general entity "qos.n" not defined and no default entity
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;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 18,
Column 116:
reference not terminated by REFC delimiter
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 18,
Column 116:
reference to entity "qos.n" for which no system identifier could be generated
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;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 18,
Column 110:
entity was defined here
….ti=' + QosInitTime + '&ts=' + time + '&qos.tl=' + QosLoadTime + '&qos.n=' + n;…e('<img src="' + src + '" alt="" width="1" height="1" style="display:none"/>');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 40,
Column 87:
character "&" is the first character of a delimiter but occurred as data
…age/shared/core/2/js/js.ashx?pt=hpPage&"></script><link rel="stylesheet" type=…This message may appear in several cases:
Line 40,
Column 1995:
character "&" is the first character of a delimiter but occurred as data
…-task" content="name=Microsoft Safety & Security Center;action-uri=http://www.…This message may appear in several cases:
Line 41,
Column 27:
there is no attribute "bi:type"
<body class="ltr" bi:type="hpMaster">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 62,
Column 13:
there is no attribute "bi:type"
bi:type="hpHeader">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 69,
Column 96:
there is no attribute "bi:index"
…"ctl00_ctl08_LogoStaticSec" class="hpHdr_StaticSec hpHdr_LogoSec" bi:index="0">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 82,
Column 166:
there is no attribute "bi:titleflag"
…er_ctl00_MenuLink" class="hpHdr_MenuLink hpHdr_FlyoutLink" bi:titleflag="item">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 83,
Column 195:
there is no attribute "bi:title"
…_MenuLinkAnchor" class="hpHdr_MenuLinkAnchor" bi:title="item" bi:track="false">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 83,
Column 211:
there is no attribute "bi:track"
…_MenuLinkAnchor" class="hpHdr_MenuLinkAnchor" bi:title="item" bi:track="false">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 85,
Column 159:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…ater_ctl00_ItemRepeater_ctl00_MenuLinkImage" class="hpHdr_MenuLinkImg png-img">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 91,
Column 151:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…tionRepeater_ctl00_ItemRepeater_ctl00_MenuLinkDesc" class="hpHdr_MenuLinkDesc">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 94,
Column 70:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="cssClear">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 98,
Column 159:
there is no attribute "bi:parenttitle"
…mRepeater_ctl00_HeaderFlyoutPos" class="hpHdr_FlyoutPos" bi:parenttitle="item">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 107,
Column 49:
there is no attribute "bi:type"
<ul class="hpPrt" style="width: 410px;" bi:type="hpProductTiles">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 110,
Column 192:
there is no attribute "bi:cpid"
…_Repeater_ctl00_ctl01_Repeater_ctl00_ItemLink" bi:cpid="hpHeader" bi:index="0">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 110,
Column 212:
there is no attribute "bi:index"
…_Repeater_ctl00_ctl01_Repeater_ctl00_ItemLink" bi:cpid="hpHeader" bi:index="0">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 111,
Column 45:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="hpPrt_Image">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 116,
Column 153:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…_Repeater_ctl00_ctl01_Repeater_ctl00_LinkText" class="hpPrt_Text">Windows</div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 122,
Column 45:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="hpPrt_Image">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 127,
Column 153:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…1_Repeater_ctl00_ctl01_Repeater_ctl01_LinkText" class="hpPrt_Text">Office</div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 133,
Column 45:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="hpPrt_Image">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 138,
Column 153:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…l01_Repeater_ctl00_ctl01_Repeater_ctl02_LinkText" class="hpPrt_Text">Xbox</div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 144,
Column 45:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="hpPrt_Image">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 149,
Column 153:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…ter_ctl00_ctl01_Repeater_ctl03_LinkText" class="hpPrt_Text">Windows Phone</div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 155,
Column 45:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="hpPrt_Image">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 160,
Column 153:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…ctl00_ctl01_Repeater_ctl04_LinkText" class="hpPrt_Text">Internet Explorer</div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 170,
Column 99:
there is no attribute "bi:index"
…l hpPrl_Size_small" style="width: 200px;" bi:type="hpProductList" bi:index="0">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 171,
Column 30:
there is no attribute "bi:titleflag"
<li bi:titleflag="item">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 172,
Column 52:
there is no attribute "bi:title"
<div class="hpPrl_Header" bi:title="item">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 176,
Column 40:
there is no attribute "bi:parenttitle"
<li bi:parenttitle="item">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 277,
Column 23:
document type does not allow element "style" here
<style type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 286,
Column 254:
there is no attribute "autocomplete"
…m" class="hpSrc_Textbox" autocomplete="off" /><span id="ctl00_ctl08_SectionRep…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 291,
Column 46:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="hpSrc_DropdownPositioner">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 292,
Column 50:
there is no attribute "bi:track"
<div class="hpSrc_Dropdown" bi:track="false">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 295,
Column 25:
end tag for "ul" which is not finished
</ul>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
Line 303,
Column 103:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
… <a href="javascript:void(0)" tabindex="-1"><div class="hpSrc_Text">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 311,
Column 103:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
… <a href="javascript:void(0)" tabindex="-1"><div class="hpSrc_Text">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 324,
Column 293:
cannot generate system identifier for general entity "mkt"
…icrosoft.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest"…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 324,
Column 293:
general entity "mkt" not defined and no default entity
…icrosoft.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest"…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 324,
Column 296:
reference not terminated by REFC delimiter
…osoft.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 324,
Column 296:
reference to entity "mkt" for which no system identifier could be generated
…osoft.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"…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 324,
Column 292:
entity was defined here
…microsoft.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest…….com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"Servi…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 324,
Column 301:
general entity "setlang" not defined and no default entity
….com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"Servi…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 324,
Column 308:
reference not terminated by REFC delimiter
…sults.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFo…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 324,
Column 308:
reference to entity "setlang" for which no system identifier could be generated
…sults.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFo…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 324,
Column 300:
entity was defined here
…t.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"Serv…….aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFormat"…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 324,
Column 313:
general entity "q" not defined and no default entity
….aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFormat"…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 324,
Column 314:
reference not terminated by REFC delimiter
…aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFormat":…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 324,
Column 314:
reference to entity "q" for which no system identifier could be generated
…aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFormat":…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 324,
Column 312:
entity was defined here
…s.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFormat……tp://www.bing.com/search?form=MSHPLS&q={0}&mkt={1}","AutoSuggest":null,"BI":{"…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 324,
Column 707:
reference to entity "q" for which no system identifier could be generated
…tp://www.bing.com/search?form=MSHPLS&q={0}&mkt={1}","AutoSuggest":null,"BI":{"…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 324,
Column 312:
entity was defined here
…s.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest":{"ServiceUrlFormat…….bing.com/search?form=MSHPLS&q={0}&mkt={1}","AutoSuggest":null,"BI":{"Data":[{…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 324,
Column 715:
reference to entity "mkt" for which no system identifier could be generated
….bing.com/search?form=MSHPLS&q={0}&mkt={1}","AutoSuggest":null,"BI":{"Data":[{…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 324,
Column 292:
entity was defined here
…microsoft.com/results.aspx?form=MSHOME&mkt={1}&setlang={1}&q={0}","AutoSuggest……ter_ctl00_MenuLinkText" class="hpHdr_MenuLinkTxt">United States (English)</div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 340,
Column 70:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div class="cssClear">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 355,
Column 26:
there is no attribute "bi:title"
<h3 bi:title="item">This site in other countries/regions:</h3>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 362,
Column 82:
there is no attribute "bi:locale"
…ft.com/en/xf/" bi:index="0" bi:locale="en-xf" bi:type="locale" >Africa - Engli…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 362,
Column 98:
there is no attribute "bi:type"
…xf/" bi:index="0" bi:locale="en-xf" bi:type="locale" >Africa - English</a></li>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 620,
Column 28:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.LocalePicker) {This message may appear in several cases:
Line 620,
Column 29:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.LocalePicker) {This message may appear in several cases:
Line 624,
Column 28:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.GeoLocale) {This message may appear in several cases:
Line 624,
Column 29:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.GeoLocale) {This message may appear in several cases:
Line 658,
Column 24:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.FlyoutMenu) {This message may appear in several cases:
Line 658,
Column 25:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.FlyoutMenu) {This message may appear in several cases:
Line 661,
Column 30:
character "&" is the first character of a delimiter but occurred as data
if ($.bi && $.bi.dataRetrievers.structure) {This message may appear in several cases:
Line 661,
Column 31:
character "&" is the first character of a delimiter but occurred as data
if ($.bi && $.bi.dataRetrievers.structure) {This message may appear in several cases:
Line 762,
Column 50:
there is no attribute "bi:type"
<span id="ctl00_ctl12" class="msMnu" bi:type="hpMenu">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 763,
Column 34:
document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<ul class="msMnu_Section">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 765,
Column 99:
there is no attribute "bi:index"
… id="ctl00_ctl12_ItemsRepeater_ctl00_MenuItem" class="msMnu_Item" bi:index="0">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 779,
Column 196:
there is no attribute "bi:titleflag"
… msMnu_Level2Cat noLink" bi:titleflag="item" bi:title="item">Products</h3><ul …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 779,
Column 361:
there is no attribute "bi:parenttitle"
…" class="msMnu_Level3" bi:parenttitle="item" bi:index="0"><li ><a class="hpFea…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 966,
Column 24:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.FlyoutMenu) {This message may appear in several cases:
Line 966,
Column 25:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.FlyoutMenu) {This message may appear in several cases:
Line 969,
Column 30:
character "&" is the first character of a delimiter but occurred as data
if ($.bi && $.bi.dataRetrievers.structure) {This message may appear in several cases:
Line 969,
Column 31:
character "&" is the first character of a delimiter but occurred as data
if ($.bi && $.bi.dataRetrievers.structure) {This message may appear in several cases:
Line 1058,
Column 50:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
… ><div class="hpVpv_Title"><span id="ctl00_ctl15_TileRepeater_ctl0…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 1060,
Column 29:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
><img alt="" src="/global/en-us/homepage/Publishing…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 1068,
Column 50:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
… ><div class="hpVpv_Title"><span id="ctl00_ctl15_TileRepeater_ctl0…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 1070,
Column 29:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
><img alt="" src="/global/en-us/homepage/Publishing…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 1078,
Column 50:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
… ><div class="hpVpv_Title"><span id="ctl00_ctl15_TileRepeater_ctl0…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 1080,
Column 29:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
><img alt="" src="/global/en-us/homepage/Publishing…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 1088,
Column 50:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
… ><div class="hpVpv_Title"><span id="ctl00_ctl15_TileRepeater_ctl0…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 1090,
Column 29:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
><img alt="" src="/global/en-us/homepage/Publishing…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 1110,
Column 125:
there is no attribute "bi:title"
…0_HiddenTitle" class="hidden hpVpv_HiddenTitle" bi:title="item">For Home</span>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 1115,
Column 136:
there is no attribute "bi:gridindex"
…lumn" class="hpGrd_Column hpGrd_Span80 " bi:gridindex="0" bi:gridtype="column">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 1115,
Column 152:
there is no attribute "bi:gridtype"
…lumn" class="hpGrd_Column hpGrd_Span80 " bi:gridindex="0" bi:gridtype="column">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 1135,
Column 149:
cannot generate system identifier for general entity "hroi"
…peater_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Previ…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 1135,
Column 149:
general entity "hroi" not defined and no default entity
…peater_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Previ…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 1135,
Column 153:
reference not terminated by REFC delimiter
…er_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Previous"…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1135,
Column 153:
reference to external entity in attribute value
…er_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Previous"…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1135,
Column 153:
reference to entity "hroi" for which no system identifier could be generated
…er_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Previous"…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 1135,
Column 148:
entity was defined here
…epeater_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Prev……er_ctl00_CellRepeater_ctl00_ctl01&hroi=1" class="hpHro_Next" title="Next"><img…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1138,
Column 153:
reference to external entity in attribute value
…er_ctl00_CellRepeater_ctl00_ctl01&hroi=1" class="hpHro_Next" title="Next"><img…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1138,
Column 153:
reference to entity "hroi" for which no system identifier could be generated
…er_ctl00_CellRepeater_ctl00_ctl01&hroi=1" class="hpHro_Next" title="Next"><img…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 1135,
Column 148:
entity was defined here
…epeater_ctl00_CellRepeater_ctl00_ctl01&hroi=-1" class="hpHro_Prev" title="Prev……ss="hpHro_Item" style="width:530px; " index="0" bi:index="0" bi:type="infotem">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 1147,
Column 66:
there is no attribute "rel"
<div class="hpHro_ImgWrap" style="height:320px;" rel="320">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 1148,
Column 87:
there is no attribute "bi:linkid"
…T/go/352390268/direct/01/" bi:linkid="100-00-124GMUS017361" bi:campaignname="…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 1148,
Column 126:
there is no attribute "bi:campaignname"
…100-00-124GMUS017361" bi:campaignname="(Q4 Office Try/Buy)" bi:cpid="homeFeatu…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 1157,
Column 37:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && !$('#ctl00_ctl15_BodyRepeater_ctl00_ctl0…This message may appear in several cases:
Line 1157,
Column 38:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && !$('#ctl00_ctl15_BodyRepeater_ctl00_ctl0…This message may appear in several cases:
Line 1158,
Column 20:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.Hero) {This message may appear in several cases:
Line 1158,
Column 21:
character "&" is the first character of a delimiter but occurred as data
if (Hp && Hp.Hero) {This message may appear in several cases:
Line 1187,
Column 38:
there is no attribute "bi:titleflag"
<h4 bi:titleflag="item"><a href="/en-us/default.aspx?accid=…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 1187,
Column 181:
cannot generate system identifier for general entity "acci"
…peater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpen…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 1187,
Column 181:
general entity "acci" not defined and no default entity
…peater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpen…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 1187,
Column 185:
reference not terminated by REFC delimiter
…er_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpen" bi…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1187,
Column 185:
reference to external entity in attribute value
…er_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpen" bi…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1187,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpen" bi…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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe……itle hpFeat_Item noLink" bi:titleflag="item" bi:title="item">Xbox 360 offers m…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 1197,
Column 98:
there is no attribute "bi:title"
… noLink" bi:titleflag="item" bi:title="item">Xbox 360 offers more ways to be e…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 1199,
Column 89:
there is no attribute "bi:parenttitle"
…on hpFeat_Item noLink" bi:parenttitle="item">Change the way you watch HDTV and…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 1226,
Column 185:
reference not terminated by REFC delimiter
…er_ctl00_CellRepeater_ctl01_ctl01&acci=1" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1226,
Column 185:
reference to external entity in attribute value
…er_ctl00_CellRepeater_ctl01_ctl01&acci=1" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1226,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl00_CellRepeater_ctl01_ctl01&acci=1" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe…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 1190,
Column 35:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1191,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_Image" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1194,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1208,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_PrimaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R……er_ctl00_CellRepeater_ctl01_ctl01&acci=2" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1265,
Column 185:
reference to external entity in attribute value
…er_ctl00_CellRepeater_ctl01_ctl01&acci=2" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1265,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl00_CellRepeater_ctl01_ctl01&acci=2" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe…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 1190,
Column 35:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1191,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_Image" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1194,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1208,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl00_CellRepeater_ctl01_ctl01_featureItemID_PrimaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 1306,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 1306,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 1306,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 1345,
Column 26:
there is no attribute "bi:track"
<ul bi:track="false" >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 1349,
Column 165:
cannot generate system identifier for general entity "crsci"
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"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 1349,
Column 165:
general entity "crsci" not defined and no default entity
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=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 1349,
Column 170:
reference not terminated by REFC delimiter
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1349,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1349,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0" indx="0" bi:index="0">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 1364,
Column 170:
reference not terminated by REFC delimiter
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=1"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1364,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=1"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1364,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=2"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1379,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=2"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1379,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=2"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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=3"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1394,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=3"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1394,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=3"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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=4"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1409,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=4"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1409,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=4"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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=5"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1424,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=5"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1424,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=5"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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0"…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=6"If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 1439,
Column 170:
reference to external entity in attribute value
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=6"This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 1439,
Column 170:
reference to entity "crsci" for which no system identifier could be generated
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=6"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 1349,
Column 164:
entity was defined here
…_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01&crsci=0" style="width:246px;" indx="0" bi:index="0">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 1493,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_Container" already defined
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1460,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1461,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_Image" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1464,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1478,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_PrimaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1460,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1461,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_Image" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1464,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1478,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl01_CellRepeater_ctl00_ctl01_Item_PrimaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… if (typeof $ != 'undefined' && !$('#ctl00_ctl15_BodyRepeater_ctl00_ctl0…This message may appear in several cases:
Line 1571,
Column 38:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && !$('#ctl00_ctl15_BodyRepeater_ctl00_ctl0…This message may appear in several cases:
Line 1572,
Column 41:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Carousel) {This message may appear in several cases:
Line 1572,
Column 42:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Carousel) {This message may appear in several cases:
Line 1572,
Column 47:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Carousel) {This message may appear in several cases:
Line 1572,
Column 48:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Carousel) {This message may appear in several cases:
Line 1630,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" already defined
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1597,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1601,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1617,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R……08556" bi:campaignname="(Windows Help & how-to (GEN))" bi:cpid="homeProductLis…This message may appear in several cases:
Line 1661,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" already defined
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1597,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1601,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1617,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R……008554" bi:campaignname="(Office Help & How-to (GEN))" bi:cpid="homeProductLis…This message may appear in several cases:
Line 1692,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" already defined
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1597,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1601,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1617,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…… bi:campaignname="(Windows Phone Help & how-to (GEN))" bi:cpid="homeProductLis…This message may appear in several cases:
Line 1723,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" already defined
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1597,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1601,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1617,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R……campaignname="(Internet Explorer Help & How to (GEN))" bi:cpid="homeProductLis…This message may appear in several cases:
Line 1754,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" already defined
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1597,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1601,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1617,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl00_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1804,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1806,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1822,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1804,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1806,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1822,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1804,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1806,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1822,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1804,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1806,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1822,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1804,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1806,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1822,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 1804,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 1806,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 1822,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 2040,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2042,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2058,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 2040,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2042,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2058,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 2040,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2042,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2058,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate…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 2040,
Column 30:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeate… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2042,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2058,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl02_CellRepeater_ctl02_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R……er_ctl03_CellRepeater_ctl00_ctl01&acci=0" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2227,
Column 185:
reference to external entity in attribute value
…er_ctl03_CellRepeater_ctl00_ctl01&acci=0" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 2227,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl03_CellRepeater_ctl00_ctl01&acci=0" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe……er_ctl03_CellRepeater_ctl00_ctl01&acci=1" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2309,
Column 185:
reference to external entity in attribute value
…er_ctl03_CellRepeater_ctl00_ctl01&acci=1" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 2309,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl03_CellRepeater_ctl00_ctl01&acci=1" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe…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 2230,
Column 35:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl00_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2232,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl00_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2248,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl00_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2393,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2393,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2393,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2418,
Column 185:
reference not terminated by REFC delimiter
…er_ctl03_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2418,
Column 185:
reference to external entity in attribute value
…er_ctl03_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 2418,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl03_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe……er_ctl03_CellRepeater_ctl01_ctl01&acci=1" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2496,
Column 185:
reference to external entity in attribute value
…er_ctl03_CellRepeater_ctl01_ctl01&acci=1" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 2496,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl03_CellRepeater_ctl01_ctl01&acci=1" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe…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 2421,
Column 35:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl01_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2423,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl01_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2439,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl01_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2576,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2576,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2576,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2601,
Column 185:
reference not terminated by REFC delimiter
…er_ctl03_CellRepeater_ctl02_ctl01&acci=0" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2601,
Column 185:
reference to external entity in attribute value
…er_ctl03_CellRepeater_ctl02_ctl01&acci=0" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 2601,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl03_CellRepeater_ctl02_ctl01&acci=0" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe……er_ctl03_CellRepeater_ctl02_ctl01&acci=1" class="hpAccTitle" bi:title="item" …If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2683,
Column 185:
reference to external entity in attribute value
…er_ctl03_CellRepeater_ctl02_ctl01&acci=1" class="hpAccTitle" bi:title="item" …This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 2683,
Column 185:
reference to entity "acci" for which no system identifier could be generated
…er_ctl03_CellRepeater_ctl02_ctl01&acci=1" class="hpAccTitle" bi:title="item" …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 1187,
Column 180:
entity was defined here
…epeater_ctl00_CellRepeater_ctl01_ctl01&acci=0" class="hpAccTitle hpAccTitleOpe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe…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 2604,
Column 35:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl02_ctl01_featureItemID_Container" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRe… <div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR…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 2606,
Column 18:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl02_ctl01_featureItemID_TextContainer" first defined here
<div id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowR… <ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R…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 2622,
Column 21:
ID "ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_RowRepeater_ctl03_CellRepeater_ctl02_ctl01_featureItemID_SecondaryCta" first defined here
<ul id="ctl00_ctl15_BodyRepeater_ctl00_ctl01_ColumnRepeater_ctl00_R… if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2763,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2763,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2763,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Accordion) {This message may appear in several cases:
Line 2778,
Column 33:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2778,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2778,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2778,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2794,
Column 82:
there is no attribute "data-component"
…pv_DynLoadPlaceholder" data-component="/en-us/homepage/component.asch?k=%2fen-…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 2826,
Column 33:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.VPivot) {This message may appear in several cases:
Line 2826,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.VPivot) {This message may appear in several cases:
Line 2826,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.VPivot) {This message may appear in several cases:
Line 2826,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.VPivot) {This message may appear in several cases:
Line 2863,
Column 27:
cannot generate system identifier for general entity "PG"
'&PG=CMSHPA&AP=1390', 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 2863,
Column 27:
general entity "PG" not defined and no default entity
'&PG=CMSHPA&AP=1390', 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 2863,
Column 29:
reference not terminated by REFC delimiter
'&PG=CMSHPA&AP=1390', If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2863,
Column 29:
reference to entity "PG" for which no system identifier could be generated
'&PG=CMSHPA&AP=1390', 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 2863,
Column 26:
entity was defined here
'&PG=CMSHPA&AP=1390', '&PG=CMSHPA&AP=1390', 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 2863,
Column 37:
general entity "AP" not defined and no default entity
'&PG=CMSHPA&AP=1390', 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 2863,
Column 39:
reference not terminated by REFC delimiter
'&PG=CMSHPA&AP=1390', If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 2863,
Column 39:
reference to entity "AP" for which no system identifier could be generated
'&PG=CMSHPA&AP=1390', 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 2863,
Column 36:
entity was defined here
'&PG=CMSHPA&AP=1390', if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2889,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2889,
Column 39:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2889,
Column 40:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != 'undefined' && Hp && Hp.Grid) {This message may appear in several cases:
Line 2959,
Column 37:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != "undefined" && typeof $.bi != "undefined") {This message may appear in several cases:
Line 2959,
Column 38:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != "undefined" && typeof $.bi != "undefined") {This message may appear in several cases:
Line 2965,
Column 56:
character "&" is the first character of a delimiter but occurred as data
…ypeof $.bi.dataConsumers != undefined && $.bi.dataConsumers.webtrends != "unde…This message may appear in several cases:
Line 2965,
Column 57:
character "&" is the first character of a delimiter but occurred as data
…peof $.bi.dataConsumers != undefined && $.bi.dataConsumers.webtrends != "undef…This message may appear in several cases:
Line 2965,
Column 103:
character "&" is the first character of a delimiter but occurred as data
…ataConsumers.webtrends != "undefined" && typeof $.bi.dataConsumers.webtrends.W…This message may appear in several cases:
Line 2965,
Column 104:
character "&" is the first character of a delimiter but occurred as data
…taConsumers.webtrends != "undefined" && typeof $.bi.dataConsumers.webtrends.We…This message may appear in several cases:
Line 2975,
Column 37:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != "undefined" && typeof WTOptimize != "undefined"){This message may appear in several cases:
Line 2975,
Column 38:
character "&" is the first character of a delimiter but occurred as data
if (typeof $ != "undefined" && typeof WTOptimize != "undefined"){This message may appear in several cases:
