asyouporn.com

Network: hq-xnxx xnudegirls.com Erotica hq xvideos Porn Videos, Gratis Porn, Sex Tube @ As You Porn This website, which is not youporn but offers the same amount of free porn, will be sure ...

This data was last updated from 21-10-2014 04:07:07  (update).

Overview Info



  • Domain Name
    asyouporn.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    216.172.57.179
  • Page Size
    134.7 KB
  • Images
    0 GIF, 245 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 240 0 0 0

Website Meta Analysis



  • Title
    Free Erotic Movies, Sex Videos, Porn Movs @ As You Porn
  • Meta Keyword
  • Meta Description
    Network: hq-xnxx xnudegirls.com Erotica hq xvideos Porn Videos, Gratis Porn, Sex Tube @ As You Porn This website, which is not youporn but offers the same amount of free porn, will be sure to keep you busy and entertained whenever you are feeling ...

Technical Analysis



  • Webserver
    nginx/1.2.6
  • Ip Address
    216.172.57.179
  • Domain Age
    1 Years, 3 Months, 16 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.6
  • date: Tue, 21 Oct 2014 16:07:07 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.4.24
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for asyouporn.com

DNS Analysis


DNS servers
ns1.asyouporn.com [109.206.172.213]
ns2.asyouporn.com [109.206.172.213]


DNS Records

Answer records
asyouporn.com SOA
server: ns1.asyouporn.com
email: [email protected]
serial: 2012020800
refresh: 28800
retry: 3600
expire: 302400
minimum ttl: 86400
86400s
asyouporn.com NS  ns1.asyouporn.com 86400s
asyouporn.com NS  ns2.asyouporn.com 86400s
asyouporn.com MX
preference: 10
exchange: asyouporn.com
86400s
asyouporn.com A 109.206.172.213 86400s

Authority records

Additional records
ns1.asyouporn.com A 109.206.172.213 86400s
ns2.asyouporn.com A 109.206.172.213 86400s
asyouporn.com A 109.206.172.213 86400s

IP 216.172.57.179 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 99 Errors
  • 148 Warnings
Ratio Text/Html
  • 0.7834587992979708
