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.
Character Encoding Override in effect!
The detected character encoding
"utf-8"
has been suppressed and
"iso-8859-1" used instead.
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 5,
Column 47:
invalid comment declaration: found delimiter "[" outside comment but inside comment declaration
<!--[if gt IE 8]> <html class="no-js"> <!--[endif]-->
Line 5,
Column 1:
comment declaration started here
<!--[if gt IE 8]> <html class="no-js"> <!--[endif]--> <head> <head>
Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
<html xmlns="http://www.w3.org/1999/xhtml">
Line 7,
Column 19:
there is no attribute "charset"
<meta charset="utf-8" />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 7,
Column 28:
required attribute "content" not specified
<meta charset="utf-8" />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 17,
Column 49:
"correio" is not a member of a group specified for any attribute
…="keywords" content="viactt, "correio digital", "pagamento faturas", ctt, "cor……rds" content="viactt, "correio digital", "pagamento faturas", ctt, "correio se…
Have you forgotten the "equal" sign marking the separation
between the attribute and its declared value?
Typical syntax is attribute="value".
Line 17,
Column 57:
end tag for "meta" omitted, but OMITTAG NO was specified
…ds" content="viactt, "correio digital", "pagamento faturas", ctt, "correio sem…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 17,
Column 1:
start tag was here
<meta name="keywords" content="viactt, "correio digital", "pagamento faturas", ……ds" content="viactt, "correio digital", "pagamento faturas", ctt, "correio sem…You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 18,
Column 16:
there is no attribute "property"
<meta property="og:description" content="Crie uma caixa de correio digital segu…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 33,
Column 7:
invalid comment declaration: found delimiter "[" outside comment but inside comment declaration
<!--[endif]--> <!--[if lt IE 9]><link rel="apple-touch-icon" sizes="57x57" href="/application/themes/images/ico…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 48,
Column 7:
required attribute "type" not specified
<style>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 67,
Column 16:
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 77,
Column 87:
"async" is not a member of a group specified for any attribute
…c='//grmtech.net/r/pt44c4c17332cace2124a1a836d9fc4b6f.js' async defer></script>…c='//grmtech.net/r/pt44c4c17332cace2124a1a836d9fc4b6f.js' async defer></script>"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.
How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
Line 77,
Column 92:
required attribute "type" not specified
…c='//grmtech.net/r/pt44c4c17332cace2124a1a836d9fc4b6f.js' async defer></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 83,
Column 84:
"data-widget-cookie-warning" is not a member of a group specified for any attribute
… <div id="cookie-warning" data-widget-cookie-warning> <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 110,
Column 15:
there is no attribute "class"
<header class="page-header particulares" role="banner">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 110,
Column 47:
there is no attribute "role"
<header class="page-header particulares" role="banner">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 110,
Column 55:
element "header" undefined
<header class="page-header particulares" role="banner">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 115,
Column 116:
end tag for "img" omitted, but OMITTAG NO was specified
…ulares/index"><img src="/application/themes/images/logo-ctt.svg" alt="CTT"></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 115,
Column 52:
start tag was here
… <a href="/particulares/index"><img src="/application/themes/images/log……nav-toggle" href="#main-nav-mobile" class="nav-toggle" data-main-nav-toggle="">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 121,
Column 65:
"data-primary-nav-back" is not a member of a group specified for any attribute
<a href="#" class="mobile-back-button" data-primary-nav-back> <div class="nav-mobile" id="main-nav-mobile" data-main-nav-content> <nav class="primary-nav nav-drop-wrap" role="navigation">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 126,
Column 49:
there is no attribute "role"
<nav class="primary-nav nav-drop-wrap" role="navigation">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 126,
Column 61:
element "nav" undefined
<nav class="primary-nav nav-drop-wrap" role="navigation">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 130,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3">…f="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e embal…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 154,
Column 102:
general entity "categoryCode" not defined and no default entity
…f="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e embal…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 154,
Column 114:
reference not terminated by REFC delimiter
…e/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e embalagens</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 154,
Column 114:
reference to external entity in attribute value
…e/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e embalagens</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 154,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
…e/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e embalagens</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba… <article>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 193,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3">…tegory.jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber cor…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 220,
Column 114:
reference to external entity in attribute value
…tegory.jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber cor…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 220,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
…tegory.jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber cor…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 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba…….jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber correio</…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 220,
Column 120:
general entity "showAll" not defined and no default entity
….jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber correio</…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 220,
Column 127:
reference not terminated by REFC delimiter
…jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber correio</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 220,
Column 127:
reference to external entity in attribute value
…jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber correio</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 220,
Column 127:
reference to entity "showAll" for which no system identifier could be generated
…jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber correio</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 220,
Column 119:
entity was defined here
…y.jspx?shopCode=LOJV&categoryCode=9854&showAll=1">Caixas para receber correio<… <article>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 259,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3"> <article>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 313,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3"> <article>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 367,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3">…femce/category.jspx?shopCode=LOJV&categoryCode=0002">Comprar na Loja Online</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 405,
Column 114:
reference to external entity in attribute value
…femce/category.jspx?shopCode=LOJV&categoryCode=0002">Comprar na Loja Online</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 405,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
…femce/category.jspx?shopCode=LOJV&categoryCode=0002">Comprar na Loja Online</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba…… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">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 411,
Column 318:
general entity "itemCode" not defined and no default entity
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">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 411,
Column 326:
reference not terminated by REFC delimiter
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">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 411,
Column 326:
reference to external entity in attribute value
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">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 411,
Column 326:
reference to entity "itemCode" for which no system identifier could be generated
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">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 411,
Column 317:
entity was defined here
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599"> <article>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 424,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3">…"/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Correio e encomendas</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 436,
Column 114:
reference to external entity in attribute value
…"/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Correio e encomendas</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 436,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
…"/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Correio e encomendas</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba……mce/category.jspx?shopCode=LOJV&categoryCode=0002">Filatelia e colecionismo</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 439,
Column 114:
reference to external entity in attribute value
…mce/category.jspx?shopCode=LOJV&categoryCode=0002">Filatelia e colecionismo</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 439,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
…mce/category.jspx?shopCode=LOJV&categoryCode=0002">Filatelia e colecionismo</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba…… <a href="/femce/category.jspx?shopCode=LOJV&categoryCode=0004">Presentes</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 442,
Column 114:
reference to external entity in attribute value
… <a href="/femce/category.jspx?shopCode=LOJV&categoryCode=0004">Presentes</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 442,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
… <a href="/femce/category.jspx?shopCode=LOJV&categoryCode=0004">Presentes</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba… <article>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 478,
Column 112:
"data-drilldown-nav" is not a member of a group specified for any attribute
… <li data-drilldown-nav class="has-drop drop-grid-3">… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1200000">Festival</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 490,
Column 114:
reference to external entity in attribute value
… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1200000">Festival</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 490,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1200000">Festival</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba…… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1500000">Música</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 493,
Column 114:
reference to external entity in attribute value
… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1500000">Música</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 493,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1500000">Música</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba…… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1800000">Aventura</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 496,
Column 114:
reference to external entity in attribute value
… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1800000">Aventura</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 496,
Column 114:
reference to entity "categoryCode" for which no system identifier could be generated
… <a href="/feblh/category.jspx?shopCode=BLHT&categoryCode=1800000">Aventura</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba……/feblh/sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000…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 504,
Column 105:
reference to external entity in attribute value
…/feblh/sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000…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 504,
Column 105:
reference to entity "itemCode" for which no system identifier could be generated
…/feblh/sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000…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 411,
Column 317:
entity was defined here
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">…ku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">…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 504,
Column 113:
general entity "idShow" not defined and no default entity
…ku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">…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 504,
Column 119:
reference not terminated by REFC delimiter
…x?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">NOS Al…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 504,
Column 119:
reference to external entity in attribute value
…x?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">NOS Al…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 504,
Column 119:
reference to entity "idShow" for which no system identifier could be generated
…x?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">NOS Al…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 504,
Column 112:
entity was defined here
…sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022"……e=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">NOS Alive'20</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 504,
Column 139:
reference to external entity in attribute value
…e=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">NOS Alive'20</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 504,
Column 139:
reference to entity "categoryCode" for which no system identifier could be generated
…e=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022">NOS Alive'20</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba……/feblh/sku.jspx?shopCode=BLHT&itemCode=174919&idShow=174919&categoryCode=25000…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 507,
Column 105:
reference to external entity in attribute value
…/feblh/sku.jspx?shopCode=BLHT&itemCode=174919&idShow=174919&categoryCode=25000…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 507,
Column 105:
reference to entity "itemCode" for which no system identifier could be generated
…/feblh/sku.jspx?shopCode=BLHT&itemCode=174919&idShow=174919&categoryCode=25000…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 411,
Column 317:
entity was defined here
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">…x?shopCode=BLHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns N…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 507,
Column 119:
reference to external entity in attribute value
…x?shopCode=BLHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns N…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 507,
Column 119:
reference to entity "idShow" for which no system identifier could be generated
…x?shopCode=BLHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns 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 504,
Column 112:
entity was defined here
…sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022"……LHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns Nâ Roses</a>If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 507,
Column 139:
reference to external entity in attribute value
…LHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns Nâ Roses</a>This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 507,
Column 139:
reference to entity "categoryCode" for which no system identifier could be generated
…LHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns Nâ Roses</a>This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba……/feblh/sku.jspx?shopCode=BLHT&itemCode=174129&idShow=174129&categoryCode=25000…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 510,
Column 105:
reference to external entity in attribute value
…/feblh/sku.jspx?shopCode=BLHT&itemCode=174129&idShow=174129&categoryCode=25000…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 510,
Column 105:
reference to entity "itemCode" for which no system identifier could be generated
…/feblh/sku.jspx?shopCode=BLHT&itemCode=174129&idShow=174129&categoryCode=25000…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 411,
Column 317:
entity was defined here
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">…x?shopCode=BLHT&itemCode=174129&idShow=174129&categoryCode=25000000619">Harry …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 510,
Column 119:
reference to external entity in attribute value
…x?shopCode=BLHT&itemCode=174129&idShow=174129&categoryCode=25000000619">Harry …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 510,
Column 119:
reference to entity "idShow" for which no system identifier could be generated
…x?shopCode=BLHT&itemCode=174129&idShow=174129&categoryCode=25000000619">Harry …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 504,
Column 112:
entity was defined here
…sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022"……Code=174129&idShow=174129&categoryCode=25000000619">Harry Potter The Exhibitio…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 510,
Column 139:
reference to external entity in attribute value
…Code=174129&idShow=174129&categoryCode=25000000619">Harry Potter The Exhibitio…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 510,
Column 139:
reference to entity "categoryCode" for which no system identifier could be generated
…Code=174129&idShow=174129&categoryCode=25000000619">Harry Potter The Exhibitio…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 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba……/feblh/sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000…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 516,
Column 326:
reference to external entity in attribute value
…/feblh/sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000…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 516,
Column 326:
reference to entity "itemCode" for which no system identifier could be generated
…/feblh/sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000…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 411,
Column 317:
entity was defined here
… <a href="/femce/sku.jspx?shopCode=LOJV&itemCode=20203519599">…sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000000275">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 516,
Column 340:
reference to external entity in attribute value
…sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000000275">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 516,
Column 340:
reference to entity "idShow" for which no system identifier could be generated
…sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000000275">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 504,
Column 112:
entity was defined here
…sku.jspx?shopCode=BLHT&itemCode=174128&idShow=174128&categoryCode=25000000022"……sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000000275">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 516,
Column 360:
reference to external entity in attribute value
…sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000000275">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 516,
Column 360:
reference to entity "categoryCode" for which no system identifier could be generated
…sku.jspx?shopCode=BLHT&itemCode=175134&idShow=175134&categoryCode=25000000275">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 154,
Column 101:
entity was defined here
…ef="/femce/category.jspx?shopCode=LOJV&categoryCode=5261">Comprar selos e emba… <article>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 529,
Column 39:
"data-drilldown-nav" is not a member of a group specified for any attribute
<li data-drilldown-nav id="tools" class="has-drop drop-grid-1"> <a href> <li data-drilldown-nav class="has-drop drop-grid-3 hide-for-large-up"> <nav class="secondary-nav nav-drop-wrap">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 606,
Column 44:
"data-drilldown-nav" is not a member of a group specified for any attribute
<li class="has-drop" data-drilldown-nav> <a href><span>Particulares</span></a>… <a id="segments-nav-toggle" href="#" class="nav-toggle" data-nav-drop-close> <input type="hidden" id="hidden_lang" value="1555597541833"> <input type="hidden" id="hidden_lang" value="1555597541833">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 624,
Column 8:
start tag was here
<input type="hidden" id="hidden_lang" value="1555597541833">… <li id="s-nav-user" class="has-drop" data-drilldown-nav data-dropdown-desktop>… <li id="s-nav-user" class="has-drop" data-drilldown-nav data-dropdown-desktop>… <li id="s-nav-user" class="has-drop" data-drilldown-nav data-dropdown-desktop>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 626,
Column 42:
cannot generate system identifier for general entity "redirect"
… <a href="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Cont…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 626,
Column 42:
general entity "redirect" not defined and no default entity
… <a href="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Cont…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 626,
Column 50:
reference not terminated by REFC delimiter
…f="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Conta</span>…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 626,
Column 50:
reference to external entity in attribute value
…f="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Conta</span>…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 626,
Column 50:
reference to entity "redirect" for which no system identifier could be generated
…f="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Conta</span>…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 626,
Column 41:
entity was defined here
… <a href="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Con… <a id="segments-nav-toggle" href="#" class="nav-toggle" data-nav-drop…An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 610,
Column 14:
ID "segments-nav-toggle" first defined here
<a id="segments-nav-toggle" href="#" class="nav-toggle" data-nav-drop-clo……<a id="segments-nav-toggle" href="#" class="nav-toggle" data-nav-drop-close="">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 638,
Column 87:
reference not terminated by REFC delimiter
…serEnrollAction.jspx?lang=def&redirect=" id="nav-user-register">Faça o seu re…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 638,
Column 87:
reference to external entity in attribute value
…serEnrollAction.jspx?lang=def&redirect=" id="nav-user-register">Faça o seu re…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 638,
Column 87:
reference to entity "redirect" for which no system identifier could be generated
…serEnrollAction.jspx?lang=def&redirect=" id="nav-user-register">Faça o seu 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 626,
Column 41:
entity was defined here
… <a href="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Con……erProfileAction.jspx?lang=def&redirect=" class="primary-link" id="nav-user-edi…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 649,
Column 91:
reference to external entity in attribute value
…erProfileAction.jspx?lang=def&redirect=" class="primary-link" id="nav-user-edi…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 649,
Column 91:
reference to entity "redirect" for which no system identifier could be generated
…erProfileAction.jspx?lang=def&redirect=" class="primary-link" id="nav-user-edi…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 626,
Column 41:
entity was defined here
… <a href="/femgu/login.jspx?lang=def&redirect=/particulares/index"><span>Con… <li id="s-nav-help">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 658,
Column 63:
"data-dropdown-desktop" is not a member of a group specified for any attribute
<li id="s-nav-lang" class="has-drop" data-dropdown-desktop> <li id="s-nav-lang" class="has-drop" data-dropdown-desktop>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 667,
Column 94:
"data-dropdown" is not a member of a group specified for any attribute
… <li id="s-nav-search" class="has-drop" data-dropdown>… <li id="s-nav-search" class="has-drop" data-dropdown>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 672,
Column 27:
value of attribute "type" cannot be "search"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
<input type="search" id="header-search-input" name="q" class="storenav-s…
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 672,
Column 105:
there is no attribute "placeholder"
…s="storenav-search-input" placeholder='Insira os termos de pesquisa' autocompl…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 672,
Column 149:
there is no attribute "autocomplete"
…av-search-input" placeholder='Insira os termos de pesquisa' autocomplete="off">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 672,
Column 155:
end tag for "input" omitted, but OMITTAG NO was specified
…av-search-input" placeholder='Insira os termos de pesquisa' autocomplete="off">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 672,
Column 8:
start tag was here
<input type="search" id="header-search-input" name="q" class="storenav-s… <input type="submit" value='Pesquisa' hidden>"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.
How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
Line 673,
Column 52:
duplicate specification of attribute "type"
<input type="submit" value='Pesquisa' hidden>
You have specified an attribute more than once. Example: Using
the "height" attribute twice on the same
"img" tag.
Line 673,
Column 53:
end tag for "input" omitted, but OMITTAG NO was specified
<input type="submit" value='Pesquisa' hidden>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 673,
Column 8:
start tag was here
<input type="submit" value='Pesquisa' hidden> <a href="#" data-nav-drop-close><i class="ctt-icon-menu-close"></i></a> </ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 624,
Column 8:
start tag was here
<input type="hidden" id="hidden_lang" value="1555597541833"> <ul class="slides" data-orbit> <div class="caption-button-wrap" data-button-app="">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 713,
Column 99:
"data-stick" is not a member of a group specified for any attribute
…ass="contextnav collapsible" role="navigation" data-stick data-collapsible="" >…ass="contextnav collapsible" role="navigation" data-stick data-collapsible="" >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 713,
Column 119:
element "nav" undefined
…ass="contextnav collapsible" role="navigation" data-stick data-collapsible="" >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 719,
Column 14:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li class="">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 743,
Column 23:
end tag for "li" omitted, but OMITTAG NO was specified
</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 717,
Column 3:
start tag was here
<li class="contextnav-title"><a href="">ViaCTT</a>… <section class="product-benefits" style="min-height:aut…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 750,
Column 88:
there is no attribute "style"
… <section class="product-benefits" style="min-height:auto">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 750,
Column 105:
element "section" undefined
… <section class="product-benefits" style="min-height:auto">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 762,
Column 10:
element "figure" undefined
<figure>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 763,
Column 125:
end tag for "img" omitted, but OMITTAG NO was specified
…e21-468f-b0c6-3a33c1e528aa/imagem/0102fdc0-59b3-4dc4-a070-20504ea9ab1e" alt="">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 763,
Column 3:
start tag was here
<img src="/contentAsset/raw-data/3170337f-1e21-468f-b0c6-3a33c1e528aa/imagem/… </section><section class="product-how-it-works alt-background">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 797,
Column 52:
element "section" undefined
</section><section class="row product-faqs section">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 802,
Column 66:
"data-accordion" is not a member of a group specified for any attribute
… <dl class="accordion" data-accordion aria-multiselectable="true">… <dl class="accordion" data-accordion aria-multiselectable="true">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 880,
Column 49:
element "section" undefined
</section><section class="banner-card-button ">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 883,
Column 19:
there is no attribute "class"
<article class="card">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 883,
Column 25:
element "article" undefined
<article class="card">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 899,
Column 59:
element "section" undefined
</section> <section class="product-text-section">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 901,
Column 27:
element "header" undefined
<header class="column">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 913,
Column 44:
there is no attribute "id"
… <footer id="page-footer" class="small-container">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 913,
Column 64:
there is no attribute "class"
… <footer id="page-footer" class="small-container">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 913,
Column 81:
element "footer" undefined
… <footer id="page-footer" class="small-container">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 924,
Column 61:
"data-accordion" is not a member of a group specified for any attribute
<dl class="accordion column show-for-small" data-accordion>…oogle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaigni…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 954,
Column 103:
general entity "id" not defined and no default entity
…oogle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaigni…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 954,
Column 105:
reference not terminated by REFC delimiter
…gle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=…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 954,
Column 105:
reference to external entity in attribute value
…gle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=…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 954,
Column 105:
reference to entity "id" for which no system identifier could be generated
…gle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=…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 954,
Column 102:
entity was defined here
…google.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaign……l=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtn…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 954,
Column 133:
general entity "pcampaignid" not defined and no default entity
…l=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtn…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 954,
Column 144:
reference not terminated by REFC delimiter
…ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBa…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 954,
Column 144:
reference to external entity in attribute value
…ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBa…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 954,
Column 144:
reference to entity "pcampaignid" for which no system identifier could be generated
…ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBa…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 954,
Column 132:
entity was defined here
…hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prt……ef="https://www.bancoctt.pt" target="_blank" target="_blank">Banco CTT</a></li>
You have specified an attribute more than once. Example: Using
the "height" attribute twice on the same
"img" tag.
Line 967,
Column 154:
duplicate specification of attribute "target"
… <li><a href="https://dott.pt/" target="_blank" target="_blank">Dott</a></li>
You have specified an attribute more than once. Example: Using
the "height" attribute twice on the same
"img" tag.
Line 968,
Column 165:
duplicate specification of attribute "target"
…tps://www.cttexpress.com/" target="_blank" target="_blank">CTT Express</a></li>
You have specified an attribute more than once. Example: Using
the "height" attribute twice on the same
"img" tag.
Line 991,
Column 105:
reference not terminated by REFC delimiter
…gle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=…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 991,
Column 105:
reference to external entity in attribute value
…gle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=…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 991,
Column 105:
reference to entity "id" for which no system identifier could be generated
…gle.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=…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 954,
Column 102:
entity was defined here
…google.com/store/apps/details?hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaign……ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBa…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 991,
Column 144:
reference to external entity in attribute value
…ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBa…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 991,
Column 144:
reference to entity "pcampaignid" for which no system identifier could be generated
…ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBa…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 954,
Column 132:
entity was defined here
…hl=pt-pt&id=ctt.mobile.android.app.ctt&pcampaignid=MKT-Other-global-all-co-prt……os/livro_reclamacoes_bw.png" alt="livroreclamacoes" class="logo-complaints bw">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 1029,
Column 6:
start tag was here
<img src="/application/themes/images/footer_logos/livro_reclamacoes_bw.png……os/livro_reclamacoes.png" alt="livroreclamacoes" class="logo-complaints hover">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 1030,
Column 6:
start tag was here
<img src="/application/themes/images/footer_logos/livro_reclamacoes.png" a…