Thai Poony is a Thai Sex blog featuring free Thai pussy and Thai Porn, this hardcore Thai Porn Blog features Thai xxx pictures and porn from Thailand. Also Free Thai aGoGo reviews and ...

thaipoony.com
  • Domain Name
    thaipoony.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #480459
  • Page Size
    69.6 KB
  • Ip Address
    199.241.96.4
  • Heading
    H1: 0, H2: 42, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    5 GIF, 47 JPG, 0 PNG

Website Meta Analysis

  • Title
    Thai Sex, Thai Porn, Asian Porn, Thai Pussy, Free Thailand Porn Tube - THAI POONY
  • Meta Keyword
    Thai Porn, Asian Porn, Thai Pussy, Asian Pussy, Thai Sex, Asian Sex Thumbs, Thai Bargirls, Thai hookers, Pattaya Porn, Pattaya Bargirls, Thailand Discos
  • Meta Description
    Thai Poony is a Thai Sex blog featuring free Thai pussy and Thai Porn, this hardcore Thai Porn Blog features Thai xxx pictures and porn from Thailand. Also Free Thai aGoGo reviews and amateur pictures, Free Thai Whore videos. Free thai movies. Free thai porn tube. thai XXX Sex

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    199.241.96.4
  • Domain Age
    6 Years, 6 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from thaipoony.com.

HTML Analysis

  • date: Fri, 04 Oct 2013 05:18:10 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.18
  • x-pingback: http://thaipoony.com/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • content-length: 64021
  • age: 13
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for thaipoony.com

DNS Analysis


DNS servers
ns1.mojohost.com [64.59.64.2]
ns2.mojohost.com [64.59.65.2]


DNS Records

Answer records
thaipoony.com SOA
server: ns1.mojohost.com
email: postmaster@mojohost.com
serial: 2012100101
refresh: 28800
retry: 14400
expire: 3600000
minimum ttl: 86400
3600s
thaipoony.com NS  ns1.mojohost.com 3600s
thaipoony.com NS  ns2.mojohost.com 3600s
thaipoony.com A 199.241.96.4 3600s
thaipoony.com MX
preference: 10
exchange: thaipoony.com
3600s

Authority records

Additional records
ns1.mojohost.com A 64.59.64.2 300s
ns2.mojohost.com A 64.59.65.2 300s

IP 199.241.96.4 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 199.241.96.4"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=199.241.96.4?showDetails=true&showARIN=false&ext=netref2
    #

    Mojohost VL475 ASIANDREAM NET-199-241-96-0-28 (NET-199-241-96-0-2) 199.241.96.0 - 199.241.96.15
    MOJOHOST EOS10 (NET-199-241-96-0-1) 199.241.96.0 - 199.241.103.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 564 Errors
  • 269 Warnings
Ratio Text/Html
  • 0.6994472657893999
