Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 2,
Column 3:
DTDs other than base allowed only if CONCUR YES or EXPLICIT YES
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.o…<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.o…<html>
Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
<html xmlns="http://www.w3.org/1999/xhtml">
Line 6,
Column 119:
character "&" is the first character of a delimiter but occurred as data
…t?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*…This message may appear in several cases:
Line 6,
Column 120:
character "&" is the first character of a delimiter but occurred as data
…?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*"…This message may appear in several cases:
Line 7,
Column 127:
character "&" is the first character of a delimiter but occurred as data
…d?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*…This message may appear in several cases:
Line 7,
Column 128:
character "&" is the first character of a delimiter but occurred as data
…?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*"…This message may appear in several cases:
Line 10,
Column 49:
character "&" is the first character of a delimiter but occurred as data
…(u_global_data.clunduse)!='undefined' && u_global_data.clunduse>0 || (u_global…This message may appear in several cases:
Line 10,
Column 50:
character "&" is the first character of a delimiter but occurred as data
…u_global_data.clunduse)!='undefined' && u_global_data.clunduse>0 || (u_global_…This message may appear in several cases:
Line 10,
Column 95:
character "&" is the first character of a delimiter but occurred as data
…' && u_global_data.clunduse>0 || (u_global_data && u_global_data.is_u_main_h)){This message may appear in several cases:
Line 10,
Column 96:
character "&" is the first character of a delimiter but occurred as data
…' && u_global_data.clunduse>0 || (u_global_data && u_global_data.is_u_main_h)){This message may appear in several cases:
Line 11,
Column 32:
character "&" is the first character of a delimiter but occurred as data
if(typeof(console)=='object' && typeof(console.log)=='function') console.log(…This message may appear in several cases:
Line 11,
Column 33:
character "&" is the first character of a delimiter but occurred as data
if(typeof(console)=='object' && typeof(console.log)=='function') console.log(…This message may appear in several cases:
Line 22,
Column 51:
character "&" is the first character of a delimiter but occurred as data
…ypeof(u_global_data.clunduse)!='undefined' && u_global_data.clunduse>1) return;This message may appear in several cases:
Line 22,
Column 52:
character "&" is the first character of a delimiter but occurred as data
…ypeof(u_global_data.clunduse)!='undefined' && u_global_data.clunduse>1) return;This message may appear in several cases:
Line 23,
Column 33:
character "&" is the first character of a delimiter but occurred as data
if(typeof(console)=='object' && typeof(console.log)=='function') console.log…This message may appear in several cases:
Line 23,
Column 34:
character "&" is the first character of a delimiter but occurred as data
if(typeof(console)=='object' && typeof(console.log)=='function') console.log…This message may appear in several cases:
Line 26,
Column 101:
character "&" is the first character of a delimiter but occurred as data
…k?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*…This message may appear in several cases:
Line 26,
Column 102:
character "&" is the first character of a delimiter but occurred as data
…?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*"…This message may appear in several cases:
Line 30,
Column 99:
character "&" is the first character of a delimiter but occurred as data
…d?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*…This message may appear in several cases:
Line 30,
Column 100:
character "&" is the first character of a delimiter but occurred as data
…?r"+escape(document.referrer)+(screen&&";s"+screen.width+"*"+screen.height+"*"…This message may appear in several cases:
Line 34,
Column 57:
character "&" is the first character of a delimiter but occurred as data
…l_data.preroll_video_57322)=='object' && u_global_data.preroll_video_57322.act…This message may appear in several cases:
Line 34,
Column 58:
character "&" is the first character of a delimiter but occurred as data
…_data.preroll_video_57322)=='object' && u_global_data.preroll_video_57322.acti…This message may appear in several cases:
Line 35,
Column 32:
character "&" is the first character of a delimiter but occurred as data
if(typeof(console)=='object' && typeof(console.log)=='function') console.log(…This message may appear in several cases:
Line 35,
Column 33:
character "&" is the first character of a delimiter but occurred as data
if(typeof(console)=='object' && typeof(console.log)=='function') console.log(…This message may appear in several cases:
Line 41,
Column 68:
end tag for "meta" omitted, but OMITTAG NO was specified
<meta http-equiv="content-type" content="text/html; charset=UTF-8">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 41,
Column 1:
start tag was here
<meta http-equiv="content-type" content="text/html; charset=UTF-8">…итесь на сайте, где можете скачать песни, музыку, хиты 2014 года бесплатно. "> 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 43,
Column 1:
start tag was here
<meta name="description" content="Уважаемый гость нашего сайта, Вы находитесь н… <script src="/.s/src/jquery-1.12.4.min.js"></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 52,
Column 35:
required attribute "type" not specified
<script src="/.s/src/uwnd.min.js"></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 53,
Column 51:
cannot generate system identifier for general entity "ca"
…="//s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123">…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 53,
Column 51:
general entity "ca" not defined and no default entity
…="//s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123">…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 53,
Column 53:
reference not terminated by REFC delimiter
…//s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></…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 53,
Column 53:
reference to external entity in attribute value
…//s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></…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 53,
Column 53:
reference to entity "ca" for which no system identifier could be generated
…//s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></…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 53,
Column 50:
entity was defined here
…c="//s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"……68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></scr…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 53,
Column 56:
general entity "ug" not defined and no default entity
…68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></scr…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 53,
Column 58:
reference not terminated by REFC delimiter
….ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></scrip…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 53,
Column 58:
reference to external entity in attribute value
….ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></scrip…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 53,
Column 58:
reference to entity "ug" for which no system identifier could be generated
….ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></scrip…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 53,
Column 55:
entity was defined here
…s68.ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></sc……ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 63:
general entity "isp" not defined and no default entity
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 66:
reference not terminated by REFC delimiter
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 66:
reference to external entity in attribute value
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 66:
reference to entity "isp" for which no system identifier could be generated
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 62:
entity was defined here
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 69:
general entity "r" not defined and no default entity
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 70:
reference not terminated by REFC delimiter
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 70:
reference to external entity in attribute value
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 70:
reference to entity "r" for which no system identifier could be generated
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>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 53,
Column 68:
entity was defined here
…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></script>…ucoz.net/cgi/uutils.fcg?a=uSD&ca=2&ug=999&isp=0&r=0.0590399870699123"></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 54,
Column 8:
required attribute "type" not specified
<script>/* --- UCOZ-JS-INIT_CODE --- */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 60,
Column 50:
required attribute "type" not specified
<script src="/.s/src/ulightbox/ulightbox.min.js"></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 61,
Column 16:
"async" is not a member of a group specified for any attribute
<script async defer src="https://www.google.com/recaptcha/api.js?onload=reCall… <script async defer src="https://www.google.com/recaptcha/api.js?onload=reCall…"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 61,
Column 85:
cannot generate system identifier for general entity "render"
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 85:
general entity "render" not defined and no default entity
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 91:
reference not terminated by REFC delimiter
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 91:
reference to external entity in attribute value
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 91:
reference to entity "render" for which no system identifier could be generated
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 84:
entity was defined here
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 101:
general entity "hl" not defined and no default entity
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 103:
reference not terminated by REFC delimiter
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 103:
reference to external entity in attribute value
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 103:
reference to entity "hl" for which no system identifier could be generated
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>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 61,
Column 100:
entity was defined here
….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></script>….google.com/recaptcha/api.js?onload=reCallback&render=explicit&hl=ru"></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 62,
Column 9:
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 70,
Column 4:
character "&" is the first character of a delimiter but occurred as data
&& _uPostForm('', { type:'POST', url:'/' + mod + path, data:{ a, id, mark, m…This message may appear in several cases:
Line 70,
Column 5:
character "&" is the first character of a delimiter but occurred as data
&& _uPostForm('', { type:'POST', url:'/' + mod + path, data:{ a, id, mark, m…This message may appear in several cases:
Line 74,
Column 168:
character "&" is the first character of a delimiter but occurred as data
… location.search ? location.search + '&' : '?' ) + 'rnd=' + Date.now() + locat…This message may appear in several cases:
Line 87,
Column 31:
character "&" is the first character of a delimiter but occurred as data
if ($(element).is(':empty') && grecaptcha.render) {This message may appear in several cases:
Line 87,
Column 32:
character "&" is the first character of a delimiter but occurred as data
if ($(element).is(':empty') && grecaptcha.render) {This message may appear in several cases:
Line 98,
Column 9:
character "&" is the first character of a delimiter but occurred as data
reset && grecaptcha.reset(reset.previousElementSibling.getAttribute('rcid'));This message may appear in several cases:
Line 98,
Column 10:
character "&" is the first character of a delimiter but occurred as data
reset && grecaptcha.reset(reset.previousElementSibling.getAttribute('rcid'));This message may appear in several cases:
Line 104,
Column 8:
required attribute "type" not specified
<style>.UhideBlock{display:none; }</style>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 123,
Column 5:
end tag for "ul" which is not finished
</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 130,
Column 163:
end tag for "input" omitted, but OMITTAG NO was specified
…gth="30" size="20" class="queryField"><input type="submit" class="searchSbmFl"…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 130,
Column 91:
start tag was here
…t" style="margin:0" action="/search/"><input type="text" name="q" maxlength="3……nput type="submit" class="searchSbmFl" name="sfSbm" value="Найти"></form></div>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 130,
Column 163:
start tag was here
…gth="30" size="20" class="queryField"><input type="submit" class="searchSbmFl"……iv class="avatar_p"><img src="/img/avatar.jpg" alt="Гость" title="Гость"></div>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 134,
Column 23:
start tag was here
<div class="avatar_p"><img src="/img/avatar.jpg" alt="Гость" title="Гость"></di…<link media="screen" href="/css/tipsy.css" type="text/css" rel="stylesheet" />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 154,
Column 62:
document type does not allow element "meta" here
<meta name='yandex-verification' content='6280e70d23d1aacf' />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 156,
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 171,
Column 30:
character "&" is the first character of a delimiter but occurred as data
<p>Создан новый раздел House & Techno музыки, в котором Вы найдете много ярких …This message may appear in several cases:
Line 171,
Column 399:
character "&" is the first character of a delimiter but occurred as data
… шанс, начните это делать прямо сейчас, перейдя в категорию House & Techno.</p>This message may appear in several cases:
Line 189,
Column 68:
required attribute "type" not specified
<div id="nativeroll_video_cont" style="display:none;"></div><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 190,
Column 111:
character "&" is the first character of a delimiter but occurred as data
…ar e=$(this);e.prop("selectedIndex")>0&&(other_filters_params+=t+e.attr("id")+…This message may appear in several cases:
Line 190,
Column 112:
character "&" is the first character of a delimiter but occurred as data
…r e=$(this);e.prop("selectedIndex")>0&&(other_filters_params+=t+e.attr("id")+"…This message may appear in several cases:
Line 190,
Column 166:
character "&" is the first character of a delimiter but occurred as data
…"selectedIndex")>0&&(other_filters_params+=t+e.attr("id")+"="+e.val(),t="&")});This message may appear in several cases:
Line 194,
Column 37:
character "&" is the first character of a delimiter but occurred as data
if (other_filters_params.length && other_filters_params.indexOf('?') < 0) {This message may appear in several cases:
Line 194,
Column 38:
character "&" is the first character of a delimiter but occurred as data
if (other_filters_params.length && other_filters_params.indexOf('?') < 0) {This message may appear in several cases:
Line 194,
Column 74:
character "<" is the first character of a delimiter but occurred as data
if (other_filters_params.length && other_filters_params.indexOf('?') < 0) {This message may appear in several cases:
Line 199,
Column 32:
required attribute "type" not specified
<div id="allEntries"><script>var filtch=function(t,e,l){var i=window.locatio…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 199,
Column 171:
character "&" is the first character of a delimiter but occurred as data
….each(function(){var t=$(this);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",…This message may appear in several cases:
Line 199,
Column 173:
cannot generate system identifier for general entity "t.prop"
…ach(function(){var t=$(this);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n=…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 199,
Column 173:
general entity "t.prop" not defined and no default entity
…ach(function(){var t=$(this);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n=…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 199,
Column 179:
reference not terminated by REFC delimiter
…nction(){var t=$(this);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n=0):i+=…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 199,
Column 179:
reference to entity "t.prop" for which no system identifier could be generated
…nction(){var t=$(this);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n=0):i+=…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 199,
Column 172:
entity was defined here
…each(function(){var t=$(this);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n……is);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n=0):i+="&",i+=t.attr("id")…This message may appear in several cases:
Line 199,
Column 199:
character "&" is the first character of a delimiter but occurred as data
…s);t.val()&&t.prop("selectedIndex")>0&&(n?(i+="?",n=0):i+="&",i+=t.attr("id")+…This message may appear in several cases:
Line 199,
Column 220:
character "&" is the first character of a delimiter but occurred as data
…electedIndex")>0&&(n?(i+="?",n=0):i+="&",i+=t.attr("id")+"="+t.val())}),docume…This message may appear in several cases:
Line 225,
Column 97:
character "&" is the first character of a delimiter but occurred as data
…po_kolibri_glupyshka/6-1-0-910">Kavabanga & Depo & Kolibri – Глупышка</a></div>This message may appear in several cases:
Line 225,
Column 104:
character "&" is the first character of a delimiter but occurred as data
…po_kolibri_glupyshka/6-1-0-910">Kavabanga & Depo & Kolibri – Глупышка</a></div>This message may appear in several cases:
Line 261,
Column 98:
character "&" is the first character of a delimiter but occurred as data
…_matanga_makdim_nevinnaja/6-1-0-901">Витя Матанга & MakDim – Невинная</a></div>This message may appear in several cases:
Line 265,
Column 75:
character "&" is the first character of a delimiter but occurred as data
…_2"><a href="/load/rep/vnuk_tbili_poka/6-1-0-900">Vnuk & Тбили – Пока</a></div>This message may appear in several cases:
Line 289,
Column 145:
character "&" is the first character of a delimiter but occurred as data
…1-0-894">Pra(Killa'Gramm) при уч. Stankey & Grob- – Мрази в форме</a></div>This message may appear in several cases:
Line 325,
Column 143:
character "&" is the first character of a delimiter but occurred as data
…l_mix/3-1-0-885">DJ Fisun feat. Алисия – Black & White (Original Mix)</a></div>This message may appear in several cases:
Line 363,
Column 366:
required attribute "type" not specified
…iv></div></div></li></ul></div><script>$(function(){_uBuildMenu('#uMenuDiv1',0…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 376,
Column 80:
document type does not allow element "table" here; assuming missing "li" start-tag
…cing="0" width="100%" class="infTable"><tr><td class="infTitle" colspan="0"><a…</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 376,
Column 1:
start tag was here
<table border="0" cellpadding="3" cellspacing="0" width="100%" class="infTable"…… rel="nofollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" titl…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 389,
Column 41:
general entity "u" not defined and no default entity
… rel="nofollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" titl…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 389,
Column 42:
reference not terminated by REFC delimiter
…rel="nofollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title…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 389,
Column 42:
reference to external entity in attribute value
…rel="nofollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title…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 389,
Column 42:
reference to entity "u" for which no system identifier could be generated
…rel="nofollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title…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 389,
Column 40:
entity was defined here
…a rel="nofollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" tit……ollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz 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 389,
Column 50:
general entity "d" not defined and no default entity
…ollow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz 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 389,
Column 51:
reference not terminated by REFC delimiter
…llow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Co…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 389,
Column 51:
reference to external entity in attribute value
…llow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Co…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 389,
Column 51:
reference to entity "d" for which no system identifier could be generated
…llow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Co…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 389,
Column 49:
entity was defined here
…follow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz ……w" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Count…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 389,
Column 54:
general entity "il" not defined and no default entity
…w" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Count…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 389,
Column 56:
reference not terminated by REFC delimiter
… href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Counter…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 389,
Column 56:
reference to external entity in attribute value
… href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Counter…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 389,
Column 56:
reference to entity "il" for which no system identifier could be generated
… href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Counter…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 389,
Column 53:
entity was defined here
…ow" href="/panel/?a=ustat&u=muzyka&d=e&il=ru" target="_blank" title="uCoz Coun…
Copyright © 2024 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.