SMThemes Support » Framework

WC3 Markup Validation failure

Latest Reply from Dave at 2014-01-29 03:22:41
10 years ago
My website, built with the Janela theme, has failed the WC3 markup validation miserably...............

With no plugins running, it has 53 errors and 36 warnings. When I switch the theme to Twenty Fourteen there are no errors and the site passes with flying colours.

I have experimented by trying some of the other themes from SMThemes and these has also had 50+ errors on each one tried.

As these issues appear to affect all the SMthemes that I have tried, does this mean that it is a framework problem or is there any way that the Janela theme can be made compliant?
10 years ago
Hi!
Could you clarify the problem? Some warnings should be, otherwise the theme will not work. However, these warnings are not dangerous for the proper work of your website and do not cause optimization problems. As I can see your websites work. Could you specify the warnings and errors that you get.
10 years ago
[b]Please note that these errors are not present when the theme is changed to 2011, 2012, 2013, or 2014[/b]

Error Line 113, Column 75: there is no attribute "layout"
<body class="home page page-id-5 page-template-default content-r" layout='2'>
✉
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.

Error Line 132, Column 36: there is no attribute "ifaviconffd"
<form method="get" ifaviconffd="searchform" action="http://www.pro-holistic…
✉
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.

Error Line 150, Column 98: required attribute "type" not specified
…obile-menu' id='mobile-sec-menu'><option value='#'>Go to ...</option> <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>.

Error Line 150, Column 98: document type does not allow element "script" here
…obile-menu' id='mobile-sec-menu'><option value='#'>Go to ...</option> <script>
✉
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).

Error Line 153, Column 23: document type does not allow element "option" here
jQuery('<option />', {
✉
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).

Error Line 167, Column 46: document type does not allow element "div" here; assuming missing "li" start-tag
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
✉
Error Line 168, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-65"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 169, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
</div></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 ">".

Info Line 167, Column 22: start tag was here
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
Error Line 172, Column 46: document type does not allow element "div" here; assuming missing "li" start-tag
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
✉
Error Line 173, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-68"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 174, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-69"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 175, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-67"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 176, Column 103: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…e menu-item-object-page menu-item-774"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 177, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
</div></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 ">".

Info Line 172, Column 22: start tag was here
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
Error Line 180, Column 46: document type does not allow element "div" here; assuming missing "li" start-tag
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
✉
Error Line 181, Column 105: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
… menu-item-object-page menu-item-2130"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 182, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-73"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 183, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-72"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 184, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-71"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 185, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
</div></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 ">".

Info Line 180, Column 22: start tag was here
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
Error Line 188, Column 46: document type does not allow element "div" here; assuming missing "li" start-tag
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
✉
Error Line 189, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-75"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 190, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-78"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 191, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-76"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 192, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-77"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 193, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
</div></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 ">".

Info Line 188, Column 22: start tag was here
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
Error Line 196, Column 46: document type does not allow element "div" here; assuming missing "li" start-tag
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
✉
Error Line 197, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-85"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 198, Column 101: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
…pe menu-item-object-page menu-item-86"><a href="http://www.pro-holistic.co.uk/…
✉
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>").

Error Line 199, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
</div></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 ">".

Info Line 196, Column 22: start tag was here
<ul class='sub-menu'><div class='transparent'></div><div class='inner'>
Error Line 298, Column 26: ID "s" already defined
name="s" id="s" onblur="if (this.value == '') {this.value = 'Sear…
✉
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

Info Line 135, Column 26: ID "s" first defined here
name="s" id="s" onblur="if (this.value == '') {this.value = 'Sear…
Warning Line 310, Column 22: character "&" is the first character of a delimiter but occurred as data
<p>Dates: April 26th & 27th 2014<br />
✉
This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Warning Line 466, Column 94: cannot generate system identifier for general entity "send"
…p?href=http://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&sho…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 94: general entity "send" not defined and no default entity
…p?href=http://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&sho…
✉
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.

Warning Line 466, Column 98: reference not terminated by REFC delimiter
…ef=http://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_fa…
✉
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.

Warning Line 466, Column 98: reference to external entity in attribute value
…ef=http://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_fa…
✉
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 '&amp;'.

Error Line 466, Column 98: reference to entity "send" for which no system identifier could be generated
…ef=http://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_fa…
✉
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.

Info Line 466, Column 93: entity was defined here
…hp?href=http://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&sh…
Warning Line 466, Column 105: cannot generate system identifier for general entity "layout"
…://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_faces=fal…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 105: general entity "layout" not defined and no default entity
…://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_faces=fal…
✉
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.

Warning Line 466, Column 111: reference not terminated by REFC delimiter
….pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_faces=false&act…
✉
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.

Warning Line 466, Column 111: reference to external entity in attribute value
….pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_faces=false&act…
✉
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 '&amp;'.

Error Line 466, Column 111: reference to entity "layout" for which no system identifier could be generated
….pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_faces=false&act…
✉
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.

Info Line 466, Column 104: entity was defined here
…p://www.pro-holistic.co.uk/&send=false&layout=box_count&width=50&show_faces=fa…
Warning Line 466, Column 122: cannot generate system identifier for general entity "width"
…ic.co.uk/&send=false&layout=box_count&width=50&show_faces=false&action=like&co…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 122: general entity "width" not defined and no default entity
…ic.co.uk/&send=false&layout=box_count&width=50&show_faces=false&action=like&co…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Warning Line 466, Column 127: reference not terminated by REFC delimiter
….uk/&send=false&layout=box_count&width=50&show_faces=false&action=like&colorsc…
✉
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.

Warning Line 466, Column 127: reference to external entity in attribute value
….uk/&send=false&layout=box_count&width=50&show_faces=false&action=like&colorsc…
✉
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 '&amp;'.

Error Line 466, Column 127: reference to entity "width" for which no system identifier could be generated
….uk/&send=false&layout=box_count&width=50&show_faces=false&action=like&colorsc…
✉
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.

Info Line 466, Column 121: entity was defined here
…tic.co.uk/&send=false&layout=box_count&width=50&show_faces=false&action=like&c…
Warning Line 466, Column 131: cannot generate system identifier for general entity "show_faces"
…&send=false&layout=box_count&width=50&show_faces=false&action=like&colorscheme…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 131: general entity "show_faces" not defined and no default entity
…&send=false&layout=box_count&width=50&show_faces=false&action=like&colorscheme…
✉
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.

Warning Line 466, Column 141: reference not terminated by REFC delimiter
…e&layout=box_count&width=50&show_faces=false&action=like&colorscheme=light&fon…
✉
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.

Warning Line 466, Column 141: reference to external entity in attribute value
…e&layout=box_count&width=50&show_faces=false&action=like&colorscheme=light&fon…
✉
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 '&amp;'.

Error Line 466, Column 141: reference to entity "show_faces" for which no system identifier could be generated
…e&layout=box_count&width=50&show_faces=false&action=like&colorscheme=light&fon…
✉
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.

Info Line 466, Column 130: entity was defined here
…/&send=false&layout=box_count&width=50&show_faces=false&action=like&colorschem…
Warning Line 466, Column 148: cannot generate system identifier for general entity "action"
…t=box_count&width=50&show_faces=false&action=like&colorscheme=light&font&heigh…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 148: general entity "action" not defined and no default entity
…t=box_count&width=50&show_faces=false&action=like&colorscheme=light&font&heigh…
✉
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.

Warning Line 466, Column 154: reference not terminated by REFC delimiter
…count&width=50&show_faces=false&action=like&colorscheme=light&font&height=65&l…
✉
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.

Warning Line 466, Column 154: reference to external entity in attribute value
…count&width=50&show_faces=false&action=like&colorscheme=light&font&height=65&l…
✉
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 '&amp;'.

Error Line 466, Column 154: reference to entity "action" for which no system identifier could be generated
…count&width=50&show_faces=false&action=like&colorscheme=light&font&height=65&l…
✉
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.

Info Line 466, Column 147: entity was defined here
…ut=box_count&width=50&show_faces=false&action=like&colorscheme=light&font&heig…
Warning Line 466, Column 160: cannot generate system identifier for general entity "colorscheme"
…width=50&show_faces=false&action=like&colorscheme=light&font&height=65&locale=…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 160: general entity "colorscheme" not defined and no default entity
…width=50&show_faces=false&action=like&colorscheme=light&font&height=65&locale=…
✉
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.

Warning Line 466, Column 171: reference not terminated by REFC delimiter
…ow_faces=false&action=like&colorscheme=light&font&height=65&locale=en_US" scro…
✉
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.

Warning Line 466, Column 171: reference to external entity in attribute value
…ow_faces=false&action=like&colorscheme=light&font&height=65&locale=en_US" scro…
✉
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 '&amp;'.

Error Line 466, Column 171: reference to entity "colorscheme" for which no system identifier could be generated
…ow_faces=false&action=like&colorscheme=light&font&height=65&locale=en_US" scro…
✉
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.

Info Line 466, Column 159: entity was defined here
…&width=50&show_faces=false&action=like&colorscheme=light&font&height=65&locale…
Warning Line 466, Column 178: cannot generate system identifier for general entity "font"
…s=false&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 178: general entity "font" not defined and no default entity
…s=false&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="…
✉
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.

Warning Line 466, Column 182: reference not terminated by REFC delimiter
…lse&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" …
✉
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.

Warning Line 466, Column 182: reference to external entity in attribute value
…lse&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" …
✉
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 '&amp;'.

Error Line 466, Column 182: reference to entity "font" for which no system identifier could be generated
…lse&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" …
✉
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.

Info Line 466, Column 177: entity was defined here
…es=false&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling=…
Warning Line 466, Column 183: cannot generate system identifier for general entity "height"
…se&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" f…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 183: general entity "height" not defined and no default entity
…se&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" f…
✉
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.

Warning Line 466, Column 189: reference not terminated by REFC delimiter
…ion=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" framebo…
✉
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.

Warning Line 466, Column 189: reference to external entity in attribute value
…ion=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" framebo…
✉
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 '&amp;'.

Error Line 466, Column 189: reference to entity "height" for which no system identifier could be generated
…ion=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" framebo…
✉
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.

Info Line 466, Column 182: entity was defined here
…lse&action=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" …
Warning Line 466, Column 193: cannot generate system identifier for general entity "locale"
…like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" frameborder…
✉
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 "&amp;" (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 &aelig; 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.

Error Line 466, Column 193: general entity "locale" not defined and no default entity
…like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" frameborder…
✉
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.

Warning Line 466, Column 199: reference not terminated by REFC delimiter
…olorscheme=light&font&height=65&locale=en_US" scrolling="no" frameborder="0" s…
✉
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.

Warning Line 466, Column 199: reference to external entity in attribute value
…olorscheme=light&font&height=65&locale=en_US" scrolling="no" frameborder="0" s…
✉
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 '&amp;'.

Error Line 466, Column 199: reference to entity "locale" for which no system identifier could be generated
…olorscheme=light&font&height=65&locale=en_US" scrolling="no" frameborder="0" s…
✉
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.

Info Line 466, Column 192: entity was defined here
…=like&colorscheme=light&font&height=65&locale=en_US" scrolling="no" frameborde…
Error Line 466, Column 319: there is no attribute "allowTransparency"
…50px; height:65px;" allowTransparency="true"></iframe></li><li><a href="https:…
✉
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.

Error Line 466, Column 420: there is no attribute "data-count"
…re" class="twitter-share-button" data-count="vertical" data-lang="en">Tweet</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.

Error Line 466, Column 441: there is no attribute "data-lang"
…re" class="twitter-share-button" data-count="vertical" data-lang="en">Tweet</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.

Error Line 467, Column 11: required attribute "type" not specified
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getE…
✉
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>.
10 years ago
All these warnings or errors are just tricks for the proper work of our theme. The structure of wordpress imposes certain rules. We are forced to do the tricks, but they don't cause any problems with the major browsers.
10 years ago
I realise that the theme works on all the major browsers but, as far as I have been led to believe, errors like those listed can affect the way that the Google spider indexes the site.
10 years ago
Most spiders see your website as plain text (source code), and doesn't try to render anything. Besides, the most important points to remember are:
1)Never ever customize a site for a Search Engine.
2)Develop your site for the user, take care of things like the web page is displayed correctly in all web browsers.
3)Search Engine spiders work mainly in this direction.
4)ex: Google spider -> Make pages primarily for users, not for search engines. Don't deceive your users or > > present different content to search engines than you display to users, which is commonly > referred to as "cloaking."

Leave a reply

Add codeAdd image


Search by forum

SMThemes.com Support