Errors found while checking this document as XHTML 1.0 Strict!

Result: 52 Errors, 6 warning(s)
:
: utf-8
: XHTML 1.0 Strict
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
Options

Help on the options is available.

↑ Top

Validation Output: 52 Errors

  1. Error Line 28, Column 16: there is no attribute "property"
    <meta property='vk:app_id' content='3243879' />

    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.

  2. Error Line 56, Column 17: character "%" is not allowed in the value of attribute "id"
    			<ul id="menu-%d0%bc%d0%b5%d0%bd%d1%8e" class="menu"><li class="current_page_…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  3. Error Line 87, Column 199: required attribute "alt" not specified
    …ages/home.jpg" width="26" height="24"/></a></li><li class="page_item page-item…

    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>.

  4. Error Line 97, Column 29: there is no attribute "id"
    																<article id="post-1442" class="post-1442 post type-post status-…

    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.

  5. Error Line 97, Column 47: there is no attribute "class"
    …								<article id="post-1442" class="post-1442 post type-post status-publish…

    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.

  6. Error Line 97, Column 131: element "article" undefined
    …1442 post type-post status-publish format-standard hentry category-poleznosti">

    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).
  7. Error Line 102, Column 38: there is no attribute "itemprop"
    		<span class="auth"> <span itemprop="datePublished" class="timestamp updated">…

    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.

  8. Error Line 102, Column 153: there is no attribute "itemtype"
    …hor vcard" itemprop="author" itemtype="http://schema.org/Person"><span class="…

    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.

  9. Error Line 104, Column 395: element "article" undefined
    …26 post type-post status-publish format-standard hentry category-vebmastering">

    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).
  10. Error Line 111, Column 368: element "article" undefined
    …23 post type-post status-publish format-standard hentry category-seo-internet">

    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).
  11. Error Line 117, Column 351: element "article" undefined
    …16 post type-post status-publish format-standard hentry category-seo-internet">

    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).
  12. Error Line 124, Column 361: element "article" undefined
    …10 post type-post status-publish format-standard hentry category-seo-internet">

    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).
  13. Error Line 148, Column 110: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …earfloat"><span style="font-size:18px; class="widgettitle">Рубрики</span>		<ul>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  14. Error Line 189, Column 126: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …">		<span style="font-size:18px; class="widgettitle">Свежие записи</span>		<ul>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  15. Error Line 243, Column 111: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …le="font-size:18px; class="widgettitle">Популярные статьи</span>			<div class=…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  16. Error Line 244, Column 15: there is no attribute "target"
    <li><a target="_blank" href="http://seowara.ru/seo-internet/%D0%B1%D0%B8%D0%B7%…

    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.

  17. Error Line 247, Column 4: document type does not allow element "hr" here; assuming missing "li" start-tag
    <hr>

  18. Error Line 247, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  19. Info Line 247, Column 1: start tag was here
    <hr>
  20. Error Line 248, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a target="_blank" href="http://seowara.ru/poleznosti/istoriya-23-letnego-l…

    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>").

  21. Error Line 249, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  22. Info Line 249, Column 1: start tag was here
    <hr>
  23. Error Line 251, Column 4: document type does not allow element "hr" here; assuming missing "li" start-tag
    <hr>

  24. Error Line 251, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  25. Info Line 251, Column 1: start tag was here
    <hr>
  26. Error Line 252, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a target="_blank" href="http://seowara.ru/poleznosti/otkroveniya-insajdera…

    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>").

  27. Error Line 253, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  28. Info Line 253, Column 1: start tag was here
    <hr>
  29. Error Line 254, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a target="_blank" href="http://seowara.ru/istorii-uspeha/%D0%B0%D0%BB%D0%B…

    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>").

  30. Error Line 255, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  31. Info Line 255, Column 1: start tag was here
    <hr>
  32. Error Line 256, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a target="_blank" href="http://seowara.ru/poleznosti/mark-dyuma-i-ego-bela…

    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>").

  33. Error Line 257, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  34. Info Line 257, Column 1: start tag was here
    <hr>
  35. Error Line 258, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a target="_blank" href="http://seowara.ru/poleznosti/kapriznyj-starik-stix…

    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>").

  36. Error Line 260, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  37. Info Line 260, Column 1: start tag was here
    <hr>
  38. Error Line 261, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><a target="_blank" href="http://seowara.ru/poleznosti/kak-skachat-video-ili…

    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>").

  39. Error Line 262, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul></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 ">".

  40. Info Line 251, Column 1: start tag was here
    <hr>
  41. Error Line 263, Column 124: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …le="font-size:18px; class="widgettitle">Инвестиции в памм-счета</span>			<div …

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  42. Error Line 263, Column 191: element "noindex" undefined
    …widgettitle">Инвестиции в памм-счета</span>			<div class="textwidget"><noindex>

    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).
  43. Error Line 270, Column 70: end tag for "param" omitted, but OMITTAG NO was specified
            value="targetLink=http://fx-trend.com/new/home?agent=503507">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  44. Info Line 269, Column 5: start tag was here
        <param name="FlashVars"
  45. Error Line 271, Column 40: end tag for "param" omitted, but OMITTAG NO was specified
        <param name="wmode" value="opaque">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  46. Info Line 271, Column 5: start tag was here
        <param name="wmode" value="opaque">
  47. Warning Line 272, Column 59: unclosed start-tag requires SHORTTAG YES
        <p><a href="http://fx-trend.com/new/home?agent=503507"</a></p>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  48. Error Line 294, Column 80: element "noindex" undefined
    <div id="text-2" class="widget widget_text">			<div class="textwidget"><noindex>

    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).
  49. Error Line 295, Column 8: element "center" undefined
    <center>

    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).
  50. Error Line 307, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  51. Info Line 307, Column 1: start tag was here
    <br>
  52. Error Line 308, Column 10: end tag for "center" omitted, but OMITTAG NO was specified
    </noindex>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  53. Info Line 295, Column 1: start tag was here
    <center>
  54. Error Line 315, Column 49: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <a href="http://top100.rambler.ru/navi/2721056/">

    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>").

  55. Error Line 316, Column 87: there is no attribute "border"
    …p://counter.rambler.ru/top100.cnt?2721056" alt="Rambler's Top100" border="0" />

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  56. Error Line 324, Column 9: element "noindex" undefined
    <noindex>

    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).
  57. Error Line 325, Column 5: end tag for element "br" which is not open
    </br>

    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.

  58. Warning Line 326, Column 54: cannot generate system identifier for general entity "type"
    …/blogs.yandex.ru/button/?id=139864603&type=link"><img src="http://button.blogs…

    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.

  59. Error Line 326, Column 54: general entity "type" not defined and no default entity
    …/blogs.yandex.ru/button/?id=139864603&type=link"><img src="http://button.blogs…

    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.

  60. Warning Line 326, Column 58: reference not terminated by REFC delimiter
    …gs.yandex.ru/button/?id=139864603&type=link"><img src="http://button.blogs.yan…

    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.

  61. Warning Line 326, Column 58: reference to external entity in attribute value
    …gs.yandex.ru/button/?id=139864603&type=link"><img src="http://button.blogs.yan…

    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;'.

  62. Error Line 326, Column 58: reference to entity "type" for which no system identifier could be generated
    …gs.yandex.ru/button/?id=139864603&type=link"><img src="http://button.blogs.yan…

    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.

  63. Info Line 326, Column 53: entity was defined here
    …//blogs.yandex.ru/button/?id=139864603&type=link"><img src="http://button.blog…
  64. Error Line 446, Column 237: end tag for "img" omitted, but OMITTAG NO was specified
    …ptimizator.jpg" alt="seo оптимизатор"><p style="color:#fff;">Меня зовут Алексе…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  65. Info Line 446, Column 119: start tag was here
    …БЛОГ</span>			<div class="textwidget"><img style="float:right;"src="http://seo…
  66. Warning Line 530, Column 23: character "&" is the first character of a delimiter but occurred as data
            if (window.Ya && window.Ya.Share) {

    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.
  67. Warning Line 530, Column 24: character "&" is the first character of a delimiter but occurred as data
            if (window.Ya && window.Ya.Share) {

    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.
  68. Error Line 554, 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>.

  69. Error Line 574, Column 27: document type does not allow element "style" here
        <style 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).

  70. Error Line 607, Column 12: element "center" undefined
        <center>

    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).
  71. Error Line 608, Column 167: end tag for "br" omitted, but OMITTAG NO was specified
    …ание в памм счета, не много форекса и чуть-чуть про личные успехи!</strong><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  72. Info Line 608, Column 163: start tag was here
    …ание в памм счета, не много форекса и чуть-чуть про личные успехи!</strong><br>
  73. Error Line 609, Column 460: end tag for "img" omitted, but OMITTAG NO was specified
    …"это черный парень который карает молодые блоги, которые ворую контент"></span>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  74. Info Line 609, Column 197: start tag was here
    …этот черный парень и покарает твой ГС <img style="width:60px;  height:60px;" s…

↑ Top