Message Error
  • Warning Line 14, Column 26: character "&" is the first character of a delimiter but occurred as data
    	} else if( window.opera && window.print ) { return true; } } 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 14, Column 27: character "&" is the first character of a delimiter but occurred as data
    	} else if( window.opera && window.print ) { return true; } } 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 63, Column 86: cannot generate system identifier for general entity "PA"
    …com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='ht…

    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 63, Column 86: general entity "PA" not defined and no default entity
    …com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='ht…

    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 63, Column 88: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='http…

    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 63, Column 88: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='http…

    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 63, Column 88: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='http…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Error Line 63, Column 174: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mg src='http://thaipoony.com/banners/468x80-7.jpg' border=1 vspace=5></a></div>
  • Error Line 63, Column 183: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mg src='http://thaipoony.com/banners/468x80-7.jpg' border=1 vspace=5></a></div>
  • Error Line 63, Column 184: required attribute "alt" not specified
    …mg src='http://thaipoony.com/banners/468x80-7.jpg' border=1 vspace=5></a></div>

    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 63, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src='http://thaipoony.com/banners/468x80-7.jpg' border=1 vspace=5></a></div>

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

  • Info Line 63, Column 114: start tag was here
    …5220-0000&PA=2372389' target="_blank"><img src='http://thaipoony.com/banners/4…
  • Error Line 77, Column 215: required attribute "alt" not specified
    …com/images/apple-seed-thai-sex.jpg" title="Thai Sex at Thai Poony" /></a><br />

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

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

  • Error Line 80, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 90, Column 187: required attribute "alt" not specified
    …ttp://www.thaipoony.com/images/018-vun-1-048.jpg" title="Thai Sex" /></a><br />

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

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

  • Error Line 93, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 106, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 116, Column 196: required attribute "alt" not specified
    …http://www.thaipoony.com/images/bonkmythai-sex.jpg" title="Thai Sex" /></a></p>

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

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

  • Error Line 118, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 130, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://secure.meandmyasian.com/track/sexy…

    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 140, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div class="post" id="post-4156"><div align=center>
  • Error Line 142, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table border=0>
  • Error Line 144, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ex0_big.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 144, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex0_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90…
  • Error Line 144, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …56/Thai_Sex0_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90'></a></td>

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

  • Info Line 144, Column 107: start tag was here
    …g.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 145, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Sex1_big.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 145, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex1_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'…
  • Error Line 145, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …156/Thai_Sex1_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'></a></td>

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

  • Info Line 145, Column 106: start tag was here
    …ig.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 146, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ex2_big.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 146, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex2_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90…
  • Error Line 146, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …56/Thai_Sex2_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90'></a></td>

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

  • Info Line 146, Column 107: start tag was here
    …g.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 147, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ex3_big.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 147, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex3_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90…
  • Error Line 147, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …56/Thai_Sex3_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90'></a></td>

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

  • Info Line 147, Column 107: start tag was here
    …g.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 150, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …_Sex4_big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 150, Column 183: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex4_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'>…
  • Error Line 150, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    …4156/Thai_Sex4_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'></a></td>

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

  • Info Line 150, Column 105: start tag was here
    …big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 151, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …_Sex5_big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 151, Column 183: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex5_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'>…
  • Error Line 151, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    …4156/Thai_Sex5_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'></a></td>

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

  • Info Line 151, Column 105: start tag was here
    …big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 152, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Sex6_big.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 152, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex6_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'…
  • Error Line 152, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …156/Thai_Sex6_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'></a></td>

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

  • Info Line 152, Column 106: start tag was here
    …ig.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 153, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Sex7_big.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 153, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex7_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'…
  • Error Line 153, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …156/Thai_Sex7_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'></a></td>

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

  • Info Line 153, Column 106: start tag was here
    …ig.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 156, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …_Sex8_big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 156, Column 183: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex8_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'>…
  • Error Line 156, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    …4156/Thai_Sex8_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'></a></td>

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

  • Info Line 156, Column 105: start tag was here
    …big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 157, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ex9_big.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 157, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/grabbed4156/Thai_Sex9_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90…
  • Error Line 157, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …56/Thai_Sex9_tn.jpg' border=0 alt='Thai Pussy' width='90' height='90'></a></td>

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

  • Info Line 157, Column 107: start tag was here
    …g.jpg' title='Thai Pussy' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 158, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …x10_big.jpg' title='Thai Girls' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 158, Column 187: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …grabbed4156/Thai_Sex10_tn.jpg' border=0 alt='Thai Girls' width='90' height='90…
  • Error Line 158, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …6/Thai_Sex10_tn.jpg' border=0 alt='Thai Girls' width='90' height='90'></a></td>

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

  • Info Line 158, Column 108: start tag was here
    …g.jpg' title='Thai Girls' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 159, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Sex11_big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 159, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …grabbed4156/Thai_Sex11_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'>…
  • Error Line 159, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …156/Thai_Sex11_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'></a></td>

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

  • Info Line 159, Column 106: start tag was here
    …big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 162, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …x12_big.jpg' title='Thai Girls' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 162, Column 187: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …grabbed4156/Thai_Sex12_tn.jpg' border=0 alt='Thai Girls' width='90' height='90…
  • Error Line 162, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …6/Thai_Sex12_tn.jpg' border=0 alt='Thai Girls' width='90' height='90'></a></td>

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

  • Info Line 162, Column 108: start tag was here
    …g.jpg' title='Thai Girls' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 163, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ex13_big.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 163, Column 186: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …grabbed4156/Thai_Sex13_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'…
  • Error Line 163, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …56/Thai_Sex13_tn.jpg' border=0 alt='Thai Porn' width='90' height='90'></a></td>

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

  • Info Line 163, Column 107: start tag was here
    …ig.jpg' title='Thai Porn' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 164, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …x14_big.jpg' title='Thai Girls' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 164, Column 187: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …grabbed4156/Thai_Sex14_tn.jpg' border=0 alt='Thai Girls' width='90' height='90…
  • Error Line 164, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    …6/Thai_Sex14_tn.jpg' border=0 alt='Thai Girls' width='90' height='90'></a></td>

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

  • Info Line 164, Column 108: start tag was here
    …g.jpg' title='Thai Girls' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 165, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Sex15_big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/gal…
  • Error Line 165, Column 185: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …grabbed4156/Thai_Sex15_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'>…
  • Error Line 165, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …156/Thai_Sex15_tn.jpg' border=0 alt='Thai Sex' width='90' height='90'></a></td>

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

  • Info Line 165, Column 106: start tag was here
    …big.jpg' title='Thai Sex' class=thumb><img src='http://thaipoony.com/galleries…
  • Error Line 180, Column 208: required attribute "alt" not specified
    …ages/380-panni-play-teen-photos-1-033.jpg" title="Nude Thai Girls" /></a><br />

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

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

  • Error Line 183, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 193, Column 190: required attribute "alt" not specified
    …www.thaipoony.com/images/ama-asian-bj-tp.jpg" title="Nude Thai Porn" /></a></p>

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

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

  • Error Line 195, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a href="http://allasianpornstars.com" target="_blank" style='fon…

    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 205, Column 182: required attribute "alt" not specified
    …www.thaipoony.com/images/kam_set_2_08.jpg" title="Nude Thai Girls" /></a><br />

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

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

  • Error Line 208, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://join.tuktukpatrol.com/track/141872…

    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 218, Column 186: required attribute "alt" not specified
    …poony.com/images/asian-candy-pop-99.jpg" title="AsianCandyPop.com" /></a><br />

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

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

  • Error Line 221, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 231, Column 185: required attribute "alt" not specified
    …://www.thaipoony.com/images/181-kumlai-1-018.jpg" title="Thai Sex" /></a><br />

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

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

  • Error Line 234, Column 159: required attribute "alt" not specified
    …tp://www.thaipoony.com/images/181-kumlai-1-060.jpg" title="Thai Sex" /></a></p>

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

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

  • Error Line 235, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 248, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><b><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin/clicks.cg…

    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 258, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 260, Column 22: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<div align="center">

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

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

  • Info Line 258, Column 1: start tag was here
    <p>
  • Error Line 266, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 257, Column 1: start tag was here
    <p>
  • Warning Line 279, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372771' target="_blank"><img src='http…

    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 279, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372771' target="_blank"><img src='http…

    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 279, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372771' target="_blank"><img src='http…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Error Line 279, Column 182: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/asianporngasm.jpg' border=1 vspace=5></a></center>
  • Error Line 279, Column 191: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/asianporngasm.jpg' border=1 vspace=5></a></center>
  • Error Line 279, Column 192: required attribute "alt" not specified
    …='http://thaipoony.com/promo/asianporngasm.jpg' border=1 vspace=5></a></center>

    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 279, Column 196: end tag for "img" omitted, but OMITTAG NO was specified
    …='http://thaipoony.com/promo/asianporngasm.jpg' border=1 vspace=5></a></center>

    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 279, Column 119: start tag was here
    …5220-0000&PA=2372771' target="_blank"><img src='http://thaipoony.com/promo/asi…
  • Error Line 281, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/asian-porngasm/" target="…

    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 284, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</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 284, Column 1: start tag was here
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</br>
  • Error Line 284, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 285, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 100 Sets, High Quality</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 285, Column 1: start tag was here
    <br><b>Pictures</b>: 100 Sets, High Quality</br>
  • Error Line 285, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 100 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 286, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 60+, 10 min+</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 286, Column 1: start tag was here
    <br><b>Videos</b>: 60+, 10 min+</br>
  • Error Line 286, Column 36: end tag for element "br" which is not open
    <br><b>Videos</b>: 60+, 10 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 287, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (1280x720)</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 287, Column 1: start tag was here
    <br><b>Formats</b>: WMV (1280x720)</br>
  • Error Line 287, Column 39: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (1280x720)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 290, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 294, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    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 294, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 294, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 294, Column 109: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372771" target="_blank">VISIT ASIAN PO…

    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 294, Column 109: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372771" target="_blank">VISIT ASIAN PO…

    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 294, Column 109: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372771" target="_blank">VISIT ASIAN PO…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Error Line 294, Column 168: name start character invalid: only S separators and TAGC allowed here
    …=2372771" target="_blank">VISIT ASIAN PORNGASM</a>  </font size=2></B></center>
  • Error Line 294, Column 168: end tag for "B" omitted, but OMITTAG NO was specified
    …=2372771" target="_blank">VISIT ASIAN PORNGASM</a>  </font size=2></B></center>

    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 294, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 294, Column 178: end tag for element "B" which is not open
    …=2372771" target="_blank">VISIT ASIAN PORNGASM</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 297, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 298, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 290, Column 1: start tag was here
    <p>
  • Error Line 298, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 289, Column 1: start tag was here
    <p>
  • Warning Line 308, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 308, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 308, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 308, Column 102: cannot generate system identifier for general entity "HTML"
    …/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' t…

    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 308, Column 102: general entity "HTML" not defined and no default entity
    …/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' 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.

  • Warning Line 308, Column 106: reference not terminated by REFC delimiter
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' targe…

    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 308, Column 106: reference to external entity in attribute value
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' targe…

    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 308, Column 106: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' targe…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 308, Column 220: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/creampiethais.jpg' border=1 vspace=5></a></center>
  • Error Line 308, Column 229: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/creampiethais.jpg' border=1 vspace=5></a></center>
  • Error Line 308, Column 230: required attribute "alt" not specified
    …='http://thaipoony.com/promo/creampiethais.jpg' border=1 vspace=5></a></center>

    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 308, Column 234: end tag for "img" omitted, but OMITTAG NO was specified
    …='http://thaipoony.com/promo/creampiethais.jpg' border=1 vspace=5></a></center>

    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 157: start tag was here
    …piethais.com/z_tour/' target="_blank"><img src='http://thaipoony.com/promo/cre…
  • Error Line 310, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/creampie-thais/" target="…

    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 313, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</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 313, Column 1: start tag was here
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>
  • Error Line 313, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 314, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 100 Sets, High Quality</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 314, Column 1: start tag was here
    <br><b>Pictures</b>: 100 Sets, High Quality</br>
  • Error Line 314, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 100 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 315, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 100+, 15 min+</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 315, Column 1: start tag was here
    <br><b>Videos</b>: 100+, 15 min+</br>
  • Error Line 315, Column 37: end tag for element "br" which is not open
    <br><b>Videos</b>: 100+, 15 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 316, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (720x480)</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 316, Column 1: start tag was here
    <br><b>Formats</b>: WMV (720x480)</br>
  • Error Line 316, Column 38: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (720x480)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 319, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 324, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    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 324, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 324, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 324, Column 109: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 324, Column 109: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 324, Column 109: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 324, Column 122: reference not terminated by REFC delimiter
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/" targe…

    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 324, Column 122: reference to external entity in attribute value
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/" targe…

    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 324, Column 122: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/" targe…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 324, Column 206: name start character invalid: only S separators and TAGC allowed here
    …/z_tour/" target="_blank">VISIT CREAMPIE THAIS</a>  </font size=2></B></center>
  • Error Line 324, Column 206: end tag for "B" omitted, but OMITTAG NO was specified
    …/z_tour/" target="_blank">VISIT CREAMPIE THAIS</a>  </font size=2></B></center>

    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 324, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 324, Column 216: end tag for element "B" which is not open
    …/z_tour/" target="_blank">VISIT CREAMPIE THAIS</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 327, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 328, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 319, Column 1: start tag was here
    <p>
  • Error Line 328, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 318, Column 1: start tag was here
    <p>
  • Error Line 339, Column 175: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …c='http://thaipoony.com/promo/tuktukpatrol.jpg' border=1 vspace=5></a></center>
  • Error Line 339, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …c='http://thaipoony.com/promo/tuktukpatrol.jpg' border=1 vspace=5></a></center>
  • Error Line 339, Column 185: required attribute "alt" not specified
    …c='http://thaipoony.com/promo/tuktukpatrol.jpg' border=1 vspace=5></a></center>

    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 339, Column 189: end tag for "img" omitted, but OMITTAG NO was specified
    …c='http://thaipoony.com/promo/tuktukpatrol.jpg' border=1 vspace=5></a></center>

    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 339, Column 113: start tag was here
    ….16.15.45.20.0.0.0.0' target="_blank"><img src='http://thaipoony.com/promo/tuk…
  • Error Line 341, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/category/thai-porn/" targ…

    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 344, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $14.95 / 30 day(s) recurring</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 344, Column 1: start tag was here
    <br><b>Price</b>: $14.95 / 30 day(s) recurring</br>
  • Error Line 344, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $14.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 345, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 20 Sets, High Quality</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 345, Column 1: start tag was here
    <br><b>Pictures</b>: 20 Sets, High Quality</br>
  • Error Line 345, Column 47: end tag for element "br" which is not open
    <br><b>Pictures</b>: 20 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 346, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 20+, 15 min+</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 346, Column 1: start tag was here
    <br><b>Videos</b>: 20+, 15 min+</br>
  • Error Line 346, Column 36: end tag for element "br" which is not open
    <br><b>Videos</b>: 20+, 15 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 347, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (1280x720)</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 1: start tag was here
    <br><b>Formats</b>: WMV (1280x720)</br>
  • Error Line 347, Column 39: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (1280x720)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 350, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 354, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://join.tuktukpatrol.com/tr…

    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 354, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://join.tuktukpatrol.com/tr…
  • Error Line 354, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://join.tuktukpatrol.com/tr…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 354, Column 162: name start character invalid: only S separators and TAGC allowed here
    ….0.0.0.0" target="_blank">VISIT TUK TUK PATROL</a>  </font size=2></B></center>
  • Error Line 354, Column 162: end tag for "B" omitted, but OMITTAG NO was specified
    ….0.0.0.0" target="_blank">VISIT TUK TUK PATROL</a>  </font size=2></B></center>

    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 354, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://join.tuktukpatrol.com/tr…
  • Error Line 354, Column 172: end tag for element "B" which is not open
    ….0.0.0.0" target="_blank">VISIT TUK TUK PATROL</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 357, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 358, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 350, Column 1: start tag was here
    <p>
  • Error Line 358, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 349, Column 1: start tag was here
    <p>
  • Warning Line 370, Column 81: cannot generate system identifier for general entity "cmp"
    ….happytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http:/…

    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 370, Column 81: general entity "cmp" not defined and no default entity
    ….happytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http:/…

    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 370, Column 84: reference not terminated by REFC delimiter
    …ppytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http://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 370, Column 84: reference to external entity in attribute value
    …ppytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http://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 370, Column 84: reference to entity "cmp" for which no system identifier could be generated
    …ppytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http://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 370, Column 80: entity was defined here
    …w.happytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http:…
  • Error Line 370, Column 164: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … src='http://thaipoony.com/promo/happytugs.jpg' border=1 vspace=5></a></center>
  • Error Line 370, Column 173: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … src='http://thaipoony.com/promo/happytugs.jpg' border=1 vspace=5></a></center>
  • Error Line 370, Column 174: required attribute "alt" not specified
    … src='http://thaipoony.com/promo/happytugs.jpg' border=1 vspace=5></a></center>

    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 370, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    … src='http://thaipoony.com/promo/happytugs.jpg' border=1 vspace=5></a></center>

    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 370, Column 105: start tag was here
    …id=Blazer1182&cmp=tp' target="_blank"><img src='http://thaipoony.com/promo/hap…
  • Error Line 372, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/happy-tugs/" target="_bla…

    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 375, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</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 375, Column 1: start tag was here
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</br>
  • Error Line 375, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 376, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 15 Sets, High Quality</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 376, Column 1: start tag was here
    <br><b>Pictures</b>: 15 Sets, High Quality</br>
  • Error Line 376, Column 47: end tag for element "br" which is not open
    <br><b>Pictures</b>: 15 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 377, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 15+, 25 min+</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 377, Column 1: start tag was here
    <br><b>Videos</b>: 15+, 25 min+</br>
  • Error Line 377, Column 36: end tag for element "br" which is not open
    <br><b>Videos</b>: 15+, 25 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 378, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (1280x720)</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 378, Column 1: start tag was here
    <br><b>Formats</b>: WMV (1280x720)</br>
  • Error Line 378, Column 39: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (1280x720)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 381, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 385, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://www.happytugs.com/main.h…

    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 385, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://www.happytugs.com/main.h…
  • Error Line 385, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://www.happytugs.com/main.h…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 385, Column 100: reference not terminated by REFC delimiter
    …ppytugs.com/main.htm?id=Blazer1182&cmp=tp" target="_blank">VISIT HAPPY TUGS</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 385, Column 100: reference to external entity in attribute value
    …ppytugs.com/main.htm?id=Blazer1182&cmp=tp" target="_blank">VISIT HAPPY TUGS</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 385, Column 100: reference to entity "cmp" for which no system identifier could be generated
    …ppytugs.com/main.htm?id=Blazer1182&cmp=tp" target="_blank">VISIT HAPPY TUGS</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 370, Column 80: entity was defined here
    …w.happytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http:…
  • Error Line 385, Column 150: name start character invalid: only S separators and TAGC allowed here
    …r1182&cmp=tp" target="_blank">VISIT HAPPY TUGS</a>  </font size=2></B></center>
  • Error Line 385, Column 150: end tag for "B" omitted, but OMITTAG NO was specified
    …r1182&cmp=tp" target="_blank">VISIT HAPPY TUGS</a>  </font size=2></B></center>

    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 385, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://www.happytugs.com/main.h…
  • Error Line 385, Column 160: end tag for element "B" which is not open
    …r1182&cmp=tp" target="_blank">VISIT HAPPY TUGS</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 388, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 389, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 381, Column 1: start tag was here
    <p>
  • Error Line 389, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 380, Column 1: start tag was here
    <p>
  • Error Line 402, Column 178: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'http://thaipoony.com/promo/meandmyasian-1.jpg' border=1 vspace=5></a></center>
  • Error Line 402, Column 187: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'http://thaipoony.com/promo/meandmyasian-1.jpg' border=1 vspace=5></a></center>
  • Error Line 402, Column 188: required attribute "alt" not specified
    …'http://thaipoony.com/promo/meandmyasian-1.jpg' border=1 vspace=5></a></center>

    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 402, Column 192: end tag for "img" omitted, but OMITTAG NO was specified
    …'http://thaipoony.com/promo/meandmyasian-1.jpg' border=1 vspace=5></a></center>

    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 402, Column 114: start tag was here
    …me;8873:PPS:meandmy/' target="_blank"><img src='http://thaipoony.com/promo/mea…
  • Error Line 404, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/me-and-my-asian/" target=…

    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 407, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $39.95 / 30 day(s) recurring</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 407, Column 1: start tag was here
    <br><b>Price</b>: $39.95 / 30 day(s) recurring</br>
  • Error Line 407, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $39.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 408, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 475 Sets, High Quality</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 408, Column 1: start tag was here
    <br><b>Pictures</b>: 475 Sets, High Quality</br>
  • Error Line 408, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 475 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 409, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 85+, 10 min+</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 409, Column 1: start tag was here
    <br><b>Videos</b>: 85+, 10 min+</br>
  • Error Line 409, Column 36: end tag for element "br" which is not open
    <br><b>Videos</b>: 85+, 10 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 410, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (640x480)</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 410, Column 1: start tag was here
    <br><b>Formats</b>: WMV (640x480)</br>
  • Error Line 410, Column 38: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (640x480)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 413, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 417, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://secure.meandmyasian.com/…

    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 417, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://secure.meandmyasian.com/…
  • Error Line 417, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://secure.meandmyasian.com/…

    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 417, Column 164: name start character invalid: only S separators and TAGC allowed here
    …eandmy/" target="_blank">VISIT ME AND MY ASIAN</a>  </font size=2></B></center>
  • Error Line 417, Column 164: end tag for "B" omitted, but OMITTAG NO was specified
    …eandmy/" target="_blank">VISIT ME AND MY ASIAN</a>  </font size=2></B></center>

    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 417, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://secure.meandmyasian.com/…
  • Error Line 417, Column 174: end tag for element "B" which is not open
    …eandmy/" target="_blank">VISIT ME AND MY ASIAN</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 420, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 421, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 413, Column 1: start tag was here
    <p>
  • Error Line 421, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 412, Column 1: start tag was here
    <p>
  • Error Line 434, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tp://thaipoony.com/promo/allasianpornstars.jpg' border=1 vspace=5></a></center>
  • Error Line 434, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tp://thaipoony.com/promo/allasianpornstars.jpg' border=1 vspace=5></a></center>
  • Error Line 434, Column 141: required attribute "alt" not specified
    …tp://thaipoony.com/promo/allasianpornstars.jpg' border=1 vspace=5></a></center>

    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 434, Column 145: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://thaipoony.com/promo/allasianpornstars.jpg' border=1 vspace=5></a></center>

    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 434, Column 64: start tag was here
    …llasianpornstars.com' target="_blank"><img src='http://thaipoony.com/promo/all…
  • Error Line 436, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 449, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …c='http://thaipoony.com/promo/softcoreasia.jpg' border=1 vspace=5></a></center>
  • Error Line 449, Column 130: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …c='http://thaipoony.com/promo/softcoreasia.jpg' border=1 vspace=5></a></center>
  • Error Line 449, Column 131: required attribute "alt" not specified
    …c='http://thaipoony.com/promo/softcoreasia.jpg' border=1 vspace=5></a></center>

    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 449, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …c='http://thaipoony.com/promo/softcoreasia.jpg' border=1 vspace=5></a></center>

    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 449, Column 59: start tag was here
    …p://softcoreasia.com' target="_blank"><img src='http://thaipoony.com/promo/sof…
  • Error Line 451, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 464, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …c='http://thaipoony.com/promo/asianpornspy.jpg' border=1 vspace=5></a></center>
  • Error Line 464, Column 130: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …c='http://thaipoony.com/promo/asianpornspy.jpg' border=1 vspace=5></a></center>
  • Error Line 464, Column 131: required attribute "alt" not specified
    …c='http://thaipoony.com/promo/asianpornspy.jpg' border=1 vspace=5></a></center>

    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 464, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …c='http://thaipoony.com/promo/asianpornspy.jpg' border=1 vspace=5></a></center>

    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 464, Column 59: start tag was here
    …p://asianpornspy.com' target="_blank"><img src='http://thaipoony.com/promo/asi…
  • Error Line 466, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 478, Column 8: document type does not allow element "center" here; assuming missing "li" start-tag
    <center><script language="javascript" src="http://ifrm.camdough.com/grid.php?wi…
  • Warning Line 478, Column 89: cannot generate system identifier for general entity "cid"
    …ifrm.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg…

    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 478, Column 89: general entity "cid" not defined and no default entity
    …ifrm.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg…

    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 478, Column 92: reference not terminated by REFC delimiter
    …m.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FF…

    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 478, Column 92: reference to external entity in attribute value
    …m.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FF…

    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 478, Column 92: reference to entity "cid" for which no system identifier could be generated
    …m.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=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.

  • Info Line 478, Column 88: entity was defined here
    …/ifrm.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&f…
  • Warning Line 478, Column 97: cannot generate system identifier for general entity "rid"
    …dough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&…

    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 478, Column 97: general entity "rid" not defined and no default entity
    …dough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&…

    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 478, Column 100: reference not terminated by REFC delimiter
    …gh.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=…

    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 478, Column 100: reference to external entity in attribute value
    …gh.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=…

    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 478, Column 100: reference to entity "rid" for which no system identifier could be generated
    …gh.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=…

    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 478, Column 96: entity was defined here
    …mdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF…
  • Warning Line 478, Column 103: cannot generate system identifier for general entity "vanity"
    …com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=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 478, Column 103: general entity "vanity" not defined and no default entity
    …com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=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 478, Column 109: reference not terminated by REFC delimiter
    …id.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&tr…

    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 478, Column 109: reference to external entity in attribute value
    …id.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&tr…

    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 478, Column 109: reference to entity "vanity" for which no system identifier could be generated
    …id.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&tr…

    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 478, Column 102: entity was defined here
    ….com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=00…
  • Warning Line 478, Column 115: cannot generate system identifier for general entity "col"
    …?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=ye…

    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 478, Column 115: general entity "col" not defined and no default entity
    …?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=ye…

    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 478, Column 118: reference not terminated by REFC delimiter
    …d=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&s…

    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 478, Column 118: reference to external entity in attribute value
    …d=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&s…

    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 478, Column 118: reference to entity "col" for which no system identifier could be generated
    …d=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&s…

    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 478, Column 114: entity was defined here
    …p?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=y…
  • Warning Line 478, Column 121: cannot generate system identifier for general entity "row"
    …00330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&styl…

    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 478, Column 121: general entity "row" not defined and no default entity
    …00330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&styl…

    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 478, Column 124: reference not terminated by REFC delimiter
    …30&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1…

    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 478, Column 124: reference to external entity in attribute value
    …30&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1…

    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 478, Column 124: reference to entity "row" for which no system identifier could be generated
    …30&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1…

    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 478, Column 120: entity was defined here
    …100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&sty…
  • Warning Line 478, Column 127: cannot generate system identifier for general entity "fg"
    …cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&ca…

    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 478, Column 127: general entity "fg" not defined and no default entity
    …cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&ca…

    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 478, Column 129: reference not terminated by REFC delimiter
    …d=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=…

    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 478, Column 129: reference to external entity in attribute value
    …d=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=…

    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 478, Column 129: reference to entity "fg" for which no system identifier could be generated
    …d=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=…

    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 478, Column 126: entity was defined here
    …&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&c…
  • Warning Line 478, Column 137: cannot generate system identifier for general entity "bg"
    …d=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&oc…

    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 478, Column 137: general entity "bg" not defined and no default entity
    …d=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&oc…

    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 478, Column 139: reference not terminated by REFC delimiter
    …1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat…

    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 478, Column 139: reference to external entity in attribute value
    …1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat…

    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 478, Column 139: reference to entity "bg" for which no system identifier could be generated
    …1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat…

    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 478, Column 136: entity was defined here
    …id=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&o…
  • Warning Line 478, Column 147: cannot generate system identifier for general entity "trans"
    …=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scro…

    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 478, Column 147: general entity "trans" not defined and no default entity
    …=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scro…

    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 478, Column 152: reference not terminated by REFC delimiter
    …&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no…

    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 478, Column 152: reference to external entity in attribute value
    …&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no…

    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 478, Column 152: reference to entity "trans" for which no system identifier could be generated
    …&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no…

    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 478, Column 146: entity was defined here
    …y=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scr…
  • Warning Line 478, Column 157: cannot generate system identifier for general entity "style"
    …1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></s…

    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 478, Column 157: general entity "style" not defined and no default entity
    …1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></s…

    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 478, Column 162: reference not terminated by REFC delimiter
    …=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></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 478, Column 162: reference to external entity in attribute value
    …=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></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 478, Column 162: reference to entity "style" for which no system identifier could be generated
    …=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></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 478, Column 156: entity was defined here
    …=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></…
  • Warning Line 478, Column 165: cannot generate system identifier for general entity "cat"
    …fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></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 478, Column 165: general entity "cat" not defined and no default entity
    …fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></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 478, Column 168: reference not terminated by REFC delimiter
    …FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></cen…

    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 478, Column 168: reference to external entity in attribute value
    …FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></cen…

    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 478, Column 168: reference to entity "cat" for which no system identifier could be generated
    …FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></cen…

    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 478, Column 164: entity was defined here
    …&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script><…
  • Warning Line 478, Column 175: cannot generate system identifier for general entity "ocat"
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 175: general entity "ocat" not defined and no default entity
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 179: reference not terminated by REFC delimiter
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 179: reference to external entity in attribute value
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 179: reference to entity "ocat" for which no system identifier could be generated
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 174: entity was defined here
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>
  • Warning Line 478, Column 183: cannot generate system identifier for general entity "scroll"
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 183: general entity "scroll" not defined and no default entity
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 189: reference not terminated by REFC delimiter
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 189: reference to external entity in attribute value
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 189: reference to entity "scroll" for which no system identifier could be generated
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

    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 478, Column 182: entity was defined here
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>
  • Error Line 478, Column 193: required attribute "type" not specified
    …FFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script></center>

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

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

  • Info Line 478, Column 1: start tag was here
    <center><script language="javascript" src="http://ifrm.camdough.com/grid.php?wi…
  • Warning Line 487, Column 84: cannot generate system identifier for general entity "aff_code"
    …bar_tgp/display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&num…

    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 487, Column 84: general entity "aff_code" not defined and no default entity
    …bar_tgp/display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&num…

    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 487, Column 92: reference not terminated by REFC delimiter
    …display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&ba…

    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 487, Column 92: reference to external entity in attribute value
    …display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&ba…

    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 487, Column 92: reference to entity "aff_code" for which no system identifier could be generated
    …display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&ba…

    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 487, Column 83: entity was defined here
    …ebar_tgp/display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&nu…
  • Warning Line 487, Column 101: cannot generate system identifier for general entity "sites"
    …hp?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_…

    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 487, Column 101: general entity "sites" not defined and no default entity
    …hp?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_…

    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 487, Column 106: reference not terminated by REFC delimiter
    …sition=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color…

    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 487, Column 106: reference to external entity in attribute value
    …sition=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color…

    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 487, Column 106: reference to entity "sites" for which no system identifier could be generated
    …sition=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_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.

  • Info Line 487, Column 100: entity was defined here
    …php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background…
  • Warning Line 487, Column 111: cannot generate system identifier for general entity "width"
    …n=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=1919…

    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 487, Column 111: general entity "width" not defined and no default entity
    …n=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=1919…

    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 487, Column 116: reference not terminated by REFC delimiter
    …tical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&bo…

    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 487, Column 116: reference to external entity in attribute value
    …tical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&bo…

    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 487, Column 116: reference to entity "width" for which no system identifier could be generated
    …tical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&bo…

    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 487, Column 110: entity was defined here
    …on=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191…
  • Warning Line 487, Column 121: cannot generate system identifier for general entity "number"
    …&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&border_…

    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 487, Column 121: general entity "number" not defined and no default entity
    …&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&border_…

    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 487, Column 127: reference not terminated by REFC delimiter
    …ode=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=…

    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 487, Column 127: reference to external entity in attribute value
    …ode=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=…

    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 487, Column 127: reference to entity "number" for which no system identifier could be generated
    …ode=1415427&sites=tgw&width=160&number=3&background_color=191919&border_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.

  • Info Line 487, Column 120: entity was defined here
    …l&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&border…
  • Warning Line 487, Column 130: cannot generate system identifier for general entity "background_color"
    …=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=191…

    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 487, Column 130: general entity "background_color" not defined and no default entity
    …=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=191…

    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 487, Column 146: reference not terminated by REFC delimiter
    …gw&width=160&number=3&background_color=191919&border_color=191919&text_color=F…

    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 487, Column 146: reference to external entity in attribute value
    …gw&width=160&number=3&background_color=191919&border_color=191919&text_color=F…

    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 487, Column 146: reference to entity "background_color" for which no system identifier could be generated
    …gw&width=160&number=3&background_color=191919&border_color=191919&text_color=F…

    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 487, Column 129: entity was defined here
    …e=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=19…
  • Warning Line 487, Column 154: cannot generate system identifier for general entity "border_color"
    …=160&number=3&background_color=191919&border_color=191919&text_color=FFFFFF' t…

    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 487, Column 154: general entity "border_color" not defined and no default entity
    …=160&number=3&background_color=191919&border_color=191919&text_color=FFFFFF' 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.

  • Warning Line 487, Column 166: reference not terminated by REFC delimiter
    …3&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 487, Column 166: reference to external entity in attribute value
    …3&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 487, Column 166: reference to entity "border_color" for which no system identifier could be generated
    …3&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 487, Column 153: entity was defined here
    …h=160&number=3&background_color=191919&border_color=191919&text_color=FFFFFF' …
  • Warning Line 487, Column 174: cannot generate system identifier for general entity "text_color"
    …ound_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript…

    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 487, Column 174: general entity "text_color" not defined and no default entity
    …ound_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript…

    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 487, Column 184: reference not terminated by REFC delimiter
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 487, Column 184: reference to external entity in attribute value
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 487, Column 184: reference to entity "text_color" for which no system identifier could be generated
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 487, Column 173: entity was defined here
    …round_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascrip…
  • Error Line 487, Column 215: document type does not allow element "script" here; assuming missing "li" start-tag
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>
  • Error Line 489, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 487, Column 1: start tag was here
    <script src='http://asianbutterflies.com/sidebar_tgp/display.php?position=verti…
  • Error Line 508, Column 8: document type does not allow element "center" here; assuming missing "li" start-tag
    <center><p><a href="http://feeds.feedburner.com/ThaiPoony"><img src="http://fee…
  • Warning Line 508, Column 124: reference not terminated by REFC delimiter
    …dburner.com/~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" s…

    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 508, Column 124: reference to external entity in attribute value
    …dburner.com/~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" s…

    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 508, Column 124: reference to entity "fg" for which no system identifier could be generated
    …dburner.com/~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" s…

    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 478, Column 126: entity was defined here
    …&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=000000&trans=yes&style=1&c…
  • Warning Line 508, Column 132: cannot generate system identifier for general entity "anim"
    …com/~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" style="bo…

    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 508, Column 132: general entity "anim" not defined and no default entity
    …com/~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" style="bo…

    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 508, Column 136: reference not terminated by REFC delimiter
    …~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" style="border…

    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 508, Column 136: reference to external entity in attribute value
    …~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" style="border…

    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 508, Column 136: reference to entity "anim" for which no system identifier could be generated
    …~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" style="border…

    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 508, Column 131: entity was defined here
    ….com/~fc/ThaiPoony?bg=006600&fg=FFFFCC&anim=0" height="26" width="88" style="b…
  • Error Line 510, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 508, Column 1: start tag was here
    <center><p><a href="http://feeds.feedburner.com/ThaiPoony"><img src="http://fee…
  • Warning Line 543, Column 82: reference not terminated by REFC delimiter
    …amdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com…

    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 543, Column 82: reference to external entity in attribute value
    …amdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com…

    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 543, Column 82: reference to entity "cid" for which no system identifier could be generated
    …amdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com…

    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 478, Column 88: entity was defined here
    …/ifrm.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&f…
  • Warning Line 543, Column 90: reference not terminated by REFC delimiter
    …com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Gir…

    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 543, Column 90: reference to external entity in attribute value
    …com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Gir…

    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 543, Column 90: reference to entity "rid" for which no system identifier could be generated
    …com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Gir…

    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 478, Column 96: entity was defined here
    …mdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF…
  • Warning Line 543, Column 99: reference not terminated by REFC delimiter
    …kchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" />

    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 543, Column 99: reference to external entity in attribute value
    …kchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" />

    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 543, Column 99: reference to entity "vanity" for which no system identifier could be generated
    …kchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" />

    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 478, Column 102: entity was defined here
    ….com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=00…
  • Warning Line 543, Column 126: reference not terminated by REFC delimiter
    …kchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" />

    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 543, Column 126: reference to external entity in attribute value
    …kchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" />

    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 543, Column 126: reference to entity "cat" for which no system identifier could be generated
    …kchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" />

    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 478, Column 164: entity was defined here
    …&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script><…
  • Error Line 546, Column 12: there is no attribute "src"
    <embed src="http://liveads.camdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&va…

    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.

  • Warning Line 546, Column 67: reference not terminated by REFC delimiter
    …amdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com…

    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 546, Column 67: reference to external entity in attribute value
    …amdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com…

    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 546, Column 67: reference to entity "cid" for which no system identifier could be generated
    …amdough.com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com…

    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 478, Column 88: entity was defined here
    …/ifrm.camdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&f…
  • Warning Line 546, Column 75: reference not terminated by REFC delimiter
    …com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Gir…

    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 546, Column 75: reference to external entity in attribute value
    …com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Gir…

    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 546, Column 75: reference to entity "rid" for which no system identifier could be generated
    …com/fkchat4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Gir…

    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 478, Column 96: entity was defined here
    …mdough.com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF…
  • Warning Line 546, Column 84: reference not terminated by REFC delimiter
    …t4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" wmode…

    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 546, Column 84: reference to external entity in attribute value
    …t4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" wmode…

    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 546, Column 84: reference to entity "vanity" for which no system identifier could be generated
    …t4.swf?wid=100330&cid=103&rid=1&vanity=sexytime.asians247.com&cat=Girls" wmode…

    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 478, Column 102: entity was defined here
    ….com/grid.php?wid=100330&cid=102&rid=1&vanity=1193&col=1&row=5&fg=FFFFFF&bg=00…
  • Warning Line 546, Column 111: reference not terminated by REFC delimiter
    …id=1&vanity=sexytime.asians247.com&cat=Girls" wmode="transparent" quality="hig…

    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 546, Column 111: reference to external entity in attribute value
    …id=1&vanity=sexytime.asians247.com&cat=Girls" wmode="transparent" quality="hig…

    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 546, Column 111: reference to entity "cat" for which no system identifier could be generated
    …id=1&vanity=sexytime.asians247.com&cat=Girls" wmode="transparent" quality="hig…

    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 478, Column 164: entity was defined here
    …&fg=FFFFFF&bg=000000&trans=yes&style=1&cat=Girls&ocat=no&scroll=no"></script><…
  • Error Line 546, Column 125: there is no attribute "wmode"
    …xytime.asians247.com&cat=Girls" wmode="transparent" quality="high" bgcolor="#f…

    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 546, Column 147: there is no attribute "quality"
    …at=Girls" wmode="transparent" quality="high" bgcolor="#ffffff" width="188" hei…

    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 546, Column 162: there is no attribute "bgcolor"
    …="transparent" quality="high" bgcolor="#ffffff" width="188" height="143" name=…

    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 546, Column 178: there is no attribute "width"
    …uality="high" bgcolor="#ffffff" width="188" height="143" name="fkchat" align="…

    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 546, Column 191: there is no attribute "height"
    … bgcolor="#ffffff" width="188" height="143" name="fkchat" align="middle" allow…

    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 546, Column 202: there is no attribute "name"
    …ffffff" width="188" height="143" name="fkchat" align="middle" allowScriptAcces…

    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 546, Column 217: there is no attribute "align"
    …188" height="143" name="fkchat" align="middle" allowScriptAccess="always" type…

    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 546, Column 244: there is no attribute "allowScriptAccess"
    …hat" align="middle" allowScriptAccess="always" type="application/x-shockwave-f…

    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 546, Column 258: there is no attribute "type"
    …ddle" allowScriptAccess="always" type="application/x-shockwave-flash" pluginsp…

    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 546, Column 302: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 546, Column 349: element "embed" undefined
    …ve-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" /></object>

    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 580, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 581, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><!-- Place this tag where you want the +1 button to render -->

    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 582, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone></center>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 584, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 580, Column 1: start tag was here
    <p>
  • Error Line 584, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 579, Column 1: start tag was here
    <p>
  • Error Line 597, Column 35: document type does not allow element "div" here; assuming missing "li" start-tag
    <div id="google_translate_element"></div><script>
  • Error Line 597, Column 49: required attribute "type" not specified
    <div id="google_translate_element"></div><script>

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

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

  • Error Line 604, Column 104: required attribute "type" not specified
    …late.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>

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

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

  • Error Line 605, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 597, Column 1: start tag was here
    <div id="google_translate_element"></div><script>
  • Warning Line 616, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372773' target="_blank"><img src='http…

    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 616, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372773' target="_blank"><img src='http…

    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 616, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372773' target="_blank"><img src='http…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Error Line 616, Column 178: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … src='http://thaipoony.com/promo/160x600-5.jpg' border=1 vspace=5></a></center>
  • Error Line 616, Column 187: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … src='http://thaipoony.com/promo/160x600-5.jpg' border=1 vspace=5></a></center>
  • Error Line 616, Column 188: required attribute "alt" not specified
    … src='http://thaipoony.com/promo/160x600-5.jpg' border=1 vspace=5></a></center>

    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 616, Column 192: end tag for "img" omitted, but OMITTAG NO was specified
    … src='http://thaipoony.com/promo/160x600-5.jpg' border=1 vspace=5></a></center>

    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 616, Column 119: start tag was here
    …5220-0000&PA=2372773' target="_blank"><img src='http://thaipoony.com/promo/160…
  • Warning Line 618, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372773" target="_blank">Visit Asian Po…

    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 618, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372773" target="_blank">Visit Asian Po…

    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 618, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372773" target="_blank">Visit Asian Po…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 742, Column 88: reference not terminated by REFC delimiter
    …display.php?position=vertical&aff_code=1394711&sites=as,ct&width=160&number=14…

    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 742, Column 88: reference to external entity in attribute value
    …display.php?position=vertical&aff_code=1394711&sites=as,ct&width=160&number=14…

    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 742, Column 88: reference to entity "aff_code" for which no system identifier could be generated
    …display.php?position=vertical&aff_code=1394711&sites=as,ct&width=160&number=14…

    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 487, Column 83: entity was defined here
    …ebar_tgp/display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&nu…
  • Warning Line 742, Column 102: reference not terminated by REFC delimiter
    …sition=vertical&aff_code=1394711&sites=as,ct&width=160&number=14&background_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 742, Column 102: reference to external entity in attribute value
    …sition=vertical&aff_code=1394711&sites=as,ct&width=160&number=14&background_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 742, Column 102: reference to entity "sites" for which no system identifier could be generated
    …sition=vertical&aff_code=1394711&sites=as,ct&width=160&number=14&background_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 487, Column 100: entity was defined here
    …php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background…
  • Warning Line 742, Column 114: reference not terminated by REFC delimiter
    …cal&aff_code=1394711&sites=as,ct&width=160&number=14&background_color=191919&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 742, Column 114: reference to external entity in attribute value
    …cal&aff_code=1394711&sites=as,ct&width=160&number=14&background_color=191919&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 742, Column 114: reference to entity "width" for which no system identifier could be generated
    …cal&aff_code=1394711&sites=as,ct&width=160&number=14&background_color=191919&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 487, Column 110: entity was defined here
    …on=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191…
  • Warning Line 742, Column 125: reference not terminated by REFC delimiter
    …e=1394711&sites=as,ct&width=160&number=14&background_color=191919&border_color…

    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 742, Column 125: reference to external entity in attribute value
    …e=1394711&sites=as,ct&width=160&number=14&background_color=191919&border_color…

    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 742, Column 125: reference to entity "number" for which no system identifier could be generated
    …e=1394711&sites=as,ct&width=160&number=14&background_color=191919&border_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.

  • Info Line 487, Column 120: entity was defined here
    …l&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&border…
  • Warning Line 742, Column 145: reference not terminated by REFC delimiter
    …t&width=160&number=14&background_color=191919&border_color=191919&text_color=F…

    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 742, Column 145: reference to external entity in attribute value
    …t&width=160&number=14&background_color=191919&border_color=191919&text_color=F…

    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 742, Column 145: reference to entity "background_color" for which no system identifier could be generated
    …t&width=160&number=14&background_color=191919&border_color=191919&text_color=F…

    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 487, Column 129: entity was defined here
    …e=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=19…
  • Warning Line 742, Column 165: reference not terminated by REFC delimiter
    …4&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 742, Column 165: reference to external entity in attribute value
    …4&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 742, Column 165: reference to entity "border_color" for which no system identifier could be generated
    …4&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 487, Column 153: entity was defined here
    …h=160&number=3&background_color=191919&border_color=191919&text_color=FFFFFF' …
  • Warning Line 742, Column 183: reference not terminated by REFC delimiter
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 742, Column 183: reference to external entity in attribute value
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 742, Column 183: reference to entity "text_color" for which no system identifier could be generated
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 487, Column 173: entity was defined here
    …round_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascrip…
  • Warning Line 770, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 770, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 770, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 770, Column 106: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php' tar…

    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 770, Column 106: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php' tar…

    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 770, Column 106: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php' tar…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 770, Column 227: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p://thaipoony.com/promo/submityourthai.com.jpg' border=1 vspace=5></a></center>
  • Error Line 770, Column 236: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p://thaipoony.com/promo/submityourthai.com.jpg' border=1 vspace=5></a></center>
  • Error Line 770, Column 237: required attribute "alt" not specified
    …p://thaipoony.com/promo/submityourthai.com.jpg' border=1 vspace=5></a></center>

    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 770, Column 241: end tag for "img" omitted, but OMITTAG NO was specified
    …p://thaipoony.com/promo/submityourthai.com.jpg' border=1 vspace=5></a></center>

    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 770, Column 159: start tag was here
    …ourthai.com/tour.php' target="_blank"><img src='http://thaipoony.com/promo/sub…
  • Error Line 772, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/submit-your-thai/" target…

    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 775, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</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 775, Column 1: start tag was here
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>
  • Error Line 775, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 776, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 100 Sets, High Quality</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 776, Column 1: start tag was here
    <br><b>Pictures</b>: 100 Sets, High Quality</br>
  • Error Line 776, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 100 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 777, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 100+, 10 min+</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 777, Column 1: start tag was here
    <br><b>Videos</b>: 100+, 10 min+</br>
  • Error Line 777, Column 37: end tag for element "br" which is not open
    <br><b>Videos</b>: 100+, 10 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 778, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (1280x720)</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 778, Column 1: start tag was here
    <br><b>Formats</b>: WMV (1280x720)</br>
  • Error Line 778, Column 39: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (1280x720)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 781, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 785, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    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 785, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 785, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 785, Column 109: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 785, Column 109: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 785, Column 109: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 785, Column 122: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php" tar…

    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 785, Column 122: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php" tar…

    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 785, Column 122: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php" tar…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 785, Column 210: name start character invalid: only S separators and TAGC allowed here
    …ur.php" target="_blank">VISIT SUBMIT YOUR THAI</a>  </font size=2></B></center>
  • Error Line 785, Column 210: end tag for "B" omitted, but OMITTAG NO was specified
    …ur.php" target="_blank">VISIT SUBMIT YOUR THAI</a>  </font size=2></B></center>

    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 785, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 785, Column 220: end tag for element "B" which is not open
    …ur.php" target="_blank">VISIT SUBMIT YOUR THAI</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 786, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 787, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 781, Column 1: start tag was here
    <p>
  • Error Line 787, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 780, Column 1: start tag was here
    <p>
  • Error Line 798, Column 189: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'http://thaipoony.com/promo/ilovethaipussy.jpg' border=1 vspace=5></a></center>
  • Error Line 798, Column 198: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'http://thaipoony.com/promo/ilovethaipussy.jpg' border=1 vspace=5></a></center>
  • Error Line 798, Column 199: required attribute "alt" not specified
    …'http://thaipoony.com/promo/ilovethaipussy.jpg' border=1 vspace=5></a></center>

    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 798, Column 203: end tag for "img" omitted, but OMITTAG NO was specified
    …'http://thaipoony.com/promo/ilovethaipussy.jpg' border=1 vspace=5></a></center>

    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 798, Column 125: start tag was here
    …ps:ilovethaipussy,6/' target="_blank"><img src='http://thaipoony.com/promo/ilo…
  • Error Line 800, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/i-love-thai-pussy/" targe…

    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 803, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</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 803, Column 1: start tag was here
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</br>
  • Error Line 803, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $24.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 804, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 400 Sets, High Quality</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 804, Column 1: start tag was here
    <br><b>Pictures</b>: 400 Sets, High Quality</br>
  • Error Line 804, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 400 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 805, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 475+, 10 min+</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 805, Column 1: start tag was here
    <br><b>Videos</b>: 475+, 10 min+</br>
  • Error Line 805, Column 37: end tag for element "br" which is not open
    <br><b>Videos</b>: 475+, 10 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 806, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (640x480)</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 806, Column 1: start tag was here
    <br><b>Formats</b>: WMV (640x480)</br>
  • Error Line 806, Column 38: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (640x480)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 809, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 814, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://join.ilovethaipussy.com/…

    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 814, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://join.ilovethaipussy.com/…
  • Error Line 814, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://join.ilovethaipussy.com/…

    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 814, Column 177: name start character invalid: only S separators and TAGC allowed here
    …sy,6/" target="_blank">VISIT I LOVE THAI PUSSY</a>  </font size=2></B></center>
  • Error Line 814, Column 177: end tag for "B" omitted, but OMITTAG NO was specified
    …sy,6/" target="_blank">VISIT I LOVE THAI PUSSY</a>  </font size=2></B></center>

    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 814, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://join.ilovethaipussy.com/…
  • Error Line 814, Column 187: end tag for element "B" which is not open
    …sy,6/" target="_blank">VISIT I LOVE THAI PUSSY</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 817, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 818, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 809, Column 1: start tag was here
    <p>
  • Error Line 818, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 808, Column 1: start tag was here
    <p>
  • Warning Line 828, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146' target="_blank"><img src='http…

    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 828, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146' target="_blank"><img src='http…

    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 828, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146' target="_blank"><img src='http…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Error Line 828, Column 183: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'http://thaipoony.com/promo/asianappleseed.jpg' border=1 vspace=5></a></center>
  • Error Line 828, Column 192: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'http://thaipoony.com/promo/asianappleseed.jpg' border=1 vspace=5></a></center>
  • Error Line 828, Column 193: required attribute "alt" not specified
    …'http://thaipoony.com/promo/asianappleseed.jpg' border=1 vspace=5></a></center>

    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 828, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …'http://thaipoony.com/promo/asianappleseed.jpg' border=1 vspace=5></a></center>

    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 828, Column 119: start tag was here
    …9150-0000&PA=1682146' target="_blank"><img src='http://thaipoony.com/promo/asi…
  • Error Line 830, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/asian-apple-seed/" target…

    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 833, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $39.95 / 30 day(s) recurring</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 833, Column 1: start tag was here
    <br><b>Price</b>: $39.95 / 30 day(s) recurring</br>
  • Error Line 833, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $39.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 834, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 105 Sets, High Quality</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 834, Column 1: start tag was here
    <br><b>Pictures</b>: 105 Sets, High Quality</br>
  • Error Line 834, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 105 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 835, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 105+, 10 min+</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 835, Column 1: start tag was here
    <br><b>Videos</b>: 105+, 10 min+</br>
  • Error Line 835, Column 37: end tag for element "br" which is not open
    <br><b>Videos</b>: 105+, 10 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 836, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (1280x720)</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 836, Column 1: start tag was here
    <br><b>Formats</b>: WMV (1280x720)</br>
  • Error Line 836, Column 39: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (1280x720)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 839, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 843, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    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 843, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 843, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 843, Column 109: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146" target="_blank">VISIT ASIAN AP…

    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 843, Column 109: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146" target="_blank">VISIT ASIAN AP…

    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 843, Column 109: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146" target="_blank">VISIT ASIAN AP…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Error Line 843, Column 170: name start character invalid: only S separators and TAGC allowed here
    …682146" target="_blank">VISIT ASIAN APPLE SEED</a>  </font size=2></B></center>
  • Error Line 843, Column 170: end tag for "B" omitted, but OMITTAG NO was specified
    …682146" target="_blank">VISIT ASIAN APPLE SEED</a>  </font size=2></B></center>

    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 843, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 843, Column 180: end tag for element "B" which is not open
    …682146" target="_blank">VISIT ASIAN APPLE SEED</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 844, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 845, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 839, Column 1: start tag was here
    <p>
  • Error Line 845, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 838, Column 1: start tag was here
    <p>
  • Warning Line 856, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

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

  • Warning Line 856, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

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

  • Error Line 856, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 856, Column 106: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

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

  • Warning Line 856, Column 106: reference to external entity in attribute value
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

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

  • Error Line 856, Column 106: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 856, Column 234: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ttp://thaipoony.com/promo/asian-whore-pass.jpg' border=1 vspace=5></a></center>
  • Error Line 856, Column 243: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ttp://thaipoony.com/promo/asian-whore-pass.jpg' border=1 vspace=5></a></center>
  • Error Line 856, Column 244: required attribute "alt" not specified
    …ttp://thaipoony.com/promo/asian-whore-pass.jpg' border=1 vspace=5></a></center>

    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 856, Column 248: end tag for "img" omitted, but OMITTAG NO was specified
    …ttp://thaipoony.com/promo/asian-whore-pass.jpg' border=1 vspace=5></a></center>

    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 856, Column 168: start tag was here
    …ss.com/tc/index.html' target="_blank"><img src='http://thaipoony.com/promo/asi…
  • Error Line 858, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/category/thai-porn/" targ…

    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 861, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</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 861, Column 1: start tag was here
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>
  • Error Line 861, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 862, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 300 Sets, High Quality</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 862, Column 1: start tag was here
    <br><b>Pictures</b>: 300 Sets, High Quality</br>
  • Error Line 862, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 300 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 863, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 300+, 15 min+</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 863, Column 1: start tag was here
    <br><b>Videos</b>: 300+, 15 min+</br>
  • Error Line 863, Column 37: end tag for element "br" which is not open
    <br><b>Videos</b>: 300+, 15 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 864, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (720x480)</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 864, Column 1: start tag was here
    <br><b>Formats</b>: WMV (720x480)</br>
  • Error Line 864, Column 38: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (720x480)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 867, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 871, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    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 871, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 871, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 871, Column 109: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 871, Column 109: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 871, Column 109: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 871, Column 122: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 871, Column 122: reference to external entity in attribute value
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 871, Column 122: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 871, Column 219: name start character invalid: only S separators and TAGC allowed here
    …x.html" target="_blank">VISIT ASIAN WHORE PASS</a>  </font size=2></B></center>
  • Error Line 871, Column 219: end tag for "B" omitted, but OMITTAG NO was specified
    …x.html" target="_blank">VISIT ASIAN WHORE PASS</a>  </font size=2></B></center>

    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 871, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 871, Column 229: end tag for element "B" which is not open
    …x.html" target="_blank">VISIT ASIAN WHORE PASS</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 874, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 875, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 867, Column 1: start tag was here
    <p>
  • Error Line 875, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 866, Column 1: start tag was here
    <p>
  • Warning Line 886, Column 93: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 886, Column 93: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 886, Column 93: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 886, Column 106: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php' targ…

    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 886, Column 106: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php' targ…

    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 886, Column 106: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php' targ…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 886, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/thaigirlswild.jpg' border=1 vspace=5></a></center>
  • Error Line 886, Column 230: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/thaigirlswild.jpg' border=1 vspace=5></a></center>
  • Error Line 886, Column 231: required attribute "alt" not specified
    …='http://thaipoony.com/promo/thaigirlswild.jpg' border=1 vspace=5></a></center>

    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 886, Column 235: end tag for "img" omitted, but OMITTAG NO was specified
    …='http://thaipoony.com/promo/thaigirlswild.jpg' border=1 vspace=5></a></center>

    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 886, Column 158: start tag was here
    …rlswild.com/tour.php' target="_blank"><img src='http://thaipoony.com/promo/tha…
  • Error Line 888, Column 11: element "B" undefined
    <center><B><a href="http://allasianreviews.com/review/thai-girls-wild/" target=…

    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 891, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</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 891, Column 1: start tag was here
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>
  • Error Line 891, Column 51: end tag for element "br" which is not open
    <br><b>Price</b>: $29.95 / 30 day(s) recurring</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 892, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Pictures</b>: 125 Sets, High Quality</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 892, Column 1: start tag was here
    <br><b>Pictures</b>: 125 Sets, High Quality</br>
  • Error Line 892, Column 48: end tag for element "br" which is not open
    <br><b>Pictures</b>: 125 Sets, High Quality</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 893, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Videos</b>: 60+, 10 min+</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 893, Column 1: start tag was here
    <br><b>Videos</b>: 60+, 10 min+</br>
  • Error Line 893, Column 36: end tag for element "br" which is not open
    <br><b>Videos</b>: 60+, 10 min+</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 894, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>Formats</b>: WMV (1280x720)</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 894, Column 1: start tag was here
    <br><b>Formats</b>: WMV (1280x720)</br>
  • Error Line 894, Column 39: end tag for element "br" which is not open
    <br><b>Formats</b>: WMV (1280x720)</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 897, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

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

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

  • Error Line 902, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    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 902, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 902, Column 24: element "B" undefined
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 902, Column 109: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 902, Column 109: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 902, Column 109: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 902, Column 122: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php" targ…

    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 902, Column 122: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php" targ…

    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 902, Column 122: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php" targ…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Error Line 902, Column 208: name start character invalid: only S separators and TAGC allowed here
    …our.php" target="_blank">VISIT THAI GIRLS WILD</a>  </font size=2></B></center>
  • Error Line 902, Column 208: end tag for "B" omitted, but OMITTAG NO was specified
    …our.php" target="_blank">VISIT THAI GIRLS WILD</a>  </font size=2></B></center>

    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 902, Column 22: start tag was here
    <center><font size=2><B><a rel="nofollow" href="http://refer.ccbill.com/cgi-bin…
  • Error Line 902, Column 218: end tag for element "B" which is not open
    …our.php" target="_blank">VISIT THAI GIRLS WILD</a>  </font size=2></B></center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 905, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 906, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 897, Column 1: start tag was here
    <p>
  • Error Line 906, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 896, Column 1: start tag was here
    <p>
  • Error Line 916, Column 117: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src='http://thaipoony.com/promo/asianpoony.jpg' border=1 vspace=5></a></center>
  • Error Line 916, Column 126: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src='http://thaipoony.com/promo/asianpoony.jpg' border=1 vspace=5></a></center>
  • Error Line 916, Column 127: required attribute "alt" not specified
    …src='http://thaipoony.com/promo/asianpoony.jpg' border=1 vspace=5></a></center>

    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 916, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …src='http://thaipoony.com/promo/asianpoony.jpg' border=1 vspace=5></a></center>

    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 916, Column 57: start tag was here
    …ttp://asianpoony.com' target="_blank"><img src='http://thaipoony.com/promo/asi…
  • Error Line 918, Column 12: end tag for element "a" which is not open
    					   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 932, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/filipinapoony.jpg' border=1 vspace=5></a></center>
  • Error Line 932, Column 132: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='http://thaipoony.com/promo/filipinapoony.jpg' border=1 vspace=5></a></center>
  • Error Line 932, Column 133: required attribute "alt" not specified
    …='http://thaipoony.com/promo/filipinapoony.jpg' border=1 vspace=5></a></center>

    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 932, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …='http://thaipoony.com/promo/filipinapoony.jpg' border=1 vspace=5></a></center>

    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 932, Column 60: start tag was here
    …://filipinapoony.com' target="_blank"><img src='http://thaipoony.com/promo/fil…
  • Error Line 934, Column 13: end tag for element "a" which is not open
    						   </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 947, Column 117: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src='http://thaipoony.com/promo/tokyopoony.jpg' border=1 vspace=5></a></center>
  • Error Line 947, Column 126: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src='http://thaipoony.com/promo/tokyopoony.jpg' border=1 vspace=5></a></center>
  • Error Line 947, Column 127: required attribute "alt" not specified
    …src='http://thaipoony.com/promo/tokyopoony.jpg' border=1 vspace=5></a></center>

    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 947, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …src='http://thaipoony.com/promo/tokyopoony.jpg' border=1 vspace=5></a></center>

    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 947, Column 57: start tag was here
    …ttp://tokyopoony.com' target="_blank"><img src='http://thaipoony.com/promo/tok…
  • Error Line 949, Column 13: end tag for element "a" which is not open
    						   </a>

    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 1014, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372763" target="_blank">Asian Porngasm…

    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 1014, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372763" target="_blank">Asian Porngasm…

    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 1014, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372763" target="_blank">Asian Porngasm…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1016, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansybian.com/tou…

    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 1016, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansybian.com/tou…

    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 1016, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansybian.com/tou…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1016, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansybian.com/tour.php" target…

    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 1016, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansybian.com/tour.php" target…

    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 1016, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansybian.com/tour.php" target…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1018, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 1018, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 1018, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1018, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 1018, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 1018, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.asianwhorepass.com/tc/index.…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1020, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansuckdolls.com/…

    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 1020, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansuckdolls.com/…

    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 1020, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansuckdolls.com/…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1020, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansuckdolls.com/z_tour/" targ…

    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 1020, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansuckdolls.com/z_tour/" targ…

    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 1020, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://asiansuckdolls.com/z_tour/" targ…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1022, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Ap…

    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 1022, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Ap…

    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 1022, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Ap…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1022, Column 98: cannot generate system identifier for general entity "BAN"
    …/clicks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Apple Seed<…

    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 1022, Column 98: general entity "BAN" not defined and no default entity
    …/clicks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Apple Seed<…

    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 1022, Column 101: reference not terminated by REFC delimiter
    …icks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Apple Seed</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 1022, Column 101: reference to external entity in attribute value
    …icks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Apple Seed</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 1022, Column 101: reference to entity "BAN" for which no system identifier could be generated
    …icks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Apple Seed</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 1022, Column 97: entity was defined here
    …n/clicks.cgi?CA=929150-0000&PA=1682146&BAN=0" target="_blank">Asian Apple Seed…
  • Warning Line 1024, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0004&PA=2132553&HTML=http://www.asianbabymakers…

    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 1024, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0004&PA=2132553&HTML=http://www.asianbabymakers…

    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 1024, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0004&PA=2132553&HTML=http://www.asianbabymakers…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1024, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0004&PA=2132553&HTML=http://www.asianbabymakers.com/tc/index…

    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 1024, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=924105-0004&PA=2132553&HTML=http://www.asianbabymakers.com/tc/index…

    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 1024, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0004&PA=2132553&HTML=http://www.asianbabymakers.com/tc/index…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1026, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0002&PA=2132553&HTML=http://www.bangkokstreetwh…

    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 1026, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0002&PA=2132553&HTML=http://www.bangkokstreetwh…

    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 1026, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0002&PA=2132553&HTML=http://www.bangkokstreetwh…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1026, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0002&PA=2132553&HTML=http://www.bangkokstreetwhores.com/tc/i…

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

  • Warning Line 1026, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=924105-0002&PA=2132553&HTML=http://www.bangkokstreetwhores.com/tc/i…

    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 1026, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0002&PA=2132553&HTML=http://www.bangkokstreetwhores.com/tc/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.

  • Info Line 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1028, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 1028, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 1028, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1028, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/" targe…

    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 1028, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/" targe…

    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 1028, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/" targe…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1030, Column 80: reference not terminated by REFC delimiter
    …appytugs.com/main.htm?id=Blazer1182&cmp=tp" target="_blank">Happy Tugs</a></li>

    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 1030, Column 80: reference to external entity in attribute value
    …appytugs.com/main.htm?id=Blazer1182&cmp=tp" target="_blank">Happy Tugs</a></li>

    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 1030, Column 80: reference to entity "cmp" for which no system identifier could be generated
    …appytugs.com/main.htm?id=Blazer1182&cmp=tp" target="_blank">Happy Tugs</a></li>

    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 370, Column 80: entity was defined here
    …w.happytugs.com/main.htm?id=Blazer1182&cmp=tp' target="_blank"><img src='http:…
  • Warning Line 1042, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://lulusexbomb.com/t1/…

    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 1042, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://lulusexbomb.com/t1/…

    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 1042, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://lulusexbomb.com/t1/…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1042, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://lulusexbomb.com/t1/" target="_bl…

    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 1042, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://lulusexbomb.com/t1/" target="_bl…

    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 1042, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://lulusexbomb.com/t1/" target="_bl…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1044, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.siamslam.com/tc…

    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 1044, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.siamslam.com/tc…

    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 1044, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.siamslam.com/tc…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1044, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.siamslam.com/tc/index.html" …

    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 1044, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.siamslam.com/tc/index.html" …

    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 1044, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0005&PA=2132553&HTML=http://www.siamslam.com/tc/index.html" …

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1046, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 1046, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 1046, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1046, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php" tar…

    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 1046, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php" tar…

    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 1046, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://submityourthai.com/tour.php" tar…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1050, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thainee.com/main/" …

    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 1050, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thainee.com/main/" …

    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 1050, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thainee.com/main/" …

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1050, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thainee.com/main/" target="_blan…

    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 1050, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thainee.com/main/" target="_blan…

    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 1050, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thainee.com/main/" target="_blan…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1052, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 1052, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 1052, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1052, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php" targ…

    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 1052, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php" targ…

    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 1052, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=929899-0000&PA=1415427&HTML=http://thaigirlswild.com/tour.php" targ…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1056, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=901169-0100&PA=1397750&HTML=http://www.thaichix.com/in…

    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 1056, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=901169-0100&PA=1397750&HTML=http://www.thaichix.com/in…

    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 1056, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=901169-0100&PA=1397750&HTML=http://www.thaichix.com/in…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1056, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=901169-0100&PA=1397750&HTML=http://www.thaichix.com/index.php?p=0&s…

    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 1056, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=901169-0100&PA=1397750&HTML=http://www.thaichix.com/index.php?p=0&s…

    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 1056, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=901169-0100&PA=1397750&HTML=http://www.thaichix.com/index.php?p=0&s…

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1056, Column 141: cannot generate system identifier for general entity "sp"
    …http://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a>…

    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 1056, Column 141: general entity "sp" not defined and no default entity
    …http://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</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.

  • Warning Line 1056, Column 143: reference not terminated by REFC delimiter
    …tp://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</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 1056, Column 143: reference to external entity in attribute value
    …tp://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</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 1056, Column 143: reference to entity "sp" for which no system identifier could be generated
    …tp://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</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 1056, Column 140: entity was defined here
    …=http://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a…
  • Warning Line 1056, Column 146: cannot generate system identifier for general entity "po"
    …://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a></li>

    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 1056, Column 146: general entity "po" not defined and no default entity
    …://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a></li>

    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 1056, Column 148: reference not terminated by REFC delimiter
    …://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a></li>

    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 1056, Column 148: reference to external entity in attribute value
    …://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a></li>

    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 1056, Column 148: reference to entity "po" for which no system identifier could be generated
    …://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a></li>

    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 1056, Column 145: entity was defined here
    …://www.thaichix.com/index.php?p=0&sp=1&po=5" target="_blank">Thai Chix</a></li…
  • Warning Line 1058, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=934130-0000&PA=1703537" target="_blank">The Black Alle…

    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 1058, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=934130-0000&PA=1703537" target="_blank">The Black Alle…

    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 1058, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=934130-0000&PA=1703537" target="_blank">The Black Alle…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1062, Column 89: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=924105-0011&PA=2132553&HTML=http://www.xlasians.com/tc…

    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 1062, Column 89: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=924105-0011&PA=2132553&HTML=http://www.xlasians.com/tc…

    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 1062, Column 89: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=924105-0011&PA=2132553&HTML=http://www.xlasians.com/tc…

    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 63, Column 85: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=945220-0000&PA=2372389' target="_blank"><img src='h…
  • Warning Line 1062, Column 102: reference not terminated by REFC delimiter
    …cks.cgi?CA=924105-0011&PA=2132553&HTML=http://www.xlasians.com/tc/index.html" …

    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 1062, Column 102: reference to external entity in attribute value
    …cks.cgi?CA=924105-0011&PA=2132553&HTML=http://www.xlasians.com/tc/index.html" …

    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 1062, Column 102: reference to entity "HTML" for which no system identifier could be generated
    …cks.cgi?CA=924105-0011&PA=2132553&HTML=http://www.xlasians.com/tc/index.html" …

    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 308, Column 101: entity was defined here
    …n/clicks.cgi?CA=915068-0000&PA=1394711&HTML=http://creampiethais.com/z_tour/' …
  • Warning Line 1070, Column 92: reference not terminated by REFC delimiter
    …display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=5&ba…

    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 1070, Column 92: reference to external entity in attribute value
    …display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=5&ba…

    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 1070, Column 92: reference to entity "aff_code" for which no system identifier could be generated
    …display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=5&ba…

    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 487, Column 83: entity was defined here
    …ebar_tgp/display.php?position=vertical&aff_code=1415427&sites=tgw&width=160&nu…
  • Warning Line 1070, Column 106: reference not terminated by REFC delimiter
    …sition=vertical&aff_code=1415427&sites=tgw&width=160&number=5&background_color…

    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 1070, Column 106: reference to external entity in attribute value
    …sition=vertical&aff_code=1415427&sites=tgw&width=160&number=5&background_color…

    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 1070, Column 106: reference to entity "sites" for which no system identifier could be generated
    …sition=vertical&aff_code=1415427&sites=tgw&width=160&number=5&background_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.

  • Info Line 487, Column 100: entity was defined here
    …php?position=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background…
  • Warning Line 1070, Column 116: reference not terminated by REFC delimiter
    …tical&aff_code=1415427&sites=tgw&width=160&number=5&background_color=191919&bo…

    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 1070, Column 116: reference to external entity in attribute value
    …tical&aff_code=1415427&sites=tgw&width=160&number=5&background_color=191919&bo…

    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 1070, Column 116: reference to entity "width" for which no system identifier could be generated
    …tical&aff_code=1415427&sites=tgw&width=160&number=5&background_color=191919&bo…

    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 487, Column 110: entity was defined here
    …on=vertical&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191…
  • Warning Line 1070, Column 127: reference not terminated by REFC delimiter
    …ode=1415427&sites=tgw&width=160&number=5&background_color=191919&border_color=…

    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 1070, Column 127: reference to external entity in attribute value
    …ode=1415427&sites=tgw&width=160&number=5&background_color=191919&border_color=…

    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 1070, Column 127: reference to entity "number" for which no system identifier could be generated
    …ode=1415427&sites=tgw&width=160&number=5&background_color=191919&border_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.

  • Info Line 487, Column 120: entity was defined here
    …l&aff_code=1415427&sites=tgw&width=160&number=3&background_color=191919&border…
  • Warning Line 1070, Column 146: reference not terminated by REFC delimiter
    …gw&width=160&number=5&background_color=191919&border_color=191919&text_color=F…

    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 1070, Column 146: reference to external entity in attribute value
    …gw&width=160&number=5&background_color=191919&border_color=191919&text_color=F…

    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 1070, Column 146: reference to entity "background_color" for which no system identifier could be generated
    …gw&width=160&number=5&background_color=191919&border_color=191919&text_color=F…

    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 487, Column 129: entity was defined here
    …e=1415427&sites=tgw&width=160&number=3&background_color=191919&border_color=19…
  • Warning Line 1070, Column 166: reference not terminated by REFC delimiter
    …5&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 1070, Column 166: reference to external entity in attribute value
    …5&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 1070, Column 166: reference to entity "border_color" for which no system identifier could be generated
    …5&background_color=191919&border_color=191919&text_color=FFFFFF' type='text/ja…

    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 487, Column 153: entity was defined here
    …h=160&number=3&background_color=191919&border_color=191919&text_color=FFFFFF' …
  • Warning Line 1070, Column 184: reference not terminated by REFC delimiter
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 1070, Column 184: reference to external entity in attribute value
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 1070, Column 184: reference to entity "text_color" for which no system identifier could be generated
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>

    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 487, Column 173: entity was defined here
    …round_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascrip…
  • Error Line 1070, Column 215: document type does not allow element "script" here; assuming missing "li" start-tag
    …und_color=191919&border_color=191919&text_color=FFFFFF' type='text/javascript'>
  • Error Line 1072, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 1070, Column 1: start tag was here
    <script src='http://asianbutterflies.com/sidebar_tgp/display.php?position=verti…

Visitor Analysis

Daily Visitor
  • 210 visits