Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 10,
Column 84:
end tag for "link" omitted, but OMITTAG NO was specified
….hupso.com/share/js/share_toolbar.js"><link rel="preconnect" href="https://sta…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 10,
Column 1:
start tag was here
<link rel="dns-prefetch" href="https://static.hupso.com/share/js/share_toolbar.…….hupso.com/share/js/share_toolbar.js"><link rel="preload" href="https://static…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 10,
Column 84:
start tag was here
….hupso.com/share/js/share_toolbar.js"><link rel="preconnect" href="https://sta…….hupso.com/share/js/share_toolbar.js"><link rel="alternate" type="application/…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 10,
Column 165:
start tag was here
….hupso.com/share/js/share_toolbar.js"><link rel="preload" href="https://static…
Line 54,
Column 1415:
cannot generate system identifier for general entity "d"
…4c0dcdbcb0c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}…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 54,
Column 1415:
general entity "d" not defined and no default entity
…4c0dcdbcb0c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}…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 54,
Column 1416:
reference not terminated by REFC delimiter
…c0dcdbcb0c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}…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 54,
Column 1416:
reference to entity "d" for which no system identifier could be generated
…c0dcdbcb0c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}…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 54,
Column 1414:
entity was defined here
…/4c0dcdbcb0c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96……c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}}</script>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 54,
Column 1427:
general entity "r" not defined and no default entity
…c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}}</script>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 54,
Column 1428:
reference not terminated by REFC delimiter
…c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}}</script>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 54,
Column 1428:
reference to entity "r" for which no system identifier could be generated
…c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}}</script>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 54,
Column 1426:
entity was defined here
…c97ff70ed8ea358ce7d35c?s=96&d=identicon&r=g","height":96,"width":96}}}</script><script async src="https://www.googletagmanager.com/gtag/js?id=UA-130212153-1">……sync src="https://www.googletagmanager.com/gtag/js?id=UA-130212153-1"></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 62,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 69,
Column 39:
required attribute "type" not specified
<script src="/custom/scripts.js?v=021"></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 70,
Column 121:
end tag for "link" omitted, but OMITTAG NO was specified
…mily=Open+Sans+Condensed:700|Open+Sans:400,700|Special+Elite" rel="stylesheet">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 70,
Column 1:
start tag was here
<link href="//fonts.googleapis.com/css?family=Open+Sans+Condensed:700|Open+Sans…<meta name="viewport" content="width=device-width" id="tubViewport">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 71,
Column 1:
start tag was here
<meta name="viewport" content="width=device-width" id="tubViewport">…unker.png" width="280" height="60" border="0" alt="The Underground Bunker"></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 86,
Column 13:
start tag was here
<a href="/"><img src="//tonyortega.org/wp-content/uploads/2018/12/the_undergrou……iv class="adbannerHead"><script async src="//pagead2.googlesyndication.com/pag…… async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.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 91,
Column 16:
there is no attribute "data-ad-client"
data-ad-client="ca-pub-3646955839994638"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 92,
Column 14:
there is no attribute "data-ad-slot"
data-ad-slot="7356419147"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 93,
Column 16:
there is no attribute "data-ad-format"
data-ad-format="horizontal"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 94,
Column 28:
there is no attribute "data-full-width-responsive"
data-full-width-responsive="true"></ins>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 95,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 131,
Column 117:
required attribute "alt" not specified
…alt="M"/></div><a href="/"><img src="/i/m_logo.png" id="mobile_logo"></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 131,
Column 121:
end tag for "img" omitted, but OMITTAG NO was specified
…alt="M"/></div><a href="/"><img src="/i/m_logo.png" id="mobile_logo"></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 131,
Column 76:
start tag was here
…ile_1.png" alt="M"/></div><a href="/"><img src="/i/m_logo.png" id="mobile_logo……/icon_fb.png?v=001" alt="facebook"></a><a href="https://twitter.com/TonyOrtega…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 133,
Column 73:
start tag was here
…//www.facebook.com/TonyOrtegaWriter/"><img src="/i/icon_fb.png?v=001" alt="fac……itter.com/TonyOrtega94"><img src="/i/icon_t.png?v=001" alt="twitter"></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 133,
Column 167:
start tag was here
…ef="https://twitter.com/TonyOrtega94"><img src="/i/icon_t.png?v=001" alt="twit……ss="textwidget"><div class="widg-title">SUPPORT THE<br>UNDERGROUND BUNKER</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 177,
Column 165:
start tag was here
…ss="textwidget"><div class="widg-title">SUPPORT THE<br>UNDERGROUND BUNKER</div>…ttps://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="6"><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 180,
Column 1:
start tag was here
<img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif…<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 181,
Column 1:
start tag was here
<input type="hidden" name="cmd" value="_s-xclick"><input type="hidden" name="hosted_button_id" value="5S2T4ZNR6Y3PA">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 182,
Column 1:
start tag was here
<input type="hidden" name="hosted_button_id" value="5S2T4ZNR6Y3PA">…donate_LG.gif" alt="PayPal - The safer, easier way to pay online!" border="0">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 183,
Column 165:
end tag for "input" omitted, but OMITTAG NO was specified
…donate_LG.gif" alt="PayPal - The safer, easier way to pay online!" border="0">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 183,
Column 1:
start tag was here
<input name="submit" type="image" src="https://www.paypalobjects.com/en_US/i/bt……ttps://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"></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 184,
Column 1:
start tag was here
<img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif…<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 187,
Column 1:
start tag was here
<input type="hidden" name="cmd" value="_s-xclick"><input type="hidden" name="hosted_button_id" value="ZV8XMSVBFH7X8">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 188,
Column 1:
start tag was here
<input type="hidden" name="hosted_button_id" value="ZV8XMSVBFH7X8"><tr><td><input type="hidden" name="on0" value="Payment options">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 190,
Column 9:
start tag was here
<tr><td><input type="hidden" name="on0" value="Payment options"></select> </div> <img alt="" border="0" src="https://www.paypalobjects.com/en_U…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 191,
Column 92:
start tag was here
…n subscribe and get billed monthly: </div></td></tr><tr><td><select name="os0"></select> </div> <img alt="" border="0" src="https://www.paypalobjects.com/en_U…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 191,
Column 88:
start tag was here
…n subscribe and get billed monthly: </div></td></tr><tr><td><select name="os0"></select> </div> <img alt="" border="0" src="https://www.paypalobjects.com/en_U…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 189,
Column 1:
start tag was here
<table></select> </div> <img alt="" border="0" src="https://www.paypalobjects.com/en_U…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 186,
Column 1:
start tag was here
<form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top……//www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="10"></td></tr>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 196,
Column 18:
start tag was here
</select> </div> <img alt="" border="0" src="https://www.paypalobjects.com/en_U……//www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="10"></td></tr>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 177,
Column 14:
start tag was here
</form></div><div id="duplicate_widget-8" class=" text-14 widget_text widget wi…<input type="hidden" name="currency_code" value="USD">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 198,
Column 1:
start tag was here
<input type="hidden" name="currency_code" value="USD">….gif" alt="PayPal - The safer, easier way to pay online!" border="0"></valign>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 199,
Column 160:
end tag for "input" omitted, but OMITTAG NO was specified
….gif" alt="PayPal - The safer, easier way to pay online!" border="0"></valign>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 199,
Column 1:
start tag was here
<input name="submit" type="image" src="//tonyortega.org/img/paypal_subscribe-on……rc="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="20">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 200,
Column 1:
start tag was here
<img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif…</form></div>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 202,
Column 332:
value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
…eight="32" border="0" align="absmiddle"></a> <a href="https://twitter.com/Tony…
The value of the attribute is defined to be one of a list of possible
values but in the document it contained something that is not allowed
for that type of attribute. For instance, the “selected” attribute must be either
minimized as “selected”
or spelled out in full as “selected="selected"”; a value like
“selected="true"” is not
allowed.
Line 202,
Column 333:
required attribute "alt" not specified
…ight="32" border="0" align="absmiddle"></a> <a href="https://twitter.com/TonyO…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 202,
Column 337:
end tag for "img" omitted, but OMITTAG NO was specified
…="32" border="0" align="absmiddle"></a> <a href="https://twitter.com/TonyOrteg…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 202,
Column 228:
start tag was here
…om/pages/Tony-Ortega/196428147077253"><img src="https://tonyortega.org/i/icon_……png?v=001" width="32" height="32" border="0" align="absmiddle"></a></div></div>
The value of the attribute is defined to be one of a list of possible
values but in the document it contained something that is not allowed
for that type of attribute. For instance, the “selected” attribute must be either
minimized as “selected”
or spelled out in full as “selected="selected"”; a value like
“selected="true"” is not
allowed.
Line 202,
Column 486:
required attribute "alt" not specified
…png?v=001" width="32" height="32" border="0" align="absmiddle"></a></div></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 202,
Column 490:
end tag for "img" omitted, but OMITTAG NO was specified
…png?v=001" width="32" height="32" border="0" align="absmiddle"></a></div></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 202,
Column 382:
start tag was here
…ef="https://twitter.com/TonyOrtega94"><img src="https://tonyortega.org/i/icon_……http://www.amazon.com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=178…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 203,
Column 186:
general entity "tag" not defined and no default entity
…http://www.amazon.com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=178…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 203,
Column 189:
reference not terminated by REFC delimiter
…p://www.amazon.com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&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 203,
Column 189:
reference to external entity in attribute value
…p://www.amazon.com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&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 203,
Column 189:
reference to entity "tag" for which no system identifier could be generated
…p://www.amazon.com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&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 203,
Column 185:
entity was defined here
…"http://www.amazon.com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=17……om/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" re…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 203,
Column 205:
general entity "linkCode" not defined and no default entity
…om/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" re…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 203,
Column 213:
reference not terminated by REFC delimiter
…oding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noope…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 203,
Column 213:
reference to external entity in attribute value
…oding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noope…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 203,
Column 213:
reference to entity "linkCode" for which no system identifier could be generated
…oding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noope…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 203,
Column 204:
entity was defined here
…com/?_encoding=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" r……=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener n…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 203,
Column 218:
general entity "camp" not defined and no default entity
…=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener n…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 203,
Column 222:
reference not terminated by REFC delimiter
…8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noref…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 203,
Column 222:
reference to external entity in attribute value
…8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noref…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 203,
Column 222:
reference to entity "camp" for which no system identifier could be generated
…8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noref…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 203,
Column 217:
entity was defined here
…g=UTF8&tag=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener ……theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noreferrer"…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 203,
Column 228:
general entity "creative" not defined and no default entity
…theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noreferrer"…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 203,
Column 236:
reference not terminated by REFC delimiter
…unk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noreferrer"><img sr…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 203,
Column 236:
reference to external entity in attribute value
…unk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noreferrer"><img sr…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 203,
Column 236:
reference to entity "creative" for which no system identifier could be generated
…unk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noreferrer"><img sr…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 203,
Column 227:
entity was defined here
…=theundebunk-20&linkCode=ur2&camp=1789&creative=9325" rel="noopener noreferrer……ssoc-amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="…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 203,
Column 472:
general entity "l" not defined and no default entity
…ssoc-amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="…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 203,
Column 473:
reference not terminated by REFC delimiter
…soc-amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="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 203,
Column 473:
reference to external entity in attribute value
…soc-amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="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 203,
Column 473:
reference to entity "l" for which no system identifier could be generated
…soc-amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="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 203,
Column 471:
entity was defined here
…assoc-amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border=……mazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="0" alt…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 203,
Column 478:
general entity "o" not defined and no default entity
…mazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="0" alt…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 203,
Column 479:
reference not terminated by REFC delimiter
…azon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="0" alt=…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 203,
Column 479:
reference to external entity in attribute value
…azon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="0" alt=…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 203,
Column 479:
reference to entity "o" for which no system identifier could be generated
…azon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="0" alt=…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 203,
Column 477:
entity was defined here
…amazon.com/e/ir?t=theundebunk-20&l=ur2&o=1" width="1" height="1" border="0" al…<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 414,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 418,
Column 5:
end tag for element "td" which is not open
</td>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 421,
Column 16:
document type does not allow element "td" here
<td id="middle">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 424,
Column 493:
there is no attribute "srcset"
…lt="" width="300" height="168" srcset="https://tonyortega.org/wp-content/uploa…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 424,
Column 664:
there is no attribute "sizes"
…nixthemaster1-300x168.jpg 300w" sizes="(max-width: 300px) 100vw, 300px" /></a>…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 424,
Column 3289:
character "&" is the first character of a delimiter but occurred as data
… false;" title="Printer Friendly, PDF & Email"><img style="border:none;-webkit…This message may appear in several cases:
Line 424,
Column 3511:
character "&" is the first character of a delimiter but occurred as data
…on-nobg.png" alt="Print Friendly, PDF & Email" /></a></div></div></div> <…This message may appear in several cases:
Line 432,
Column 16:
there is no attribute "data-ad-layout"
data-ad-layout="in-article"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 436,
Column 8:
required attribute "type" not specified
<script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 459,
Column 5:
end tag for element "tr" which is not open
</tr>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 461,
Column 4:
document type does not allow element "tr" here; assuming missing "table" start-tag
<tr><script async src='https://cdn.printfriendly.com/printfriendly.js'></script><script async src='https://cdn.printfriendly.com/printfriendly.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 497,
Column 6:
end tag for element "div" which is not open
</div><!-- / container -->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 498,
Column 6:
end tag for element "div" which is not open
</div><!-- / wrapper -->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 499,
Column 30:
required attribute "type" not specified
<script language="javascript">The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Below is the source input I used for this validation:
