Sexiest and hottest desktop wallpapers. High quality and resolution. Users daily update our image archive and rate wallpapers. We have 100225 walls! ...

ftop.ru
  • Domain Name
    ftop.ru
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #22967
  • Page Size
    51.1 KB
  • Ip Address
    95.211.189.20
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 18 JPG, 37 PNG

Website Meta Analysis

  • Title
    Hot and sexy pictures and wallpapers » Ftop.ru
  • Meta Keyword
    wallpaper, desktop wallpapers, daily updates, sexy walls, high resolution
  • Meta Description
    Sexiest and hottest desktop wallpapers. High quality and resolution. Users daily update our image archive and rate wallpapers. We have 100225 walls!

Technical Analysis

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

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

HTML Analysis

  • server: nginx
  • date: Thu, 11 Sep 2014 22:57:15 GMT
  • content-type: text/html
  • content-length: 7916
  • connection: keep-alive
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • last-modified: Thu, 11 Sep 2014 16:55:23 +0400 GMT
  • vary: Accept-Encoding
  • 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: FTOP.RU
nserver: ns1.fastvps.ru.
nserver: ns2.fastvps.ru.
nserver: ns3.fastvps.ru.
nserver: ns4.fastvps.ru.
state: REGISTERED, DELEGATED, UNVERIFIED
person: Private Person
registrar: REGRU-REG-RIPN
admin-contact: http://www.reg.ru/whois/admin_contact
created: 2003.09.08
paid-till: 2013.09.08
free-date: 2013.10.09
source: TCI

Last updated on 2012.10.06 11:31:37 MSK

DNS Analysis


DNS servers
ns1.fastvps.ru [95.211.92.14]
ns4.fastvps.ru [93.170.127.130]
ns3.fastvps.ru [46.4.4.96]
ns2.fastvps.ru [178.132.200.26]


DNS Records

Answer records
ftop.ru MX
preference: 10
exchange: mx.yandex.ru
3600s
ftop.ru TXT v=spf1 ip4:78.47.76.4 a mx ~all 3600s
ftop.ru SOA
server: ns3.fastvps.ru
email: support@fastvps.ru
serial: 2009110708
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
3600s
ftop.ru NS  ns3.fastvps.ru 3600s
ftop.ru NS  ns4.fastvps.ru 3600s
ftop.ru A 95.211.134.6 3600s

Authority records

Additional records
mx.yandex.ru A 5.9.118.162 3600s
ns3.fastvps.ru A 46.4.4.96 3600s
ns4.fastvps.ru A 93.170.127.130 3600s

IP 95.211.189.20 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 257 Errors
  • 168 Warnings
Ratio Text/Html
  • 0.7375485153815269
