Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Mismatch between Public and System identifiers in the DOCTYPE declaration
This document uses an inconsistent DOCTYPE declaration.
The Public Identifier
-//W3C//DTD XHTML 1.0 Transitional//EN declares the
XHTML 1.0 Transitional document type, but the associated System Identifier
https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd does not match this document type.
The recommended System Identifier
for XHTML 1.0 Transitional is http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd.
The safest way to use a correct DOCTYPE declaration is to copy and paste one from the recommended list and avoid editing that part of your markup by hand.
Line 2,
Column 43:
value of fixed attribute "xmlns" not equal to default
<html xmlns="https://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US"><html xmlns="https://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US"><script type="text/javascript" async src="https://static.addtoany.com/menu/page…<script type="text/javascript" async src="https://meria.net/wp-content/plugins/…<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 126,
Column 92:
required attribute "alt" not specified
…> <a href="/"><img src="/header.png" width="960" height="174" border="0" /></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 139,
Column 16:
syntax of attribute value does not conform to declared value
<ul id="" class="">
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 197,
Column 16:
syntax of attribute value does not conform to declared value
<ul id="" class="">
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 227,
Column 246:
there is no attribute "decoding"
…-thumb wp-post-image" alt="" decoding="async" loading="lazy" srcset="https://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 227,
Column 262:
there is no attribute "loading"
…mage" alt="" decoding="async" loading="lazy" srcset="https://meria.net/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 227,
Column 276:
there is no attribute "srcset"
…ecoding="async" loading="lazy" srcset="https://meria.net/wp-content/uploads/20…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 227,
Column 597:
there is no attribute "sizes"
…06/ALFRED_WEBRE-125-42x42.jpg 42w" sizes="(max-width: 90px) 100vw, 90px" /></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 362,
Column 298:
there is no attribute "fetchpriority"
…"entry-thumb wp-post-image" alt="" decoding="async" fetchpriority="high" /></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 370,
Column 243:
end tag for element "span" which is not open
…ia-with-dr-barry-krakow-life-saving-sleep/#respond">0 comment</a></span></span>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 383,
Column 219:
end tag for element "span" which is not open
…/meria.net/2024/02/meria-with-the-news-61/#respond">0 comment</a></span></span>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 396,
Column 219:
end tag for element "span" which is not open
…/meria.net/2024/02/meria-with-the-news-60/#respond">0 comment</a></span></span>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 409,
Column 245:
end tag for element "span" which is not open
…-and-hope-with-meria-and-richard-grove-20/#respond">0 comment</a></span></span>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 422,
Column 219:
end tag for element "span" which is not open
…/meria.net/2024/01/meria-with-the-news-59/#respond">0 comment</a></span></span>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 430,
Column 195:
value of attribute "method" cannot be "POST"; must be one of "get", "post"
…ginform" id="loginform" action="https://meria.net/amember/login" method="POST">
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 432,
Column 104:
end tag for "input" omitted, but OMITTAG NO was specified
…t type="text" name="amember_login" class="input" id="user_login" size="15"></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 432,
Column 21:
start tag was here
<input type="text" name="amember_login" class="input" id="u……="password" name="amember_pass" id="user_password" class="input" size="15"></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 434,
Column 17:
start tag was here
<input type="password" name="amember_pass" id="user_password" c……"hidden" name="_amember_redirect_url" value="aHR0cHM6Ly9tZXJpYS5uZXQ6NDQzLw==">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 435,
Column 33:
start tag was here
<input type="hidden" name="_amember_redirect_ur…… <input type="submit" name="wp-submit" id="wp-submit" value="Login">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 437,
Column 21:
start tag was here
<input type="submit" name="wp-submit" id="wp-submit" value=……"/private-consultations-with-meria/"><img src="/consultations.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 962,
Column 14:
there is no attribute "color"
<hr color="#f0f0f0" style="height:1px; width:600px" />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 963,
Column 16:
there is no attribute "ALIGN"
<DIV ALIGN=CENTER>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 963,
Column 16:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<DIV ALIGN=CENTER> <DIV ALIGN=CENTER>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 965,
Column 51:
end tag for "input" omitted, but OMITTAG NO was specified
<input type="hidden" value="_s-xclick" name="cmd">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 965,
Column 1:
start tag was here
<input type="hidden" value="_s-xclick" name="cmd"><input type="hidden" value="G8N9ZB73Q2K9N" name="hosted_button_id">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 966,
Column 1:
start tag was here
<input type="hidden" value="G8N9ZB73Q2K9N" name="hosted_button_id">…="https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif" name="submit">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 967,
Column 1:
start tag was here
<input type="image" alt="PayPal - The safer, easier way to pay online!" src="ht……1" border="0" alt="" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif">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 968,
Column 1:
start tag was here
<img width="1" height="1" border="0" alt="" src="https://www.paypalobjects.com/……nsultations-with-meria/" target="_blank"><IMG border=0 src="/readings.jpg"></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 974,
Column 74:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…nsultations-with-meria/" target="_blank"><IMG border=0 src="/readings.jpg"></a>…nsultations-with-meria/" target="_blank"><IMG border=0 src="/readings.jpg"></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 974,
Column 95:
element "IMG" undefined
…nsultations-with-meria/" target="_blank"><IMG border=0 src="/readings.jpg"></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 974,
Column 99:
end tag for "IMG" omitted, but OMITTAG NO was specified
…nsultations-with-meria/" target="_blank"><IMG border=0 src="/readings.jpg"></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 974,
Column 62:
start tag was here
…nsultations-with-meria/" target="_blank"><IMG border=0 src="/readings.jpg"></a><td><img src="/apple-footer.gif" width="150" height="50" /></td>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 995,
Column 100:
required attribute "alt" not specified
…/merias-books/"><img src="/book.gif" width="550" height="100" border="0" /></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 998,
Column 53:
cannot generate system identifier for general entity "tag"
…//www.amazon.com//ref=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creativ…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 998,
Column 53:
general entity "tag" not defined and no default entity
…//www.amazon.com//ref=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creativ…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 998,
Column 56:
reference not terminated by REFC delimiter
…ww.amazon.com//ref=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=4…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 998,
Column 56:
reference to external entity in attribute value
…ww.amazon.com//ref=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=4…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 998,
Column 56:
reference to entity "tag" for which no system identifier could be generated
…ww.amazon.com//ref=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=4…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 998,
Column 52:
entity was defined here
…://www.amazon.com//ref=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creati……=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1…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 998,
Column 74:
general entity "camp" not defined and no default entity
…=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1…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 998,
Column 78:
reference not terminated by REFC delimiter
…sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adi…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 998,
Column 78:
reference to external entity in attribute value
…sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adi…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 998,
Column 78:
reference to entity "camp" for which no system identifier could be generated
…sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adi…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 998,
Column 73:
entity was defined here
…f=as_sl_pc_tf_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur……_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG…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 998,
Column 86:
general entity "creative" not defined and no default entity
…_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG…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 998,
Column 94:
reference not terminated by REFC delimiter
…=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB…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 998,
Column 94:
reference to external entity in attribute value
…=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB…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 998,
Column 94:
reference to entity "creative" for which no system identifier could be generated
…=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB…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 998,
Column 85:
entity was defined here
…f_lc?&tag=meriahellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2E……llerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&…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 998,
Column 102:
general entity "linkCode" not defined and no default entity
…llerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&…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 998,
Column 110:
reference not terminated by REFC delimiter
…0&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refU…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 998,
Column 110:
reference to external entity in attribute value
…0&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refU…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 998,
Column 110:
reference to entity "linkCode" for which no system identifier could be generated
…0&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refU…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 998,
Column 101:
entity was defined here
…ellerco-20&camp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&……p=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=ht…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 998,
Column 115:
general entity "adid" not defined and no default entity
…p=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=ht…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 998,
Column 119:
reference not terminated by REFC delimiter
…6797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 998,
Column 119:
reference to external entity in attribute value
…6797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 998,
Column 119:
reference to entity "adid" for which no system identifier could be generated
…6797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 998,
Column 114:
entity was defined here
…mp=216797&creative=493965&linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=h……linkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-…This message may appear in several cases:
Line 998,
Column 142:
cannot generate system identifier for general entity "ref-refURL"
…nkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-ad…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 998,
Column 142:
general entity "ref-refURL" not defined and no default entity
…nkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-ad…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 998,
Column 152:
reference not terminated by REFC delimiter
…&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-adsystem.com…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 998,
Column 152:
reference to external entity in attribute value
…&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-adsystem.com…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 998,
Column 152:
reference to entity "ref-refURL" for which no system identifier could be generated
…&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-adsystem.com…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 998,
Column 141:
entity was defined here
…inkCode=ur1&adid=02R2EG9DA94BBB8W75Z5&&ref-refURL=http%3A%2F%2Frcm-na.amazon-a……ank"><img src="/amazon.png" width="180" height="150" style="border:none;"></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 998,
Column 407:
end tag for "img" omitted, but OMITTAG NO was specified
…ank"><img src="/amazon.png" width="180" height="150" style="border:none;"></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 998,
Column 334:
start tag was here
…D%3DV3DZCKGUSULPQBKH" target="_blank"><img src="/amazon.png" width="180" heigh……="_blank"><img src="/silverlungs.gif" width="550" height="100" border="0"> </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 1015,
Column 118:
end tag for "img" omitted, but OMITTAG NO was specified
…="_blank"><img src="/silverlungs.gif" width="550" height="100" border="0"> </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 1015,
Column 54:
start tag was here
…/www.silverlungs.com" target="_blank"><img src="/silverlungs.gif" width="550" …</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 963,
Column 5:
start tag was here
<DIV ALIGN=CENTER></div> <!--end #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.
