Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 143,
Column 155:
there is no attribute "size"
…amareleja.drealentejo.pt/"><font size="2">http://agvamareleja.drealentejo.pt/<…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 143,
Column 158:
element "font" undefined
…releja.drealentejo.pt/"><font size="2">http://agvamareleja.drealentejo.pt/</fo…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 169,
Column 215:
there is no attribute "face"
…t-align: center;"><font size="6" face="Alba Super" color="#3399ff"><img src="h…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 169,
Column 234:
there is no attribute "color"
…font size="6" face="Alba Super" color="#3399ff"><img src="http://agvamareleja.…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 169,
Column 243:
element "font" undefined
…="6" face="Alba Super" color="#3399ff"><img src="http://agvamareleja.drealente…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 169,
Column 364:
there is no attribute "border"
…g" alt="escola" title="escola" border="0" hspace="0" vspace="0" width="497" he…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 169,
Column 375:
there is no attribute "hspace"
…ola" title="escola" border="0" hspace="0" vspace="0" width="497" height="200" …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 169,
Column 386:
there is no attribute "vspace"
…"escola" border="0" hspace="0" vspace="0" width="497" height="200" /><br /></f…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 169,
Column 484:
element "font" undefined
…="6" face="Alba Super" color="#3399ff"><marquee scrolldelay="215" scrollamount…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 169,
Column 506:
there is no attribute "scrolldelay"
… color="#3399ff"><marquee scrolldelay="215" scrollamount="10">Agrupamento de E…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 169,
Column 525:
there is no attribute "scrollamount"
…arquee scrolldelay="215" scrollamount="10">Agrupamento de Escolas de Amareleja…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 169,
Column 529:
element "marquee" undefined
…ee scrolldelay="215" scrollamount="10">Agrupamento de Escolas de Amareleja - A…You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 171,
Column 33:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
<div style="text-align: center;"><span class="label"><font size="3"><span style…The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 171,
Column 68:
element "font" undefined
…r;"><span class="label"><font size="3"><span style="color: rgb(0, 0, 153); fon…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 209,
Column 785:
there is no attribute "src"
…lock"><div class="content"><embed src="http://www.clocklink.com/clocks/bloguru…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 209,
Column 855:
character "&" is the first character of a delimiter but occurred as data
…/bloguru003-black.swf?TimeZone=GMT0100&" width="150" height="150" wmode="tran…This message may appear in several cases:
Line 209,
Column 865:
there is no attribute "width"
…3-black.swf?TimeZone=GMT0100&" width="150" height="150" wmode="transparent" t…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 209,
Column 878:
there is no attribute "height"
…imeZone=GMT0100&" width="150" height="150" wmode="transparent" type="applicat…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 209,
Column 890:
there is no attribute "wmode"
…100&" width="150" height="150" wmode="transparent" type="application/x-shockw…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 209,
Column 909:
there is no attribute "type"
…height="150" wmode="transparent" type="application/x-shockwave-flash"></div></…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 209,
Column 940:
element "embed" undefined
…" type="application/x-shockwave-flash"></div></div><script type="text/javascri…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 209,
Column 946:
end tag for "embed" omitted, but OMITTAG NO was specified
…ype="application/x-shockwave-flash"></div></div><script type="text/javascript">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 209,
Column 774:
start tag was here
…_html sideblock"><div class="content"><embed src="http://www.clocklink.com/clo……object width="180" height="138" align="top" data="http://netweather.accuweathe…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 263,
Column 592:
cannot generate system identifier for general entity "myspace"
…" /> <param value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=E…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 263,
Column 592:
general entity "myspace" not defined and no default entity
…" /> <param value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=E…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 263,
Column 599:
reference not terminated by REFC delimiter
…aram value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|P…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 599:
reference to external entity in attribute value
…aram value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|P…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 599:
reference to entity "myspace" for which no system identifier could be generated
…aram value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|P…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 263,
Column 591:
entity was defined here
…r" /> <param value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=……m value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO00…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 263,
Column 602:
general entity "logo" not defined and no default entity
…m value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO00…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 263,
Column 606:
reference not terminated by REFC delimiter
…lue="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MO…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 606:
reference to external entity in attribute value
…lue="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MO…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 606:
reference to entity "logo" for which no system identifier could be generated
…lue="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MO…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 263,
Column 601:
entity was defined here
…am value="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO0……="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA…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 263,
Column 609:
general entity "tStyle" not defined and no default entity
…="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA…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 263,
Column 615:
reference not terminated by REFC delimiter
…ner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 615:
reference to external entity in attribute value
…ner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 615:
reference to entity "tStyle" for which no system identifier could be generated
…ner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang…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 263,
Column 608:
entity was defined here
…e="partner=netweather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOUR……eather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&siz…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 263,
Column 623:
general entity "zipcode" not defined and no default entity
…eather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&siz…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 263,
Column 630:
reference not terminated by REFC delimiter
…myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&th…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 630:
reference to external entity in attribute value
…myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&th…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 630:
reference to entity "zipcode" for which no system identifier could be generated
…myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&th…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 263,
Column 622:
entity was defined here
…weather&myspace=1&logo=1&tStyle=normal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&si……ormal&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="fla…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 660:
cannot generate system identifier for general entity "size"
…&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvar…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 263,
Column 660:
general entity "size" not defined and no default entity
…&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvar…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 263,
Column 664:
reference not terminated by REFC delimiter
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" /…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 664:
reference to external entity in attribute value
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" /…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 664:
reference to entity "size" for which no system identifier could be generated
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" /…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 263,
Column 659:
entity was defined here
…l&zipcode=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashva……code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />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 263,
Column 668:
general entity "theme" not defined and no default entity
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />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 263,
Column 673:
reference not terminated by REFC delimiter
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 673:
reference to external entity in attribute value
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 673:
reference to entity "theme" for which no system identifier could be generated
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />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 263,
Column 667:
entity was defined here
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />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 263,
Column 676:
general entity "metric" not defined and no default entity
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />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 263,
Column 682:
reference not terminated by REFC delimiter
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 263,
Column 682:
reference to external entity in attribute value
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 263,
Column 682:
reference to entity "metric" for which no system identifier could be generated
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />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 263,
Column 675:
entity was defined here
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />…index-forecast.asp?partner=netweather&locCode=EUR|PT|PO003|MOURA|&metric=1" st…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 265,
Column 205:
general entity "locCode" not defined and no default entity
…index-forecast.asp?partner=netweather&locCode=EUR|PT|PO003|MOURA|&metric=1" st…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 265,
Column 212:
reference not terminated by REFC delimiter
…orecast.asp?partner=netweather&locCode=EUR|PT|PO003|MOURA|&metric=1" style="co…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 265,
Column 212:
reference to external entity in attribute value
…orecast.asp?partner=netweather&locCode=EUR|PT|PO003|MOURA|&metric=1" style="co…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 265,
Column 212:
reference to entity "locCode" for which no system identifier could be generated
…orecast.asp?partner=netweather&locCode=EUR|PT|PO003|MOURA|&metric=1" style="co…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 265,
Column 204:
entity was defined here
…-index-forecast.asp?partner=netweather&locCode=EUR|PT|PO003|MOURA|&metric=1" s……her&locCode=EUR|PT|PO003|MOURA|&metric=1" style="color: rgb(0, 0, 255);">Weath…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 265,
Column 239:
reference to external entity in attribute value
…her&locCode=EUR|PT|PO003|MOURA|&metric=1" style="color: rgb(0, 0, 255);">Weath…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 265,
Column 239:
reference to entity "metric" for which no system identifier could be generated
…her&locCode=EUR|PT|PO003|MOURA|&metric=1" style="color: rgb(0, 0, 255);">Weath…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 263,
Column 675:
entity was defined here
…code=EUR|PT|PO003|MOURA|&lang=esp&size=28&theme=1&metric=1" name="flashvars" />Below is the source input I used for this validation:
