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
"HTML 4.01 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]--> <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 27:
NET-enabling start-tag requires SHORTTAG YES
<meta charset="utf-8" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 7,
Column 27:
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 7,
Column 28:
character data is not allowed here
<meta charset="utf-8" />You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 8,
Column 67:
NET-enabling start-tag requires SHORTTAG YES
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 9,
Column 75:
NET-enabling start-tag requires SHORTTAG YES
<meta content="width=device-width, initial-scale=1.0" name="viewport" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 10,
Column 94:
NET-enabling start-tag requires SHORTTAG YES
…gle-site-verification" content="Sza3VcE6z1e36W0o9PEw9KUouxK1-NlmCfjK2v7gW5U" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 15,
Column 129:
NET-enabling start-tag requires SHORTTAG YES
… correio digital segura, funcional e com valor legal com o serviço ViaCTT." />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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 56:
document type does not allow element "META" here
…rds" content="viactt, "correio digital", "pagamento faturas", ctt, "correio se…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 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 18,
Column 136:
NET-enabling start-tag requires SHORTTAG YES
… correio digital segura, funcional e com valor legal com o serviço ViaCTT." />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 18,
Column 136:
document type does not allow element "META" here
… correio digital segura, funcional e com valor legal com o serviço ViaCTT." />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 19,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
<meta property="og:site_name" content="CTT" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 19,
Column 45:
document type does not allow element "META" here
<meta property="og:site_name" content="CTT" />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 20,
Column 44:
NET-enabling start-tag requires SHORTTAG YES
<meta property="og:type" content="website" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 20,
Column 44:
document type does not allow element "META" here
<meta property="og:type" content="website" />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 21,
Column 44:
NET-enabling start-tag requires SHORTTAG YES
<meta property="og:title" content="ViaCTT" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 21,
Column 44:
document type does not allow element "META" here
<meta property="og:title" content="ViaCTT" />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 23,
Column 97:
NET-enabling start-tag requires SHORTTAG YES
…"og:url" content="https://www.ctt.pt:443/particulares/receber/viactt/index?" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 23,
Column 97:
document type does not allow element "META" here
…"og:url" content="https://www.ctt.pt:443/particulares/receber/viactt/index?" />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 24,
Column 77:
NET-enabling start-tag requires SHORTTAG YES
<meta property="og:image" content="/application/themes/images/og-image.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 24,
Column 77:
document type does not allow element "META" here
<meta property="og:image" content="/application/themes/images/og-image.png" /> 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 33,
Column 7:
invalid comment declaration: found delimiter "[" outside comment but inside comment declaration
<!--[endif]--> <!--[if lt IE 9]>…/www.ctt.pt/application/themes/images/icons/favicon.ico" type="image/x-icon" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 35,
Column 125:
document type does not allow element "LINK" here
…/www.ctt.pt/application/themes/images/icons/favicon.ico" type="image/x-icon" />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 36,
Column 91:
NET-enabling start-tag requires SHORTTAG YES
…ple-touch-icon" href="/application/themes/images/icons/apple-touch-icon.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 36,
Column 91:
document type does not allow element "LINK" here
…ple-touch-icon" href="/application/themes/images/icons/apple-touch-icon.png" />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 37,
Column 36:
there is no attribute "SIZES"
<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 37,
Column 111:
NET-enabling start-tag requires SHORTTAG YES
…s="57x57" href="/application/themes/images/icons/apple-touch-icon-57x57.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 37,
Column 111:
document type does not allow element "LINK" here
…s="57x57" href="/application/themes/images/icons/apple-touch-icon-57x57.png" />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 38,
Column 111:
NET-enabling start-tag requires SHORTTAG YES
…s="60x60" href="/application/themes/images/icons/apple-touch-icon-60x60.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 38,
Column 111:
document type does not allow element "LINK" here
…s="60x60" href="/application/themes/images/icons/apple-touch-icon-60x60.png" />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 39,
Column 111:
NET-enabling start-tag requires SHORTTAG YES
…s="72x72" href="/application/themes/images/icons/apple-touch-icon-72x72.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 39,
Column 111:
document type does not allow element "LINK" here
…s="72x72" href="/application/themes/images/icons/apple-touch-icon-72x72.png" />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 40,
Column 111:
NET-enabling start-tag requires SHORTTAG YES
…s="76x76" href="/application/themes/images/icons/apple-touch-icon-76x76.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 40,
Column 111:
document type does not allow element "LINK" here
…s="76x76" href="/application/themes/images/icons/apple-touch-icon-76x76.png" />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 41,
Column 115:
NET-enabling start-tag requires SHORTTAG YES
…14x114" href="/application/themes/images/icons/apple-touch-icon-114x114.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 41,
Column 115:
document type does not allow element "LINK" here
…14x114" href="/application/themes/images/icons/apple-touch-icon-114x114.png" />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 42,
Column 115:
NET-enabling start-tag requires SHORTTAG YES
…20x120" href="/application/themes/images/icons/apple-touch-icon-120x120.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 42,
Column 115:
document type does not allow element "LINK" here
…20x120" href="/application/themes/images/icons/apple-touch-icon-120x120.png" />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 43,
Column 115:
NET-enabling start-tag requires SHORTTAG YES
…44x144" href="/application/themes/images/icons/apple-touch-icon-144x144.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 43,
Column 115:
document type does not allow element "LINK" here
…44x144" href="/application/themes/images/icons/apple-touch-icon-144x144.png" />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 44,
Column 115:
NET-enabling start-tag requires SHORTTAG YES
…x152" href="/application/themes/images/icons/apple-touch-icon-152x152.png" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 44,
Column 115:
document type does not allow element "LINK" here
…x152" href="/application/themes/images/icons/apple-touch-icon-152x152.png" /> 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 45,
Column 106:
NET-enabling start-tag requires SHORTTAG YES
…t" href="/application/themes/css/app.min.css?t=173711022020" type="text/css" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 45,
Column 106:
document type does not allow element "LINK" here
…t" href="/application/themes/css/app.min.css?t=173711022020" type="text/css" />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 46,
Column 101:
NET-enabling start-tag requires SHORTTAG YES
…href="/application/themes/css/banner-fix.css?t=154807052020" type="text/css" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 46,
Column 101:
document type does not allow element "LINK" here
…href="/application/themes/css/banner-fix.css?t=154807052020" type="text/css" />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 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 48,
Column 7:
document type does not allow element "STYLE" here
<style>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 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>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 78,
Column 9:
end tag for element "HEAD" which is not open
</head>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 79,
Column 23:
document type does not allow element "BODY" here
<body class="floating">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 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 118,
Column 95:
there is no attribute "DATA-MAIN-NAV-TOGGLE"
…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 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 184,
Column 158:
NET-enabling start-tag requires SHORTTAG YES
…db6c5a0f588b/image/enviar-expresso-para-hoje-270-120.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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…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 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 250,
Column 161:
NET-enabling start-tag requires SHORTTAG YES
…6e3b8a94c/image/destaque-header-270-120ctt24h FEV20a.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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 304,
Column 151:
NET-enabling start-tag requires SHORTTAG YES
…b-b0c2-a7ceec79e3f4/image/sem-sair-casa-sofa-270x120.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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 358,
Column 166:
NET-enabling start-tag requires SHORTTAG YES
…8d34/image/pagamentos-matriculas-portuguesas_270-120.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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>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 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 415,
Column 153:
NET-enabling start-tag requires SHORTTAG YES
…af04-8a067a29d122/image/destaque-header-Livro-Museus.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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>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>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>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 469,
Column 142:
NET-enabling start-tag requires SHORTTAG YES
…-c755-4711-8099-586281a10574/image/obrigados-270-120.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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>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>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>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…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 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>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…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…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>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……LHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns Nâ Roses</a>You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.
Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.
This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.
Line 507,
Column 161:
non SGML character number 153
…LHT&itemCode=174919&idShow=174919&categoryCode=25000000022">Guns Nâ Roses</a>You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.
Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.
This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.
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 …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…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…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">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">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 520,
Column 136:
NET-enabling start-tag requires SHORTTAG YES
…04d708-53ea-4569-8dc2-b94981ad4354/image/destaquebil.jpg?byInode=true" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
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">… <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>… <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 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 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…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-lang" class="has-drop" data-dropdown-desktop>… <li id="s-nav-search" class="has-drop" data-dropdown> <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 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 674,
Column 39:
"DATA-NAV-DROP-CLOSE" is not a member of a group specified for any attribute
<a href="#" data-nav-drop-close><i class="ctt-icon-menu-close"></i></a> <ul class="slides" data-orbit>…8-92ee-e7036affecea/imagemBanner/7b928170-f014-4c49-8612-114f89582c12" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 700,
Column 70:
there is no attribute "DATA-BUTTON-APP"
<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 750,
Column 63:
there is no attribute "CLASS"
… <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 765,
Column 64:
element "SECTION" undefined
</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 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 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 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…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…