Porn Overdose .com - Your Porn Dose! Fresh free porn videos from best tube sites every day. ...

pornoverdose.com
  • Domain Name
    pornoverdose.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #13639
  • Page Size
    87 KB
  • Ip Address
    204.155.146.167
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 120 JPG, 7 PNG

Website Meta Analysis

  • Title
    Porn Overdose - Best Porn Tube
  • Meta Keyword
    porn, porn overdose, porn tube, porntube
  • Meta Description
    Porn Overdose .com - Your Porn Dose! Fresh free porn videos from best tube sites every day.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    204.155.146.167
  • Domain Age
    1 Years, 8 Months, 8 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Mon, 09 Sep 2013 00:54:57 GMT
  • content-type: text/html
  • connection: keep-alive
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for pornoverdose.com

DNS Analysis


DNS servers
ns1.pornoverdose.com [174.36.55.74]
ns2.pornoverdose.com [67.213.221.156]


DNS Records

Answer records
pornoverdose.com TXT v=spf1 a mx ip4:174.36.55.74 ~all 14400s
pornoverdose.com MX
preference: 10
exchange: mail.pornoverdose.com
14400s
pornoverdose.com A 174.36.55.74 14400s
pornoverdose.com SOA
server: ns1.pornoverdose.com
email: hostmaster@pornoverdose.com
serial: 2012032000
refresh: 14400
retry: 3600
expire: 1209600
minimum ttl: 86400
14400s
pornoverdose.com NS  ns2.pornoverdose.com 14400s
pornoverdose.com NS  ns1.pornoverdose.com 14400s

Authority records

Additional records
mail.pornoverdose.com A 174.36.55.74 14400s
ns1.pornoverdose.com A 174.36.55.74 14400s
ns2.pornoverdose.com A 67.213.221.156 14400s

IP 204.155.146.167 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 403 Errors
  • 265 Warnings
Ratio Text/Html
  • 0.7581815937980322
