Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 7,
Column 17:
there is no attribute "property"
<meta property="og:image" content="http://www.lawyersgunsmoneyblog.com/wp-cont…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 45,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if ((randValue == lastIndex) && (quotes.length > 1)) {This message may appear in several cases:
Line 45,
Column 35:
character "&" is the first character of a delimiter but occurred as data
if ((randValue == lastIndex) && (quotes.length > 1)) {This message may appear in several cases:
Line 117,
Column 80:
cannot generate system identifier for general entity "id"
…k/pages/dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Website…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 117,
Column 80:
general entity "id" not defined and no default entity
…k/pages/dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Website…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 117,
Column 82:
reference not terminated by REFC delimiter
…pages/dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Website</…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 117,
Column 82:
reference to external entity in attribute value
…pages/dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Website</…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 117,
Column 82:
reference to entity "id" for which no system identifier could be generated
…pages/dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Website</…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 117,
Column 79:
entity was defined here
…uk/pages/dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Websit……dynamic.asp?page=staffdetails&id=dbrockington" TARGET="_blank">Website</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 135,
Column 11:
end tag for "ul" which is not finished
<ul></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 146,
Column 18:
end tag for "ul" which is not finished
<ul></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 247,
Column 5:
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 294,
Column 5:
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 471,
Column 5:
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 524,
Column 5:
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 527,
Column 7:
end tag for "li" omitted, but OMITTAG NO was specified
</div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 477,
Column 1:
start tag was here
<li class="last-item">DJW </div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 114,
Column 3:
start tag was here
<ul class="clearfix">…https://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-mot…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 578,
Column 638:
general entity "fs" not defined and no default entity
…https://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-mot…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 578,
Column 640:
reference not terminated by REFC delimiter
…tps://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motio…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 578,
Column 640:
reference to external entity in attribute value
…tps://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motio…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 578,
Column 640:
reference to entity "fs" for which no system identifier could be generated
…tps://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motio…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 578,
Column 637:
entity was defined here
…"https://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-mo……://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%2…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 578,
Column 643:
general entity "to" not defined and no default entity
…://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%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 578,
Column 645:
reference not terminated by REFC delimiter
…/mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20c…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 578,
Column 645:
reference to external entity in attribute value
…/mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20c…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 578,
Column 645:
reference to entity "to" for which no system identifier could be generated
…/mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20c…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 578,
Column 642:
entity was defined here
…s://mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%……mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20ca…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 578,
Column 646:
general entity "su" not defined and no default entity
…mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20ca…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 578,
Column 648:
reference not terminated by REFC delimiter
…il.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20car%…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 578,
Column 648:
reference to external entity in attribute value
…il.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20car%…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 578,
Column 648:
reference to entity "su" for which no system identifier could be generated
…il.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20car%…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 578,
Column 645:
entity was defined here
…/mail.google.com/mail/?view=cm&fs=1&to&su=Brian%20Leiter%27s%20slow-motion%20c……ow-motion%20car%20crash%20accelerates&body=http%3A%2F%2Fwww.lawyersgunsmoneybl…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 578,
Column 710:
general entity "body" not defined and no default entity
…ow-motion%20car%20crash%20accelerates&body=http%3A%2F%2Fwww.lawyersgunsmoneybl…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 578,
Column 714:
reference not terminated by REFC delimiter
…otion%20car%20crash%20accelerates&body=http%3A%2F%2Fwww.lawyersgunsmoneyblog.c…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 578,
Column 714:
reference to external entity in attribute value
…otion%20car%20crash%20accelerates&body=http%3A%2F%2Fwww.lawyersgunsmoneyblog.c…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 578,
Column 714:
reference to entity "body" for which no system identifier could be generated
…otion%20car%20crash%20accelerates&body=http%3A%2F%2Fwww.lawyersgunsmoneyblog.c…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 578,
Column 709:
entity was defined here
…low-motion%20car%20crash%20accelerates&body=http%3A%2F%2Fwww.lawyersgunsmoneyb……rs-slow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style=…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 578,
Column 820:
general entity "ui" not defined and no default entity
…rs-slow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style=…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 578,
Column 822:
reference not terminated by REFC delimiter
…-slow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="c…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 578,
Column 822:
reference to external entity in attribute value
…-slow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="c…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 578,
Column 822:
reference to entity "ui" for which no system identifier could be generated
…-slow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="c…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 578,
Column 819:
entity was defined here
…ers-slow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style……ow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="curs…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 578,
Column 825:
general entity "tf" not defined and no default entity
…ow-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="curs…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 578,
Column 827:
reference not terminated by REFC delimiter
…-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor…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 578,
Column 827:
reference to external entity in attribute value
…-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor…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 578,
Column 827:
reference to entity "tf" for which no system identifier could be generated
…-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor…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 578,
Column 824:
entity was defined here
…low-motion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cur……tion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor:po…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 578,
Column 830:
general entity "shva" not defined and no default entity
…tion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor:po…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 578,
Column 834:
reference not terminated by REFC delimiter
…-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor:pointe…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 578,
Column 834:
reference to external entity in attribute value
…-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor:pointe…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 578,
Column 834:
reference to entity "shva" for which no system identifier could be generated
…-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor:pointe…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 578,
Column 829:
entity was defined here
…otion-car-crash-accelerating&ui=2&tf=1&shva=1"></a></li><li><a style="cursor:p……or:pointer" rel="nofollow" onMouseOut="fixOnMouseOut(document.getElementById('…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 578,
Column 1000:
there is no attribute "onMouseOver"
…'), event, 'post-62715')" onMouseOver="more(this,'post-62715')"><img style='ma…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 578,
Column 1139:
required attribute "alt" not specified
…tent/plugins/sociable/images/more.png'></a></li></ul><div onMouseout="fixOnMou…The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 578,
Column 1143:
end tag for "img" omitted, but OMITTAG NO was specified
…/plugins/sociable/images/more.png'></a></li></ul><div onMouseout="fixOnMouseOu…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 578,
Column 1026:
start tag was here
…onMouseOver="more(this,'post-62715')"><img style='margin-top:9px' src='http://……re.png'></a></li></ul><div onMouseout="fixOnMouseOut(this,event,'post-62715')"…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 588,
Column 3673:
cannot generate system identifier for general entity "title"
…rs-slow-motion-car-crash-accelerating&title=Brian%20Leiter%27s%20slow-motion%2…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 588,
Column 3673:
general entity "title" not defined and no default entity
…rs-slow-motion-car-crash-accelerating&title=Brian%20Leiter%27s%20slow-motion%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 588,
Column 3678:
reference not terminated by REFC delimiter
…ow-motion-car-crash-accelerating&title=Brian%20Leiter%27s%20slow-motion%20car%…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 588,
Column 3678:
reference to external entity in attribute value
…ow-motion-car-crash-accelerating&title=Brian%20Leiter%27s%20slow-motion%20car%…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 588,
Column 3678:
reference to entity "title" for which no system identifier could be generated
…ow-motion-car-crash-accelerating&title=Brian%20Leiter%27s%20slow-motion%20car%…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 588,
Column 3672:
entity was defined here
…ers-slow-motion-car-crash-accelerating&title=Brian%20Leiter%27s%20slow-motion%……e="heigth:32px;width:32px"><a onClick="javascript:var%20ipinsite='Good%20Vibes…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 588,
Column 4254:
document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
…ive messages (images and videos only)'> <img style='' src='http://www.lawyersg…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 588,
Column 4368:
required attribute "alt" not specified
…sociable/images/option1/32/vuible.png'></a></a></li><li style="heigth:32px;wid…The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 588,
Column 4372:
end tag for "img" omitted, but OMITTAG NO was specified
…able/images/option1/32/vuible.png'></a></a></li><li style="heigth:32px;width:3…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 588,
Column 4256:
start tag was here
…e messages (images and videos only)'> <img style='' src='http://www.lawyersgun……ww.lawyersgunsmoneyblog.com/wp-content/plugins/sociable/images/closelabel.png">The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 594,
Column 159:
end tag for "img" omitted, but OMITTAG NO was specified
…ww.lawyersgunsmoneyblog.com/wp-content/plugins/sociable/images/closelabel.png">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 594,
Column 5:
start tag was here
<img onclick="hide_sociable('post-62715',true)" title="close" src="http://w……"https://twitter.com/share" data-text="Brian Leiter's slow-motion car crash ac…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 602,
Column 303:
there is no attribute "data-url"
…tion-car-crash-accelerating" data-url="http://www.lawyersgunsmoneyblog.com/201…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 602,
Column 438:
there is no attribute "data-count"
…ass="twitter-share-button" data-count="horizontal">Tweet</a><script type="text…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 602,
Column 723:
cannot generate system identifier for general entity "send"
…rs-slow-motion-car-crash-accelerating&send=false&layout=button_count&show_face…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 602,
Column 723:
general entity "send" not defined and no default entity
…rs-slow-motion-car-crash-accelerating&send=false&layout=button_count&show_face…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 602,
Column 727:
reference not terminated by REFC delimiter
…low-motion-car-crash-accelerating&send=false&layout=button_count&show_faces=fa…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 602,
Column 727:
reference to external entity in attribute value
…low-motion-car-crash-accelerating&send=false&layout=button_count&show_faces=fa…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 602,
Column 727:
reference to entity "send" for which no system identifier could be generated
…low-motion-car-crash-accelerating&send=false&layout=button_count&show_faces=fa…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 602,
Column 722:
entity was defined here
…ers-slow-motion-car-crash-accelerating&send=false&layout=button_count&show_fac……ion-car-crash-accelerating&send=false&layout=button_count&show_faces=false&act…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 602,
Column 734:
general entity "layout" not defined and no default entity
…ion-car-crash-accelerating&send=false&layout=button_count&show_faces=false&act…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 602,
Column 740:
reference not terminated by REFC delimiter
…r-crash-accelerating&send=false&layout=button_count&show_faces=false&action=li…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 602,
Column 740:
reference to external entity in attribute value
…r-crash-accelerating&send=false&layout=button_count&show_faces=false&action=li…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 602,
Column 740:
reference to entity "layout" for which no system identifier could be generated
…r-crash-accelerating&send=false&layout=button_count&show_faces=false&action=li…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 602,
Column 733:
entity was defined here
…tion-car-crash-accelerating&send=false&layout=button_count&show_faces=false&ac……rating&send=false&layout=button_count&show_faces=false&action=like&colorscheme…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 602,
Column 754:
general entity "show_faces" not defined and no default entity
…rating&send=false&layout=button_count&show_faces=false&action=like&colorscheme…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 602,
Column 764:
reference not terminated by REFC delimiter
…d=false&layout=button_count&show_faces=false&action=like&colorscheme=light&fon…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 602,
Column 764:
reference to external entity in attribute value
…d=false&layout=button_count&show_faces=false&action=like&colorscheme=light&fon…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 602,
Column 764:
reference to entity "show_faces" for which no system identifier could be generated
…d=false&layout=button_count&show_faces=false&action=like&colorscheme=light&fon…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 602,
Column 753:
entity was defined here
…erating&send=false&layout=button_count&show_faces=false&action=like&colorschem……&layout=button_count&show_faces=false&action=like&colorscheme=light&font" scro…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 602,
Column 771:
general entity "action" not defined and no default entity
…&layout=button_count&show_faces=false&action=like&colorscheme=light&font" scro…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 602,
Column 777:
reference not terminated by REFC delimiter
…t=button_count&show_faces=false&action=like&colorscheme=light&font" scrolling=…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 602,
Column 777:
reference to external entity in attribute value
…t=button_count&show_faces=false&action=like&colorscheme=light&font" scrolling=…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 602,
Column 777:
reference to entity "action" for which no system identifier could be generated
…t=button_count&show_faces=false&action=like&colorscheme=light&font" scrolling=…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 602,
Column 770:
entity was defined here
…e&layout=button_count&show_faces=false&action=like&colorscheme=light&font" scr……on_count&show_faces=false&action=like&colorscheme=light&font" scrolling="no" f…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 602,
Column 783:
general entity "colorscheme" not defined and no default entity
…on_count&show_faces=false&action=like&colorscheme=light&font" scrolling="no" f…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 602,
Column 794:
reference not terminated by REFC delimiter
…ow_faces=false&action=like&colorscheme=light&font" scrolling="no" frameborder=…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 602,
Column 794:
reference to external entity in attribute value
…ow_faces=false&action=like&colorscheme=light&font" scrolling="no" frameborder=…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 602,
Column 794:
reference to entity "colorscheme" for which no system identifier could be generated
…ow_faces=false&action=like&colorscheme=light&font" scrolling="no" frameborder=…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 602,
Column 782:
entity was defined here
…ton_count&show_faces=false&action=like&colorscheme=light&font" scrolling="no" ……s=false&action=like&colorscheme=light&font" scrolling="no" frameborder="0" sty…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 602,
Column 801:
general entity "font" not defined and no default entity
…s=false&action=like&colorscheme=light&font" scrolling="no" frameborder="0" sty…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 602,
Column 805:
reference not terminated by REFC delimiter
…lse&action=like&colorscheme=light&font" scrolling="no" frameborder="0" style="…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 602,
Column 805:
reference to external entity in attribute value
…lse&action=like&colorscheme=light&font" scrolling="no" frameborder="0" style="…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 602,
Column 805:
reference to entity "font" for which no system identifier could be generated
…lse&action=like&colorscheme=light&font" scrolling="no" frameborder="0" style="…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 602,
Column 800:
entity was defined here
…es=false&action=like&colorscheme=light&font" scrolling="no" frameborder="0" st……t:32px;width:100px" allowTransparency="true"></iframe></li><li id="Google_p"><…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 602,
Column 978:
there is no attribute "annotation"
…i id="Google_p"><g:plusone annotation="bubble" href="http://www.lawyersgunsmon…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 602,
Column 992:
there is no attribute "href"
…"><g:plusone annotation="bubble" href="http://www.lawyersgunsmoneyblog.com/201…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 602,
Column 1092:
there is no attribute "size"
…w-motion-car-crash-accelerating" size="medium"></g:plusone></li><li id="Linked…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 602,
Column 1100:
element "g:plusone" undefined
…-car-crash-accelerating" size="medium"></g:plusone></li><li id="LinkedIn_Count…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 602,
Column 1258:
there is no attribute "data-url"
…ript><script type="IN/Share" data-url="http://www.lawyersgunsmoneyblog.com/201…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 602,
Column 1366:
there is no attribute "data-counter"
…-car-crash-accelerating" data-counter="right"></script></li></ul></div><!-- En…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 1981,
Column 12:
document type does not allow element "blockquote" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<blockquote>Thomson Reuters was ranked as Canada’s “leading corpora…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 1981,
Column 219:
end tag for "blockquote" omitted, but OMITTAG NO was specified
… is headquartered at 3 Times Square, Manhattan, New York City.</p></blockquote>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 1981,
Column 1:
start tag was here
<blockquote>Thomson Reuters was ranked as Canada’s “leading corpora…… is headquartered at 3 Times Square, Manhattan, New York City.</p></blockquote>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 2113,
Column 12:
document type does not allow element "blockquote" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<blockquote>calling me “unprofessional” is probably defamatory per se in Canada…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 2115,
Column 107:
end tag for "blockquote" omitted, but OMITTAG NO was specified
…m trying to plan out my litigation strategy for the next year!</p></blockquote>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 2113,
Column 1:
start tag was here
<blockquote>calling me “unprofessional” is probably defamatory per se in Canada……m trying to plan out my litigation strategy for the next year!</p></blockquote>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 2834,
Column 12:
document type does not allow element "blockquote" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<blockquote>Carrie finds it very unsettling – scary, even – that Leiter assumed…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 2834,
Column 258:
end tag for "blockquote" omitted, but OMITTAG NO was specified
…or fear of similar interpretation, leading to similar results.</p></blockquote>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 2834,
Column 1:
start tag was here
<blockquote>Carrie finds it very unsettling – scary, even – that Leiter assumed……or fear of similar interpretation, leading to similar results.</p></blockquote>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 5325,
Column 130:
end tag for "a" omitted, but OMITTAG NO was specified
…ttps://files.nyu.edu/dv26/public/Statement_of_Concern.html" rel="nofollow"></p>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 5325,
Column 42:
start tag was here
…p>I want to add a link from NewAPPS. <a href="https://files.nyu.edu/dv26/publ……omments reveal more of the history of BL’s bullying and paranoia.</a></p>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 6175,
Column 250:
required attribute "alt" not specified
…yblog.com/wp-content/uploads/2013/02/lgm-podcast-title-e1360545152614.png"></a>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6175,
Column 254:
end tag for "img" omitted, but OMITTAG NO was specified
…yblog.com/wp-content/uploads/2013/02/lgm-podcast-title-e1360545152614.png"></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6175,
Column 140:
start tag was here
…smoneyblog.com/category/podcast/feed"><img src="http://www.lawyersgunsmoneyblo…<input type="hidden" name="cmd" value="_s-xclick">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6179,
Column 1:
start tag was here
<input type="hidden" name="cmd" value="_s-xclick">">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6180,
Column 1:
start tag was here
<input type="hidden" name="encrypted" value="-----BEGIN PKCS7-----MIIHNwYJKoZIh……en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safe…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 6182,
Column 157:
end tag for "input" omitted, but OMITTAG NO was specified
…" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6182,
Column 1:
start tag was here
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_donate_LG.gif" ……er="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6183,
Column 1:
start tag was here
<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width……g.com/wp-content/uploads/2012/05/lgmblog-sunant-web-development.png"></a></div>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6188,
Column 217:
end tag for "img" omitted, but OMITTAG NO was specified
…g.com/wp-content/uploads/2012/05/lgmblog-sunant-web-development.png"></a></div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6188,
Column 105:
start tag was here
…get"><a href="http://www.sunant.com/"><img src="http://www.lawyersgunsmoneyblo……rcm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866…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 6202,
Column 130:
general entity "o" not defined and no default entity
…rcm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866…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 6202,
Column 131:
reference not terminated by REFC delimiter
…cm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=33778660…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 6202,
Column 131:
reference to external entity in attribute value
…cm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=33778660…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 6202,
Column 131:
reference to entity "o" for which no system identifier could be generated
…cm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=33778660…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 6202,
Column 129:
entity was defined here
…/rcm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=337786……amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&…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 6202,
Column 134:
general entity "p" not defined and no default entity
…amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&…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 6202,
Column 135:
reference not terminated by REFC delimiter
…mazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&f…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 6202,
Column 135:
reference to external entity in attribute value
…mazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&f…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 6202,
Column 135:
reference to entity "p" for which no system identifier could be generated
…mazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&f…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 6202,
Column 133:
entity was defined here
….amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011……n.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=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 6202,
Column 139:
general entity "l" not defined and no default entity
…n.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=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 6202,
Column 140:
reference not terminated by REFC delimiter
….com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=00…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 6202,
Column 140:
reference to external entity in attribute value
….com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=00…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 6202,
Column 140:
reference to entity "l" for which no system identifier could be generated
….com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=00…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 6202,
Column 138:
entity was defined here
…on.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=……e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000&…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 6202,
Column 145:
general entity "mode" not defined and no default entity
…e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000&…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 6202,
Column 149:
reference not terminated by REFC delimiter
…?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<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 6202,
Column 149:
reference to external entity in attribute value
…?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<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 6202,
Column 149:
reference to entity "mode" for which no system identifier could be generated
…?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<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 6202,
Column 144:
entity was defined here
…/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000……unandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&…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 6202,
Column 156:
general entity "browse" not defined and no default entity
…unandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&…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 6202,
Column 162:
reference not terminated by REFC delimiter
…on-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=33…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 6202,
Column 162:
reference to external entity in attribute value
…on-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=33…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 6202,
Column 162:
reference to entity "browse" for which no system identifier could be generated
…on-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=33…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 6202,
Column 155:
entity was defined here
…gunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank……14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFF…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 6202,
Column 174:
general entity "fc1" not defined and no default entity
…14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFF…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 6202,
Column 177:
reference not terminated by REFC delimiter
…l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF…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 6202,
Column 177:
reference to external entity in attribute value
…l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF…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 6202,
Column 177:
reference to entity "fc1" for which no system identifier could be generated
…l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF…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 6202,
Column 173:
entity was defined here
…=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FF……de=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" …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 6202,
Column 185:
general entity "lt1" not defined and no default entity
…de=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" …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 6202,
Column 188:
reference not terminated by REFC delimiter
…books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…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 6202,
Column 188:
reference to external entity in attribute value
…books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…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 6202,
Column 188:
reference to entity "lt1" for which no system identifier could be generated
…books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…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 6202,
Column 184:
entity was defined here
…ode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr"……owse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth…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 6202,
Column 196:
general entity "lc1" not defined and no default entity
…owse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth…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 6202,
Column 199:
reference not terminated by REFC delimiter
…e=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="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 6202,
Column 199:
reference to external entity in attribute value
…e=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="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 6202,
Column 199:
reference to entity "lc1" for which no system identifier could be generated
…e=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="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 6202,
Column 195:
entity was defined here
…rowse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidt……6011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margin…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 6202,
Column 207:
general entity "bg1" not defined and no default entity
…6011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margin…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 6202,
Column 210:
reference not terminated by REFC delimiter
…1&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…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 6202,
Column 210:
reference to external entity in attribute value
…1&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…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 6202,
Column 210:
reference to entity "bg1" for which no system identifier could be generated
…1&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…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 6202,
Column 206:
entity was defined here
…66011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margi……0000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="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 6202,
Column 218:
general entity "f" not defined and no default entity
…0000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="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 6202,
Column 219:
reference not terminated by REFC delimiter
…000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…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 6202,
Column 219:
reference to external entity in attribute value
…000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…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 6202,
Column 219:
reference to entity "f" for which no system identifier could be generated
…000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…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 6202,
Column 217:
entity was defined here
…00000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0"……t="0" width="160" height="600" border="0" frameborder="0" style="border:none;"…You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 6285,
Column 173:
there is no attribute "data-widget-id"
…awyers-guns-and-money" data-widget-id="324714165296037888">Tweets from @drfarl…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 6286,
Column 8:
required attribute "type" not specified
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.te…The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6307,
Column 236:
required attribute "alt" not specified
….com/wp-content/uploads/2012/01/Lawyer-of-the-Month-e1325796365969.jpeg"><br />The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6307,
Column 237:
end tag for "img" omitted, but OMITTAG NO was specified
….com/wp-content/uploads/2012/01/Lawyer-of-the-Month-e1325796365969.jpeg"><br />You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6307,
Column 123:
start tag was here
…an></h3> <div class="textwidget"><p><img src="http://www.lawyersgunsmoneyblo……m/wp-content/uploads/2012/01/Clio-Awards-2011-series-e1325796312863.jpg"><br />The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6309,
Column 121:
end tag for "img" omitted, but OMITTAG NO was specified
…m/wp-content/uploads/2012/01/Clio-Awards-2011-series-e1325796312863.jpg"><br />You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6309,
Column 4:
start tag was here
<p><img src="http://www.lawyersgunsmoneyblog.com/wp-content/uploads/2012/01/Cli……anguage="javascript" src="http://cache.blogads.com/882138591/feed.js"></script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6323,
Column 248:
cannot generate system identifier for general entity "OneJS"
…com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=…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 6323,
Column 248:
general entity "OneJS" not defined and no default entity
…com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=…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 6323,
Column 253:
reference not terminated by REFC delimiter
…idgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&so…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 6323,
Column 253:
reference to external entity in attribute value
…idgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&so…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 6323,
Column 253:
reference to entity "OneJS" for which no system identifier could be generated
…idgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&so…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 6323,
Column 247:
entity was defined here
….com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace……ets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&sourc…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 6323,
Column 256:
general entity "Operation" not defined and no default entity
…ets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&sourc…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 6323,
Column 265:
reference not terminated by REFC delimiter
…viceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=…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 6323,
Column 265:
reference to external entity in attribute value
…viceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=…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 6323,
Column 265:
reference to entity "Operation" for which no system identifier could be generated
…viceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=…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 6323,
Column 255:
entity was defined here
…gets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&sour……=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_t…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 6323,
Column 276:
general entity "MarketPlace" not defined and no default entity
…=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_t…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 6323,
Column 287:
reference not terminated by REFC delimiter
…neJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product…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 6323,
Column 287:
reference to external entity in attribute value
…neJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product…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 6323,
Column 287:
reference to entity "MarketPlace" for which no system identifier could be generated
…neJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product…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 6323,
Column 275:
entity was defined here
…n=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_……=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_lin…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 6323,
Column 291:
general entity "source" not defined and no default entity
…=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_lin…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 6323,
Column 297:
reference not terminated by REFC delimiter
…ration=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&trac…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 6323,
Column 297:
reference to external entity in attribute value
…ration=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&trac…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 6323,
Column 297:
reference to entity "source" for which no system identifier could be generated
…ration=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&trac…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 6323,
Column 290:
entity was defined here
…S=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_li……on=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking…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 6323,
Column 301:
general entity "ref" not defined and no default entity
…on=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking…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 6323,
Column 304:
reference not terminated by REFC delimiter
…GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id…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 6323,
Column 304:
reference to external entity in attribute value
…GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id…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 6323,
Column 304:
reference to entity "ref" for which no system identifier could be generated
…GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id…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 6323,
Column 300:
entity was defined here
…ion=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&trackin……l&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id=lawguna…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 6323,
Column 312:
general entity "ad_type" not defined and no default entity
…l&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id=lawguna…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 6323,
Column 319:
reference not terminated by REFC delimiter
…tPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgunandmon-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 6323,
Column 319:
reference to external entity in attribute value
…tPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgunandmon-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 6323,
Column 319:
reference to entity "ad_type" for which no system identifier could be generated
…tPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgunandmon-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 6323,
Column 311:
entity was defined here
…ml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgun……ce=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgunandmon-20&marketplace=…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 6323,
Column 333:
general entity "tracking_id" not defined and no default entity
…ce=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgunandmon-20&marketplace=…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 6323,
Column 344:
reference not terminated by REFC delimiter
…s_til&ad_type=product_link&tracking_id=lawgunandmon-20&marketplace=amazon®i…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 6323,
Column 344:
reference to external entity in attribute value
…s_til&ad_type=product_link&tracking_id=lawgunandmon-20&marketplace=amazon®i…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 6323,
Column 344:
reference to entity "tracking_id" for which no system identifier could be generated
…s_til&ad_type=product_link&tracking_id=lawgunandmon-20&marketplace=amazon®i…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 6323,
Column 332:
entity was defined here
…rce=ss&ref=ss_til&ad_type=product_link&tracking_id=lawgunandmon-20&marketplace……duct_link&tracking_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B…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 6323,
Column 361:
general entity "marketplace" not defined and no default entity
…duct_link&tracking_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B…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 6323,
Column 372:
reference not terminated by REFC delimiter
…racking_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&a…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 6323,
Column 372:
reference to external entity in attribute value
…racking_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&a…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 6323,
Column 372:
reference to entity "marketplace" for which no system identifier could be generated
…racking_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&a…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 360:
entity was defined here
…oduct_link&tracking_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=……id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00…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 6323,
Column 380:
general entity "region" not defined and no default entity
…id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00…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 6323,
Column 386:
reference not terminated by REFC delimiter
…gunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT…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 6323,
Column 386:
reference to external entity in attribute value
…gunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT…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 6323,
Column 386:
reference to entity "region" for which no system identifier could be generated
…gunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT…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 6323,
Column 379:
entity was defined here
…_id=lawgunandmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B0……ndmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&li…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 6323,
Column 390:
general entity "placement" not defined and no default entity
…ndmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&li…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 399:
reference not terminated by REFC delimiter
…marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOF…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 6323,
Column 399:
reference to external entity in attribute value
…marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOF…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 6323,
Column 399:
reference to entity "placement" for which no system identifier could be generated
…marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOF…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 6323,
Column 389:
entity was defined here
…andmon-20&marketplace=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&l……amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP…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 6323,
Column 411:
general entity "asins" not defined and no default entity
…amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP…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 6323,
Column 416:
reference not terminated by REFC delimiter
…n®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show…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 6323,
Column 416:
reference to external entity in attribute value
…n®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show…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 6323,
Column 416:
reference to entity "asins" for which no system identifier could be generated
…n®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show…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 6323,
Column 410:
entity was defined here
…=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TS……placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true…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 6323,
Column 428:
general entity "linkId" not defined and no default entity
…placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true…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 6323,
Column 434:
reference not terminated by REFC delimiter
…ent=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_…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 6323,
Column 434:
reference to external entity in attribute value
…ent=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_…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 6323,
Column 434:
reference to entity "linkId" for which no system identifier could be generated
…ent=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_…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 6323,
Column 427:
entity was defined here
…&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=tru……ns=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_windo…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 6323,
Column 452:
general entity "show_border" not defined and no default entity
…ns=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_windo…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 6323,
Column 463:
reference not terminated by REFC delimiter
…T6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 6323,
Column 463:
reference to external entity in attribute value
…T6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 6323,
Column 463:
reference to entity "show_border" for which no system identifier could be generated
…T6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 451:
entity was defined here
…ins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_wind……&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br />An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (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 6323,
Column 469:
general entity "link_opens_in_new_window" not defined and no default entity
…&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br />This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 493:
reference not terminated by REFC delimiter
…&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br />If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 6323,
Column 493:
reference to external entity in attribute value
…&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br />This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 6323,
Column 493:
reference to entity "link_opens_in_new_window" for which no system identifier could be generated
…&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br />This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 468:
entity was defined here
…&linkId=BKOFIGNR6MGH3TSP&show_border=true&link_opens_in_new_window=true"><br />…a.amazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&l…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 6325,
Column 67:
general entity "bc1" not defined and no default entity
…a.amazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&l…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 6325,
Column 70:
reference not terminated by REFC delimiter
…mazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=…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 6325,
Column 70:
reference to external entity in attribute value
…mazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=…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 6325,
Column 70:
reference to entity "bc1" for which no system identifier could be generated
…mazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=…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 6325,
Column 66:
entity was defined here
…na.amazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&……system.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t…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 6325,
Column 78:
general entity "IS2" not defined and no default entity
…system.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t…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 6325,
Column 81:
reference not terminated by REFC delimiter
…tem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=la…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 6325,
Column 81:
reference to external entity in attribute value
…tem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=la…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 6325,
Column 81:
reference to entity "IS2" for which no system identifier could be generated
…tem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=la…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 6325,
Column 77:
entity was defined here
…dsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&……m/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunan…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 6325,
Column 87:
reference to external entity in attribute value
…m/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunan…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 6325,
Column 87:
reference to entity "bg1" for which no system identifier could be generated
…m/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunan…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 6202,
Column 206:
entity was defined here
…66011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margi……_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=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 6325,
Column 98:
reference to external entity in attribute value
…_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=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 6325,
Column 98:
reference to entity "fc1" for which no system identifier could be generated
…_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=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 6202,
Column 173:
entity was defined here
…=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FF……000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&…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 6325,
Column 109:
reference to external entity in attribute value
…000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&…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 6325,
Column 109:
reference to entity "lc1" for which no system identifier could be generated
…000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&…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 6202,
Column 195:
entity was defined here
…rowse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidt……S2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon…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 6325,
Column 117:
general entity "t" not defined and no default entity
…S2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon…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 6325,
Column 118:
reference not terminated by REFC delimiter
…2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&…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 6325,
Column 118:
reference to external entity in attribute value
…2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&…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 6325,
Column 118:
reference to entity "t" for which no system identifier could be generated
…2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&…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 6325,
Column 116:
entity was defined here
…IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazo……=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&a…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 6325,
Column 136:
reference to external entity in attribute value
…=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&a…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 6325,
Column 136:
reference to entity "o" for which no system identifier could be generated
…=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&a…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6202,
Column 129:
entity was defined here
…/rcm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=337786……000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins…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 6325,
Column 140:
reference to external entity in attribute value
…000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins…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 6325,
Column 140:
reference to entity "p" for which no system identifier could be generated
…000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins…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 6202,
Column 133:
entity was defined here
….amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011……lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=081…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 6325,
Column 144:
reference to external entity in attribute value
…lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=081…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 6325,
Column 144:
reference to entity "l" for which no system identifier could be generated
…lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=081…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 6202,
Column 138:
entity was defined here
…on.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=……000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=08131449…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 6325,
Column 149:
general entity "m" not defined and no default entity
…000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=08131449…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 6325,
Column 150:
reference not terminated by REFC delimiter
…00FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=081314495…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 6325,
Column 150:
reference to external entity in attribute value
…00FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=081314495…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 6325,
Column 150:
reference to entity "m" for which no system identifier could be generated
…00FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=081314495…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 6325,
Column 148:
entity was defined here
…0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144……wgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style=…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 6325,
Column 159:
reference to external entity in attribute value
…wgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style=…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 6325,
Column 159:
reference to entity "f" for which no system identifier could be generated
…wgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style=…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 6202,
Column 217:
entity was defined here
…00000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0"……on-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style="width: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 6325,
Column 167:
reference to external entity in attribute value
…on-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style="width: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 6325,
Column 167:
reference to entity "ref" for which no system identifier could be generated
…on-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style="width:1…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 300:
entity was defined here
…ion=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&trackin……&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style="width:120px;height: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 6325,
Column 180:
reference to external entity in attribute value
…&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style="width:120px;height: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 6325,
Column 180:
reference to entity "asins" for which no system identifier could be generated
…&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144957" style="width:120px;height: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 6323,
Column 410:
entity was defined here
…=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TS……mazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=…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 6326,
Column 70:
reference to external entity in attribute value
…mazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=…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 6326,
Column 70:
reference to entity "bc1" for which no system identifier could be generated
…mazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=…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 6325,
Column 66:
entity was defined here
…na.amazon-adsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&……tem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=la…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 6326,
Column 81:
reference to external entity in attribute value
…tem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=la…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 6326,
Column 81:
reference to entity "IS2" for which no system identifier could be generated
…tem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=la…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 6325,
Column 77:
entity was defined here
…dsystem.com/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&……m/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunan…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 6326,
Column 87:
reference to external entity in attribute value
…m/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunan…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 6326,
Column 87:
reference to entity "bg1" for which no system identifier could be generated
…m/e/cm?lt1=_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunan…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 6202,
Column 206:
entity was defined here
…66011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margi……_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=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 6326,
Column 98:
reference to external entity in attribute value
…_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=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 6326,
Column 98:
reference to entity "fc1" for which no system identifier could be generated
…_blank&bc1=000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=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 6202,
Column 173:
entity was defined here
…=14&l=bn1&mode=books&browse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FF……000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&…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 6326,
Column 109:
reference to external entity in attribute value
…000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&…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 6326,
Column 109:
reference to entity "lc1" for which no system identifier could be generated
…000000&IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&…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 6202,
Column 195:
entity was defined here
…rowse=3377866011&fc1=000000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidt……2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&…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 6326,
Column 118:
reference to external entity in attribute value
…2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&…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 6326,
Column 118:
reference to entity "t" for which no system identifier could be generated
…2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&…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 6325,
Column 116:
entity was defined here
…IS2=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazo……=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&a…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 6326,
Column 136:
reference to external entity in attribute value
…=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&a…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 6326,
Column 136:
reference to entity "o" for which no system identifier could be generated
…=000000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&a…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6202,
Column 129:
entity was defined here
…/rcm.amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=337786……000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins…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 6326,
Column 140:
reference to external entity in attribute value
…000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins…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 6326,
Column 140:
reference to entity "p" for which no system identifier could be generated
…000&lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins…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 6202,
Column 133:
entity was defined here
….amazon.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011……lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=148…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 6326,
Column 144:
reference to external entity in attribute value
…lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=148…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 6326,
Column 144:
reference to entity "l" for which no system identifier could be generated
…lc1=0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=148…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 6202,
Column 138:
entity was defined here
…on.com/e/cm?t=lawgunandmon-20&o=1&p=14&l=bn1&mode=books&browse=3377866011&fc1=……00FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=148016368…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 6326,
Column 150:
reference to external entity in attribute value
…00FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=148016368…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 6326,
Column 150:
reference to entity "m" for which no system identifier could be generated
…00FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=148016368…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 6325,
Column 148:
entity was defined here
…0000FF&t=lawgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=0813144……wgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style=…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 6326,
Column 159:
reference to external entity in attribute value
…wgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style=…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 6326,
Column 159:
reference to entity "f" for which no system identifier could be generated
…wgunandmon-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style=…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 6202,
Column 217:
entity was defined here
…00000<1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0"……on-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style="width: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 6326,
Column 167:
reference to external entity in attribute value
…on-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style="width: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 6326,
Column 167:
reference to entity "ref" for which no system identifier could be generated
…on-20&o=1&p=8&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style="width:1…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 6323,
Column 300:
entity was defined here
…ion=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_type=product_link&trackin……&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style="width:120px;height: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 6326,
Column 180:
reference to external entity in attribute value
…&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style="width:120px;height: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 6326,
Column 180:
reference to entity "asins" for which no system identifier could be generated
…&l=as4&m=amazon&f=ifr&ref=ss_til&asins=1480163686" style="width:120px;height: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 6323,
Column 410:
entity was defined here
…=amazon®ion=US&placement=B00JIV2ZT6&asins=B00JIV2ZT6&linkId=BKOFIGNR6MGH3TS…<p><OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http:…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 6327,
Column 74:
there is no attribute "codebase"
…AE6D-11cf-96B8-444553540000" codebase="http://fpdownload.macromedia.com/get/fl…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 6327,
Column 148:
there is no attribute "id"
…t/flashplayer/current/swflash.cab" id="Player_4f5e2755-3436-4571-9358-59968bdc…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 6327,
Column 201:
there is no attribute "WIDTH"
…5-3436-4571-9358-59968bdcac46" WIDTH="160px" HEIGHT="600px"> <PARAM NAME="mov…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 6327,
Column 216:
there is no attribute "HEIGHT"
…8-59968bdcac46" WIDTH="160px" HEIGHT="600px"> <PARAM NAME="movie" VALUE="http…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 6327,
Column 223:
element "OBJECT" undefined
…bdcac46" WIDTH="160px" HEIGHT="600px"> <PARAM NAME="movie" VALUE="http://ws.a…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 237:
there is no attribute "NAME"
…H="160px" HEIGHT="600px"> <PARAM NAME="movie" VALUE="http://ws.amazon.com/widg…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 6327,
Column 251:
there is no attribute "VALUE"
…HT="600px"> <PARAM NAME="movie" VALUE="http://ws.amazon.com/widgets/q?rt=tf_cw…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 6327,
Column 292:
cannot generate system identifier for general entity "ServiceVersion"
…tp://ws.amazon.com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&I…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 6327,
Column 292:
general entity "ServiceVersion" not defined and no default entity
…tp://ws.amazon.com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&I…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 6327,
Column 306:
reference not terminated by REFC delimiter
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 306:
reference to external entity in attribute value
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 306:
reference to entity "ServiceVersion" for which no system identifier could be generated
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 291:
entity was defined here
…ttp://ws.amazon.com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&……cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6327,
Column 327:
reference to external entity in attribute value
…cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6327,
Column 327:
reference to entity "MarketPlace" for which no system identifier could be generated
…cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6323,
Column 275:
entity was defined here
…n=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_……erviceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F80…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 6327,
Column 331:
general entity "ID" not defined and no default entity
…erviceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F80…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 6327,
Column 333:
reference not terminated by REFC delimiter
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 333:
reference to external entity in attribute value
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 333:
reference to entity "ID" for which no system identifier could be generated
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 330:
entity was defined here
…ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8……-3436-4571-9358-59968bdcac46&Operation=GetDisplayTemplate"><PARAM NAME="qualit…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 6327,
Column 422:
reference to external entity in attribute value
…-3436-4571-9358-59968bdcac46&Operation=GetDisplayTemplate"><PARAM NAME="qualit…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 6327,
Column 422:
reference to entity "Operation" for which no system identifier could be generated
…-3436-4571-9358-59968bdcac46&Operation=GetDisplayTemplate"><PARAM NAME="qualit…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 6323,
Column 255:
entity was defined here
…gets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&sour……8bdcac46&Operation=GetDisplayTemplate"><PARAM NAME="quality" VALUE="high"><PAR…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 477:
element "PARAM" undefined
…te"><PARAM NAME="quality" VALUE="high"><PARAM NAME="bgcolor" VALUE="#FFFFFF"><…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 515:
element "PARAM" undefined
…><PARAM NAME="bgcolor" VALUE="#FFFFFF"><PARAM NAME="allowscriptaccess" VALUE="…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 562:
element "PARAM" undefined
…AME="allowscriptaccess" VALUE="always"><embed src="http://ws.amazon.com/widget…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 574:
there is no attribute "src"
…riptaccess" VALUE="always"><embed src="http://ws.amazon.com/widgets/q?rt=tf_cw…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 6327,
Column 629:
reference not terminated by REFC delimiter
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 629:
reference to external entity in attribute value
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 629:
reference to entity "ServiceVersion" for which no system identifier could be generated
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 291:
entity was defined here
…ttp://ws.amazon.com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&……cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6327,
Column 650:
reference to external entity in attribute value
…cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6327,
Column 650:
reference to entity "MarketPlace" for which no system identifier could be generated
…cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6323,
Column 275:
entity was defined here
…n=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_……viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 656:
reference to external entity in attribute value
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 656:
reference to entity "ID" for which no system identifier could be generated
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 330:
entity was defined here
…ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8……-3436-4571-9358-59968bdcac46&Operation=GetDisplayTemplate" id="Player_4f5e2755…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 6327,
Column 745:
reference to external entity in attribute value
…-3436-4571-9358-59968bdcac46&Operation=GetDisplayTemplate" id="Player_4f5e2755…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 6327,
Column 745:
reference to entity "Operation" for which no system identifier could be generated
…-3436-4571-9358-59968bdcac46&Operation=GetDisplayTemplate" id="Player_4f5e2755…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 6323,
Column 255:
entity was defined here
…gets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&sour……ac46&Operation=GetDisplayTemplate" id="Player_4f5e2755-3436-4571-9358-59968bdc…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 6327,
Column 823:
there is no attribute "quality"
…-3436-4571-9358-59968bdcac46" quality="high" bgcolor="#ffffff" name="Player_4f…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 6327,
Column 838:
there is no attribute "bgcolor"
…-59968bdcac46" quality="high" bgcolor="#ffffff" name="Player_4f5e2755-3436-457…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 6327,
Column 853:
there is no attribute "name"
…quality="high" bgcolor="#ffffff" name="Player_4f5e2755-3436-4571-9358-59968bdc…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 6327,
Column 917:
there is no attribute "allowscriptaccess"
…-9358-59968bdcac46" allowscriptaccess="always" type="application/x-shockwave-…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 6327,
Column 932:
there is no attribute "type"
…c46" allowscriptaccess="always" type="application/x-shockwave-flash" align="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 6327,
Column 970:
there is no attribute "align"
…"application/x-shockwave-flash" align="middle" height="600px" width="160px"></…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 6327,
Column 986:
there is no attribute "height"
…hockwave-flash" align="middle" height="600px" width="160px"></embed></OBJECT> …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 6327,
Column 1000:
there is no attribute "width"
…" align="middle" height="600px" width="160px"></embed></OBJECT> <NOSCRIPT><A H…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 6327,
Column 1007:
element "embed" undefined
…="middle" height="600px" width="160px"></embed></OBJECT> <NOSCRIPT><A HREF="ht…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 1024:
end tag for "PARAM" omitted, but OMITTAG NO was specified
…"600px" width="160px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.co…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6327,
Column 516:
start tag was here
…<PARAM NAME="bgcolor" VALUE="#FFFFFF"><PARAM NAME="allowscriptaccess" VALUE="a……"600px" width="160px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.co…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6327,
Column 478:
start tag was here
…e"><PARAM NAME="quality" VALUE="high"><PARAM NAME="bgcolor" VALUE="#FFFFFF"><P……"600px" width="160px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.co…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6327,
Column 443:
start tag was here
…bdcac46&Operation=GetDisplayTemplate"><PARAM NAME="quality" VALUE="high"><PARA……"600px" width="160px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.co…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6327,
Column 225:
start tag was here
…cac46" WIDTH="160px" HEIGHT="600px"> <PARAM NAME="movie" VALUE="http://ws.ama……th="160px"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.com/widgets/q…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6327,
Column 1044:
there is no attribute "HREF"
…"></embed></OBJECT> <NOSCRIPT><A HREF="http://ws.amazon.com/widgets/q?rt=tf_cw…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 6327,
Column 1099:
reference not terminated by REFC delimiter
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 1099:
reference to external entity in attribute value
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 1099:
reference to entity "ServiceVersion" for which no system identifier could be generated
….com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…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 6327,
Column 291:
entity was defined here
…ttp://ws.amazon.com/widgets/q?rt=tf_cw&ServiceVersion=20070822&MarketPlace=US&……cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6327,
Column 1120:
reference to external entity in attribute value
…cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6327,
Column 1120:
reference to entity "MarketPlace" for which no system identifier could be generated
…cw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%…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 6323,
Column 275:
entity was defined here
…n=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=ss_til&ad_……viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 1126:
reference to external entity in attribute value
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 1126:
reference to entity "ID" for which no system identifier could be generated
…viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8010…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 6327,
Column 330:
entity was defined here
…ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Flawgunandmon-20%2F8……-3436-4571-9358-59968bdcac46&Operation=NoScript">Amazon.com Widgets</A></NOSCR…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 6327,
Column 1215:
reference to external entity in attribute value
…-3436-4571-9358-59968bdcac46&Operation=NoScript">Amazon.com Widgets</A></NOSCR…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 6327,
Column 1215:
reference to entity "Operation" for which no system identifier could be generated
…-3436-4571-9358-59968bdcac46&Operation=NoScript">Amazon.com Widgets</A></NOSCR…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 6323,
Column 255:
entity was defined here
…gets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&sour……571-9358-59968bdcac46&Operation=NoScript">Amazon.com Widgets</A></NOSCRIPT></p>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6332,
Column 56:
cannot generate system identifier for general entity "z"
…://www.lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></sc…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 6332,
Column 56:
general entity "z" not defined and no default entity
…://www.lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></sc…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 6332,
Column 57:
reference not terminated by REFC delimiter
…//www.lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></scr…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 6332,
Column 57:
reference to external entity in attribute value
…//www.lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></scr…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 6332,
Column 57:
reference to entity "z" for which no system identifier could be generated
…//www.lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></scr…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 6332,
Column 55:
entity was defined here
…p://www.lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></s……ijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></script></d…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 6332,
Column 64:
general entity "n" not defined and no default entity
…ijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></script></d…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 6332,
Column 65:
reference not terminated by REFC delimiter
…jit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></script></di…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 6332,
Column 65:
reference to external entity in attribute value
…jit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></script></di…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 6332,
Column 65:
reference to entity "n" for which no system identifier could be generated
…jit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></script></di…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 6332,
Column 63:
entity was defined here
…lijit.com/delivery/fp?u=farlio&z=58835&n=1" type="text/javascript"></script></……s1-1001" class="cpi cpi-s1" affiliate="" tracking="lefarkins" color="" source=…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 6334,
Column 186:
there is no attribute "tracking"
…ss="cpi cpi-s1" affiliate="" tracking="lefarkins" color="" source="shop:lefark…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 6334,
Column 204:
there is no attribute "color"
…filiate="" tracking="lefarkins" color="" source="shop:lefarkins" width="160" h…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 6334,
Column 214:
there is no attribute "source"
… tracking="lefarkins" color="" source="shop:lefarkins" width="160" height="200…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 6334,
Column 237:
there is no attribute "width"
…olor="" source="shop:lefarkins" width="160" height="200">Make <a href="ht…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 6334,
Column 250:
there is no attribute "height"
…e="shop:lefarkins" width="160" height="200">Make <a href="http://www.cafe…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 6340,
Column 196:
required attribute "alt" not specified
…tent/uploads/2012/09/oldfashionedrevisedandsharpened-e1348603402357.jpg"></div>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6340,
Column 202:
end tag for "img" omitted, but OMITTAG NO was specified
…tent/uploads/2012/09/oldfashionedrevisedandsharpened-e1348603402357.jpg"></div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6340,
Column 72:
start tag was here
…dget_text"> <div class="textwidget"><img src="http://www.lawyersgunsmoneyblo……an></h3> <div class="textwidget"><li><A href="http://delong.typepad.com/">Br…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 6471,
Column 133:
there is no attribute "href"
… <div class="textwidget"><li><A href="http://delong.typepad.com/">Brad Delong…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 6471,
Column 161:
element "A" undefined
…lass="textwidget"><li><A href="http://delong.typepad.com/">Brad Delong</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6472,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://www.crookedtimber.org/">Crooked Timber</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6472,
Column 44:
element "A" undefined
<li><A href="http://www.crookedtimber.org/">Crooked Timber</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6473,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://dailykos.com/">Daily Kos</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6473,
Column 35:
element "A" undefined
<li><A href="http://dailykos.com/">Daily Kos</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6474,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://www.wired.com/dangerroom/">Danger Room</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6474,
Column 47:
element "A" undefined
<li><A href="http://www.wired.com/dangerroom/">Danger Room</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6475,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://www.eschatonblog.com/">Eschaton</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6475,
Column 43:
element "A" undefined
<li><A href="http://www.eschatonblog.com/">Eschaton</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6476,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://voices.washingtonpost.com/ezra-klein/">Ezra Klein</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6476,
Column 59:
element "A" undefined
<li><A href="http://voices.washingtonpost.com/ezra-klein/">Ezra Klein</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6477,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://feministe.us/blog/">Feministe</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6477,
Column 40:
element "A" undefined
<li><A href="http://feministe.us/blog/">Feministe</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6478,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://talkingpointsmemo.com/">Talking Points Memo</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6478,
Column 44:
element "A" undefined
<li><A href="http://talkingpointsmemo.com/">Talking Points Memo</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6479,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://feministing.com/">Feministing</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6479,
Column 38:
element "A" undefined
<li><A href="http://feministing.com/">Feministing</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6480,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://www.salon.com/opinion/greenwald/">Glenn Greenwald</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6480,
Column 54:
element "A" undefined
<li><A href="http://www.salon.com/opinion/greenwald/">Glenn Greenwald</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6481,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://juancole.com/">Juan Cole</A></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6481,
Column 35:
element "A" undefined
<li><A href="http://juancole.com/">Juan Cole</A></li>You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6482,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><A href="http://www.themonkeycage.org/">Monkey Cage</A></li> The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 6482,
Column 44:
element "A" undefined
<li><A href="http://www.themonkeycage.org/">Monkey Cage</A></li> You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 6487,
Column 203:
required attribute "alt" not specified
…prose"><img src="http://www.blogads.com/advertise/the_liberal_prose/logo" ></a>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 6487,
Column 207:
end tag for "img" omitted, but OMITTAG NO was specified
…prose"><img src="http://www.blogads.com/advertise/the_liberal_prose/logo" ></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6487,
Column 136:
start tag was here
…gads.com/advertise/the_liberal_prose"><img src="http://www.blogads.com/adverti…</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6487,
Column 72:
start tag was here
…dget_text"> <div class="textwidget"><p><a href="http://web.blogads.com/adver…</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6487,
Column 48:
start tag was here
…ext-21" class="widget widget_text"> <div class="textwidget"><p><a href="http…</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 6487,
Column 1:
start tag was here
<li id="text-21" class="widget widget_text"> <div class="textwidget"><p><a hr… </li>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 6492,
Column 9:
end tag for element "ul" which is not open
</ul>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 6501,
Column 10:
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 6507,
Column 10:
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 6535,
Column 6:
end tag for element "div" which is not open
</div>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
