Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 62,
Column 19:
there is no attribute "crossorigin"
<link crossorigin='anonymous' rel='stylesheet' id='all-css-0-1' href='https://s…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 62,
Column 265:
cannot generate system identifier for general entity "cssminify"
…NORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='al…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 62,
Column 265:
general entity "cssminify" not defined and no default entity
…NORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='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 62,
Column 274:
reference not terminated by REFC delimiter
…HDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='all' />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 62,
Column 274:
reference to external entity in attribute value
…HDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='all' />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 62,
Column 274:
reference to entity "cssminify" for which no system identifier could be generated
…HDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a…<style id='wp-emoji-styles-inline-css'>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 274:
reference not terminated by REFC delimiter
…/CbISc+CT3583M1/NMg6zGbc3O1tP4A==&cssminify=yes' type='text/css' media='all' />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 77,
Column 274:
reference to external entity in attribute value
…/CbISc+CT3583M1/NMg6zGbc3O1tP4A==&cssminify=yes' type='text/css' media='all' />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 77,
Column 274:
reference to entity "cssminify" for which no system identifier could be generated
…/CbISc+CT3583M1/NMg6zGbc3O1tP4A==&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a…<style id='wp-block-library-inline-css'>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 84,
Column 222:
reference not terminated by REFC delimiter
…D5sM02efaGpoZmFkYGRuZGmQBAHPvL0Y=&cssminify=yes' type='text/css' media='all' />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 84,
Column 222:
reference to external entity in attribute value
…D5sM02efaGpoZmFkYGRuZGmQBAHPvL0Y=&cssminify=yes' type='text/css' media='all' />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 84,
Column 222:
reference to entity "cssminify" for which no system identifier could be generated
…D5sM02efaGpoZmFkYGRuZGmQBAHPvL0Y=&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a…<style id='jetpack-sharing-buttons-style-inline-css'>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 88,
Column 44:
required attribute "type" not specified
<style id='classic-theme-styles-inline-css'>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 92,
Column 233:
reference not terminated by REFC delimiter
…-premium-themes.css?m=1432920480j&cssminify=yes' type='text/css' media='all' />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 92,
Column 233:
reference to external entity in attribute value
…-premium-themes.css?m=1432920480j&cssminify=yes' type='text/css' media='all' />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 92,
Column 233:
reference to entity "cssminify" for which no system identifier could be generated
…-premium-themes.css?m=1432920480j&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a…<style id='global-styles-inline-css'>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 99,
Column 259:
reference not terminated by REFC delimiter
…Kj4Qbz3X5rtd2meLhHOPpOMXHB5BCPss=&cssminify=yes' type='text/css' media='all' />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 99,
Column 259:
reference to external entity in attribute value
…Kj4Qbz3X5rtd2meLhHOPpOMXHB5BCPss=&cssminify=yes' type='text/css' media='all' />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 99,
Column 259:
reference to entity "cssminify" for which no system identifier could be generated
…Kj4Qbz3X5rtd2meLhHOPpOMXHB5BCPss=&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a……/global-print.css?m=1465851035i&cssminify=yes' type='text/css' media='print' />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 100,
Column 167:
reference to external entity in attribute value
…/global-print.css?m=1465851035i&cssminify=yes' type='text/css' media='print' />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 100,
Column 167:
reference to entity "cssminify" for which no system identifier could be generated
…/global-print.css?m=1465851035i&cssminify=yes' type='text/css' media='print' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a…<style id='jetpack-global-styles-frontend-style-inline-css'>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 104,
Column 275:
reference not terminated by REFC delimiter
…bSKznwK/DsR787Kd5P/ntbnkAuNBIYA==&cssminify=yes' type='text/css' media='all' />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 104,
Column 275:
reference to external entity in attribute value
…bSKznwK/DsR787Kd5P/ntbnkAuNBIYA==&cssminify=yes' type='text/css' media='all' />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 104,
Column 275:
reference to entity "cssminify" for which no system identifier could be generated
…bSKznwK/DsR787Kd5P/ntbnkAuNBIYA==&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a…<script crossorigin='anonymous' type='text/javascript' src='https://s1.wp.com/…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 127,
Column 16:
there is no attribute "property"
<meta property="og:type" content="website" />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 92:
there is no attribute "sizes"
…icon" href="https://s1.wp.com/i/favicon.ico" sizes="16x16 24x24 32x32 48x48" />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 174,
Column 139:
character ";" not allowed in attribute specification list
…tring"==typeof a?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a))……tring"==typeof a?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,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 174,
Column 153:
character "&" is the first character of a delimiter but occurred as data
… a?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a)){b=e;break a}b…This message may appear in several cases:
Line 174,
Column 155:
cannot generate system identifier for general entity "b.call"
…?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a)){b=e;break a}b=-…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 174,
Column 155:
general entity "b.call" not defined and no default entity
…?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a)){b=e;break a}b=-…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 174,
Column 161:
reference not terminated by REFC delimiter
…it(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a)){b=e;break a}b=-1}retu…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 174,
Column 161:
reference to entity "b.call" for which no system identifier could be generated
…it(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a)){b=e;break a}b=-1}retu…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 174,
Column 154:
entity was defined here
…a?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a)){b=e;break a}b=……g(c)):"";if(b+=c){c=a.indexOf("#");0>c&&(c=a.length);var d=a.indexOf("?");if(0…This message may appear in several cases:
Line 174,
Column 345:
character "&" is the first character of a delimiter but occurred as data
…(c)):"";if(b+=c){c=a.indexOf("#");0>c&&(c=a.length);var d=a.indexOf("?");if(0>…This message may appear in several cases:
Line 174,
Column 483:
character "&" is the first character of a delimiter but occurred as data
…,d),e,a.substr(c)];c=a[1];a[1]=b?c?c+"&"+b:b:c;a=a[0]+(a[1]?"?"+a[1]:"")+a[2]}…This message may appear in several cases:
Line 174,
Column 625:
character "&" is the first character of a delimiter but occurred as data
…script");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("…This message may appear in several cases:
Line 174,
Column 627:
cannot generate system identifier for general entity "b"
…ript");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("er…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 174,
Column 627:
general entity "b" not defined and no default entity
…ript");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("er…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 174,
Column 628:
reference not terminated by REFC delimiter
…ipt");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("err…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 174,
Column 628:
reference to entity "b" for which no system identifier could be generated
…ipt");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("err…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 174,
Column 626:
entity was defined here
…cript");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("e……){b&&b(void 0)};c.onerror=function(){b&&b("error")};a=document.getElementsByTa…This message may appear in several cases:
Line 174,
Column 663:
reference not terminated by REFC delimiter
…&&b(void 0)};c.onerror=function(){b&&b("error")};a=document.getElementsByTagNa…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 174,
Column 663:
reference to entity "b" for which no system identifier could be generated
…&&b(void 0)};c.onerror=function(){b&&b("error")};a=document.getElementsByTagNa…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 174,
Column 626:
entity was defined here
…cript");c.src=a;c.onload=function(){b&&b(void 0)};c.onerror=function(){b&&b("e……t.getElementsByTagName("head");var d;a&&0!==a.length?d=a[0]:d=document.documen…This message may appear in several cases:
Line 174,
Column 722:
character "&" is the first character of a delimiter but occurred as data
….getElementsByTagName("head");var d;a&&0!==a.length?d=a[0]:d=document.document…This message may appear in several cases:
Line 174,
Column 960:
character "&" is the first character of a delimiter but occurred as data
…+"=")}))?b.split("=")[1]:""}function p(a){return"string"==typeof a&&0<a.length}This message may appear in several cases:
Line 174,
Column 961:
character "&" is the first character of a delimiter but occurred as data
…+"=")}))?b.split("=")[1]:""}function p(a){return"string"==typeof a&&0<a.length}This message may appear in several cases:
Line 174,
Column 972:
character "}" not allowed in attribute specification list
…+"=")}))?b.split("=")[1]:""}function p(a){return"string"==typeof a&&0<a.length}…+"=")}))?b.split("=")[1]:""}function p(a){return"string"==typeof a&&0<a.length}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 175,
Column 135:
character "&" is the first character of a delimiter but occurred as data
…n(e){var f=a[e],q=typeof f;"object"==q&&null!=f||"function"==q?d.push(r(f,b+e+…This message may appear in several cases:
Line 175,
Column 137:
cannot generate system identifier for general entity "null"
…e){var f=a[e],q=typeof f;"object"==q&&null!=f||"function"==q?d.push(r(f,b+e+c)…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 175,
Column 137:
general entity "null" not defined and no default entity
…e){var f=a[e],q=typeof f;"object"==q&&null!=f||"function"==q?d.push(r(f,b+e+c)…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 175,
Column 141:
reference not terminated by REFC delimiter
…ar f=a[e],q=typeof f;"object"==q&&null!=f||"function"==q?d.push(r(f,b+e+c)):nu…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 175,
Column 141:
reference to entity "null" for which no system identifier could be generated
…ar f=a[e],q=typeof f;"object"==q&&null!=f||"function"==q?d.push(r(f,b+e+c)):nu…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 175,
Column 136:
entity was defined here
…(e){var f=a[e],q=typeof f;"object"==q&&null!=f||"function"==q?d.push(r(f,b+e+c……nction"==q?d.push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e)…This message may appear in several cases:
Line 175,
Column 189:
cannot generate system identifier for general entity "void"
…tion"==q?d.push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),d…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 175,
Column 189:
general entity "void" not defined and no default entity
…tion"==q?d.push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),d…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 175,
Column 193:
reference not terminated by REFC delimiter
…"==q?d.push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),d.pus…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 175,
Column 193:
reference to entity "void" for which no system identifier could be generated
…"==q?d.push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),d.pus…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 175,
Column 188:
entity was defined here
…ction"==q?d.push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),…….push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),d.push(e+"=…This message may appear in several cases:
Line 175,
Column 200:
character "&" is the first character of a delimiter but occurred as data
…push(r(f,b+e+c)):null!==f&&void 0!==f&&(e=encodeURIComponent(b+e),d.push(e+"="…This message may appear in several cases:
Line 175,
Column 292:
character "&" is the first character of a delimiter but occurred as data
…onent(f)))});return d.filter(p).join("&")}function t(a,b){a||((window.__ATA||{…This message may appear in several cases:
Line 176,
Column 4:
character "&" is the first character of a delimiter but occurred as data
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…This message may appear in several cases:
Line 176,
Column 6:
cannot generate system identifier for general entity "w.serverDomain"
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…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 176,
Column 6:
general entity "w.serverDomain" not defined and no default entity
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…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 176,
Column 20:
reference not terminated by REFC delimiter
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…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 176,
Column 20:
reference to entity "w.serverDomain" for which no system identifier could be generated
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…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 176,
Column 5:
entity was defined here
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win… w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…This message may appear in several cases:
Line 176,
Column 21:
character "&" is the first character of a delimiter but occurred as data
w&&w.serverDomain&&(x=w.serverDomain);var y="//"+x+"/conf",z=window.top===win…This message may appear in several cases:
Line 176,
Column 101:
character "&" is the first character of a delimiter but occurred as data
…=window.top===window,A=window.__ATA_PP&&window.__ATA_PP.gdpr_applies,B="boolea…This message may appear in several cases:
Line 176,
Column 103:
cannot generate system identifier for general entity "window.__ATA_PP.gdpr_applies"
…indow.top===window,A=window.__ATA_PP&&window.__ATA_PP.gdpr_applies,B="boolean"…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 176,
Column 103:
general entity "window.__ATA_PP.gdpr_applies" not defined and no default entity
…indow.top===window,A=window.__ATA_PP&&window.__ATA_PP.gdpr_applies,B="boolean"…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 176,
Column 131:
reference not terminated by REFC delimiter
…__ATA_PP&&window.__ATA_PP.gdpr_applies,B="boolean"===typeof A?Number(A):null,C…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 176,
Column 131:
reference to entity "window.__ATA_PP.gdpr_applies" for which no system identifier could be generated
…__ATA_PP&&window.__ATA_PP.gdpr_applies,B="boolean"===typeof A?Number(A):null,C…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 176,
Column 102:
entity was defined here
…window.top===window,A=window.__ATA_PP&&window.__ATA_PP.gdpr_applies,B="boolean……c]=function(d){t(void 0,d)};m(a,function(d){d&&t(d)})})(y+"?"+J);}).call(this);This message may appear in several cases:
Line 177,
Column 164:
cannot generate system identifier for general entity "t"
…c]=function(d){t(void 0,d)};m(a,function(d){d&&t(d)})})(y+"?"+J);}).call(this);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 177,
Column 164:
general entity "t" not defined and no default entity
…c]=function(d){t(void 0,d)};m(a,function(d){d&&t(d)})})(y+"?"+J);}).call(this);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 177,
Column 165:
reference not terminated by REFC delimiter
…c]=function(d){t(void 0,d)};m(a,function(d){d&&t(d)})})(y+"?"+J);}).call(this);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 177,
Column 165:
reference to entity "t" for which no system identifier could be generated
…c]=function(d){t(void 0,d)};m(a,function(d){d&&t(d)})})(y+"?"+J);}).call(this);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 177,
Column 163:
entity was defined here
…c]=function(d){t(void 0,d)};m(a,function(d){d&&t(d)})})(y+"?"+J);}).call(this); </script> <script>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 174,
Column 963:
start tag was here
…+"=")}))?b.split("=")[1]:""}function p(a){return"string"==typeof a&&0<a.length} </script> <script>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 174,
Column 137:
start tag was here
…"string"==typeof a?a.split(""):a,e=0;e<c;e++)if(e in d&&b.call(void 0,d[e],e,a… </script> <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 257,
Column 116:
there is no attribute "aria-current"
…sesolnet.wordpress.com/" aria-current="page">Syracuse Solidarity Network</a></…You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 700,
Column 26:
there is no attribute "aria-label"
</table><nav aria-label="Previous and next months" class="wp-calendar-nav">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 700,
Column 59:
there is no attribute "class"
</table><nav aria-label="Previous and next months" class="wp-calendar-nav">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 700,
Column 76:
element "nav" undefined
</table><nav aria-label="Previous and next months" class="wp-calendar-nav">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 720,
Column 69:
there is no attribute "target"
…om/event.php?eid=180772134878" target="_blank">http://www.facebook.com/event.p…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 782,
Column 28:
there is no attribute "data-attachment-id"
<p><img data-attachment-id="161" data-permalink="https://syracusesolnet.wordpre…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 782,
Column 49:
there is no attribute "data-permalink"
…ta-attachment-id="161" data-permalink="https://syracusesolnet.wordpress.com/ab…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 782,
Column 139:
there is no attribute "data-orig-file"
…ting-414/anarchybook/" data-orig-file="https://syracusesolnet.wordpress.com/wp…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 782,
Column 236:
there is no attribute "data-orig-size"
…08/04/anarchybook.gif" data-orig-size="190,200" data-comments-opened="1" data-…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 782,
Column 267:
there is no attribute "data-comments-opened"
…g-size="190,200" data-comments-opened="1" data-image-meta="{"aperture&quo…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 782,
Column 287:
there is no attribute "data-image-meta"
…a-comments-opened="1" data-image-meta="{"aperture":"0",&qu…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 782,
Column 659:
there is no attribute "data-image-title"
…quot;:""}" data-image-title="anarchybook" data-image-description="" …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 782,
Column 696:
there is no attribute "data-image-description"
…="anarchybook" data-image-description="" data-image-caption="" data-medium-fil…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 782,
Column 718:
there is no attribute "data-image-caption"
…age-description="" data-image-caption="" data-medium-file="https://syracusesol…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 782,
Column 738:
there is no attribute "data-medium-file"
…ata-image-caption="" data-medium-file="https://syracusesolnet.wordpress.com/wp…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 782,
Column 842:
there is no attribute "data-large-file"
…narchybook.gif?w=190" data-large-file="https://syracusesolnet.wordpress.com/wp…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 782,
Column 1110:
there is no attribute "srcset"
…gif?w=420" alt="anarchybook" srcset="https://syracusesolnet.wordpress.com/wp…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 782,
Column 1305:
there is no attribute "sizes"
…ybook.gif?w=143&h=150 143w" sizes="(max-width: 190px) 100vw, 190px" /><br …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 838,
Column 176:
there is no attribute "border"
…j142/nobombsnobosses315/VALENTINE.gif" border="0" alt="valentines" /></a><br />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 894,
Column 11:
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 914,
Column 340:
there is no attribute "data-shared"
…llow noopener noreferrer" data-shared="sharing-facebook-35" class="share-faceb…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 947,
Column 96:
end tag for "br" omitted, but OMITTAG NO was specified
…rdpress.com/?ref=footer_blog" rel="nofollow">Blog at WordPress.com.</a><br><br>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 947,
Column 92:
start tag was here
…rdpress.com/?ref=footer_blog" rel="nofollow">Blog at WordPress.com.</a><br><br>…rdpress.com/?ref=footer_blog" rel="nofollow">Blog at WordPress.com.</a><br><br>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 947,
Column 96:
start tag was here
…rdpress.com/?ref=footer_blog" rel="nofollow">Blog at WordPress.com.</a><br><br> <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 1028,
Column 70:
character "&" is the first character of a delimiter but occurred as data
…kieLib = {getItem:function(e){return e&&decodeURIComponent(document.cookie.rep…This message may appear in several cases:
Line 1028,
Column 72:
cannot generate system identifier for general entity "decodeURIComponent"
…eLib = {getItem:function(e){return e&&decodeURIComponent(document.cookie.repla…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 1028,
Column 72:
general entity "decodeURIComponent" not defined and no default entity
…eLib = {getItem:function(e){return e&&decodeURIComponent(document.cookie.repla…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 1028,
Column 90:
reference not terminated by REFC delimiter
…nction(e){return e&&decodeURIComponent(document.cookie.replace(new RegExp("(?:…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 1028,
Column 90:
reference to entity "decodeURIComponent" for which no system identifier could be generated
…nction(e){return e&&decodeURIComponent(document.cookie.replace(new RegExp("(?:…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 1028,
Column 71:
entity was defined here
…ieLib = {getItem:function(e){return e&&decodeURIComponent(document.cookie.repl……omponent(e).replace(/[\-\.\+\*]/g,"\\$&")+"\\s*\\=\\s*([^;]*).*$)|^.*$"),"$1")…This message may appear in several cases:
Line 1028,
Column 560:
character "&" is the first character of a delimiter but occurred as data
…n.toUTCString()}return"rootDomain"!==r&&".rootDomain"!==r||(r=(".rootDomain"==…This message may appear in several cases:
Line 1028,
Column 561:
character "&" is the first character of a delimiter but occurred as data
….toUTCString()}return"rootDomain"!==r&&".rootDomain"!==r||(r=(".rootDomain"===…This message may appear in several cases:
Line 1186,
Column 26:
character "&" is the first character of a delimiter but occurred as data
if ( window.defQueue && defQueue.isLOHP && defQueue.isLOHP === 2020 ) {This message may appear in several cases:
Line 1186,
Column 27:
character "&" is the first character of a delimiter but occurred as data
if ( window.defQueue && defQueue.isLOHP && defQueue.isLOHP === 2020 ) {This message may appear in several cases:
Line 1186,
Column 45:
character "&" is the first character of a delimiter but occurred as data
if ( window.defQueue && defQueue.isLOHP && defQueue.isLOHP === 2020 ) {This message may appear in several cases:
Line 1186,
Column 46:
character "&" is the first character of a delimiter but occurred as data
if ( window.defQueue && defQueue.isLOHP && defQueue.isLOHP === 2020 ) {This message may appear in several cases:
Line 1199,
Column 20:
there is no attribute "data-hide-timeout"
data-hide-timeout="30"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 1200,
Column 26:
there is no attribute "data-consent-expiration"
data-consent-expiration="180"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 1204,
Column 21:
required attribute "action" not specified
<form method="post">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 1205,
Column 65:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="submit" value="Close and accept" class="accept" />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 1207,
Column 3:
character data is not allowed here
Privacy & Cookies: This site uses cookies. By continuing to use this webs…You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 1207,
Column 114:
document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…uses cookies. By continuing to use this website, you agree to their use. <br />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 1209,
Column 61:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<a href="https://automattic.com/cookies/" rel="nofollow">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 1218,
Column 15:
there is no attribute "class"
<svg class="gridicon" height="20" width="20" xmlns="http://www.w3.org/2000/s…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 1218,
Column 33:
there is no attribute "height"
<svg class="gridicon" height="20" width="20" xmlns="http://www.w3.org/2000/s…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 1218,
Column 44:
there is no attribute "width"
…vg class="gridicon" height="20" width="20" xmlns="http://www.w3.org/2000/svg" …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 1218,
Column 55:
there is no attribute "xmlns"
…ridicon" height="20" width="20" xmlns="http://www.w3.org/2000/svg" viewBox="0 …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 1218,
Column 92:
there is no attribute "viewBox"
…="http://www.w3.org/2000/svg" viewBox="0 0 20 20"><path clip-rule="evenodd" d=…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 1218,
Column 103:
element "svg" undefined
…w.w3.org/2000/svg" viewBox="0 0 20 20"><path clip-rule="evenodd" d="m4 4.5h12v…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 1218,
Column 120:
there is no attribute "clip-rule"
…" viewBox="0 0 20 20"><path clip-rule="evenodd" d="m4 4.5h12v6.5h1.5v-6.5-1.5h…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 1218,
Column 132:
there is no attribute "d"
… 0 20 20"><path clip-rule="evenodd" d="m4 4.5h12v6.5h1.5v-6.5-1.5h-1.5-12-1.5v…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 1218,
Column 432:
there is no attribute "fill-rule"
…v1.5h-2.25v2.25h-1.5v-2.25h-2.25v-1.5h2.25z" fill-rule="evenodd"></path></svg>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 1218,
Column 441:
element "path" undefined
…v1.5h-2.25v2.25h-1.5v-2.25h-2.25v-1.5h2.25z" fill-rule="evenodd"></path></svg>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 1222,
Column 103:
element "svg" undefined
…w.w3.org/2000/svg" viewBox="0 0 20 20"><path fill-rule="evenodd" clip-rule="ev…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 1222,
Column 423:
there is no attribute "fill"
…11V9.5ZM5.5 12H9.5V13.5H5.5V12Z" fill="#008A20"></path><path class="following-…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 1222,
Column 432:
element "path" undefined
….5 12H9.5V13.5H5.5V12Z" fill="#008A20"></path><path class="following-icon-tick…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 1222,
Column 452:
there is no attribute "class"
…2Z" fill="#008A20"></path><path class="following-icon-tick" d="M13.5 16L15.5 1…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 1222,
Column 510:
there is no attribute "stroke"
…" d="M13.5 16L15.5 18L19 14.5" stroke="#008A20" stroke-width="1.5"></path></sv…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 1222,
Column 533:
there is no attribute "stroke-width"
… d="M13.5 16L15.5 18L19 14.5" stroke="#008A20" stroke-width="1.5"></path></svg>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 1222,
Column 538:
element "path" undefined
… d="M13.5 16L15.5 18L19 14.5" stroke="#008A20" stroke-width="1.5"></path></svg>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 1231,
Column 18:
there is no attribute "loading"
<img loading='lazy' alt='' src='https://s2.wp.com/i/logo/wpcom-gray-white.p…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 1233,
Column 49:
document type does not allow element "div" here; assuming missing "li" start-tag
<div class="actnbr-message no-display"></div> <input type="email" name="email" placeholder="Enter your email addres…
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 1236,
Column 56:
there is no attribute "placeholder"
…type="email" name="email" placeholder="Enter your email address" class="actnbr…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 1236,
Column 121:
there is no attribute "aria-label"
…il address" class="actnbr-email-field" aria-label="Enter your email address" />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 1238,
Column 65:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="action" value="subscribe" />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 1239,
Column 64:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="blog_id" value="3327420" />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 1240,
Column 93:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…ut type="hidden" name="source" value="https://syracusesolnet.wordpress.com/" />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 1241,
Column 74:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="sub-type" value="actionbar-follow" />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 1242,
Column 82:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…" name="_wpnonce" value="25e3e12bf2" /> <div class="actnbr-button-wra…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 1247,
Column 40:
document type does not allow element "li" here; missing one of "ul", "ol" start-tag
<li class="actnbr-login-nudge">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 1251,
Column 13:
end tag for "li" omitted, but OMITTAG NO was specified
</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 1233,
Column 11:
start tag was here
<div class="actnbr-message no-display"></div>…w.w3.org/2000/svg" viewBox="0 0 24 24"><g><path d="M7 12c0 1.104-.896 2-2 2s-2…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 1256,
Column 126:
element "g" undefined
…3.org/2000/svg" viewBox="0 0 24 24"><g><path d="M7 12c0 1.104-.896 2-2 2s-2-.8…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 1256,
Column 315:
element "path" undefined
… 2s.896 2 2 2 2-.896 2-2-.896-2-2-2z"/></g></svg> <div class="actnbr-popove…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 1266,
Column 129:
element "svg" undefined
…w.w3.org/2000/svg" viewBox="0 0 24 24"><g><path d="M2 6c0-1.505.78-3.08 2-4 0 …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 1266,
Column 132:
element "g" undefined
…3.org/2000/svg" viewBox="0 0 24 24"><g><path d="M2 6c0-1.505.78-3.08 2-4 0 .84…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 1266,
Column 674:
element "path" undefined
…-1.695-2.103-3.52-4.092-5.448-5.977z"/></g></svg> <span>Customize</spa…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 1271,
Column 103:
element "svg" undefined
…w.w3.org/2000/svg" viewBox="0 0 20 20"><path clip-rule="evenodd" d="m4 4.5h12v…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 1271,
Column 441:
element "path" undefined
…v1.5h-2.25v2.25h-1.5v-2.25h-2.25v-1.5h2.25z" fill-rule="evenodd"></path></svg>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 1275,
Column 103:
element "svg" undefined
…w.w3.org/2000/svg" viewBox="0 0 20 20"><path fill-rule="evenodd" clip-rule="ev…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 1275,
Column 432:
element "path" undefined
….5 12H9.5V13.5H5.5V12Z" fill="#008A20"></path><path class="following-icon-tick…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 1275,
Column 538:
element "path" undefined
… d="M13.5 16L15.5 18L19 14.5" stroke="#008A20" stroke-width="1.5"></path></svg>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 1301,
Column 8:
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 1328,
Column 5:
"itemscope" is not a member of a group specified for any attribute
itemtype="https://schema.org/ImageGallery"> itemtype="https://schema.org/ImageGallery">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 1331,
Column 59:
there is no attribute "fill"
… height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg…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 1331,
Column 100:
element "svg" undefined
…height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg">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 1332,
Column 16:
there is no attribute "id"
<mask id="maskPrev" mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y=…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 1332,
Column 37:
there is no attribute "mask-type"
<mask id="maskPrev" mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y=…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 1332,
Column 55:
there is no attribute "maskUnits"
…maskPrev" mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="9" 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 1332,
Column 74:
there is no attribute "x"
…mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="9" height="12">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 1332,
Column 80:
there is no attribute "y"
…mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="9" height="12">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 1332,
Column 90:
there is no attribute "width"
…mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="9" height="12">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 1332,
Column 101:
there is no attribute "height"
…mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="9" height="12">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 1332,
Column 105:
element "mask" undefined
…mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="9" height="12">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 1333,
Column 116:
element "path" undefined
…6 12L16.2072 7.41L14.8041 6L8.8335 12L14.8041 18L16.2072 16.59Z" fill="white"/>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 1335,
Column 15:
there is no attribute "mask"
<g mask="url(#maskPrev)">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 1335,
Column 31:
element "g" undefined
<g mask="url(#maskPrev)">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 1336,
Column 16:
there is no attribute "x"
<rect x="0.579102" width="23.8823" height="24" fill="#FFFFFF"/>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 1336,
Column 33:
there is no attribute "width"
<rect x="0.579102" width="23.8823" height="24" fill="#FFFFFF"/>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 1336,
Column 50:
there is no attribute "height"
<rect x="0.579102" width="23.8823" height="24" fill="#FFFFFF"/>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 1336,
Column 60:
there is no attribute "fill"
<rect x="0.579102" width="23.8823" height="24" fill="#FFFFFF"/>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 1336,
Column 70:
element "rect" undefined
<rect x="0.579102" width="23.8823" height="24" fill="#FFFFFF"/>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 1341,
Column 100:
element "svg" undefined
…height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg">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 1342,
Column 105:
element "mask" undefined
…mask-type="alpha" maskUnits="userSpaceOnUse" x="8" y="6" width="8" height="12">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 1343,
Column 117:
element "path" undefined
… 12L8.59814 7.41L10.0012 6L15.9718 12L10.0012 18L8.59814 16.59Z" fill="white"/>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 1345,
Column 31:
element "g" undefined
<g mask="url(#maskNext)">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 1346,
Column 69:
element "rect" undefined
<rect x="0.34375" width="23.8822" height="24" fill="#FFFFFF"/>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 1353,
Column 99:
element "svg" undefined
…height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg">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 1354,
Column 106:
element "mask" undefined
…ask-type="alpha" maskUnits="userSpaceOnUse" x="5" y="5" width="15" height="14">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 1355,
Column 190:
element "path" undefined
…L12.3509 13.41L17.9135 19L19.3166 17.59L13.754 12L19.3166 6.41Z" fill="white"/>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 1357,
Column 31:
element "g" undefined
<g mask="url(#maskClose)">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 1358,
Column 69:
element "rect" undefined
<rect x="0.409668" width="23.8823" height="24" fill="#FFFFFF"/>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 1373,
Column 81:
there is no attribute "aria-label"
…-icon-btn jp-carousel-icon-info" aria-label="Toggle photo metadata visibility">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 1375,
Column 103:
element "svg" undefined
…height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg">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 1376,
Column 109:
element "mask" undefined
…ask-type="alpha" maskUnits="userSpaceOnUse" x="2" y="2" width="21" height="20">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 1377,
Column 439:
element "path" undefined
…7144 7.59 17.142 4 12.7537 4C8.36531 4 4.79292 7.59 4.79292 12Z" fill="white"/>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 1379,
Column 34:
element "g" undefined
<g mask="url(#maskInfo)">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 1380,
Column 71:
element "rect" undefined
<rect x="0.8125" width="23.8823" height="24" fill="#FFFFFF"/>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 1387,
Column 103:
element "svg" undefined
…height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg">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 1388,
Column 113:
element "mask" undefined
…ask-type="alpha" maskUnits="userSpaceOnUse" x="2" y="2" width="21" height="20">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 1389,
Column 257:
element "path" undefined
…9 3.2325 2 4.3271 2ZM6.31729 16H20.2486V4H4.3271V18L6.31729 16Z" fill="white"/>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 1391,
Column 38:
element "g" undefined
<g mask="url(#maskComments)">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 1392,
Column 72:
element "rect" undefined
<rect x="0.34668" width="23.8823" height="24" fill="#FFFFFF"/>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 1396,
Column 69:
there is no attribute "aria-label"
…-carousel-has-comments-indicator" aria-label="This image has comments."></span>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 1414,
Column 66:
required attribute "action" not specified
<form id="jp-carousel-comment-form">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 1415,
Column 91:
document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…mment-form-comment-field" class="screen-reader-text">Write a Comment...</label>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 1420,
Column 26:
there is no attribute "placeholder"
placeholder="Write a Comment..."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 1421,
Column 13:
required attribute "rows" not specified
></textarea>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 1421,
Column 13:
required attribute "cols" not specified
></textarea>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 1421,
Column 13:
document type does not allow element "textarea" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
></textarea>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 1450,
Column 51:
there is no attribute "itemprop"
<h3 class="jp-carousel-caption" itemprop="caption description"></h3>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 1455,
Column 70:
end tag for "ul" which is not finished
<ul class="jp-carousel-image-exif" style="display: none;"></ul>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
Line 1457,
Column 103:
element "svg" undefined
…height="24" viewBox="0 0 25 24" fill="none" xmlns="http://www.w3.org/2000/svg">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 1458,
Column 106:
element "mask" undefined
…ask-type="alpha" maskUnits="userSpaceOnUse" x="3" y="3" width="19" height="18">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 1459,
Column 322:
element "path" undefined
…7V10H19.7775V6.41L9.99569 16.24L8.59261 14.83L18.3744 5H14.802Z" fill="white"/>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 1461,
Column 31:
element "g" undefined
<g mask="url(#mask0)">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 1462,
Column 73:
element "rect" undefined
<rect x="0.870605" width="23.8823" height="24" fill="#FFFFFF"/>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 1479,
Column 246:
reference not terminated by REFC delimiter
…P8H/2NZ94fltezbxMxkx61vEGx+U/hQ==&cssminify=yes' type='text/css' media='all' />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 1479,
Column 246:
reference to external entity in attribute value
…P8H/2NZ94fltezbxMxkx61vEGx+U/hQ==&cssminify=yes' type='text/css' media='all' />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 1479,
Column 246:
reference to entity "cssminify" for which no system identifier could be generated
…P8H/2NZ94fltezbxMxkx61vEGx+U/hQ==&cssminify=yes' type='text/css' media='all' />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 62,
Column 264:
entity was defined here
…WNORiHDTb0nPzkV3pODzvf7Xyb7PsL7ptDng==&cssminify=yes' type='text/css' media='a……P8H/2NZ94fltezbxMxkx61vEGx+U/hQ==&cssminify=yes' type='text/css' media='all' />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 1581,
Column 9:
cannot generate system identifier for general entity "is_post_share"
'&is_post_share=true' +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 1581,
Column 9:
general entity "is_post_share" not defined and no default entity
'&is_post_share=true' +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 1581,
Column 22:
reference not terminated by REFC delimiter
'&is_post_share=true' +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 1581,
Column 22:
reference to entity "is_post_share" for which no system identifier could be generated
'&is_post_share=true' +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 1581,
Column 8:
entity was defined here
'&is_post_share=true' + '&v=5';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 1582,
Column 9:
general entity "v" not defined and no default entity
'&v=5';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 1582,
Column 10:
reference not terminated by REFC delimiter
'&v=5';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 1582,
Column 10:
reference to entity "v" for which no system identifier could be generated
'&v=5';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 1582,
Column 8:
entity was defined here
'&v=5';…ipt src="//stats.wp.com/w.js?67" defer></script> <script type="text/javascript…"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.
How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
Line 1620,
Column 52:
required attribute "type" not specified
…ipt src="//stats.wp.com/w.js?67" defer></script> <script type="text/javascript…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 1628,
Column 143:
document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
…x;width:1px;overflow:hidden;position:absolute;bottom:1px;" alt="" /></noscript>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 1639,
Column 19:
required attribute "type" not specified
</script><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 1647,
Column 33:
cannot generate system identifier for general entity "x_"
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u…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 1647,
Column 33:
general entity "x_" not defined and no default entity
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u…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 1647,
Column 35:
reference not terminated by REFC delimiter
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u…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 1647,
Column 35:
reference to entity "x_" for which no system identifier could be generated
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u…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 1647,
Column 32:
entity was defined here
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u… mobileStatsQueryString += '&x_' + 'mobile_devices' + '=' + wpcom_mobile_use…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 1651,
Column 35:
reference to entity "x_" for which no system identifier could be generated
mobileStatsQueryString += '&x_' + 'mobile_devices' + '=' + wpcom_mobile_use…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 1647,
Column 32:
entity was defined here
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u… mobileStatsQueryString += '&x_' + 'ipad_views' + '=' + 'views';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 1655,
Column 35:
reference to entity "x_" for which no system identifier could be generated
mobileStatsQueryString += '&x_' + 'ipad_views' + '=' + 'views';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 1647,
Column 32:
entity was defined here
mobileStatsQueryString += '&x_' + 'mobile_platforms' + '=' + wpcom_mobile_u……p.com/g.gif?v=wpcom-no-pv' + mobileStatsQueryString + '&baba=' + Math.random();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 1659,
Column 118:
general entity "baba" not defined and no default entity
…p.com/g.gif?v=wpcom-no-pv' + mobileStatsQueryString + '&baba=' + Math.random();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 1659,
Column 122:
reference not terminated by REFC delimiter
…p.com/g.gif?v=wpcom-no-pv' + mobileStatsQueryString + '&baba=' + Math.random();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 1659,
Column 122:
reference to entity "baba" for which no system identifier could be generated
…p.com/g.gif?v=wpcom-no-pv' + mobileStatsQueryString + '&baba=' + Math.random();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 1659,
Column 117:
entity was defined here
…p.com/g.gif?v=wpcom-no-pv' + mobileStatsQueryString + '&baba=' + Math.random();Below is the source input I used for this validation:
Copyright © 2024 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.