Message Error
  • Error Line 12, Column 20: required attribute "type" not specified
    <script src="me.js"></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 12, Column 20: document type does not allow element "script" here; assuming missing "body" start-tag
    <script src="me.js"></script>
  • Error Line 14, Column 6: document type does not allow element "body" here
    <body>

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

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

  • Error Line 16, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 26, Column 56: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i/my.php?crc=1410212051460396" border=0 width=0 height=0 style="position: abso…
  • Error Line 26, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …?crc=1410212051460396" border=0 width=0 height=0 style="position: absolute; to…
  • Error Line 26, Column 73: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …212051460396" border=0 width=0 height=0 style="position: absolute; top: -120; …
  • Error Line 26, Column 124: required attribute "alt" not specified
    …6" border=0 width=0 height=0 style="position: absolute; top: -120; left: -120">

    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 26, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …6" border=0 width=0 height=0 style="position: absolute; top: -120; left: -120">

    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 26, Column 1: start tag was here
    <img src="/scj/cgi/my.php?crc=1410212051460396" border=0 width=0 height=0 style…
  • Error Line 39, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="http://hq-xnxx.com">hq-xnxx</a></li>

    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 41, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="http://xnudegirls.com/" title="erotic pics">xnudegirls.com</a></li>

    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 42, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="http://aserotica.com/" title="erotic">Erotica</a></li>

    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 43, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="http://hq-xvideos.com">hq xvideos</a></li>

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

    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 37, Column 6: start tag was here
        	<li class="nobg">
  • Error Line 56, Column 58: there is no attribute "onBlur"
    …ext" class="inp" name="search" onBlur="if (this.value == '') this.value = 'sea…

    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 56, Column 116: there is no attribute "onFocus"
    …') this.value = 'search...';" onFocus="if (this.value == 'search...') this.val…

    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 2320, Column 90: cannot generate system identifier for general entity "login"
    …ion.exoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title…

    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 2320, Column 90: general entity "login" not defined and no default entity
    …ion.exoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title…

    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 2320, Column 95: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

    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 2320, Column 95: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

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

    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 2320, Column 89: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_titl…
  • Warning Line 2320, Column 107: cannot generate system identifier for general entity "cat"
    …ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgc…

    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 2320, Column 107: general entity "cat" not defined and no default entity
    …ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgc…

    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 2320, Column 110: reference not terminated by REFC delimiter
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2320, Column 110: reference to external entity in attribute value
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2320, Column 110: reference to entity "cat" for which no system identifier could be generated
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2320, Column 106: entity was defined here
    …/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bg…
  • Warning Line 2320, Column 114: cannot generate system identifier for general entity "search"
    …?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FF…

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

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

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

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

  • Error Line 2320, Column 114: general entity "search" not defined and no default entity
    …?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FF…

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

  • Warning Line 2320, Column 120: reference not terminated by REFC delimiter
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 2320, Column 120: reference to external entity in attribute value
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 2320, Column 120: reference to entity "search" for which no system identifier could be generated
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 2320, Column 113: entity was defined here
    …p?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 2320, Column 122: cannot generate system identifier for general entity "ad_title_color"
    …0x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

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

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

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

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

  • Error Line 2320, Column 122: general entity "ad_title_color" not defined and no default entity
    …0x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

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

  • Warning Line 2320, Column 136: reference not terminated by REFC delimiter
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 2320, Column 136: reference to external entity in attribute value
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 2320, Column 136: reference to entity "ad_title_color" for which no system identifier could be generated
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 2320, Column 121: entity was defined here
    …00x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 2320, Column 144: cannot generate system identifier for general entity "bgcolor"
    …&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

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

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

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

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

  • Error Line 2320, Column 144: general entity "bgcolor" not defined and no default entity
    …&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

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

  • Warning Line 2320, Column 151: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

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

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

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

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

  • Info Line 2320, Column 143: entity was defined here
    …s&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 2320, Column 159: cannot generate system identifier for general entity "border"
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

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

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

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

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

  • Error Line 2320, Column 159: general entity "border" not defined and no default entity
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

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

  • Warning Line 2320, Column 165: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 2320, Column 165: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 2320, Column 165: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 2320, Column 158: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 2320, Column 168: cannot generate system identifier for general entity "border_color"
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

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

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

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

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

  • Error Line 2320, Column 168: general entity "border_color" not defined and no default entity
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

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

  • Warning Line 2320, Column 180: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

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

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

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

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

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

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

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

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

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

  • Error Line 2320, Column 188: general entity "font" not defined and no default entity
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

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

  • Warning Line 2320, Column 192: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 2320, Column 192: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 2320, Column 192: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Info Line 2320, Column 187: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 2320, Column 194: cannot generate system identifier for general entity "block_keywords"
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

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

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

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

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

  • Error Line 2320, Column 194: general entity "block_keywords" not defined and no default entity
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

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

  • Warning Line 2320, Column 208: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 2320, Column 208: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 2320, Column 208: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 2320, Column 193: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 2320, Column 210: cannot generate system identifier for general entity "ad_text_color"
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

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

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

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

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

  • Error Line 2320, Column 210: general entity "ad_text_color" not defined and no default entity
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

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

  • Warning Line 2320, Column 223: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 2320, Column 223: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 2320, Column 223: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 2320, Column 209: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 2320, Column 231: cannot generate system identifier for general entity "ad_durl_color"
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_o…

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

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

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

  • Warning Line 2320, Column 244: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 2320, Column 244: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 2320, Column 230: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 2320, Column 252: cannot generate system identifier for general entity "adult"
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idz…

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

    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 2320, Column 257: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=7…

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

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

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

    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 2320, Column 265: cannot generate system identifier for general entity "text_only"
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&id…

    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 2320, Column 265: general entity "text_only" not defined and no default entity
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&id…

    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 2320, Column 274: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

    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 2320, Column 274: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

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

    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 2320, Column 264: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&i…
  • Warning Line 2320, Column 277: cannot generate system identifier for general entity "show_thumb"
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"…

    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 2320, Column 277: general entity "show_thumb" not defined and no default entity
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"…

    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 2320, Column 287: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 287: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 287: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 276: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361…
  • Warning Line 2320, Column 289: cannot generate system identifier for general entity "idzone"
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 289: general entity "idzone" not defined and no default entity
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 295: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 295: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 295: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 288: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2320, Column 303: cannot generate system identifier for general entity "idsite"
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 303: general entity "idsite" not defined and no default entity
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 309: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 309: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 309: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 302: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2329, Column 95: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

    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 2329, Column 95: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

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

    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 2320, Column 89: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_titl…
  • Warning Line 2329, Column 110: reference not terminated by REFC delimiter
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2329, Column 110: reference to external entity in attribute value
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2329, Column 110: reference to entity "cat" for which no system identifier could be generated
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2320, Column 106: entity was defined here
    …/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bg…
  • Warning Line 2329, Column 120: reference not terminated by REFC delimiter
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 2329, Column 120: reference to external entity in attribute value
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 2329, Column 120: reference to entity "search" for which no system identifier could be generated
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 2320, Column 113: entity was defined here
    …p?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 2329, Column 136: reference not terminated by REFC delimiter
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 2329, Column 136: reference to external entity in attribute value
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 2329, Column 136: reference to entity "ad_title_color" for which no system identifier could be generated
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 2320, Column 121: entity was defined here
    …00x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 2329, Column 151: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

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

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

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

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

  • Info Line 2320, Column 143: entity was defined here
    …s&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 2329, Column 165: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 2329, Column 165: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 2329, Column 165: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 2320, Column 158: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 2329, Column 180: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

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

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

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

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

  • Info Line 2320, Column 167: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 2329, Column 192: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 2329, Column 192: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 2329, Column 192: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Info Line 2320, Column 187: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 2329, Column 208: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 2329, Column 208: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 2329, Column 208: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 2320, Column 193: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 2329, Column 223: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 2329, Column 223: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 2329, Column 223: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 2320, Column 209: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 2329, Column 244: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 2329, Column 244: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 2329, Column 244: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 2320, Column 230: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 2329, Column 257: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=7…

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

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

    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 2320, Column 251: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 2329, Column 263: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&…

    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 2329, Column 274: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

    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 2329, Column 274: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

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

    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 2320, Column 264: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&i…
  • Warning Line 2329, Column 287: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2329, Column 287: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2329, Column 287: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 276: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361…
  • Warning Line 2329, Column 295: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2329, Column 295: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2329, Column 295: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 288: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2329, Column 309: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2329, Column 309: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2329, Column 309: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 302: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2338, Column 95: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

    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 2338, Column 95: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

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

    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 2320, Column 89: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_titl…
  • Warning Line 2338, Column 110: reference not terminated by REFC delimiter
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2338, Column 110: reference to external entity in attribute value
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2338, Column 110: reference to entity "cat" for which no system identifier could be generated
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2320, Column 106: entity was defined here
    …/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bg…
  • Warning Line 2338, Column 120: reference not terminated by REFC delimiter
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 2338, Column 120: reference to external entity in attribute value
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 2338, Column 120: reference to entity "search" for which no system identifier could be generated
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 2320, Column 113: entity was defined here
    …p?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 2338, Column 136: reference not terminated by REFC delimiter
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 2338, Column 136: reference to external entity in attribute value
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 2338, Column 136: reference to entity "ad_title_color" for which no system identifier could be generated
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 2320, Column 121: entity was defined here
    …00x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 2338, Column 151: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

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

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

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

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

  • Info Line 2320, Column 143: entity was defined here
    …s&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 2338, Column 165: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 2338, Column 165: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 2338, Column 165: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 2320, Column 158: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 2338, Column 180: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

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

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

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

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

  • Info Line 2320, Column 167: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 2338, Column 192: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 2338, Column 192: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 2338, Column 192: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Info Line 2320, Column 187: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 2338, Column 208: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 2338, Column 208: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 2338, Column 208: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 2320, Column 193: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 2338, Column 223: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 2338, Column 223: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 2338, Column 223: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 2320, Column 209: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 2338, Column 244: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 2338, Column 244: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 2338, Column 244: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 2320, Column 230: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 2338, Column 257: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=7…

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

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

    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 2320, Column 251: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 2338, Column 263: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&…

    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 2338, Column 274: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

    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 2338, Column 274: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

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

    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 2320, Column 264: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&i…
  • Warning Line 2338, Column 287: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2338, Column 287: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2338, Column 287: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 276: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361…
  • Warning Line 2338, Column 295: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2338, Column 295: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2338, Column 295: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 288: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2338, Column 309: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2338, Column 309: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2338, Column 309: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 302: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2347, Column 95: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

    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 2347, Column 95: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_colo…

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

    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 2320, Column 89: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_titl…
  • Warning Line 2347, Column 110: reference not terminated by REFC delimiter
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2347, Column 110: reference to external entity in attribute value
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2347, Column 110: reference to entity "cat" for which no system identifier could be generated
    ….php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 2320, Column 106: entity was defined here
    …/ads.php?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bg…
  • Warning Line 2347, Column 120: reference not terminated by REFC delimiter
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 2347, Column 120: reference to external entity in attribute value
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 2347, Column 120: reference to entity "search" for which no system identifier could be generated
    …300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 2320, Column 113: entity was defined here
    …p?type=300x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 2347, Column 136: reference not terminated by REFC delimiter
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 2347, Column 136: reference to external entity in attribute value
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 2347, Column 136: reference to entity "ad_title_color" for which no system identifier could be generated
    …wmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 2320, Column 121: entity was defined here
    …00x250&login=bbwmasters&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 2347, Column 151: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

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

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

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

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

  • Info Line 2320, Column 143: entity was defined here
    …s&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 2347, Column 165: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 2347, Column 165: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 2347, Column 165: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 2320, Column 158: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 2347, Column 180: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

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

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

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

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

  • Info Line 2320, Column 167: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 2347, Column 192: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 2347, Column 192: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 2347, Column 192: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Info Line 2320, Column 187: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 2347, Column 208: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 2347, Column 208: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 2347, Column 208: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 2320, Column 193: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 2347, Column 223: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 2347, Column 223: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 2347, Column 223: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 2320, Column 209: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 2347, Column 244: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 2347, Column 244: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 2347, Column 244: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 2320, Column 230: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 2347, Column 257: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=7…

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

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

    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 2320, Column 251: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 2347, Column 263: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&…

    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 2347, Column 274: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

    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 2347, Column 274: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=1953…

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

    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 2320, Column 264: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&i…
  • Warning Line 2347, Column 287: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2347, Column 287: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2347, Column 287: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 276: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361…
  • Warning Line 2347, Column 295: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2347, Column 295: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2347, Column 295: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 288: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Warning Line 2347, Column 309: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2347, Column 309: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2347, Column 309: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></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 2320, Column 302: entity was defined here
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=794401&idsite=195361"></script>
  • Error Line 2362, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 2365, Column 73: required attribute "alt" not specified
    	<a href="/" title="Tube" class="f_logo"><img src="/images/f_logo.png" /></a>

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

    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 12, Column 1: start tag was here
    <script src="me.js"></script>

Visitor Analysis

Daily Visitor
  • 1.633 visits

In Page Analysis