Line 12, Column 120: document type does not allow element "noscript" here; assuming missing "object" start-tag
…p100.jcn?1812135"></script><noscript><img src="http://counter.rambler.ru/top1
✉
Line 26, Column 76: document type does not allow element "link" here
…mplates/ER-Rollout/images/favicon.ico" />
✉
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 27, Column 91: document type does not allow element "link" here
…" rel="stylesheet" type="text/css" />
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 28, Column 111: document type does not allow element "link" here
…" rel="stylesheet" type="text/css" />
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 29, Column 102: document type does not allow element "link" here
…" rel="stylesheet" type="text/css" />
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 30, Column 81: document type does not allow element "link" here
…" rel="stylesheet" type="text/css" />
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 31, Column 85: document type does not allow element "link" here
…" rel="stylesheet" type="text/css" />
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 32, Column 85: document type does not allow element "link" here
…" rel="stylesheet" type="text/css" />
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 50, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
</head>
✉
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 12, Column 110: start tag was here
…bler.ru/top100.jcn?1812135"></script><noscript><img src="http://counter.rambl
Line 126, Column 34: document type does not allow element "ul" here; assuming missing "li" start-tag
<ul class="mainmenu accordion">
✉
Line 168, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
</ul></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 126, Column 3: start tag was here
<ul class="mainmenu accordion">
Line 225, Column 864: end tag for "br" omitted, but OMITTAG NO was specified
…gif" /><!--/smile--></div></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 225, Column 859: start tag was here
…mile.gif" /><!--/smile--></div></div><br>
Line 228, Column 139: required attribute "alt" not specified
…/spacer.gif" width="25" height="1" /></td>
✉
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 240, Column 138: required attribute "alt" not specified
…s/spacer.gif" width="1" height="3" /></td>
✉
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 241, Column 127: required attribute "alt" not specified
…s/spacer.gif" width="1" height="3" /></td>
✉
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 244, Column 139: required attribute "alt" not specified
…/spacer.gif" width="25" height="1" /></td>
✉
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 310, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
<…
✉
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 310, Column 9: start tag was here
<br>
Line 333, Column 821: element "noindex" undefined. Did you mean "isindex"?
…с нами напрямую <br /><br /><noindex>manager@czech4you.ru</noindex> <br /><br
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 346, Column 10: end tag for "tr" omitted, but OMITTAG NO was specified
</td>
✉
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 344, Column 4: start tag was here
<tr valign="top">
Line 346, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
</td>
✉
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 343, Column 3: start tag was here
<table width="100%" border="0" cellspacing="0" cellpadding="0">
Line 349, Column 7: end tag for element "td" which is not open
</td>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 350, Column 40: document type does not allow element "td" here
<td width="10" height="28" class="pn"></td>
✉
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 351, Column 6: end tag for element "tr" which is not open
</tr>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 352, Column 8: end tag for element "table" which is not open
</table>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 434, Column 6: end tag for element "div" which is not open
</div>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 234, Column 37: XML Parsing Error: Opening and ending tag mismatch: br line 225 and form
</form>
✉
Line 255, Column 6: XML Parsing Error: Opening and ending tag mismatch: form line 225 and div
</div>
✉
Line 346, Column 10: XML Parsing Error: Opening and ending tag mismatch: tr line 344 and td
</td>
✉
Line 347, Column 9: XML Parsing Error: Opening and ending tag mismatch: table line 343 and tr
</tr>
✉
Line 348, Column 11: XML Parsing Error: Opening and ending tag mismatch: td line 342 and table
</table>
✉
Line 349, Column 7: XML Parsing Error: Opening and ending tag mismatch: tr line 340 and td
</td>
✉
Line 351, Column 6: XML Parsing Error: Opening and ending tag mismatch: table line 312 and tr
</tr>
✉
Line 352, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 312 and table
</table>
✉
Line 353, Column 6: XML Parsing Error: Opening and ending tag mismatch: br line 310 and div
</div>
Сообщение сайта
Что за ошибки
m0tti
0 
13.7.2009, 20:01;
Ответить: ZiTosS
Во что Вы играете?