Message Error
  • Error Line 50, Column 53: document type does not allow element "script" here; assuming missing "body" start-tag
    <script type="text/javascript" language="javascript">
  • Error Line 55, 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).

  • Warning Line 77, Column 49: cannot generate system identifier for general entity "l"
    … <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank…

    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 77, Column 49: general entity "l" not defined and no default entity
    … <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank…

    This is usually a cascading error caused by 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 77, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 77, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank"…

    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 77, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 78, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=53&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 78, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=53&l=top_top" rel="nofollow" target="_blank"…

    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 78, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=53&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 79, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=55&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 79, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=55&l=top_top" rel="nofollow" target="_blank"…

    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 79, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=55&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 80, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=50&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 80, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=50&l=top_top" rel="nofollow" target="_blank"…

    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 80, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=50&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 81, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=54&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 81, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=54&l=top_top" rel="nofollow" target="_blank"…

    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 81, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=54&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 84, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=47&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 84, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=47&l=top_top" rel="nofollow" target="_blank"…

    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 84, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=47&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 85, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=64&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 85, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=64&l=top_top" rel="nofollow" target="_blank"…

    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 85, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=64&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 86, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=27&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 86, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=27&l=top_top" rel="nofollow" target="_blank"…

    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 86, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=27&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 87, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=29&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 87, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=29&l=top_top" rel="nofollow" target="_blank"…

    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 87, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=29&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 88, Column 50: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=31&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 88, Column 50: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=31&l=top_top" rel="nofollow" target="_blank"…

    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 88, Column 50: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=31&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Error Line 116, Column 25: document type does not allow element "div" here; assuming missing "li" start-tag
       <div class="clearfix"></div>  
  • Error Line 117, Column 7: end tag for "li" omitted, but OMITTAG NO was specified
      </ul>

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

  • Info Line 116, Column 4: start tag was here
       <div class="clearfix"></div>  
  • Warning Line 771, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=87&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 771, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=87&l=top_top" rel="nofollow" target="_blank"…

    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 771, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=87&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 772, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=84&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 772, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=84&l=top_top" rel="nofollow" target="_blank"…

    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 772, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=84&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 773, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=85&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 773, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=85&l=top_top" rel="nofollow" target="_blank"…

    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 773, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=85&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 774, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=88&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 774, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=88&l=top_top" rel="nofollow" target="_blank"…

    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 774, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=88&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 775, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=64&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 775, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=64&l=top_top" rel="nofollow" target="_blank"…

    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 775, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=64&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 776, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=29&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 776, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=29&l=top_top" rel="nofollow" target="_blank"…

    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 776, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=29&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 777, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=33&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 777, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=33&l=top_top" rel="nofollow" target="_blank"…

    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 777, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=33&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 778, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=17&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 778, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=17&l=top_top" rel="nofollow" target="_blank"…

    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 778, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=17&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 779, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=46&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 779, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=46&l=top_top" rel="nofollow" target="_blank"…

    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 779, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=46&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 780, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=11&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 780, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=11&l=top_top" rel="nofollow" target="_blank"…

    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 780, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=11&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 781, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=37&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 781, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=37&l=top_top" rel="nofollow" target="_blank"…

    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 781, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=37&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 782, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=35&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 782, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=35&l=top_top" rel="nofollow" target="_blank"…

    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 782, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=35&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 785, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=31&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 785, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=31&l=top_top" rel="nofollow" target="_blank"…

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

  • Error Line 785, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=31&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 786, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=59&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 786, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=59&l=top_top" rel="nofollow" target="_blank"…

    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 786, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=59&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 787, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=54&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 787, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=54&l=top_top" rel="nofollow" target="_blank"…

    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 787, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=54&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 788, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=86&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 788, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=86&l=top_top" rel="nofollow" target="_blank"…

    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 788, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=86&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 789, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=34&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 789, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=34&l=top_top" rel="nofollow" target="_blank"…

    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 789, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=34&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 790, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=57&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 790, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=57&l=top_top" rel="nofollow" target="_blank"…

    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 790, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=57&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 791, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=36&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 791, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=36&l=top_top" rel="nofollow" target="_blank"…

    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 791, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=36&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 792, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=14&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 792, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=14&l=top_top" rel="nofollow" target="_blank"…

    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 792, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=14&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 793, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=23&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 793, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=23&l=top_top" rel="nofollow" target="_blank"…

    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 793, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=23&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 794, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=13&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 794, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=13&l=top_top" rel="nofollow" target="_blank"…

    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 794, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=13&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 795, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=24&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 795, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=24&l=top_top" rel="nofollow" target="_blank"…

    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 795, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=24&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 796, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=58&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 796, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=58&l=top_top" rel="nofollow" target="_blank"…

    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 796, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=58&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 799, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=28&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 799, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=28&l=top_top" rel="nofollow" target="_blank"…

    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 799, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=28&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 800, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=47&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 800, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=47&l=top_top" rel="nofollow" target="_blank"…

    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 800, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=47&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 801, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=30&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 801, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=30&l=top_top" rel="nofollow" target="_blank"…

    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 801, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=30&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 802, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=60&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 802, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=60&l=top_top" rel="nofollow" target="_blank"…

    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 802, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=60&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 803, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=71&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 803, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=71&l=top_top" rel="nofollow" target="_blank"…

    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 803, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=71&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 804, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=27&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 804, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=27&l=top_top" rel="nofollow" target="_blank"…

    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 804, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=27&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 805, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=65&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 805, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=65&l=top_top" rel="nofollow" target="_blank"…

    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 805, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=65&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 806, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=25&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 806, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=25&l=top_top" rel="nofollow" target="_blank"…

    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 806, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=25&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 807, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=50&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 807, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=50&l=top_top" rel="nofollow" target="_blank"…

    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 807, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=50&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 808, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=73&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 808, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=73&l=top_top" rel="nofollow" target="_blank"…

    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 808, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=73&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 809, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=81&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 809, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=81&l=top_top" rel="nofollow" target="_blank"…

    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 809, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=81&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 810, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 810, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank"…

    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 810, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 813, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=63&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 813, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=63&l=top_top" rel="nofollow" target="_blank"…

    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 813, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=63&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 814, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=80&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 814, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=80&l=top_top" rel="nofollow" target="_blank"…

    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 814, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=80&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 815, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=20&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 815, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=20&l=top_top" rel="nofollow" target="_blank"…

    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 815, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=20&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 816, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=19&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 816, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=19&l=top_top" rel="nofollow" target="_blank"…

    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 816, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=19&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 817, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=55&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 817, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=55&l=top_top" rel="nofollow" target="_blank"…

    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 817, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=55&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 818, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=68&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 818, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=68&l=top_top" rel="nofollow" target="_blank"…

    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 818, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=68&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 819, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=21&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 819, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=21&l=top_top" rel="nofollow" target="_blank"…

    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 819, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=21&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 820, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=18&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 820, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=18&l=top_top" rel="nofollow" target="_blank"…

    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 820, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=18&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 821, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=53&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 821, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=53&l=top_top" rel="nofollow" target="_blank"…

    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 821, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=53&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 822, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=61&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 822, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=61&l=top_top" rel="nofollow" target="_blank"…

    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 822, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=61&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 823, Column 43: reference not terminated by REFC delimiter
    …<a href="/cgi-bin/crtr/out.cgi?id=15&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 823, Column 43: reference to external entity in attribute value
    …<a href="/cgi-bin/crtr/out.cgi?id=15&l=top_top" rel="nofollow" target="_blank"…

    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 823, Column 43: reference to entity "l" for which no system identifier could be generated
    …<a href="/cgi-bin/crtr/out.cgi?id=15&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 824, Column 41: reference not terminated by REFC delimiter
    …. <a href="/cgi-bin/crtr/out.cgi?id=&l=top_top" rel="nofollow" target="_blank"…

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

  • Warning Line 824, Column 41: reference to external entity in attribute value
    …. <a href="/cgi-bin/crtr/out.cgi?id=&l=top_top" rel="nofollow" target="_blank"…

    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 824, Column 41: reference to entity "l" for which no system identifier could be generated
    …. <a href="/cgi-bin/crtr/out.cgi?id=&l=top_top" rel="nofollow" target="_blank"…

    This is usually a cascading error caused by 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 77, Column 48: entity was defined here
    …. <a href="/cgi-bin/crtr/out.cgi?id=52&l=top_top" rel="nofollow" target="_blan…
  • Warning Line 833, Column 107: cannot generate system identifier for general entity "login"
    …ion.exoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_col…

    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 833, Column 107: general entity "login" not defined and no default entity
    …ion.exoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_col…

    This is usually a cascading error caused by 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 833, Column 112: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=00…

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

  • Warning Line 833, Column 112: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=00…

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

    This is usually a cascading error caused by 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 833, Column 106: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_co…
  • Warning Line 833, Column 121: cannot generate system identifier for general entity "cat"
    …om/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgco…

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

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

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

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

  • Error Line 833, Column 121: general entity "cat" not defined and no default entity
    …om/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgco…

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

  • Warning Line 833, Column 124: reference not terminated by REFC delimiter
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 833, Column 124: reference to external entity in attribute value
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 833, Column 124: reference to entity "cat" for which no system identifier could be generated
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 833, Column 120: entity was defined here
    …com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 833, Column 127: cannot generate system identifier for general entity "search"
    ….php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

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

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

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

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

  • Error Line 833, Column 127: general entity "search" not defined and no default entity
    ….php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

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

  • Warning Line 833, Column 133: reference not terminated by REFC delimiter
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 833, Column 133: reference to external entity in attribute value
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 833, Column 133: reference to entity "search" for which no system identifier could be generated
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 833, Column 126: entity was defined here
    …s.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 833, Column 135: cannot generate system identifier for general entity "ad_title_color"
    …e=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

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

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

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

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

  • Error Line 833, Column 135: general entity "ad_title_color" not defined and no default entity
    …e=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

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

  • Warning Line 833, Column 149: reference not terminated by REFC delimiter
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 833, Column 149: reference to external entity in attribute value
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 833, Column 149: reference to entity "ad_title_color" for which no system identifier could be generated
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 833, Column 134: entity was defined here
    …pe=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 833, Column 157: cannot generate system identifier for general entity "bgcolor"
    …t&cat=2&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 833, Column 157: general entity "bgcolor" not defined and no default entity
    …t&cat=2&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 833, Column 164: 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 833, Column 164: 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 833, Column 164: 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 833, Column 156: entity was defined here
    …et&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 833, Column 172: 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 833, Column 172: 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 833, Column 178: 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 833, Column 178: 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 833, Column 178: 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 833, Column 171: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 833, Column 181: 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 833, Column 181: 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 833, Column 193: 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 833, Column 193: 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 833, Column 193: 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 833, Column 180: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 833, Column 201: 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 833, Column 201: 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 833, Column 205: 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 833, Column 205: 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 833, Column 205: 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 833, Column 200: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 833, Column 207: 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 833, Column 207: 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 833, Column 221: 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 833, Column 221: 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 833, Column 221: 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 833, Column 206: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 833, Column 223: 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 833, Column 223: 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 833, Column 236: 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 833, Column 236: 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 833, Column 236: 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 833, Column 222: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 833, Column 244: 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 833, Column 244: 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 833, Column 257: 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 833, Column 257: 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 833, Column 257: 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 833, Column 243: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 833, Column 265: 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 833, Column 265: 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 833, Column 270: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=2…

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

  • Warning Line 833, Column 270: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=2…

    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 833, Column 270: 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=2…

    This is usually a cascading error caused by 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 833, Column 264: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 833, Column 276: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&…

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

  • Warning Line 833, Column 278: cannot generate system identifier for general entity "text_only"
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&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 833, Column 278: general entity "text_only" not defined and no default entity
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&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 833, Column 287: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=1223…

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

  • Warning Line 833, Column 287: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=1223…

    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 833, Column 287: 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=258302&idsite=1223…

    This is usually a cascading error caused by 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 833, Column 277: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&i…
  • Warning Line 833, Column 290: cannot generate system identifier for general entity "show_thumb"
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"…

    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 833, Column 290: general entity "show_thumb" not defined and no default entity
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"…

    This is usually a cascading error caused by 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 833, Column 300: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></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 833, Column 300: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></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 833, Column 300: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></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 833, Column 289: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308…
  • Warning Line 833, Column 302: cannot generate system identifier for general entity "idzone"
    …&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></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 833, Column 302: general entity "idzone" not defined and no default entity
    …&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></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 833, Column 308: reference not terminated by REFC delimiter
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Warning Line 833, Column 308: reference to external entity in attribute value
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Error Line 833, Column 308: reference to entity "idzone" for which no system identifier could be generated
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Info Line 833, Column 301: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script><…
  • Warning Line 833, Column 316: cannot generate system identifier for general entity "idsite"
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

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

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

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

  • Error Line 833, Column 316: general entity "idsite" not defined and no default entity
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Warning Line 833, Column 322: reference not terminated by REFC delimiter
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Warning Line 833, Column 322: reference to external entity in attribute value
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Error Line 833, Column 322: reference to entity "idsite" for which no system identifier could be generated
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>

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

  • Info Line 833, Column 315: entity was defined here
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>
  • Warning Line 834, Column 112: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=00…

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

  • Warning Line 834, Column 112: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=00…

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

    This is usually a cascading error caused by 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 833, Column 106: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_co…
  • Warning Line 834, Column 124: reference not terminated by REFC delimiter
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 834, Column 124: reference to external entity in attribute value
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 834, Column 124: reference to entity "cat" for which no system identifier could be generated
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 833, Column 120: entity was defined here
    …com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 834, Column 133: reference not terminated by REFC delimiter
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 834, Column 133: reference to external entity in attribute value
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 834, Column 133: reference to entity "search" for which no system identifier could be generated
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 833, Column 126: entity was defined here
    …s.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 834, Column 149: reference not terminated by REFC delimiter
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 834, Column 149: reference to external entity in attribute value
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 834, Column 149: reference to entity "ad_title_color" for which no system identifier could be generated
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 833, Column 134: entity was defined here
    …pe=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 834, Column 164: 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 834, Column 164: 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 834, Column 164: 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 833, Column 156: entity was defined here
    …et&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 834, Column 178: 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 834, Column 178: 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 834, Column 178: 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 833, Column 171: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 834, Column 193: 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 834, Column 193: 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 834, Column 193: 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 833, Column 180: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 834, Column 205: 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 834, Column 205: 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 834, Column 205: 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 833, Column 200: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 834, Column 221: 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 834, Column 221: 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 834, Column 221: 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 833, Column 206: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 834, Column 236: 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 834, Column 236: 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 834, Column 236: 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 833, Column 222: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 834, Column 257: 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 834, Column 257: 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 834, Column 257: 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 833, Column 243: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 834, Column 270: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=2…

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

  • Warning Line 834, Column 270: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=2…

    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 834, Column 270: 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=2…

    This is usually a cascading error caused by 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 833, Column 264: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 834, Column 276: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258304&…

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

  • Warning Line 834, Column 287: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=1223…

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

  • Warning Line 834, Column 287: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=1223…

    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 834, Column 287: 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=258304&idsite=1223…

    This is usually a cascading error caused by 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 833, Column 277: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&i…
  • Warning Line 834, Column 300: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></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 834, Column 300: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></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 834, Column 300: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></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 833, Column 289: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308…
  • Warning Line 834, Column 308: reference not terminated by REFC delimiter
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></script></div>

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

  • Warning Line 834, Column 308: reference to external entity in attribute value
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></script></div>

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

  • Error Line 834, Column 308: reference to entity "idzone" for which no system identifier could be generated
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></script></div>

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

  • Info Line 833, Column 301: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script><…
  • Warning Line 834, Column 322: reference not terminated by REFC delimiter
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></script></div>

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

  • Warning Line 834, Column 322: reference to external entity in attribute value
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></script></div>

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

  • Error Line 834, Column 322: reference to entity "idsite" for which no system identifier could be generated
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258304&idsite=122308"></script></div>

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

  • Info Line 833, Column 315: entity was defined here
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>
  • Warning Line 835, Column 112: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=00…

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

  • Warning Line 835, Column 112: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=00…

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

    This is usually a cascading error caused by 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 833, Column 106: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_co…
  • Warning Line 835, Column 124: reference not terminated by REFC delimiter
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 835, Column 124: reference to external entity in attribute value
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 835, Column 124: reference to entity "cat" for which no system identifier could be generated
    …ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 833, Column 120: entity was defined here
    …com/ads.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 835, Column 133: reference not terminated by REFC delimiter
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 835, Column 133: reference to external entity in attribute value
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 835, Column 133: reference to entity "search" for which no system identifier could be generated
    …ype=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 833, Column 126: entity was defined here
    …s.php?type=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 835, Column 149: reference not terminated by REFC delimiter
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 835, Column 149: reference to external entity in attribute value
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 835, Column 149: reference to entity "ad_title_color" for which no system identifier could be generated
    …n=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 833, Column 134: entity was defined here
    …pe=300x250&login=1movnet&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 835, Column 164: 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 835, Column 164: 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 835, Column 164: 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 833, Column 156: entity was defined here
    …et&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 835, Column 178: 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 835, Column 178: 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 835, Column 178: 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 833, Column 171: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 835, Column 193: 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 835, Column 193: 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 835, Column 193: 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 833, Column 180: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 835, Column 205: 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 835, Column 205: 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 835, Column 205: 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 833, Column 200: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 835, Column 221: 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 835, Column 221: 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 835, Column 221: 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 833, Column 206: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 835, Column 236: 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 835, Column 236: 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 835, Column 236: 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 833, Column 222: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 835, Column 257: 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 835, Column 257: 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 835, Column 257: 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 833, Column 243: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 835, Column 270: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=2…

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

  • Warning Line 835, Column 270: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=2…

    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 835, Column 270: 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=2…

    This is usually a cascading error caused by 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 833, Column 264: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 835, Column 276: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258308&…

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

  • Warning Line 835, Column 287: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=1223…

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

  • Warning Line 835, Column 287: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=1223…

    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 835, Column 287: 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=258308&idsite=1223…

    This is usually a cascading error caused by 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 833, Column 277: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&i…
  • Warning Line 835, Column 300: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></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 835, Column 300: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></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 835, Column 300: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></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 833, Column 289: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308…
  • Warning Line 835, Column 308: reference not terminated by REFC delimiter
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></script></div>

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

  • Warning Line 835, Column 308: reference to external entity in attribute value
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></script></div>

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

  • Error Line 835, Column 308: reference to entity "idzone" for which no system identifier could be generated
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></script></div>

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

  • Info Line 833, Column 301: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script><…
  • Warning Line 835, Column 322: reference not terminated by REFC delimiter
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></script></div>

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

  • Warning Line 835, Column 322: reference to external entity in attribute value
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></script></div>

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

  • Error Line 835, Column 322: reference to entity "idsite" for which no system identifier could be generated
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258308&idsite=122308"></script></div>

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

  • Info Line 833, Column 315: entity was defined here
    …ult=0&sub=&text_only=0&show_thumb=&idzone=258302&idsite=122308"></script></div>
  • Error Line 865, 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 50, Column 1: start tag was here
    <script type="text/javascript" language="javascript">

Visitor Analysis

Daily Visitor
  • 16.100 visits