Message Error
  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 84, Column 143: end tag for "img" omitted, but OMITTAG NO was specified
    …d="logo" alt="Обои и картинки на рабочий стол" title="На главную страницу"></a>

    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 84, Column 19: start tag was here
      		  <a href="/"><img src= "/templates/2012/images/logo2.png" id="logo" alt="О…
  • Warning Line 105, Column 365: character "&" is the first character of a delimiter but occurred as data
    …es/" rel="index section" title="Girls & Beaches wallpapers">Girls &amp; Beache…

    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 111, Column 31: end tag for "br" omitted, but OMITTAG NO was specified
                <br class="clear">

    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 111, Column 13: start tag was here
                <br class="clear">
  • Error Line 124, Column 137: document type does not allow element "form" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
    …ews_set_sort" method="post" action="" >Sort wallpapers by:&nbsp;<img src="/tem…

    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 124, Column 378: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …','desc'); return false;"><font color=red>rating</font></a> | <a href="#" oncl…
  • Error Line 148, Column 17: element "noindex" undefined
    <center><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 150, Column 134: there is no attribute "allowtransparency"
    …ads?spot_id=188501" allowtransparency="true" marginheight="0" marginwidth="0" …

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

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

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

  • Error Line 151, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="/noad.html"><font color=red size=1>Remove all ads</font></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 151, Column 1: start tag was here
    <br><a href="/noad.html"><font color=red size=1>Remove all ads</font></a><br>
  • Error Line 151, Column 38: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <br><a href="/noad.html"><font color=red size=1>Remove all ads</font></a><br>
  • Error Line 151, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <br><a href="/noad.html"><font color=red size=1>Remove all ads</font></a><br>
  • Error Line 151, Column 78: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="/noad.html"><font color=red size=1>Remove all ads</font></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 151, Column 74: start tag was here
    <br><a href="/noad.html"><font color=red size=1>Remove all ads</font></a><br>
  • Error Line 158, Column 53: an attribute value must be a literal unless it contains only name characters
    …-up ads for registered users! <a href=/index.php?do=register>Register here</a>…

    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 159, 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 159, Column 1: start tag was here
    <hr>
  • Error Line 168, Column 211: end tag for "img" omitted, but OMITTAG NO was specified
    …302/51034.jpg" alt="Walpaper tory lane, brunette, nude, pussy" width="305"></a>

    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 168, Column 100: start tag was here
    …4-tory-lane-brunette-nude-pussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 178, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 180, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 181, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 188, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Walpaper girls, tits, big, nude, naked, model, buts, pussy" width="305"></a>

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

  • Info Line 188, Column 104: start tag was here
    …stitsbignudenakedmodelbutspussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 198, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

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

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

  • Error Line 199, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 200, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 201, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 202, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+11</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 208, Column 222: end tag for "img" omitted, but OMITTAG NO was specified
    …pg" alt="Walpaper girls, tits, big, nude, naked, model, pussy" width="305"></a>

    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 208, Column 100: start tag was here
    …girlstitsbignudenakedmodelpussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 218, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 219, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 220, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 221, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 222, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+9</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 228, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …51037.jpg" alt="Walpaper charlie laine, brunette, pussy, tits" width="305"></a>

    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 228, Column 104: start tag was here
    …arlie-laine-brunette-pussy-tits.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 238, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 239, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 240, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 241, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 242, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+13</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 248, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Walpaper girls, tits, big, nude, naked, model, buts, pussy" width="305"></a>

    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 248, Column 104: start tag was here
    …stitsbignudenakedmodelbutspussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 258, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 259, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 260, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 261, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 262, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+14</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 268, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …ini/201302/51061.jpg" alt="Walpaper brunette, hot, sexy, babe" width="305"></a>

    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 268, Column 93: start tag was here
    …es/51061-brunette-hot-sexy-babe.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 278, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 279, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 280, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 281, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 282, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+14</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 288, Column 210: end tag for "img" omitted, but OMITTAG NO was specified
    …51047.jpg" alt="Walpaper girls, tits, big, nude, naked, model" width="305"></a>

    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 95: start tag was here
    …1047-girlstitsbignudenakedmodel.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 298, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 299, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 300, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 301, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 302, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+12</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 308, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …i/201302/51059.jpg" alt="Walpaper brunette, sexy girl, bikini" width="305"></a>

    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 308, Column 96: start tag was here
    …s/51059-brunettesexy-girlbikini.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 318, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 319, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 320, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 321, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 322, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+11</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 328, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …jpg" alt="Walpaper , lesbians, bigs, girls, good, tits, hot, " width="305"></a>

    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 328, Column 98: start tag was here
    …8--lesbiansbigsgirlsgoodtitshot.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 338, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 339, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 340, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 341, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 342, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+11</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 347, Column 11: end tag for "br" omitted, but OMITTAG NO was specified
    </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 347, Column 7: start tag was here
    </div><br>
  • Warning Line 351, Column 89: cannot generate system identifier for general entity "login"
    …tion.exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=…

    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 351, Column 89: general entity "login" not defined and no default entity
    …tion.exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=…

    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 351, Column 94: reference not terminated by REFC delimiter
    …exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 351, Column 94: reference to external entity in attribute value
    …exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 351, Column 94: reference to entity "login" for which no system identifier could be generated
    …exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 351, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color…
  • Warning Line 351, Column 100: cannot generate system identifier for general entity "cat"
    …ck.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgco…

    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 351, Column 100: general entity "cat" not defined and no default entity
    …ck.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgco…

    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 351, Column 103: reference not terminated by REFC delimiter
    …com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 351, Column 103: reference to external entity in attribute value
    …com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 351, Column 103: reference to entity "cat" for which no system identifier could be generated
    …com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 351, Column 99: entity was defined here
    …ick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 351, Column 106: cannot generate system identifier for general entity "search"
    …/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    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 351, Column 106: general entity "search" not defined and no default entity
    …/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    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 351, Column 112: reference not terminated by REFC delimiter
    …hp?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 351, Column 112: reference to external entity in attribute value
    …hp?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 351, Column 112: reference to entity "search" for which no system identifier could be generated
    …hp?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 351, Column 105: entity was defined here
    …m/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 351, Column 114: cannot generate system identifier for general entity "ad_title_color"
    …?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 351, Column 114: general entity "ad_title_color" not defined and no default entity
    …?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 351, Column 128: reference not terminated by REFC delimiter
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_c…

    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 351, Column 128: reference to external entity in attribute value
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_c…

    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 351, Column 128: reference to entity "ad_title_color" for which no system identifier could be generated
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_c…

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

  • Info Line 351, Column 113: entity was defined here
    …p?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 351, Column 136: cannot generate system identifier for general entity "bgcolor"
    …p&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000…

    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 351, Column 136: general entity "bgcolor" not defined and no default entity
    …p&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000…

    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 351, Column 143: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&fon…

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

  • Warning Line 351, Column 143: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&fon…

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

  • Error Line 351, Column 143: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&fon…

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

  • Info Line 351, Column 135: entity was defined here
    …op&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=00…
  • Warning Line 351, Column 151: cannot generate system identifier for general entity "border"
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block…

    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 351, Column 151: general entity "border" not defined and no default entity
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block…

    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 351, Column 157: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywo…

    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 351, Column 157: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywo…

    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 351, Column 157: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywo…

    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 351, Column 150: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&bloc…
  • Warning Line 351, Column 160: cannot generate system identifier for general entity "border_color"
    …_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywords…

    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 351, Column 160: general entity "border_color" not defined and no default entity
    …_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywords…

    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 351, Column 172: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 351, Column 172: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 351, Column 172: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 351, Column 159: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keyword…
  • Warning Line 351, Column 180: cannot generate system identifier for general entity "font"
    …r=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 351, Column 180: general entity "font" not defined and no default entity
    …r=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 351, Column 184: reference not terminated by REFC delimiter
    …FFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 351, Column 184: reference to external entity in attribute value
    …FFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 351, Column 184: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 351, Column 179: entity was defined here
    …or=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 351, Column 186: cannot generate system identifier for general entity "block_keywords"
    …FF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 351, Column 186: general entity "block_keywords" not defined and no default entity
    …FF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 351, Column 200: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 351, Column 200: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 351, Column 200: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 351, Column 185: entity was defined here
    …FFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 351, Column 202: cannot generate system identifier for general entity "ad_text_color"
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 351, Column 202: general entity "ad_text_color" not defined and no default entity
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 351, Column 215: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 351, Column 215: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 351, Column 215: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 351, Column 201: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 351, Column 223: cannot generate system identifier for general entity "ad_durl_color"
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_…

    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 351, Column 223: general entity "ad_durl_color" not defined and no default entity
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_…

    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 351, Column 236: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 351, Column 236: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 351, Column 236: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 351, Column 222: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 351, Column 244: cannot generate system identifier for general entity "adult"
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&i…

    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 351, Column 244: general entity "adult" not defined and no default entity
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&i…

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

  • Warning Line 351, Column 249: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 351, Column 249: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 351, Column 249: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 351, Column 243: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 351, Column 255: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=40177…

    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 351, Column 258: cannot generate system identifier for general entity "text_only"
    …00&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&i…

    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 351, Column 258: general entity "text_only" not defined and no default entity
    …00&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&i…

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

  • Warning Line 351, Column 267: reference not terminated by REFC delimiter
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154…

    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 351, Column 267: reference to external entity in attribute value
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154…

    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 351, Column 267: reference to entity "text_only" for which no system identifier could be generated
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154…

    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 351, Column 257: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&…
  • Warning Line 351, Column 270: cannot generate system identifier for general entity "show_thumb"
    …olor=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398…

    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 351, Column 270: general entity "show_thumb" not defined and no default entity
    …olor=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398…

    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 351, Column 280: reference not terminated by REFC delimiter
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 280: reference to external entity in attribute value
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 280: reference to entity "show_thumb" for which no system identifier could be generated
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 269: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=15439…
  • Warning Line 351, Column 283: cannot generate system identifier for general entity "idzone"
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 283: general entity "idzone" not defined and no default entity
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 289: reference not terminated by REFC delimiter
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 289: reference to external entity in attribute value
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 289: reference to entity "idzone" for which no system identifier could be generated
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 282: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Warning Line 351, Column 297: cannot generate system identifier for general entity "idsite"
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 297: general entity "idsite" not defined and no default entity
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 303: reference not terminated by REFC delimiter
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 303: reference to external entity in attribute value
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 303: reference to entity "idsite" for which no system identifier could be generated
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></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 351, Column 296: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Error Line 355, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><div class="thumb" title="walpaper girls, tits, big, nude, naked, model…

    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 1: start tag was here
    <br><br><div class="thumb" title="walpaper girls, tits, big, nude, naked, model…
  • Error Line 355, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><div class="thumb" title="walpaper girls, tits, big, nude, naked, model…

    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 5: start tag was here
    <br><br><div class="thumb" title="walpaper girls, tits, big, nude, naked, model…
  • Error Line 356, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
    …51039.jpg" alt="Walpaper girls, tits, big, nude, naked, model" width="305"></a>

    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 356, Column 100: start tag was here
    …1039-girlstitsbignudenakedmodel.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 366, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 367, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 368, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 369, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 370, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+12</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 376, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …mini/201302/51032.jpg" alt="Walpaper blonde, back, ass, pussy" width="305"></a>

    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 376, Column 92: start tag was here
    …ies/51032-blonde-back-ass-pussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 386, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 387, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 388, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 389, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 390, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+13</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 396, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Walpaper girls, tits, big, nude, naked, model, buts, pussy" width="305"></a>

    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 396, Column 104: start tag was here
    …stitsbignudenakedmodelbutspussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 406, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 407, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 408, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 409, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 410, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+18</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 416, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …51036.jpg" alt="Walpaper charlie laine, brunette, pussy, tits" width="305"></a>

    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 416, Column 104: start tag was here
    …arlie-laine-brunette-pussy-tits.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 426, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 427, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 428, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 429, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 430, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+15</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 436, Column 221: end tag for "img" omitted, but OMITTAG NO was specified
    …1038.jpg" alt="Walpaper annalisa greco, brunette, nude, pussy" width="305"></a>

    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 436, Column 105: start tag was here
    …alisa-greco-brunette-nude-pussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 446, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 447, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 448, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 449, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 450, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+13</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 456, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …01302/51052.jpg" alt="Walpaper brunette, nude, boobs, outdoor" width="305"></a>

    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 456, Column 98: start tag was here
    …052-brunette-nude-boobs-outdoor.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 466, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 467, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 468, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 469, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 470, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+19</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 476, Column 217: end tag for "img" omitted, but OMITTAG NO was specified
    …/51056.jpg" alt="Walpaper laisa andrioli, brunette, nude, ass" width="305"></a>

    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 476, Column 103: start tag was here
    …aisa-andrioli-brunette-nude-ass.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 486, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 487, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 488, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 489, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 490, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+15</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 496, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …51058.jpg" alt="Walpaper laisa andrioli, brunette, babe, tits" width="305"></a>

    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 496, Column 104: start tag was here
    …isa-andrioli-brunette-babe-tits.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 506, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 507, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 508, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 509, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 510, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+12</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 516, Column 213: end tag for "img" omitted, but OMITTAG NO was specified
    …02/51033.jpg" alt="Walpaper tori black, brunette, nude, pussy" width="305"></a>

    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 516, Column 101: start tag was here
    …-tori-black-brunette-nude-pussy.html"><img src="http://ftop.ru/mini/201302/510…
  • Error Line 526, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0px; position:absolute;padding-right:0px; margin-top:20px; margin-left:100px;">

    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 527, Column 10: ID "ratings" already defined
    <div id="ratings"><div class="points">

    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 179, Column 10: ID "ratings" first defined here
    <div id="ratings"><div class="points">
  • Error Line 528, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_ilike.png" title="Good!" alt…

    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 529, Column 12: an attribute value must be a literal unless it contains only name characters
       <a href=#><img src="/templates/2012/images/icon_idontlike.png" title="Bad!" …

    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 530, Column 13: ID "pointsResult" already defined
       <div id="pointsResult"><div class="totalpoints">+15</div></div>

    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 182, Column 13: ID "pointsResult" first defined here
       <div id="pointsResult"><div class="totalpoints">+11</div></div>
  • Error Line 541, 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 543, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><!-- BEGIN ExoClick.com Ad Code -->

    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 543, Column 1: start tag was here
    <br><!-- BEGIN ExoClick.com Ad Code -->
  • Warning Line 544, Column 94: reference not terminated by REFC delimiter
    …exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 544, Column 94: reference to external entity in attribute value
    …exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 544, Column 94: reference to entity "login" for which no system identifier could be generated
    …exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 351, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color…
  • Warning Line 544, Column 103: reference not terminated by REFC delimiter
    …com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 544, Column 103: reference to external entity in attribute value
    …com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 544, Column 103: reference to entity "cat" for which no system identifier could be generated
    …com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 351, Column 99: entity was defined here
    …ick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 544, Column 112: reference not terminated by REFC delimiter
    …hp?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 544, Column 112: reference to external entity in attribute value
    …hp?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 544, Column 112: reference to entity "search" for which no system identifier could be generated
    …hp?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 351, Column 105: entity was defined here
    …m/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 544, Column 128: reference not terminated by REFC delimiter
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 544, Column 128: reference to external entity in attribute value
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 544, Column 128: reference to entity "ad_title_color" for which no system identifier could be generated
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 351, Column 113: entity was defined here
    …p?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 544, Column 143: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 544, Column 143: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 544, Column 143: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 351, Column 135: entity was defined here
    …op&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=00…
  • Warning Line 544, Column 157: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 544, Column 157: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 544, Column 157: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 351, Column 150: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&bloc…
  • Warning Line 544, Column 172: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 544, Column 172: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 544, Column 172: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 351, Column 159: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keyword…
  • Warning Line 544, Column 184: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 544, Column 184: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 544, Column 184: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 351, Column 179: entity was defined here
    …or=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 544, Column 200: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 544, Column 200: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 544, Column 200: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 351, Column 185: entity was defined here
    …FFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 544, Column 215: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 544, Column 215: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 544, Column 215: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 351, Column 201: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 544, Column 236: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 544, Column 236: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 544, Column 236: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 351, Column 222: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 544, Column 249: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 544, Column 249: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 544, Column 249: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 351, Column 243: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 544, Column 255: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&…

    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 544, Column 266: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=1543…

    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 544, Column 266: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=1543…

    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 544, Column 266: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=1543…

    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 351, Column 257: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&…
  • Warning Line 544, Column 279: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 544, Column 279: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 544, Column 279: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 351, Column 269: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=15439…
  • Warning Line 544, Column 287: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 544, Column 287: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 544, Column 287: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 351, Column 282: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Warning Line 544, Column 301: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 544, Column 301: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 544, Column 301: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=381502&idsite=154398"></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 351, Column 296: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Warning Line 549, Column 103: reference not terminated by REFC delimiter
    …/iframe/iframe01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Stripp…

    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 549, Column 103: reference to external entity in attribute value
    …/iframe/iframe01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Stripp…

    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 549, Column 103: reference to entity "bgcolor" for which no system identifier could be generated
    …/iframe/iframe01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Stripp…

    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 351, Column 135: entity was defined here
    …op&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=00…
  • Warning Line 549, Column 110: cannot generate system identifier for general entity "limit"
    …/iframe01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on …

    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 549, Column 110: general entity "limit" not defined and no default entity
    …/iframe01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on …

    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 549, Column 115: reference not terminated by REFC delimiter
    …me01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your …

    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 549, Column 115: reference to external entity in attribute value
    …me01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your …

    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 549, Column 115: reference to entity "limit" for which no system identifier could be generated
    …me01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your …

    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 549, Column 109: entity was defined here
    …e/iframe01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on…
  • Warning Line 549, Column 118: cannot generate system identifier for general entity "title"
    …1.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your des…

    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 549, Column 118: general entity "title" not defined and no default entity
    …1.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your des…

    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 549, Column 123: reference not terminated by REFC delimiter
    …?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your desktop!…

    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 549, Column 123: reference to external entity in attribute value
    …?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your desktop!…

    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 549, Column 123: reference to entity "title" for which no system identifier could be generated
    …?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your desktop!…

    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 549, Column 117: entity was defined here
    …01.php?ids=46173&bgcolor=FFFFF&limit=4&title=VirtuaGirl : Strippers on your de…
  • Warning Line 549, Column 164: cannot generate system identifier for general entity "color"
    …rtuaGirl : Strippers on your desktop!&color=00000&fontsize=14&card=full" frame…

    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 549, Column 164: general entity "color" not defined and no default entity
    …rtuaGirl : Strippers on your desktop!&color=00000&fontsize=14&card=full" frame…

    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 549, Column 169: reference not terminated by REFC delimiter
    …irl : Strippers on your desktop!&color=00000&fontsize=14&card=full" frameborde…

    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 549, Column 169: reference to external entity in attribute value
    …irl : Strippers on your desktop!&color=00000&fontsize=14&card=full" frameborde…

    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 549, Column 169: reference to entity "color" for which no system identifier could be generated
    …irl : Strippers on your desktop!&color=00000&fontsize=14&card=full" frameborde…

    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 549, Column 163: entity was defined here
    …irtuaGirl : Strippers on your desktop!&color=00000&fontsize=14&card=full" fram…
  • Warning Line 549, Column 176: cannot generate system identifier for general entity "fontsize"
    …trippers on your desktop!&color=00000&fontsize=14&card=full" frameborder="0" w…

    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 549, Column 176: general entity "fontsize" not defined and no default entity
    …trippers on your desktop!&color=00000&fontsize=14&card=full" frameborder="0" w…

    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 549, Column 184: reference not terminated by REFC delimiter
    … on your desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="72…

    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 549, Column 184: reference to external entity in attribute value
    … on your desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="72…

    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 549, Column 184: reference to entity "fontsize" for which no system identifier could be generated
    … on your desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="72…

    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 549, Column 175: entity was defined here
    …Strippers on your desktop!&color=00000&fontsize=14&card=full" frameborder="0" …
  • Warning Line 549, Column 188: cannot generate system identifier for general entity "card"
    …your desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="720" h…

    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 549, Column 188: general entity "card" not defined and no default entity
    …your desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="720" h…

    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 549, Column 192: reference not terminated by REFC delimiter
    … desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="720" heigh…

    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 549, Column 192: reference to external entity in attribute value
    … desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="720" heigh…

    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 549, Column 192: reference to entity "card" for which no system identifier could be generated
    … desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="720" heigh…

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

  • Info Line 549, Column 187: entity was defined here
    … your desktop!&color=00000&fontsize=14&card=full" frameborder="0" width="720" …
  • Error Line 551, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=720 align=center><tr align=center><td>
  • Error Line 551, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=720 align=center><tr align=center><td>
  • Error Line 551, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=720 align=center><tr align=center><td>
  • Warning Line 553, Column 99: cannot generate system identifier for general entity "ver"
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=89806&ver=1'></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 553, Column 99: general entity "ver" not defined and no default entity
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=89806&ver=1'></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 553, Column 102: reference not terminated by REFC delimiter
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=89806&ver=1'></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 553, Column 102: reference to external entity in attribute value
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=89806&ver=1'></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 553, Column 102: reference to entity "ver" for which no system identifier could be generated
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=89806&ver=1'></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 553, Column 98: entity was defined here
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=89806&ver=1'></script>
  • Error Line 558, Column 16: there is no attribute "border"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…

    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 558, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 558, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 558, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 558, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 558, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 558, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 558, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 558, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 558, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 558, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 558, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=185192></iframe>

    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 562, Column 95: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 562, Column 95: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 562, Column 95: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000c…

    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 351, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color…
  • Warning Line 562, Column 104: reference not terminated by REFC delimiter
    …om/ads.php?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 562, Column 104: reference to external entity in attribute value
    …om/ads.php?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 562, Column 104: reference to entity "cat" for which no system identifier could be generated
    …om/ads.php?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 351, Column 99: entity was defined here
    …ick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 562, Column 113: reference not terminated by REFC delimiter
    …p?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 562, Column 113: reference to external entity in attribute value
    …p?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 562, Column 113: reference to entity "search" for which no system identifier could be generated
    …p?type=300x250&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 351, Column 105: entity was defined here
    …m/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 562, Column 129: reference not terminated by REFC delimiter
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 562, Column 129: reference to external entity in attribute value
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 562, Column 129: reference to entity "ad_title_color" for which no system identifier could be generated
    …ogin=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 351, Column 113: entity was defined here
    …p?type=728x90&login=ftop&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 562, Column 144: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 562, Column 144: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 562, Column 144: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 351, Column 135: entity was defined here
    …op&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=00…
  • Warning Line 562, Column 158: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 562, Column 158: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 562, Column 158: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 351, Column 150: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&bloc…
  • Warning Line 562, Column 173: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 562, Column 173: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 562, Column 173: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 351, Column 159: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=1&border_color=000000&font=&block_keyword…
  • Warning Line 562, Column 185: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 562, Column 185: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 562, Column 185: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 351, Column 179: entity was defined here
    …or=FFFFFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 562, Column 201: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 562, Column 201: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 562, Column 201: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 351, Column 185: entity was defined here
    …FFF&border=1&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 562, Column 216: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 562, Column 216: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 562, Column 216: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 351, Column 201: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 562, Column 237: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 562, Column 237: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 562, Column 237: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 351, Column 222: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 562, Column 250: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

    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 562, Column 250: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

    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 562, Column 250: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

    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 351, Column 243: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 562, Column 256: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&…

    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 562, Column 267: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=1543…

    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 562, Column 267: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=1543…

    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 562, Column 267: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=1543…

    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 351, Column 257: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&…
  • Warning Line 562, Column 280: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 562, Column 280: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 562, Column 280: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 351, Column 269: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=15439…
  • Warning Line 562, Column 288: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 562, Column 288: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 562, Column 288: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 351, Column 282: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Warning Line 562, Column 302: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 562, Column 302: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 562, Column 302: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=439958&idsite=154398"></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 351, Column 296: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Error Line 570, Column 19: end tag for "br" omitted, but OMITTAG NO was specified
    <br class="clear"><br class="clear">

    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 570, Column 1: start tag was here
    <br class="clear"><br class="clear">
  • Error Line 570, Column 37: end tag for "br" omitted, but OMITTAG NO was specified
    <br class="clear"><br class="clear">

    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 570, Column 19: start tag was here
    <br class="clear"><br class="clear">
  • Error Line 596, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 596, Column 1: start tag was here
    <br><br>
  • Error Line 596, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 596, Column 5: start tag was here
    <br><br>
  • Error Line 622, Column 73: end tag for "br" omitted, but OMITTAG NO was specified
    "border=0 width=1 height=1><\/a>")//--></script><!--/LiveInternet--><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 622, Column 69: start tag was here
    "border=0 width=1 height=1><\/a>")//--></script><!--/LiveInternet--><br>
  • Error Line 635, Column 19: end tag for "br" omitted, but OMITTAG NO was specified
    <br class="clear">

    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 635, Column 1: start tag was here
    <br class="clear">
  • Error Line 638, Column 11: ID "menu" already defined
    	<div id="menu" class="wrapper clearfix"> 

    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 82, Column 11: ID "menu" first defined here
    	<div id="menu" class="wrapper clearfix"> 
  • Error Line 645, 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 645, Column 1: start tag was here
    <br>
  • Error Line 648, 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 648, Column 1: start tag was here
    <br>
  • Error Line 651, 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 651, Column 1: start tag was here
    <br>
  • Error Line 660, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/temp/ style="font-weight:bold;">Sandbox</a>

    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 661, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/celebrities/>Celebrities</a>

    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 662, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/girls-beaches/>Girls & Beaches</a>

    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.

  • Warning Line 662, Column 31: character "&" is the first character of a delimiter but occurred as data
    <a href=/girls-beaches/>Girls & Beaches</a>

    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 663, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/girls-cars/>Girls & Cars</a>

    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.

  • Warning Line 663, Column 28: character "&" is the first character of a delimiter but occurred as data
    <a href=/girls-cars/>Girls & Cars</a>

    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 664, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/girls-bikes/>Girls & Bikes</a>

    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.

  • Warning Line 664, Column 29: character "&" is the first character of a delimiter but occurred as data
    <a href=/girls-bikes/>Girls & Bikes</a>

    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 665, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/lingerie-girls/>Lingerie Girls</a>

    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 668, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/asian-girls/>Asian Girls</a>

    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 669, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/holidays/>Holidays</a>

    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 670, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/xxx-walls/>XXX walls</a>

    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 671, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/fantasy-girls/>Fantasy Girls</a>

    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 672, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/vect/>3D & Vector Girls</a>

    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.

  • Warning Line 672, Column 19: character "&" is the first character of a delimiter but occurred as data
    <a href=/vect/>3D & Vector Girls</a>

    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 673, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/celebrity-fakes/>Celebrity Fakes</a>

    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 676, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/archive.html>Wallpaper archive</a>

    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 677, 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 682, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <a target=_blank href=mailto:admin@ftop.ru>admin@ftop.ru</a>
  • Error Line 682, Column 23: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <a target=_blank href=mailto:admin@ftop.ru>admin@ftop.ru</a>
  • Error Line 682, Column 35: an attribute value must be a literal unless it contains only name characters
    <a target=_blank href=mailto:admin@ftop.ru>admin@ftop.ru</a>

    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 688, Column 31: end tag for "br" omitted, but OMITTAG NO was specified
                <br class="clear">

    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 688, Column 13: start tag was here
                <br class="clear">
  • Warning Line 701, Column 92: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"…

    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 701, Column 92: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"…

    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 701, Column 92: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"…

    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 351, Column 296: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Warning Line 701, Column 106: reference not terminated by REFC delimiter
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 106: reference to external entity in attribute value
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 106: reference to entity "idzone" for which no system identifier could be generated
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 351, Column 282: entity was defined here
    …0&adult=0&sub=0&text_only=0&show_thumb=0&idzone=401772&idsite=154398"></script>
  • Warning Line 701, Column 119: reference not terminated by REFC delimiter
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 119: reference to external entity in attribute value
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 119: reference to entity "login" for which no system identifier could be generated
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 351, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=ftop&cat=2&search=&ad_title_color…
  • Warning Line 701, Column 125: cannot generate system identifier for general entity "type"
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 125: general entity "type" not defined and no default entity
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 129: reference not terminated by REFC delimiter
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 129: reference to external entity in attribute value
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 129: reference to entity "type" for which no system identifier could be generated
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></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 701, Column 124: entity was defined here
    …k.com/splash.php?cat=2&idsite=154398&idzone=385968&login=ftop&type=3"></script>
  • Error Line 702, Column 18: there is no attribute "Language"
    <script Language="JavaScript">

    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 702, Column 30: required attribute "type" not specified
    <script Language="JavaScript">

    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 709, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body> 

    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 79, Column 1: start tag was here
    <div id="px">

Visitor Analysis

Daily Visitor
  • 5.950 visits