zerx.ru

Фильмы онлайн смотреть бесплатно в хорошем качестве, смотреть кино онлайн ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    zerx.ru
  • Favicon
  • Alexa Rank
    #2705
  • Google Page Rank
    PR 3
  • Ip Address
    46.249.47.203
  • Page Size
    162.3 KB
  • Images
    2 GIF, 15 JPG, 17 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Фильмы онлайн смотреть бесплатно фильмы онлайн в хорошем качестве, онлайн фильмы смотреть бесплатно, смотреть кино онлайн.
  • Meta Keyword
    фильмы, онлайн, кино, смотреть, бесплатно, онлайн фильмы, мультфильмы, регистрации, фильмы онлайн, смотреть бесплатно, в хорошем качестве, кино
  • Meta Description
    Фильмы онлайн смотреть бесплатно в хорошем качестве, смотреть кино онлайн

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    46.249.47.203
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from zerx.ru.

HTML Analysis

  • server: nginx
  • date: Tue, 17 Sep 2013 21:00:53 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.19
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: ZERX.RU
nserver: ns1.zerx.ru. 94.242.214.136
nserver: ns2.zerx.ru. 94.242.214.250
state: REGISTERED, DELEGATED, UNVERIFIED
person: Private Person
registrar: NAUNET-REG-RIPN
admin-contact: https://client.naunet.ru/c/whoiscontact
created: 2008.06.04
paid-till: 2013.06.04
free-date: 2013.07.05
source: TCI

Last updated on 2012.11.22 10:41:35 MSK

DNS Analysis


DNS servers
ns2.zerx.ru [93.170.135.5]
ns1.zerx.ru [212.113.36.67]

DNS Records

Answer records
zerx.ru SOA
server: ns1.zerx.ru
email: slava@servers-support.ru
serial: 2012121901
refresh: 10800
retry: 1800
expire: 604800
minimum ttl: 86400
60s
zerx.ru NS  ns2.zerx.ru 60s
zerx.ru NS  ns1.zerx.ru 60s
zerx.ru A 212.113.36.75 60s

Authority records

Additional records
ns1.zerx.ru A 212.113.36.67 60s
ns2.zerx.ru A 93.170.135.5 60s

IP 46.249.47.203 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 46.249.47.203

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 349 Errors
  • 32 Warnings
Ratio Text/Html
  • 0.5380129628626622
