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.
DOCTYPE Override in effect!
The detected DOCTYPE Declaration
"<!DOCTYPE HTML>" has been
suppressed and the DOCTYPE for
"XHTML 1.0 Transitional" inserted instead,
but even if no errors are shown below the document will not be Valid
until you update it to reflect this new DOCTYPE.
Line 25,
Column 69:
document type does not allow element "a" here
… <a id="foxyform_embed_link_180169" href="http://fr.foxyform.com/">foxyform</a>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 26,
Column 34:
document type does not allow element "script" here
<script type="text/javascript">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 30,
Column 56:
cannot generate system identifier for general entity "sec_hash"
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 56:
general entity "sec_hash" not defined and no default entity
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 64:
reference not terminated by REFC delimiter
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 64:
reference to entity "sec_hash" for which no system identifier could be generated
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 55:
entity was defined here
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 77:
general entity "width" not defined and no default entity
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 82:
reference not terminated by REFC delimiter
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 82:
reference to entity "width" for which no system identifier could be generated
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px";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 30,
Column 76:
entity was defined here
…c = "http://fr.foxyform.com/js.php?id=180169&sec_hash=ccb8eeadc83&width=350px"; </head>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
Line 44,
Column 89:
there is no attribute "data-cd"
…s://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Accueil_principal" data-cd="PageLink">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 45,
Column 88:
required attribute "alt" not specified
…img style="width:100%;height:100%;border:none" src="WEFiles/Image/empty.png" />The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 107,
Column 88:
required attribute "alt" not specified
…img style="width:100%;height:100%;border:none" src="WEFiles/Image/empty.png" />The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 114,
Column 58:
end tag for "input" omitted, but OMITTAG NO was specified
<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 114,
Column 8:
start tag was here
<input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="U3YEYTPQTCENS">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 115,
Column 8:
start tag was here
<input type="hidden" name="hosted_button_id" value="U3YEYTPQTCENS">…/FR/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal, le réflex…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 116,
Column 178:
end tag for "input" omitted, but OMITTAG NO was specified
…border="0" name="submit" alt="PayPal, le réflexe sécurité pour payer en ligne">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 116,
Column 8:
start tag was here
<input type="image" src="https://www.paypalobjects.com/fr_FR/FR/i/btn/bt……src="https://www.paypalobjects.com/fr_FR/i/scr/pixel.gif" width="1" height="1">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 117,
Column 8:
start tag was here
<img alt="" border="0" src="https://www.paypalobjects.com/fr_FR/i/scr/pi… <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 124,
Column 8:
start tag was here
<input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="ZKVW48RZQEVHN">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 125,
Column 8:
start tag was here
<input type="hidden" name="hosted_button_id" value="ZKVW48RZQEVHN">…bmit" alt="PayPal - A forma mais fácil e segura de efetuar pagamentos online!">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 126,
Column 8:
start tag was here
<input type="image" src="https://www.paypalobjects.com/pt_PT/PT/i/btn/bt……src="https://www.paypalobjects.com/fr_FR/i/scr/pixel.gif" width="1" height="1">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 127,
Column 8:
start tag was here
<img alt="" border="0" src="https://www.paypalobjects.com/fr_FR/i/scr/pi……rc="WEFiles/Image/empty.png" style="width:100%;height:100%;border:none;" alt />…rc="WEFiles/Image/empty.png" style="width:100%;height:100%;border:none;" alt />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>.