Message Error
  • Error Line 78, Column 7: required attribute "type" not specified
    <style>.style_1 img { float: left; width: 200px; margin-right: 5px; border: 1px…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 78, Column 7: document type does not allow element "style" here
    <style>.style_1 img { float: left; width: 200px; margin-right: 5px; border: 1px…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 135, Column 9: element "noindex" undefined
    <noindex><noscript><div class="no_ys">Уважаемый пользователь! В Вашем браузере …

    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).
  • Error Line 150, Column 10: 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>.

  • Warning Line 153, Column 36: character "&" is the first character of a delimiter but occurred as data
         if (ev.target.id != blocks.id && blocks.style.display == 'block')  {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 153, Column 37: character "&" is the first character of a delimiter but occurred as data
         if (ev.target.id != blocks.id && blocks.style.display == 'block')  {

    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.
  • Error Line 176, Column 78: end tag for "input" omitted, but OMITTAG NO was specified
      onfocus="if(this.value=='Поиск по актёрам...') this.value='';" type="text">

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

  • Info Line 174, Column 3: start tag was here
      <input class="reset sinput" name="name" value="Поиск по актёрам..." 
  • Error Line 178, Column 113: end tag for "input" omitted, but OMITTAG NO was specified
    …pe="image" src="/templates/zerxnew/images/spacer.gif" alt="Поиск"></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 ">".

  • Info Line 178, Column 3: start tag was here
      <input class="submit" value="Поиск" type="image" src="/templates/zerxnew/imag…
  • Error Line 179, 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).
  • Error Line 200, Column 55: element "noindex" undefined
    …s="main_link" rel="nofollow" ><noindex><div id="cmain_link"></div></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).
  • Error Line 209, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<div id=films_prev class="films_l_arrow"><div  class="left_arrow" onclick="sli…
  • Error Line 210, Column 36: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
     <div class="films_images" onclick=slideractive(this) onmouseleave=sliderclean(…
  • Error Line 210, Column 48: an attribute value must be a literal unless it contains only name characters
    …ss="films_images" onclick=slideractive(this) onmouseleave=sliderclean(this)><d…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 210, Column 68: there is no attribute "onmouseleave"
    …click=slideractive(this) onmouseleave=sliderclean(this)><div class=scroll><div…

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

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

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

  • Error Line 210, Column 68: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …click=slideractive(this) onmouseleave=sliderclean(this)><div class=scroll><div…
  • Error Line 210, Column 79: an attribute value must be a literal unless it contains only name characters
    …ractive(this) onmouseleave=sliderclean(this)><div class=scroll><div class="fil…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 210, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nmouseleave=sliderclean(this)><div class=scroll><div class="films_images_item">
  • Error Line 211, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/uploads/posts/rate/39999.jpg" alt="" title="Хранилище 13 (4 сезон)"></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 ">".

  • Info Line 211, Column 121: start tag was here
    …/39999-hranilische-13-4-sezon.html'" ><img src="/uploads/posts/rate/39999.jpg"…
  • Error Line 211, Column 205: end tag for "a" omitted, but OMITTAG NO was specified
    …rc="/uploads/posts/rate/39999.jpg" alt="" title="Хранилище 13 (4 сезон)"></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 ">".

  • Info Line 211, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 214, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …/uploads/posts/rate/39834.jpg" alt="" title="Однажды в сказке (2 сезон)"></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 ">".

  • Info Line 214, Column 124: start tag was here
    …834-odnazhdy-v-skazke-2-sezon.html'" ><img src="/uploads/posts/rate/39834.jpg"…
  • Error Line 214, Column 212: end tag for "a" omitted, but OMITTAG NO was specified
    …/uploads/posts/rate/39834.jpg" alt="" title="Однажды в сказке (2 сезон)"></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 ">".

  • Info Line 214, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 217, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …c="/uploads/posts/rate/40446.jpg" alt="" title="Тайны Хейвена (3 сезон)"></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 ">".

  • Info Line 217, Column 120: start tag was here
    …'/40446-tayny-heyvena-3-sezon.html'" ><img src="/uploads/posts/rate/40446.jpg"…
  • Error Line 217, Column 205: end tag for "a" omitted, but OMITTAG NO was specified
    …c="/uploads/posts/rate/40446.jpg" alt="" title="Тайны Хейвена (3 сезон)"></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 ">".

  • Info Line 217, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 220, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/uploads/posts/rate/40638.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 ">".

  • Info Line 220, Column 121: start tag was here
    …/40638-poka-cvetet-paporotnik.html'" ><img src="/uploads/posts/rate/40638.jpg"…
  • Error Line 220, Column 205: end tag for "a" omitted, but OMITTAG NO was specified
    …rc="/uploads/posts/rate/40638.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 ">".

  • Info Line 220, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 223, Column 223: end tag for "img" omitted, but OMITTAG NO was specified
    …/posts/rate/35509.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 ">".

  • Info Line 223, Column 127: start tag was here
    …-voskreshenie-temnogo-rycarya.html'" ><img src="/uploads/posts/rate/35509.jpg"…
  • Error Line 223, Column 223: end tag for "a" omitted, but OMITTAG NO was specified
    …/posts/rate/35509.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 ">".

  • Info Line 223, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 226, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …loads/posts/rate/41420.jpg" alt="" title="Записки юного врача (1 сезон)"></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 ">".

  • Info Line 226, Column 128: start tag was here
    …zapiski-yunogo-vracha-1-sezon.html'" ><img src="/uploads/posts/rate/41420.jpg"…
  • Error Line 226, Column 219: end tag for "a" omitted, but OMITTAG NO was specified
    …loads/posts/rate/41420.jpg" alt="" title="Записки юного врача (1 сезон)"></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 ">".

  • Info Line 226, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 229, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="/uploads/posts/rate/39885.jpg" alt="" title="Сплетница (6 сезон)"></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 ">".

  • Info Line 229, Column 116: start tag was here
    …ref='/39885-spletnica-6-sezon.html'" ><img src="/uploads/posts/rate/39885.jpg"…
  • Error Line 229, Column 197: end tag for "a" omitted, but OMITTAG NO was specified
    …g src="/uploads/posts/rate/39885.jpg" alt="" title="Сплетница (6 сезон)"></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 ">".

  • Info Line 229, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 232, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …c="/uploads/posts/rate/40593.jpeg" alt="" title="Сыны Анархии (5 сезон)"></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 ">".

  • Info Line 232, Column 119: start tag was here
    …='/40593-syny-anarhii-5-sezon.html'" ><img src="/uploads/posts/rate/40593.jpeg…
  • Error Line 232, Column 204: end tag for "a" omitted, but OMITTAG NO was specified
    …c="/uploads/posts/rate/40593.jpeg" alt="" title="Сыны Анархии (5 сезон)"></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 ">".

  • Info Line 232, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 235, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …posts/rate/23085.jpg" alt="" title="Человек-паук 4 / Новый Человек-паук"></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 ">".

  • Info Line 235, Column 136: start tag was here
    …-pauk-4-trejjler-spider-man-4.html'" ><img src="/uploads/posts/rate/23085.jpg"…
  • Error Line 235, Column 233: end tag for "a" omitted, but OMITTAG NO was specified
    …posts/rate/23085.jpg" alt="" title="Человек-паук 4 / Новый Человек-паук"></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 ">".

  • Info Line 235, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 238, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …/uploads/posts/rate/37890.jpg" alt="" title="007: Координаты «Скайфолл»"></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 ">".

  • Info Line 238, Column 114: start tag was here
    ….href='/37890-dzheyms-bond-23.html'" ><img src="/uploads/posts/rate/37890.jpg"…
  • Error Line 238, Column 202: end tag for "a" omitted, but OMITTAG NO was specified
    …/uploads/posts/rate/37890.jpg" alt="" title="007: Координаты «Скайфолл»"></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 ">".

  • Info Line 238, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 241, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …ds/posts/rate/39667.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 ">".

  • Info Line 241, Column 130: start tag was here
    …i-bogatyrya-na-dalnih-beregah.html'" ><img src="/uploads/posts/rate/39667.jpg"…
  • Error Line 241, Column 224: end tag for "a" omitted, but OMITTAG NO was specified
    …ds/posts/rate/39667.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 ">".

  • Info Line 241, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 244, Column 183: end tag for "img" omitted, but OMITTAG NO was specified
    …l'" ><img src="/uploads/posts/rate/41306.png" alt="" title="Крутые 90-е"></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 ">".

  • Info Line 244, Column 110: start tag was here
    …tion.href='/41306-krutye-90-e.html'" ><img src="/uploads/posts/rate/41306.png"…
  • Error Line 244, Column 183: end tag for "a" omitted, but OMITTAG NO was specified
    …l'" ><img src="/uploads/posts/rate/41306.png" alt="" title="Крутые 90-е"></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 ">".

  • Info Line 244, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 247, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …/uploads/posts/rate/39797.jpg" alt="" title="Счастливы вместе (6 сезон)"></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 ">".

  • Info Line 247, Column 124: start tag was here
    …797-schastlivy-vmeste-6-sezon.html'" ><img src="/uploads/posts/rate/39797.jpg"…
  • Error Line 247, Column 212: end tag for "a" omitted, but OMITTAG NO was specified
    …/uploads/posts/rate/39797.jpg" alt="" title="Счастливы вместе (6 сезон)"></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 ">".

  • Info Line 247, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 250, Column 173: end tag for "img" omitted, but OMITTAG NO was specified
    …v.html'" ><img src="/uploads/posts/rate/40530.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 ">".

  • Info Line 250, Column 105: start tag was here
    ….location.href='/40530-karpov.html'" ><img src="/uploads/posts/rate/40530.jpg"…
  • Error Line 250, Column 173: end tag for "a" omitted, but OMITTAG NO was specified
    …v.html'" ><img src="/uploads/posts/rate/40530.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 ">".

  • Info Line 250, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 253, Column 245: end tag for "img" omitted, but OMITTAG NO was specified
    …te/41004.jpg" alt="" title="Портал юрского периода: Новый мир (1 сезон)"></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 ">".

  • Info Line 253, Column 140: start tag was here
    …ogo-perioda-novyy-mir-1-sezon.html'" ><img src="/uploads/posts/rate/41004.jpg"…
  • Error Line 253, Column 245: end tag for "a" omitted, but OMITTAG NO was specified
    …te/41004.jpg" alt="" title="Портал юрского периода: Новый мир (1 сезон)"></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 ">".

  • Info Line 253, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 256, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …" ><img src="/uploads/posts/rate/36856.jpg" alt="" title="Неудержимые 2"></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 ">".

  • Info Line 256, Column 113: start tag was here
    …n.href='/36856-neuderzhimye-2.html'" ><img src="/uploads/posts/rate/36856.jpg"…
  • Error Line 256, Column 188: end tag for "a" omitted, but OMITTAG NO was specified
    …" ><img src="/uploads/posts/rate/36856.jpg" alt="" title="Неудержимые 2"></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 ">".

  • Info Line 256, Column 37: start tag was here
     <div class="films_images_item_img"><a href="#"  onclick="document.location.hre…
  • Error Line 259, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
     <div id=films_next class="films_r_arrow"><div  id="actor_arrow_r" onclick="sli…
  • Error Line 263, Column 76: "itemscope" is not a member of a group specified for any attribute
    …iv class="rcolomn mainside" itemscope itemtype="http://schema.org/Movie">  <ta…
  • Error Line 263, Column 85: there is no attribute "itemtype"
    …"rcolomn mainside" itemscope itemtype="http://schema.org/Movie">  <table 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.

  • Error Line 270, Column 355: required attribute "alt" not specified
    …olid; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38973-o…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 270, Column 359: end tag for "img" omitted, but OMITTAG NO was specified
    …; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38973-ohotn…

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

  • Info Line 270, Column 176: start tag was here
    …ru/38973-ohotniki-na-gangsterov.html"><img src="http://img2.zerx.ru/uploads/po…
  • Error Line 270, Column 364: end tag for "br" omitted, but OMITTAG NO was specified
    …ding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38973-ohotniki-n…

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

  • Info Line 270, Column 360: start tag was here
    … padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38973-ohotni…
  • Error Line 270, Column 453: end tag for "br" omitted, but OMITTAG NO was specified
    …v.html">Охотники на гангстеров</a><br><a href="http://zerx.ru/?do=premiere"></…

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

  • Info Line 270, Column 449: start tag was here
    …terov.html">Охотники на гангстеров</a><br><a href="http://zerx.ru/?do=premiere…
  • Error Line 270, Column 750: required attribute "alt" not specified
    …olid; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/40739-p…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 270, Column 754: end tag for "img" omitted, but OMITTAG NO was specified
    …; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/40739-parke…

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

  • Info Line 270, Column 587: start tag was here
    …ef="http://zerx.ru/40739-parker.html"><img src="http://img2.zerx.ru/uploads/po…
  • Error Line 270, Column 759: end tag for "br" omitted, but OMITTAG NO was specified
    …ding: 5px; background: #000;"></a><br><a href="http://zerx.ru/40739-parker.htm…

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

  • Info Line 270, Column 755: start tag was here
    … padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/40739-parker…
  • Error Line 270, Column 816: end tag for "br" omitted, but OMITTAG NO was specified
    …x.ru/40739-parker.html">Паркер</a><br><a href="http://zerx.ru/?do=premiere"></…

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

  • Info Line 270, Column 812: start tag was here
    …/zerx.ru/40739-parker.html">Паркер</a><br><a href="http://zerx.ru/?do=premiere…
  • Error Line 270, Column 1142: required attribute "alt" not specified
    …olid; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38091-n…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 270, Column 1146: end tag for "img" omitted, but OMITTAG NO was specified
    …; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38091-ne-ro…

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

  • Info Line 270, Column 970: start tag was here
    …8091-ne-rozhden-byt-gladiatorom.html"><img src="http://img2.zerx.ru/uploads/po…
  • Error Line 270, Column 1151: end tag for "br" omitted, but OMITTAG NO was specified
    …ding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38091-ne-rozhden…

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

  • Info Line 270, Column 1147: start tag was here
    … padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/38091-ne-roz…
  • Error Line 270, Column 1237: end tag for "br" omitted, but OMITTAG NO was specified
    …diatorom.html">Гладиаторы Рима</a><br><a href="http://zerx.ru/?do=premiere"></…

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

  • Info Line 270, Column 1233: start tag was here
    …-gladiatorom.html">Гладиаторы Рима</a><br><a href="http://zerx.ru/?do=premiere…
  • Error Line 270, Column 1546: required attribute "alt" not specified
    …olid; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/37650-h…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 270, Column 1550: end tag for "img" omitted, but OMITTAG NO was specified
    …; padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/37650-hroni…

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

  • Info Line 270, Column 1382: start tag was here
    …zerx.ru/37650-hroniki-riddika-2.html"><img src="http://img2.zerx.ru/uploads/po…
  • Error Line 270, Column 1555: end tag for "br" omitted, but OMITTAG NO was specified
    …ding: 5px; background: #000;"></a><br><a href="http://zerx.ru/37650-hroniki-ri…

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

  • Info Line 270, Column 1551: start tag was here
    … padding: 5px; background: #000;"></a><br><a href="http://zerx.ru/37650-hronik…
  • Error Line 270, Column 1646: end tag for "br" omitted, but OMITTAG NO was specified
    …>Хроники Риддика 2 / Риддик 3D</a><br><a href="http://zerx.ru/?do=premiere"></…

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

  • Info Line 270, Column 1642: start tag was here
    …tml">Хроники Риддика 2 / Риддик 3D</a><br><a href="http://zerx.ru/?do=premiere…
  • Error Line 288, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …emplates/zerxnew/images/utorrent.png' title='Torrent' alt='Torrent'></a></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 ">".

  • Info Line 288, Column 131: start tag was here
    …ef="/39747-torrent-dzhek-richer.html"><img src='http://zerx.ru/templates/zerxn…
  • Warning Line 303, Column 242: cannot generate system identifier for general entity "year"
    …><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </d…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 303, Column 242: general entity "year" not defined and no default entity
    …><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </d…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 303, Column 246: reference not terminated by REFC delimiter
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 303, Column 246: reference to external entity in attribute value
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 303, Column 246: reference to entity "year" for which no system identifier could be generated
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 303, Column 252: cannot generate system identifier for general entity "month"
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 303, Column 252: general entity "month" not defined and no default entity
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 303, Column 257: reference not terminated by REFC delimiter
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 303, Column 257: reference to external entity in attribute value
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 303, Column 257: reference to entity "month" for which no system identifier could be generated
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 303, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </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 ">".

  • Info Line 303, Column 264: start tag was here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Warning Line 304, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 304, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 304, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 334, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 340, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …emplates/zerxnew/images/utorrent.png' title='Torrent' alt='Torrent'></a></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 ">".

  • Info Line 340, Column 127: start tag was here
    …a href="/40735-torrent-movie-43.html"><img src='http://zerx.ru/templates/zerxn…
  • Warning Line 355, Column 246: reference not terminated by REFC delimiter
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 355, Column 246: reference to external entity in attribute value
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 355, Column 246: reference to entity "year" for which no system identifier could be generated
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 355, Column 257: reference not terminated by REFC delimiter
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 355, Column 257: reference to external entity in attribute value
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 355, Column 257: reference to entity "month" for which no system identifier could be generated
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 355, Column 267: end tag for "br" omitted, but OMITTAG NO was specified
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </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 ">".

  • Info Line 355, Column 263: start tag was here
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=01">3<br>января</a> </div>
  • Warning Line 356, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 356, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 356, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 386, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 388, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div><div class="basebox">

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

  • Info Line 263, Column 138: start tag was here
    …org/Movie">  <table class="conts"><tr><td style="padding: 0"> 	<div class="blo…
  • Error Line 388, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div><div class="basebox">

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

  • Info Line 263, Column 134: start tag was here
    …ema.org/Movie">  <table class="conts"><tr><td style="padding: 0"> 	<div class=…
  • Error Line 388, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div><div class="basebox">

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

  • Info Line 263, Column 113: start tag was here
    … itemtype="http://schema.org/Movie">  <table class="conts"><tr><td style="padd…
  • Error Line 392, Column 229: end tag for "img" omitted, but OMITTAG NO was specified
    …emplates/zerxnew/images/utorrent.png' title='Torrent' alt='Torrent'></a></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 ">".

  • Info Line 392, Column 132: start tag was here
    …f="/39647-torrent-anna-karenina.html"><img src='http://zerx.ru/templates/zerxn…
  • Warning Line 407, Column 246: reference not terminated by REFC delimiter
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 407, Column 246: reference to external entity in attribute value
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 407, Column 246: reference to entity "year" for which no system identifier could be generated
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 407, Column 257: reference not terminated by REFC delimiter
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 407, Column 257: reference to external entity in attribute value
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 407, Column 257: reference to entity "month" for which no system identifier could be generated
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 407, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </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 ">".

  • Info Line 407, Column 264: start tag was here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Warning Line 408, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 408, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 408, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 438, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 444, Column 238: end tag for "img" omitted, but OMITTAG NO was specified
    …emplates/zerxnew/images/utorrent.png' title='Torrent' alt='Torrent'></a></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 ">".

  • Info Line 444, Column 141: start tag was here
    …-torrent-dzhango-osvobozhdennyy.html"><img src='http://zerx.ru/templates/zerxn…
  • Warning Line 459, Column 246: reference not terminated by REFC delimiter
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 459, Column 246: reference to external entity in attribute value
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 459, Column 246: reference to entity "year" for which no system identifier could be generated
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 459, Column 257: reference not terminated by REFC delimiter
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 459, Column 257: reference to external entity in attribute value
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 459, Column 257: reference to entity "month" for which no system identifier could be generated
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 459, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </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 ">".

  • Info Line 459, Column 264: start tag was here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">17<br>января</a> </div>
  • Warning Line 460, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 460, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 460, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 490, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 538, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('morok', 'ht…

    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).
  • Error Line 586, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('parovoz0083…

    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).
  • Error Line 606, Column 1473: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …><!--/colorstart--><div align="center">4-й этап будет закончен в пятницу, в 22…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 634, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('parovoz0083…

    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).
  • Error Line 640, Column 222: end tag for "img" omitted, but OMITTAG NO was specified
    …emplates/zerxnew/images/utorrent.png' title='Torrent' alt='Torrent'></a></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 ">".

  • Info Line 640, Column 125: start tag was here
    …><a href="/34467-torrent-hobbit.html"><img src='http://zerx.ru/templates/zerxn…
  • Warning Line 655, Column 246: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 655, Column 246: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 655, Column 246: reference to entity "year" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 655, Column 257: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 655, Column 257: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 655, Column 257: reference to entity "month" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 655, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </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 ">".

  • Info Line 655, Column 264: start tag was here
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">20<br>декабря</a> </div>
  • Warning Line 656, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 656, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 656, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 686, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Warning Line 707, Column 246: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 707, Column 246: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 707, Column 246: reference to entity "year" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 707, Column 257: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 707, Column 257: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 707, Column 257: reference to entity "month" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 707, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </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 ">".

  • Info Line 707, Column 264: start tag was here
    … href="http://zerx.ru/?do=premiere&year=2012&month=12">31<br>декабря</a> </div>
  • Warning Line 708, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 708, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 708, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 738, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('rapxrap', '…

    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).
  • Error Line 740, Column 6: end tag for element "div" which is not open
    </div><div class="basebox">

    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.

  • Error Line 744, Column 96: element "noindex" undefined
    …x; top: 0px;margin-top:0.8em"><noindex><nofollow><a href='/torrent/42009/'><im…

    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).
  • Error Line 744, Column 106: element "nofollow" undefined
    …x;margin-top:0.8em"><noindex><nofollow><a href='/torrent/42009/'><img src='htt…

    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).
  • Error Line 744, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …es/utorrent.png' title='Torrent' alt='Torrent'></a></nofollow></noindex></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 ">".

  • Info Line 744, Column 133: start tag was here
    …x><nofollow><a href='/torrent/42009/'><img src='http://zerx.ru/templates/zerxn…
  • Error Line 786, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('rapxrap', '…

    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).
  • Error Line 788, Column 6: end tag for element "div" which is not open
    </div><div class="basebox">

    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.

  • Error Line 792, Column 96: element "noindex" undefined
    …x; top: 0px;margin-top:0.8em"><noindex><nofollow><a href='/torrent/41959/'><im…

    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).
  • Error Line 792, Column 106: element "nofollow" undefined
    …x;margin-top:0.8em"><noindex><nofollow><a href='/torrent/41959/'><img src='htt…

    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).
  • Error Line 792, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …es/utorrent.png' title='Torrent' alt='Torrent'></a></nofollow></noindex></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 ">".

  • Info Line 792, Column 133: start tag was here
    …x><nofollow><a href='/torrent/41959/'><img src='http://zerx.ru/templates/zerxn…
  • Error Line 834, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('rapxrap', '…

    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).
  • Error Line 836, Column 6: end tag for element "div" which is not open
    </div><div class="basebox">

    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.

  • Warning Line 855, Column 246: reference not terminated by REFC delimiter
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 855, Column 246: reference to external entity in attribute value
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 855, Column 246: reference to entity "year" for which no system identifier could be generated
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 855, Column 257: reference not terminated by REFC delimiter
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 855, Column 257: reference to external entity in attribute value
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 855, Column 257: reference to entity "month" for which no system identifier could be generated
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 855, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </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 ">".

  • Info Line 855, Column 264: start tag was here
    …<a href="http://zerx.ru/?do=premiere&year=2013&month=03">20<br>марта</a> </div>
  • Warning Line 856, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 856, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 856, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 886, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 888, Column 6: end tag for element "div" which is not open
    </div><div class="basebox">

    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.

  • Warning Line 907, Column 246: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 907, Column 246: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 907, Column 246: reference to entity "year" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 907, Column 257: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 907, Column 257: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 907, Column 257: reference to entity "month" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 907, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </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 ">".

  • Info Line 907, Column 264: start tag was here
    … href="http://zerx.ru/?do=premiere&year=2013&month=02">28<br>февраля</a> </div>
  • Warning Line 908, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 908, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 908, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2013">2013</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 938, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 940, Column 6: end tag for element "div" which is not open
    </div><div class="basebox">

    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.

  • Error Line 944, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …emplates/zerxnew/images/utorrent.png' title='Torrent' alt='Torrent'></a></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 ">".

  • Info Line 944, Column 163: start tag was here
    …den-naruto-shippuuden-2007-2008.html"><img src='http://zerx.ru/templates/zerxn…
  • Error Line 986, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('Slavik', 'h…

    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).
  • Error Line 988, Column 6: end tag for element "div" which is not open
    </div><div class="basebox">

    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.

  • Warning Line 1007, Column 246: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1007, Column 246: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1007, Column 246: reference to entity "year" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Warning Line 1007, Column 257: reference not terminated by REFC delimiter
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1007, Column 257: reference to external entity in attribute value
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1007, Column 257: reference to entity "month" for which no system identifier could be generated
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 251: entity was defined here
    …a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </div>
  • Error Line 1007, Column 268: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </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 ">".

  • Info Line 1007, Column 264: start tag was here
    … href="http://zerx.ru/?do=premiere&year=2012&month=10">15<br>октября</a> </div>
  • Warning Line 1008, Column 174: reference not terminated by REFC delimiter
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1008, Column 174: reference to external entity in attribute value
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1008, Column 174: reference to entity "year" for which no system identifier could be generated
    …padding: 3px 0;"><a href="http://zerx.ru/?do=premiere&year=2012">2012</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 303, Column 241: entity was defined here
    …"><a href="http://zerx.ru/?do=premiere&year=2013&month=01">10<br>января</a> </…
  • Error Line 1038, Column 14: element "noindex" undefined
    		<p><noindex><span class="arg">Разместил: <a onclick="ShowProfile('rapxrap', '…

    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).
  • Error Line 1040, Column 6: end tag for element "div" which is not open
    </div><div align="center" class="basenavi">

    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.

  • Error Line 1045, Column 8: required attribute "type" not specified
    <script>var count_all = '{count_all}';</script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1048, Column 114: end tag for element "div" which is not open
    …Page.png" onclick="pageLocat()" value="Go" /></div><br></div></td></tr></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.

  • Error Line 1048, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …Page.png" onclick="pageLocat()" value="Go" /></div><br></div></td></tr></table>

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

  • Info Line 1048, Column 105: start tag was here
    …Page.png" onclick="pageLocat()" value="Go" /></div><br></div></td></tr></table>
  • Error Line 1048, Column 119: end tag for element "td" which is not open
    …Page.png" onclick="pageLocat()" value="Go" /></div><br></div></td></tr></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.

  • Error Line 1048, Column 124: end tag for element "tr" which is not open
    …Page.png" onclick="pageLocat()" value="Go" /></div><br></div></td></tr></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.

  • Error Line 1048, Column 132: end tag for element "table" which is not open
    …Page.png" onclick="pageLocat()" value="Go" /></div><br></div></td></tr></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.

  • Error Line 1057, 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.

  • Error Line 1074, 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 ">".

  • Info Line 1074, Column 1: start tag was here
    <hr>
  • Error Line 1076, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="/top100/">ТОП-100 фильмов ZERX.RU</a><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 ">".

  • Info Line 1076, Column 47: start tag was here
    <a href="/top100/">ТОП-100 фильмов ZERX.RU</a><br>
  • Error Line 1092, Column 127: document type does not allow element "link" here
    …emplates/zerxnew/style/top_profile_new.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).

  • Error Line 1096, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_209952.jpg" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1096, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_209952.jpg" style="width:50px; height:50px;">

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

  • Info Line 1096, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_209952.jpg" style="width:50px; height:50…
  • Error Line 1098, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1101, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_285203.jpg" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1101, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_285203.jpg" style="width:50px; height:50px;">

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

  • Info Line 1101, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_285203.jpg" style="width:50px; height:50…
  • Error Line 1103, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1106, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_408253.png" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1106, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_408253.png" style="width:50px; height:50px;">

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

  • Info Line 1106, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_408253.png" style="width:50px; height:50…
  • Error Line 1108, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1111, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_467422.jpg" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1111, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_467422.jpg" style="width:50px; height:50px;">

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

  • Info Line 1111, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_467422.jpg" style="width:50px; height:50…
  • Error Line 1113, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1116, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_217473.jpg" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1116, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_217473.jpg" style="width:50px; height:50px;">

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

  • Info Line 1116, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_217473.jpg" style="width:50px; height:50…
  • Error Line 1118, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1121, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_430207.gif" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1121, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_430207.gif" style="width:50px; height:50px;">

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

  • Info Line 1121, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_430207.gif" style="width:50px; height:50…
  • Error Line 1123, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1126, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_108899.gif" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1126, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_108899.gif" style="width:50px; height:50px;">

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

  • Info Line 1126, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_108899.gif" style="width:50px; height:50…
  • Error Line 1128, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1131, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_367852.jpg" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1131, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_367852.jpg" style="width:50px; height:50px;">

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

  • Info Line 1131, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_367852.jpg" style="width:50px; height:50…
  • Error Line 1133, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1136, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_199692.jpg" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1136, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_199692.jpg" style="width:50px; height:50px;">

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

  • Info Line 1136, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_199692.jpg" style="width:50px; height:50…
  • Error Line 1138, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1141, Column 84: required attribute "alt" not specified
    …				<img src="/uploads/fotos/foto_292883.gif" style="width:50px; height:50px;">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1141, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …				<img src="/uploads/fotos/foto_292883.gif" style="width:50px; height:50px;">

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

  • Info Line 1141, Column 10: start tag was here
    									<img src="/uploads/fotos/foto_292883.gif" style="width:50px; height:50…
  • Error Line 1143, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1156, Column 25: there is no attribute "data"
    	<span id="a34467" data="/data/34467/" class="betterTip" title=""></span>

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

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

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

  • Error Line 1282, Column 4: element "BR" undefined
    <BR></table></div></div></div></div></div></div>

    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).
  • Error Line 1282, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    <BR></table></div></div></div></div></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 ">".

  • Info Line 1282, Column 1: start tag was here
    <BR></table></div></div></div></div></div></div>
  • Error Line 1285, Column 9: element "noindex" undefined
    <noindex><noindex><!-- MComposite Start -->

    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).
  • Error Line 1285, Column 18: element "noindex" undefined
    <noindex><noindex><!-- MComposite Start -->

    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).
  • Error Line 1289, Column 9: element "noindex" undefined
    <noindex><div id="MarketGidComposite15580"></div></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).
  • Error Line 1289, Column 19: ID "MarketGidComposite15580" already defined
    <noindex><div id="MarketGidComposite15580"></div></noindex>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1286, Column 10: ID "MarketGidComposite15580" first defined here
    <div id="MarketGidComposite15580"></div>
  • Error Line 1291, Column 9: element "noindex" undefined
    <noindex><noindex><!-- MComposite Start -->

    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).
  • Error Line 1291, Column 18: element "noindex" undefined
    <noindex><noindex><!-- MComposite Start -->

    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).
  • Error Line 1296, Column 17: document type does not allow element "tr" here
    <tr valign="top"><td width="50%"><div class="slavik-10-top">Сегодня родились</d…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1296, Column 206: required attribute "alt" not specified
    …oads/peoples/28911.jpg" style="width: 120px; height: 190px;" /></a><br /><br />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1297, Column 250: end tag for "br" omitted, but OMITTAG NO was specified
    …11/">Анна Руднева</a> (1990)<br /><br><a href="/actors/born/11/01/">Все именин…

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

  • Info Line 1297, Column 246: start tag was here
    …/33311/">Анна Руднева</a> (1990)<br /><br><a href="/actors/born/11/01/">Все им…
  • Error Line 1298, Column 187: element "BR" undefined
    …op/'"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr…

    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).
  • Error Line 1298, Column 191: element "BR" undefined
    …"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr><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).
  • Error Line 1298, Column 222: end tag for "BR" omitted, but OMITTAG NO was specified
    …"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr><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 ">".

  • Info Line 1298, Column 188: start tag was here
    …p/'"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr>…
  • Error Line 1298, Column 222: end tag for "BR" omitted, but OMITTAG NO was specified
    …"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr><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 ">".

  • Info Line 1298, Column 184: start tag was here
    …s/top/'"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td><…
  • Error Line 1298, Column 231: element "BR" undefined
    …"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr><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).
  • Error Line 1299, Column 8: end tag for "BR" omitted, but OMITTAG NO was specified
    </table></div></div></div></div></div></div><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 ">".

  • Info Line 1298, Column 228: start tag was here
    …"><b>ТОП 100 АКТЕРОВ</b></span><BR><BR><div id="lx_373158"></div></td></tr><BR>
  • Error Line 1299, Column 8: "tr" not finished but containing element ended
    </table></div></div></div></div></div></div><br />
  • Error Line 1299, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table></div></div></div></div></div></div><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 ">".

  • Info Line 1295, Column 188: start tag was here
    …table width="100%" border="0" cellspacing="0" cellpadding="0"><tr valign="top">
  • Error Line 1303, Column 24: end tag for "br" omitted, but OMITTAG NO was specified
    <div class="dcont"><br><br></div></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 ">".

  • Info Line 1303, Column 20: start tag was here
    <div class="dcont"><br><br></div></div></div>
  • Error Line 1303, Column 33: end tag for "br" omitted, but OMITTAG NO was specified
    <div class="dcont"><br><br></div></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 ">".

  • Info Line 1303, Column 24: start tag was here
    <div class="dcont"><br><br></div></div></div>
  • Error Line 1309, Column 9: element "noindex" undefined
    <noindex><!--LiveInternet counter--><script type="text/javascript" src="/templa…

    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).
  • Error Line 1320, 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 ">".

  • Info Line 1320, Column 1: start tag was here
    <br>
  • Error Line 1327, Column 126: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …"" onclick="setcookie(); return false;" type="checkbox" value="" checked />)');

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

  • Error Line 1327, Column 126: document type does not allow element "input" here
    …"" onclick="setcookie(); return false;" type="checkbox" value="" checked />)');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1331, Column 118: document type does not allow element "input" here
    …ut name="" onclick="setcookie(); return false;" type="checkbox" value="" />)');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1348, Column 29: end tag for element "div" which is not open
    <div class="clr"></div></div></div></div></div></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.

  • Error Line 1348, Column 35: end tag for element "div" which is not open
    <div class="clr"></div></div></div></div></div></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.

  • Error Line 1348, Column 41: end tag for element "div" which is not open
    <div class="clr"></div></div></div></div></div></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.

  • Error Line 1348, Column 47: end tag for element "div" which is not open
    <div class="clr"></div></div></div></div></div></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.

  • Error Line 1348, Column 53: end tag for element "div" which is not open
    <div class="clr"></div></div></div></div></div></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.

  • Error Line 1350, Column 66: element "noindex" undefined
    …ss="fmenu"><div class="fmenu"><noindex><a class="thide lnkhome" href="/" rel="…

    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).
  • Error Line 1351, Column 135: element "noindex" undefined
    …right &copy; 2006-2012 Проект <noindex><a href="/">ZERX.RU</a></noindex></span…

    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).
  • Error Line 1353, 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.

  • Error Line 1355, 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).
  • Warning Line 1358, Column 106: cannot generate system identifier for general entity "div"
    … src="http://www.directadvert.ru/show.cgi?adp=76496&div=DIV_DA_76496"></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 "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1358, Column 106: general entity "div" not defined and no default entity
    … src="http://www.directadvert.ru/show.cgi?adp=76496&div=DIV_DA_76496"></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.

  • Warning Line 1358, Column 109: reference not terminated by REFC delimiter
    … src="http://www.directadvert.ru/show.cgi?adp=76496&div=DIV_DA_76496"></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.

  • Warning Line 1358, Column 109: reference to external entity in attribute value
    … src="http://www.directadvert.ru/show.cgi?adp=76496&div=DIV_DA_76496"></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 '&amp;'.

  • Error Line 1358, Column 109: reference to entity "div" for which no system identifier could be generated
    … src="http://www.directadvert.ru/show.cgi?adp=76496&div=DIV_DA_76496"></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.

  • Info Line 1358, Column 105: entity was defined here
    … src="http://www.directadvert.ru/show.cgi?adp=76496&div=DIV_DA_76496"></script>
  • Error Line 1368, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1368, Column 21: element "scr" undefined
    document.write('<scr'

    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).
  • Error Line 1375, Column 33: delimiter "'" invalid: only S separators and TAGC allowed here
    +'" charset="windows-1251"></scr'+'ipt>');
  • Error Line 1379, Column 53: an attribute specification must start with a name or name token
    …                  document.write('<scr'+'ipt language="javascript" type="text/…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1379, Column 53: element "scr" undefined
    …                  document.write('<scr'+'ipt language="javascript" type="text/…

    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).
  • Warning Line 1379, Column 160: cannot generate system identifier for general entity "rt"
    …1.luxup.ru/show/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1379, Column 160: general entity "rt" not defined and no default entity
    …1.luxup.ru/show/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 1379, Column 162: reference not terminated by REFC delimiter
    …luxup.ru/show/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+…

    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.

  • Error Line 1379, Column 162: reference to entity "rt" for which no system identifier could be generated
    …luxup.ru/show/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 1379, Column 159: entity was defined here
    …91.luxup.ru/show/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referre…
  • Warning Line 1379, Column 172: cannot generate system identifier for general entity "r"
    …how/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+'"><'+'/sc…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1379, Column 172: general entity "r" not defined and no default entity
    …how/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+'"><'+'/sc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 1379, Column 173: reference not terminated by REFC delimiter
    …ow/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+'"><'+'/scr…

    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.

  • Error Line 1379, Column 173: reference to entity "r" for which no system identifier could be generated
    …ow/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+'"><'+'/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.

  • Info Line 1379, Column 171: entity was defined here
    …show/373158/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+'"><'+'/s…
  • Warning Line 1379, Column 205: character "<" is the first character of a delimiter but occurred as data
    …/?div=lx_373158&rt='+__rt+'&r='+escape(document.referrer)+'"><'+'/scr'+'ipt>');

    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.
  • Error Line 1380, Column 41: end tag for "scr" omitted, but OMITTAG NO was specified
                                    </script>

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

  • Info Line 1379, Column 49: start tag was here
    …                      document.write('<scr'+'ipt language="javascript" type="t…

Visitor Analysis

Daily Visitor
  • 51.333 visits

In Page Analysis