GetItOn.com is a unique adult dating compatibility matching site. Browse our sex classifieds and find your ideal match for sex dating on GetitOn. ...

getiton.com
  • Domain Name
    getiton.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #8405
  • Page Size
    285.1 KB
  • Ip Address
    208.88.182.181
  • Heading
    H1: 2, H2: 0, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    3 GIF, 8 JPG, 5 PNG

Website Meta Analysis

  • Title
    Sex Classifieds & Adult Dating on GetItOn
  • Meta Keyword
    GetItOn, Sex Classifieds, Adult Dating, Sex Dating, Sex Personals, Adult Personals, Sex Web Cam Chats, Adult Hookups, Sex Hookups, Hookups, Swingers, Swingers Personals, Hookups
  • Meta Description
    GetItOn.com is a unique adult dating compatibility matching site. Browse our sex classifieds and find your ideal match for sex dating on GetitOn.

Technical Analysis

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

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

HTML Analysis

  • date: Fri, 16 Aug 2013 22:54:33 GMT
  • server: Apache
  • etag: TESTBED
  • p3p: CP="DSP LAW"
  • x-apacheserver: ii103-11.friendfinderinc.com
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 56765
  • content-type: text/html;charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for getiton.com

IP 208.88.182.181 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Sunnyvale
  • Continent Code
    94089
  • Latitude
    408
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 208.88.182.181"
    #
    # Use "?" to get help.
    #

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

    NetRange: 208.88.176.0 - 208.88.183.255
    CIDR: 208.88.176.0/21
    OriginAS: AS32527
    NetName: VARIOUS
    NetHandle: NET-208-88-176-0-1
    Parent: NET-208-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2008-03-24
    Updated: 2012-06-06
    Ref: http://whois.arin.net/rest/net/NET-208-88-176-0-1

    OrgName: FriendFinder Networks Inc
    OrgId: FRIEN-11
    Address: 220 Humboldt ct
    City: Sunnyvale
    StateProv: CA
    PostalCode: 94089
    Country: US
    RegDate: 2008-07-18
    Updated: 2012-08-26
    Ref: http://whois.arin.net/rest/org/FRIEN-11

    OrgAbuseHandle: OPERA393-ARIN
    OrgAbuseName: Operations
    OrgAbusePhone: +1-408-745-5000
    OrgAbuseEmail: ff_ops@ffn.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/OPERA393-ARIN

    OrgTechHandle: CWU4-ARIN
    OrgTechName: WU, CATHERINE
    OrgTechPhone: +1-408-745-5598
    OrgTechEmail: cwu@ffn.com
    OrgTechRef: http://whois.arin.net/rest/poc/CWU4-ARIN

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 296 Errors
  • 343 Warnings
Ratio Text/Html
  • 0.09325107983407721
Message Error
  • Warning Line 18, Column 24: character "&" is the first character of a delimiter but occurred as data
    <title>Sex Classifieds & Adult Dating on GetItOn</title>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2281, Column 15: character "&" is the first character of a delimiter but occurred as data
    /* PAGE WIDTH & COLUMN WIDTH OVERRIDES */

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2300, Column 15: character "&" is the first character of a delimiter but occurred as data
    /* PAGINATION & SORT TAGS */

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2412, Column 13: character "&" is the first character of a delimiter but occurred as data
    /* USERNAME & SAVED SEARCH*/

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 2831, Column 7: required attribute "type" not specified
    <style> 

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

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

  • Error Line 3555, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 4175, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 4187, Column 7: required attribute "type" not specified
    <style>.hide_last_element :last-child { display: none;} </style>

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

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

  • Error Line 4188, Column 7: required attribute "type" not specified
    <style>/* bg_screening */

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

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

  • Error Line 4192, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 4209, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 4209, Column 30: document type does not allow element "script" here; assuming missing "body" start-tag
    <script language="javascript">
  • Warning Line 4211, Column 28: character "&" is the first character of a delimiter but occurred as data
      if(window.XMLHttpRequest && window.ActiveXObject){

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 4282, Column 62: an attribute specification must start with a name or name token
    …"text/javascript">document.write('<scr' + 'ipt type="text/javascript" src="' +…

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

  • Error Line 4282, Column 62: element "scr" undefined
    …"text/javascript">document.write('<scr' + 'ipt type="text/javascript" src="' +…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4282, Column 182: delimiter "'" invalid: only S separators and TAGC allowed here
    …//www.medleyads.com/confirm18.js?site=getiton') + '"></scr' + 'ipt>');</script>
  • Warning Line 4298, Column 21: character "&" is the first character of a delimiter but occurred as data
        if (user_erotic && rating == 1) {

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4326, Column 33: cannot generate system identifier for general entity "who"
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

    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 4326, Column 33: general entity "who" not defined and no default entity
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

    This is usually a cascading error caused by 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 4326, Column 36: reference not terminated by REFC delimiter
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Error Line 4326, Column 36: reference to entity "who" for which no system identifier could be generated
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4326, Column 168: cannot generate system identifier for general entity "is_flash"
    …Jz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + u…

    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 4326, Column 168: general entity "is_flash" not defined and no default entity
    …Jz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + u…

    This is usually a cascading error caused by 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 4326, Column 176: reference not terminated by REFC delimiter
    …wqUjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + …

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

  • Error Line 4326, Column 176: reference to entity "is_flash" for which no system identifier could be generated
    …wqUjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + …

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

  • Info Line 4326, Column 167: entity was defined here
    …JJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + …
  • Warning Line 4326, Column 179: cannot generate system identifier for general entity "action"
    …jxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&v…

    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 4326, Column 179: general entity "action" not defined and no default entity
    …jxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&v…

    This is usually a cascading error caused by 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 4326, Column 185: reference not terminated by REFC delimiter
    …C/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&videonu…

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

  • Error Line 4326, Column 185: reference to entity "action" for which no system identifier could be generated
    …C/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&videonu…

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

  • Info Line 4326, Column 178: entity was defined here
    …UjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&…
  • Warning Line 4326, Column 196: cannot generate system identifier for general entity "userid"
    …0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&videonum=" + video…

    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 4326, Column 196: general entity "userid" not defined and no default entity
    …0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&videonum=" + video…

    This is usually a cascading error caused by 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 4326, Column 202: reference not terminated by REFC delimiter
    …4kE&is_flash=1&action=view" + "&userid=" + userid + "&videonum=" + videonum + …

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

  • Error Line 4326, Column 202: reference to entity "userid" for which no system identifier could be generated
    …4kE&is_flash=1&action=view" + "&userid=" + userid + "&videonum=" + videonum + …

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

  • Info Line 4326, Column 195: entity was defined here
    …v0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&videonum=" + vide…
  • Warning Line 4326, Column 218: cannot generate system identifier for general entity "videonum"
    …ction=view" + "&userid=" + userid + "&videonum=" + videonum + "&realvideonum="…

    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 4326, Column 218: general entity "videonum" not defined and no default entity
    …ction=view" + "&userid=" + userid + "&videonum=" + videonum + "&realvideonum="…

    This is usually a cascading error caused by 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 4326, Column 226: reference not terminated by REFC delimiter
    …ew" + "&userid=" + userid + "&videonum=" + videonum + "&realvideonum=" + realv…

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

  • Error Line 4326, Column 226: reference to entity "videonum" for which no system identifier could be generated
    …ew" + "&userid=" + userid + "&videonum=" + videonum + "&realvideonum=" + realv…

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

  • Info Line 4326, Column 217: entity was defined here
    …action=view" + "&userid=" + userid + "&videonum=" + videonum + "&realvideonum=…
  • Warning Line 4326, Column 244: cannot generate system identifier for general entity "realvideonum"
    … userid + "&videonum=" + videonum + "&realvideonum=" + realvideonum + "&stream…

    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 4326, Column 244: general entity "realvideonum" not defined and no default entity
    … userid + "&videonum=" + videonum + "&realvideonum=" + realvideonum + "&stream…

    This is usually a cascading error caused by 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 4326, Column 256: reference not terminated by REFC delimiter
    …videonum=" + videonum + "&realvideonum=" + realvideonum + "&streamtype=" + str…

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

  • Error Line 4326, Column 256: reference to entity "realvideonum" for which no system identifier could be generated
    …videonum=" + videonum + "&realvideonum=" + realvideonum + "&streamtype=" + str…

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

  • Info Line 4326, Column 243: entity was defined here
    …+ userid + "&videonum=" + videonum + "&realvideonum=" + realvideonum + "&strea…
  • Warning Line 4326, Column 278: cannot generate system identifier for general entity "streamtype"
    …+ "&realvideonum=" + realvideonum + "&streamtype=" + streamtype + "&user_handl…

    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 4326, Column 278: general entity "streamtype" not defined and no default entity
    …+ "&realvideonum=" + realvideonum + "&streamtype=" + streamtype + "&user_handl…

    This is usually a cascading error caused by 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 4326, Column 288: reference not terminated by REFC delimiter
    …deonum=" + realvideonum + "&streamtype=" + streamtype + "&user_handle=" + hand…

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

  • Error Line 4326, Column 288: reference to entity "streamtype" for which no system identifier could be generated
    …deonum=" + realvideonum + "&streamtype=" + streamtype + "&user_handle=" + hand…

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

  • Info Line 4326, Column 277: entity was defined here
    … + "&realvideonum=" + realvideonum + "&streamtype=" + streamtype + "&user_hand…
  • Warning Line 4326, Column 308: cannot generate system identifier for general entity "user_handle"
    …num + "&streamtype=" + streamtype + "&user_handle=" + handle + "&videomode=" +…

    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 4326, Column 308: general entity "user_handle" not defined and no default entity
    …num + "&streamtype=" + streamtype + "&user_handle=" + handle + "&videomode=" +…

    This is usually a cascading error caused by 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 4326, Column 319: reference not terminated by REFC delimiter
    …eamtype=" + streamtype + "&user_handle=" + handle + "&videomode=" + videomode …

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

  • Error Line 4326, Column 319: reference to entity "user_handle" for which no system identifier could be generated
    …eamtype=" + streamtype + "&user_handle=" + handle + "&videomode=" + videomode …

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

  • Info Line 4326, Column 307: entity was defined here
    …onum + "&streamtype=" + streamtype + "&user_handle=" + handle + "&videomode=" …
  • Warning Line 4326, Column 335: cannot generate system identifier for general entity "videomode"
    …amtype + "&user_handle=" + handle + "&videomode=" + videomode + "&stream_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 4326, Column 335: general entity "videomode" not defined and no default entity
    …amtype + "&user_handle=" + handle + "&videomode=" + videomode + "&stream_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 4326, Column 344: reference not terminated by REFC delimiter
    …"&user_handle=" + handle + "&videomode=" + videomode + "&stream_id=" + streams…

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

  • Error Line 4326, Column 344: reference to entity "videomode" for which no system identifier could be generated
    …"&user_handle=" + handle + "&videomode=" + videomode + "&stream_id=" + streams…

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

  • Info Line 4326, Column 334: entity was defined here
    …eamtype + "&user_handle=" + handle + "&videomode=" + videomode + "&stream_id="…
  • Warning Line 4326, Column 363: cannot generate system identifier for general entity "stream_id"
    …andle + "&videomode=" + videomode + "&stream_id=" + streams + "&filename=" + f…

    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 4326, Column 363: general entity "stream_id" not defined and no default entity
    …andle + "&videomode=" + videomode + "&stream_id=" + streams + "&filename=" + f…

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

  • Warning Line 4326, Column 372: reference not terminated by REFC delimiter
    …&videomode=" + videomode + "&stream_id=" + streams + "&filename=" + filename +…

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

  • Error Line 4326, Column 372: reference to entity "stream_id" for which no system identifier could be generated
    …&videomode=" + videomode + "&stream_id=" + streams + "&filename=" + filename +…

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

  • Info Line 4326, Column 362: entity was defined here
    …handle + "&videomode=" + videomode + "&stream_id=" + streams + "&filename=" + …
  • Warning Line 4326, Column 389: cannot generate system identifier for general entity "filename"
    …deomode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + s…

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

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

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

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

  • Error Line 4326, Column 389: general entity "filename" not defined and no default entity
    …deomode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + s…

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

  • Warning Line 4326, Column 397: reference not terminated by REFC delimiter
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;

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

  • Error Line 4326, Column 397: reference to entity "filename" for which no system identifier could be generated
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;

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

  • Info Line 4326, Column 388: entity was defined here
    …ideomode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + …
  • Warning Line 4326, Column 415: cannot generate system identifier for general entity "filesize"
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;

    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 4326, Column 415: general entity "filesize" not defined and no default entity
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;

    This is usually a cascading error caused by 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 4326, Column 423: reference not terminated by REFC delimiter
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;

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

  • Error Line 4326, Column 423: reference to entity "filesize" for which no system identifier could be generated
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;

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

  • Info Line 4326, Column 414: entity was defined here
    …mode + "&stream_id=" + streams + "&filename=" + filename + "&filesize=" + size;
  • Warning Line 4329, Column 200: cannot generate system identifier for general entity "site"
    …Jz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p…

    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 4329, Column 200: general entity "site" not defined and no default entity
    …Jz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p…

    This is usually a cascading error caused by 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 4329, Column 204: reference not terminated by REFC delimiter
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pws…

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

  • Error Line 4329, Column 204: reference to entity "site" for which no system identifier could be generated
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pws…

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

  • Info Line 4329, Column 199: entity was defined here
    …JJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&…
  • Warning Line 4329, Column 213: cannot generate system identifier for general entity "form_only"
    …KkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + us…

    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 4329, Column 213: general entity "form_only" not defined and no default entity
    …KkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + us…

    This is usually a cascading error caused by 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 4329, Column 222: reference not terminated by REFC delimiter
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

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

  • Error Line 4329, Column 222: reference to entity "form_only" for which no system identifier could be generated
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

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

  • Info Line 4329, Column 212: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + u…
  • Warning Line 4329, Column 225: cannot generate system identifier for general entity "origin"
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

    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 4329, Column 225: general entity "origin" not defined and no default entity
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

    This is usually a cascading error caused by 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 4329, Column 231: reference not terminated by REFC delimiter
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

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

  • Error Line 4329, Column 231: reference to entity "origin" for which no system identifier could be generated
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

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

  • Info Line 4329, Column 224: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4329, Column 239: cannot generate system identifier for general entity "p_pwsid"
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

    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 4329, Column 239: general entity "p_pwsid" not defined and no default entity
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

    This is usually a cascading error caused by 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 4329, Column 246: reference not terminated by REFC delimiter
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

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

  • Error Line 4329, Column 246: reference to entity "p_pwsid" for which no system identifier could be generated
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;

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

  • Info Line 4329, Column 238: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4337, Column 42: reference not terminated by REFC delimiter
    …ar popurl=" /p/imc/view_video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4337, Column 42: reference to entity "who" for which no system identifier could be generated
    …ar popurl=" /p/imc/view_video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4337, Column 180: reference not terminated by REFC delimiter
    …YRwqUjxKkJAC/57PSZqKev0VvL244kE&action=view" + "&streamid=" + streamid + "&use…

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

  • Error Line 4337, Column 180: reference to entity "action" for which no system identifier could be generated
    …YRwqUjxKkJAC/57PSZqKev0VvL244kE&action=view" + "&streamid=" + streamid + "&use…

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

  • Info Line 4326, Column 178: entity was defined here
    …UjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&…
  • Warning Line 4337, Column 191: cannot generate system identifier for general entity "streamid"
    …C/57PSZqKev0VvL244kE&action=view" + "&streamid=" + streamid + "&user_handle=" …

    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 4337, Column 191: general entity "streamid" not defined and no default entity
    …C/57PSZqKev0VvL244kE&action=view" + "&streamid=" + streamid + "&user_handle=" …

    This is usually a cascading error caused by 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 4337, Column 199: reference not terminated by REFC delimiter
    …Kev0VvL244kE&action=view" + "&streamid=" + streamid + "&user_handle=" + handle…

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

  • Error Line 4337, Column 199: reference to entity "streamid" for which no system identifier could be generated
    …Kev0VvL244kE&action=view" + "&streamid=" + streamid + "&user_handle=" + handle…

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

  • Info Line 4337, Column 190: entity was defined here
    …AC/57PSZqKev0VvL244kE&action=view" + "&streamid=" + streamid + "&user_handle="…
  • Warning Line 4337, Column 228: reference not terminated by REFC delimiter
    …&streamid=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "…

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

  • Error Line 4337, Column 228: reference to entity "user_handle" for which no system identifier could be generated
    …&streamid=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "…

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

  • Info Line 4326, Column 307: entity was defined here
    …onum + "&streamtype=" + streamtype + "&user_handle=" + handle + "&videomode=" …
  • Warning Line 4337, Column 244: cannot generate system identifier for general entity "user_pwsid"
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

    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 4337, Column 244: general entity "user_pwsid" not defined and no default entity
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

    This is usually a cascading error caused by 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 4337, Column 254: reference not terminated by REFC delimiter
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

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

  • Error Line 4337, Column 254: reference to entity "user_pwsid" for which no system identifier could be generated
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

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

  • Info Line 4337, Column 243: entity was defined here
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";
  • Warning Line 4337, Column 269: cannot generate system identifier for general entity "from"
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

    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 4337, Column 269: general entity "from" not defined and no default entity
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

    This is usually a cascading error caused by 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 4337, Column 273: reference not terminated by REFC delimiter
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

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

  • Error Line 4337, Column 273: reference to entity "from" for which no system identifier could be generated
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";

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

  • Info Line 4337, Column 268: entity was defined here
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";
  • Error Line 4420, Column 67: required attribute "type" not specified
    <script src="http://graphics.pop6.com/images/common/js/blockui.js"></script>

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

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

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

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

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

  • Error Line 4519, Column 61: document type does not allow element "body" here
    <body id="getiton" onload="poptest.blur(); window.focus(); ">

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

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

  • Error Line 4520, Column 10: required attribute "type" not specified
      <script>

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

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

  • Error Line 4662, Column 92: required attribute "type" not specified
    …aphics.pop6.com/css/live_cd/getiton/english/0/infoicon-1318453332.js"></script>

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

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

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

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

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

  • Warning Line 4681, Column 49: reference not terminated by REFC delimiter
    …ow.location.href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4681, Column 49: reference to entity "who" for which no system identifier could be generated
    …ow.location.href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4681, Column 185: reference not terminated by REFC delimiter
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&t…

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

  • Error Line 4681, Column 185: reference to entity "from" for which no system identifier could be generated
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&t…

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

  • Info Line 4337, Column 268: entity was defined here
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";
  • Warning Line 4681, Column 194: cannot generate system identifier for general entity "geonames_reg"
    …KkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="+…

    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 4681, Column 194: general entity "geonames_reg" not defined and no default entity
    …KkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="+…

    This is usually a cascading error caused by 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 4681, Column 206: reference not terminated by REFC delimiter
    …Kev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribu…

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

  • Error Line 4681, Column 206: reference to entity "geonames_reg" for which no system identifier could be generated
    …Kev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribu…

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

  • Info Line 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Warning Line 4681, Column 215: reference not terminated by REFC delimiter
    …4kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid…

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

  • Error Line 4681, Column 215: reference to entity "origin" for which no system identifier could be generated
    …4kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid…

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

  • Info Line 4329, Column 224: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4681, Column 224: cannot generate system identifier for general entity "topwsid"
    …hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&show…

    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 4681, Column 224: general entity "topwsid" not defined and no default entity
    …hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&show…

    This is usually a cascading error caused by 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 4681, Column 231: reference not terminated by REFC delimiter
    …&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid=…

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

  • Error Line 4681, Column 231: reference to entity "topwsid" for which no system identifier could be generated
    …&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid=…

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

  • Info Line 4681, Column 223: entity was defined here
    …=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&sho…
  • Warning Line 4681, Column 260: cannot generate system identifier for general entity "show_pwsid"
    …otlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')

    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 4681, Column 260: general entity "show_pwsid" not defined and no default entity
    …otlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')

    This is usually a cascading error caused by 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 4681, Column 270: reference not terminated by REFC delimiter
    …otlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')

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

  • Error Line 4681, Column 270: reference to entity "show_pwsid" for which no system identifier could be generated
    …otlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')

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

  • Info Line 4681, Column 259: entity was defined here
    …otlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')
  • Warning Line 4685, Column 35: reference not terminated by REFC delimiter
        var url = "/p/hotlist.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbxM…

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

  • Error Line 4685, Column 35: reference to entity "who" for which no system identifier could be generated
        var url = "/p/hotlist.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbxM…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4686, Column 46: character "&" is the first character of a delimiter but occurred as data
    …(a.getElementsByTagName('IMG').length && a.getElementsByTagName('IMG')[0].clas…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4686, Column 47: character "&" is the first character of a delimiter but occurred as data
    …a.getElementsByTagName('IMG').length && a.getElementsByTagName('IMG')[0].class…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4688, Column 53: character "&" is the first character of a delimiter but occurred as data
    …(a.getElementsByTagName('IMG').length && a.getElementsByTagName('IMG')[0].clas…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4688, Column 54: character "&" is the first character of a delimiter but occurred as data
    …a.getElementsByTagName('IMG').length && a.getElementsByTagName('IMG')[0].class…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4695, Column 22: character "&" is the first character of a delimiter but occurred as data
        if (self.members && members[to_pwsid]) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4695, Column 23: character "&" is the first character of a delimiter but occurred as data
        if (self.members && members[to_pwsid]) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4698, Column 22: character "&" is the first character of a delimiter but occurred as data
        if (self.profile && profile.getElementsByTagName('pwsid').length && profile…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4698, Column 23: character "&" is the first character of a delimiter but occurred as data
        if (self.profile && profile.getElementsByTagName('pwsid').length && profile…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4698, Column 70: character "&" is the first character of a delimiter but occurred as data
    ….getElementsByTagName('pwsid').length && profile.getElementsByTagName('pwsid')…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4698, Column 71: character "&" is the first character of a delimiter but occurred as data
    …getElementsByTagName('pwsid').length && profile.getElementsByTagName('pwsid')[…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4706, Column 49: reference not terminated by REFC delimiter
    …ow.location.href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4706, Column 49: reference to entity "who" for which no system identifier could be generated
    …ow.location.href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4706, Column 185: reference not terminated by REFC delimiter
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&from=wink&geonames_reg=1&origin=winks&topwsi…

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

  • Error Line 4706, Column 185: reference to entity "from" for which no system identifier could be generated
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&from=wink&geonames_reg=1&origin=winks&topwsi…

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

  • Info Line 4337, Column 268: entity was defined here
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";
  • Warning Line 4706, Column 203: reference not terminated by REFC delimiter
    …SZqKev0VvL244kE&from=wink&geonames_reg=1&origin=winks&topwsid="+a.getAttribute…

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

  • Error Line 4706, Column 203: reference to entity "geonames_reg" for which no system identifier could be generated
    …SZqKev0VvL244kE&from=wink&geonames_reg=1&origin=winks&topwsid="+a.getAttribute…

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

  • Info Line 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Warning Line 4706, Column 212: reference not terminated by REFC delimiter
    …L244kE&from=wink&geonames_reg=1&origin=winks&topwsid="+a.getAttribute('pwsid')…

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

  • Error Line 4706, Column 212: reference to entity "origin" for which no system identifier could be generated
    …L244kE&from=wink&geonames_reg=1&origin=winks&topwsid="+a.getAttribute('pwsid')…

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

  • Info Line 4329, Column 224: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4706, Column 226: reference not terminated by REFC delimiter
    …nk&geonames_reg=1&origin=winks&topwsid="+a.getAttribute('pwsid')+"&show_pwsid=…

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

  • Error Line 4706, Column 226: reference to entity "topwsid" for which no system identifier could be generated
    …nk&geonames_reg=1&origin=winks&topwsid="+a.getAttribute('pwsid')+"&show_pwsid=…

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

  • Info Line 4681, Column 223: entity was defined here
    …=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&sho…
  • Warning Line 4706, Column 265: reference not terminated by REFC delimiter
    …"+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')+"&flirt_type=…

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

  • Error Line 4706, Column 265: reference to entity "show_pwsid" for which no system identifier could be generated
    …"+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')+"&flirt_type=…

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

  • Info Line 4681, Column 259: entity was defined here
    …otlist&topwsid="+a.getAttribute('pwsid')+"&show_pwsid="+a.getAttribute('pwsid')
  • Warning Line 4706, Column 294: cannot generate system identifier for general entity "flirt_type"
    …how_pwsid="+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type'…

    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 4706, Column 294: general entity "flirt_type" not defined and no default entity
    …how_pwsid="+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type'…

    This is usually a cascading error caused by 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 4706, Column 304: reference not terminated by REFC delimiter
    …"+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type')+"&action…

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

  • Error Line 4706, Column 304: reference to entity "flirt_type" for which no system identifier could be generated
    …"+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type')+"&action…

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

  • Info Line 4706, Column 293: entity was defined here
    …show_pwsid="+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type…
  • Warning Line 4706, Column 344: reference not terminated by REFC delimiter
    …+a.getAttribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute(…

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

  • Error Line 4706, Column 344: reference to entity "action" for which no system identifier could be generated
    …+a.getAttribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute(…

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

  • Info Line 4326, Column 178: entity was defined here
    …UjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&…
  • Warning Line 4706, Column 358: cannot generate system identifier for general entity "tohandle"
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')

    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 4706, Column 358: general entity "tohandle" not defined and no default entity
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')

    This is usually a cascading error caused by 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 4706, Column 366: reference not terminated by REFC delimiter
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')

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

  • Error Line 4706, Column 366: reference to entity "tohandle" for which no system identifier could be generated
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')

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

  • Info Line 4706, Column 357: entity was defined here
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')
  • Warning Line 4707, Column 36: character "&" is the first character of a delimiter but occurred as data
        } else if (parseInt('') == 100 && parseInt('') != 2 && parseInt('') != 3 &&…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4707, Column 37: character "&" is the first character of a delimiter but occurred as data
        } else if (parseInt('') == 100 && parseInt('') != 2 && parseInt('') != 3 &&…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4707, Column 57: character "&" is the first character of a delimiter but occurred as data
    …seInt('') == 100 && parseInt('') != 2 && parseInt('') != 3 && parseInt('') != …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4707, Column 58: character "&" is the first character of a delimiter but occurred as data
    …eInt('') == 100 && parseInt('') != 2 && parseInt('') != 3 && parseInt('') != 5…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4707, Column 78: character "&" is the first character of a delimiter but occurred as data
    …nt('') == 100 && parseInt('') != 2 && parseInt('') != 3 && parseInt('') != 5) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4707, Column 79: character "&" is the first character of a delimiter but occurred as data
    …nt('') == 100 && parseInt('') != 2 && parseInt('') != 3 && parseInt('') != 5) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4708, Column 207: reference not terminated by REFC delimiter
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&from=wink&origin=winks&p_pwsid=…

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

  • Error Line 4708, Column 207: reference to entity "site" for which no system identifier could be generated
    …LdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&from=wink&origin=winks&p_pwsid=…

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

  • Info Line 4329, Column 199: entity was defined here
    …JJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&…
  • Warning Line 4708, Column 220: reference not terminated by REFC delimiter
    …C/57PSZqKev0VvL244kE&site=getiton&from=wink&origin=winks&p_pwsid="+a.getAttrib…

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

  • Error Line 4708, Column 220: reference to entity "from" for which no system identifier could be generated
    …C/57PSZqKev0VvL244kE&site=getiton&from=wink&origin=winks&p_pwsid="+a.getAttrib…

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

  • Info Line 4337, Column 268: entity was defined here
    …d=" + streamid + "&user_handle=" + handle + "&user_pwsid=" + pwsid + "&from= ";
  • Warning Line 4708, Column 232: reference not terminated by REFC delimiter
    …VvL244kE&site=getiton&from=wink&origin=winks&p_pwsid="+a.getAttribute('pwsid')…

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

  • Error Line 4708, Column 232: reference to entity "origin" for which no system identifier could be generated
    …VvL244kE&site=getiton&from=wink&origin=winks&p_pwsid="+a.getAttribute('pwsid')…

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

  • Info Line 4329, Column 224: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4708, Column 246: reference not terminated by REFC delimiter
    …getiton&from=wink&origin=winks&p_pwsid="+a.getAttribute('pwsid')+"&topwsid="+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.

  • Error Line 4708, Column 246: reference to entity "p_pwsid" for which no system identifier could be generated
    …getiton&from=wink&origin=winks&p_pwsid="+a.getAttribute('pwsid')+"&topwsid="+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 4329, Column 238: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4708, Column 282: reference not terminated by REFC delimiter
    …id="+a.getAttribute('pwsid')+"&topwsid="+a.getAttribute('pwsid')+"&flirt_type=…

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

  • Error Line 4708, Column 282: reference to entity "topwsid" for which no system identifier could be generated
    …id="+a.getAttribute('pwsid')+"&topwsid="+a.getAttribute('pwsid')+"&flirt_type=…

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

  • Info Line 4681, Column 223: entity was defined here
    …=hotlist&geonames_reg=1&origin=hotlist&topwsid="+a.getAttribute('pwsid')+"&sho…
  • Warning Line 4708, Column 321: reference not terminated by REFC delimiter
    …"+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type')+"&action…

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

  • Error Line 4708, Column 321: reference to entity "flirt_type" for which no system identifier could be generated
    …"+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type')+"&action…

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

  • Info Line 4706, Column 293: entity was defined here
    …show_pwsid="+a.getAttribute('pwsid')+"&flirt_type="+a.getAttribute('flirt_type…
  • Warning Line 4708, Column 361: reference not terminated by REFC delimiter
    …+a.getAttribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute(…

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

  • Error Line 4708, Column 361: reference to entity "action" for which no system identifier could be generated
    …+a.getAttribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute(…

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

  • Info Line 4326, Column 178: entity was defined here
    …UjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&…
  • Warning Line 4708, Column 383: reference not terminated by REFC delimiter
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')

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

  • Error Line 4708, Column 383: reference to entity "tohandle" for which no system identifier could be generated
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')

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

  • Info Line 4706, Column 357: entity was defined here
    …tribute('flirt_type')+"&action=single_flirt&tohandle="+a.getAttribute('handle')
  • Warning Line 4710, Column 40: reference not terminated by REFC delimiter
    …           var url = "/p/wink.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4710, Column 40: reference to entity "who" for which no system identifier could be generated
    …           var url = "/p/wink.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4710, Column 178: reference not terminated by REFC delimiter
    …DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&origin=wink&action=single_flirt;no_perf=1;";

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

  • Error Line 4710, Column 178: reference to entity "origin" for which no system identifier could be generated
    …DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&origin=wink&action=single_flirt;no_perf=1;";

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

  • Info Line 4329, Column 224: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Warning Line 4710, Column 190: reference not terminated by REFC delimiter
    …DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&origin=wink&action=single_flirt;no_perf=1;";

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

  • Error Line 4710, Column 190: reference to entity "action" for which no system identifier could be generated
    …DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&origin=wink&action=single_flirt;no_perf=1;";

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

  • Info Line 4326, Column 178: entity was defined here
    …UjxKkJAC/57PSZqKev0VvL244kE&is_flash=1&action=view" + "&userid=" + userid + "&…
  • Warning Line 4711, Column 24: character "&" is the first character of a delimiter but occurred as data
          if (self.members && members[a.getAttribute('pwsid')]) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4711, Column 25: character "&" is the first character of a delimiter but occurred as data
          if (self.members && members[a.getAttribute('pwsid')]) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 4712, Column 47: element "wink_sent" undefined
            var winked = string_to_xml("<wink_sent>1</wink_sent>")

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 4716, Column 24: character "&" is the first character of a delimiter but occurred as data
          if (self.profile && profile.getElementsByTagName('pwsid').length && profi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4716, Column 25: character "&" is the first character of a delimiter but occurred as data
          if (self.profile && profile.getElementsByTagName('pwsid').length && profi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4716, Column 72: character "&" is the first character of a delimiter but occurred as data
    ….getElementsByTagName('pwsid').length && profile.getElementsByTagName('pwsid')…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4716, Column 73: character "&" is the first character of a delimiter but occurred as data
    …getElementsByTagName('pwsid').length && profile.getElementsByTagName('pwsid')[…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4729, Column 53: character "&" is the first character of a delimiter but occurred as data
    …(a.getElementsByTagName('IMG').length && a.getElementsByTagName('IMG')[0] && a…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4729, Column 54: character "&" is the first character of a delimiter but occurred as data
    …a.getElementsByTagName('IMG').length && a.getElementsByTagName('IMG')[0] && a.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4729, Column 89: character "&" is the first character of a delimiter but occurred as data
    …h && a.getElementsByTagName('IMG')[0] && a.getElementsByTagName('IMG')[0].clas…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4729, Column 90: character "&" is the first character of a delimiter but occurred as data
    … && a.getElementsByTagName('IMG')[0] && a.getElementsByTagName('IMG')[0].class…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4753, Column 15: character "<" is the first character of a delimiter but occurred as data
            if (x < parseInt(width)/2) {x = x + 110;p = 1;} else {x = x - 285;p = 2…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 4769, Column 62: element "response" undefined
    …000_00000'] = string_to_xml('<response><data><handle></handle><pwsid>0000000_0…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 68: element "data" undefined
    …000'] = string_to_xml('<response><data><handle></handle><pwsid>0000000_00000</…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 76: element "handle" undefined
    …string_to_xml('<response><data><handle></handle><pwsid>0000000_00000</pwsid><l…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 92: element "pwsid" undefined
    …response><data><handle></handle><pwsid>0000000_00000</pwsid><location> , </loc…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 123: element "location" undefined
    …><pwsid>0000000_00000</pwsid><location> , </location><ti'+'tle></ti'+'tle><dis…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 141: an attribute specification must start with a name or name token
    …000</pwsid><location> , </location><ti'+'tle></ti'+'tle><distance></distance><…

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

  • Error Line 4769, Column 141: element "ti" undefined
    …000</pwsid><location> , </location><ti'+'tle></ti'+'tle><distance></distance><…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 152: delimiter "'" invalid: only S separators and TAGC allowed here
    …<location> , </location><ti'+'tle></ti'+'tle><distance></distance><photos><pho…
  • Error Line 4769, Column 168: element "distance" undefined
    …ocation><ti'+'tle></ti'+'tle><distance></distance><photos><photo><allowVoting>…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 187: element "photos" undefined
    …/ti'+'tle><distance></distance><photos><photo><allowVoting>1</allowVoting><vot…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 194: element "photo" undefined
    …le><distance></distance><photos><photo><allowVoting>1</allowVoting><votedScore…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 207: element "allowVoting" undefined
    …</distance><photos><photo><allowVoting>1</allowVoting><votedScore>0</votedScor…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 234: element "votedScore" undefined
    …allowVoting>1</allowVoting><votedScore>0</votedScore><numVotes>0</numVotes><av…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 258: element "numVotes" undefined
    …ng><votedScore>0</votedScore><numVotes>0</numVotes><averageVote>0</averageVote…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 283: element "averageVote" undefined
    …ore><numVotes>0</numVotes><averageVote>0</averageVote><url>'+image+'</url><pho…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 303: element "url" undefined
    …Votes><averageVote>0</averageVote><url>'+image+'</url><photoid>00000000</photo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 327: element "photoid" undefined
    …erageVote><url>'+image+'</url><photoid>00000000</photoid><photonum>1</photonum…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4769, Column 355: element "photonum" undefined
    …l><photoid>00000000</photoid><photonum>1</photonum></photo></photos> </data></…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 4774, Column 40: reference not terminated by REFC delimiter
    …     var ajaxurl = "/p/member.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4774, Column 40: reference to entity "who" for which no system identifier could be generated
    …     var ajaxurl = "/p/member.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4774, Column 178: reference not terminated by REFC delimiter
    …YRwqUjxKkJAC/57PSZqKev0VvL244kE&origin=member;ajax=1;mid="+pwsid+';timestamp='…

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

  • Error Line 4774, Column 178: reference to entity "origin" for which no system identifier could be generated
    …YRwqUjxKkJAC/57PSZqKev0VvL244kE&origin=member;ajax=1;mid="+pwsid+';timestamp='…

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

  • Info Line 4329, Column 224: entity was defined here
    …C/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&p_pwsid=" + userid;
  • Error Line 4779, Column 62: element "links" undefined
    …     var links = string_to_xml("<links><profileurl><![CDATA[/p/register.cgi?&w…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4779, Column 74: element "profileurl" undefined
    …ks = string_to_xml("<links><profileurl><![CDATA[/p/register.cgi?&who=r,JM8_Qib…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4779, Column 276: element "emaillink" undefined
    …onames_reg=1]]></profileurl><emaillink><![CDATA[/p/register.cgi?&who=r,JM8_Qib…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4779, Column 479: element "wink_upsale" undefined
    …names_reg=1]]></emaillink><wink_upsale><![CDATA[/p/register.cgi?&who=r,JM8_Qib…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4779, Column 678: element "order" undefined
    …&geonames_reg=1]]></wink_upsale><order><![CDATA[/p/register.cgi?&who=r,JM8_Qib…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4779, Column 871: element "flirt" undefined
    …L244kE&geonames_reg=1]]></order><flirt><![CDATA[/p/register.cgi?&who=r,JM8_Qib…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 4782, Column 32: character "&" is the first character of a delimiter but occurred as data
                if (current.length && current[0] == pwsid) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4782, Column 33: character "&" is the first character of a delimiter but occurred as data
                if (current.length && current[0] == pwsid) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 4791, Column 49: element "response" undefined
          members[pwsid] = string_to_xml("<response/>")

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 4823, Column 29: character "&" is the first character of a delimiter but occurred as data
            if (!self.show_info && document.getElementById('memberinfo')) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4823, Column 30: character "&" is the first character of a delimiter but occurred as data
            if (!self.show_info && document.getElementById('memberinfo')) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 4836, Column 32: character "[" not allowed in attribute specification list
        for (var i=0;i<self.members[a.getAttribute('uid')].getElementsByTagName('ph…
  • Error Line 4836, Column 32: element "self.members" undefined
        for (var i=0;i<self.members[a.getAttribute('uid')].getElementsByTagName('ph…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4852, Column 41: element "vote" undefined
            var vote = string_to_xml("<vote/>")

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 4859, Column 36: reference not terminated by REFC delimiter
        var url="/p/ratemember.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Error Line 4859, Column 36: reference to entity "who" for which no system identifier could be generated
        var url="/p/ratemember.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Error Line 4863, Column 9: end tag for "self.members" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 4836, Column 19: start tag was here
        for (var i=0;i<self.members[a.getAttribute('uid')].getElementsByTagName('ph…
  • Warning Line 4873, Column 92: reference not terminated by REFC delimiter
    …         <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 4873, Column 92: reference to external entity in attribute value
    …         <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4873, Column 92: reference to entity "who" for which no system identifier could be generated
    …         <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4873, Column 236: reference not terminated by REFC delimiter
    …BfKMf/olJNM_3/IA5hd0f3eLJJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1">

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

  • Warning Line 4873, Column 236: reference to external entity in attribute value
    …BfKMf/olJNM_3/IA5hd0f3eLJJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1">

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

  • Error Line 4873, Column 236: reference to entity "geonames_reg" for which no system identifier could be generated
    …BfKMf/olJNM_3/IA5hd0f3eLJJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1">

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

  • Info Line 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Error Line 4874, Column 191: required attribute "alt" not specified
    …s/getiton/spacer.gif" width="205" height="40" title="GetItOn" border="0" /></a>

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

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

  • Warning Line 4897, Column 74: character "&" is the first character of a delimiter but occurred as data
    …loc = (self.location.href.replace(/[\?&](m|show_lang|lang)=(\w+|\d+)/gi, '')+'…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4897, Column 119: reference not terminated by REFC delimiter
    …ow_lang|lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?…

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

  • Warning Line 4897, Column 129: cannot generate system identifier for general entity "show_lang"
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');

    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 4897, Column 129: general entity "show_lang" not defined and no default entity
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');

    This is usually a cascading error caused by 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 4897, Column 138: reference not terminated by REFC delimiter
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');

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

  • Error Line 4897, Column 138: reference to entity "show_lang" for which no system identifier could be generated
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');

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

  • Info Line 4897, Column 128: entity was defined here
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');
  • Warning Line 4897, Column 159: character "&" is the first character of a delimiter but occurred as data
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4898, Column 61: cannot generate system identifier for general entity "m"
                                //self.location.href = newloc+"&m="+"";

    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 4898, Column 61: general entity "m" not defined and no default entity
                                //self.location.href = newloc+"&m="+"";

    This is usually a cascading error caused by 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 4898, Column 62: reference not terminated by REFC delimiter
                                //self.location.href = newloc+"&m="+"";

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

  • Error Line 4898, Column 62: reference to entity "m" for which no system identifier could be generated
                                //self.location.href = newloc+"&m="+"";

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

  • Info Line 4898, Column 60: entity was defined here
                                //self.location.href = newloc+"&m="+"";
  • Error Line 4904, Column 187: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ended';"><div class="lang_flag_arrows">&nbsp;</div><div class="lang_flag_engli…

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

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

  • Error Line 4904, Column 230: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …p;</div><div class="lang_flag_english">&nbsp;</div><span>English</span></a>   …

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

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

  • Error Line 4905, Column 128: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ish');"><div class="lang_flag_spanish">&nbsp;</div><span>Espa&#241;ol</span></…

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

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

  • Error Line 4905, Column 267: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ench');"><div class="lang_flag_french">&nbsp;</div><span>Fran&#231;ais</span><…

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

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

  • Error Line 4905, Column 407: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rman');"><div class="lang_flag_german">&nbsp;</div><span>Deutsch</span></a>   …

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

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

  • Error Line 4905, Column 545: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …se');"><div class="lang_flag_japanese">&nbsp;</div><span>&#26085;&#26412;&#354…

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

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

  • Error Line 4905, Column 696: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rean');"><div class="lang_flag_korean">&nbsp;</div><span>&#54620;&#44544;</spa…

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

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

  • Error Line 4905, Column 847: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …');"><div class="lang_flag_portuguese">&nbsp;</div><span>Portugu&ecirc;s</span…

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

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

  • Error Line 4905, Column 991: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ian');"><div class="lang_flag_italian">&nbsp;</div><span>Italiano</span></a>  …

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

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

  • Error Line 4905, Column 1124: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …dutch');"><div class="lang_flag_dutch">&nbsp;</div><span>Nederlands</span></a>…

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

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

  • Error Line 4905, Column 1263: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ish');"><div class="lang_flag_swedish">&nbsp;</div><span>Svenska</span></a>   …

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

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

  • Error Line 4905, Column 1399: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ese');"><div class="lang_flag_chinese">&nbsp;</div><span>&#32321;&#39636;&#200…

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

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

  • Error Line 4910, Column 23: 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 4890, Column 41: start tag was here
                                            <li class="end">
  • Error Line 4919, Column 41: there is no attribute "border"
    …          <a id="x_loginPanel" border="0" href="javascript:void(0);" onclick="…

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

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

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

  • Error Line 4919, Column 177: required attribute "alt" not specified
    … src="http://graphics.pop6.com/images/getiton/cover/38151/btn_close.png" /></a>

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

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

  • Error Line 4926, Column 62: end tag for element "td" which is not open
                            <th colspan="2">Login to GetItOn!</td>

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

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

  • Error Line 4927, Column 25: end tag for "th" omitted, but OMITTAG NO was specified
                        </tr>

    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 4926, Column 25: start tag was here
                            <th colspan="2">Login to GetItOn!</td>
  • Error Line 4930, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …                     <td><input type="text" name="handle" id="mem_handle"></td>

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

  • Info Line 4930, Column 29: start tag was here
                            <td><input type="text" name="handle" id="mem_handle"></…
  • Error Line 4934, Column 90: end tag for "input" omitted, but OMITTAG NO was specified
    …             <td><input type="password" name="password" id="mem_password"></td>

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

  • Info Line 4934, Column 29: start tag was here
                            <td><input type="password" name="password" id="mem_pass…
  • Warning Line 4938, Column 83: reference not terminated by REFC delimiter
    … href="/go/page/forgot_login.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 4938, Column 83: reference to external entity in attribute value
    … href="/go/page/forgot_login.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4938, Column 83: reference to entity "who" for which no system identifier could be generated
    … href="/go/page/forgot_login.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Error Line 4948, Column 155: end tag for element "button" which is not open
    …dbtn2 uppercase" type="submit" name="submit"/><span>Login</span></button></div>

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

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

  • Error Line 4954, Column 20: required attribute "type" not specified
                <script>

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

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

  • Warning Line 4956, Column 40: character "&" is the first character of a delimiter but occurred as data
                        if (a.handle.value && a.password.value) {return true;}

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 4978, Column 46: reference not terminated by REFC delimiter
    …         <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 4978, Column 46: reference to external entity in attribute value
    …         <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 4978, Column 46: reference to entity "who" for which no system identifier could be generated
    …         <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 4978, Column 190: reference not terminated by REFC delimiter
    …dYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" class="join-now">Join Now </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 4978, Column 190: reference to external entity in attribute value
    …dYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" class="join-now">Join Now </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 4978, Column 190: reference to entity "geonames_reg" for which no system identifier could be generated
    …dYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" class="join-now">Join Now </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 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Error Line 5006, Column 75: required attribute "src" not specified
            <img id="caution" alt="getiton roadsign" title="getiton roadsign"/>

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

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

  • Error Line 5018, Column 104: required attribute "alt" not specified
    …   <img src="http://graphics.pop6.com/images/getiton/cover/38151/quotes.png" />

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

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

  • Error Line 5024, Column 100: required attribute "alt" not specified
    …   <img src="http://graphics.pop6.com/images/getiton/cover/38151/quotes.png" />

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

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

  • Error Line 5030, Column 100: required attribute "alt" not specified
    …   <img src="http://graphics.pop6.com/images/getiton/cover/38151/quotes.png" />

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

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

  • Error Line 5036, Column 100: required attribute "alt" not specified
    …   <img src="http://graphics.pop6.com/images/getiton/cover/38151/quotes.png" />

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

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

  • Warning Line 5076, Column 69: reference not terminated by REFC delimiter
    …="rcIE9"><a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5076, Column 69: reference to external entity in attribute value
    …="rcIE9"><a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5076, Column 69: reference to entity "who" for which no system identifier could be generated
    …="rcIE9"><a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5076, Column 213: reference not terminated by REFC delimiter
    …xKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" id="joinnowbtn" class="bigredbtn2">J…

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

  • Warning Line 5076, Column 213: reference to external entity in attribute value
    …xKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" id="joinnowbtn" class="bigredbtn2">J…

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

  • Error Line 5076, Column 213: reference to entity "geonames_reg" for which no system identifier could be generated
    …xKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" id="joinnowbtn" class="bigredbtn2">J…

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

  • Info Line 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Warning Line 5090, Column 45: reference not terminated by REFC delimiter
    …    near <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5090, Column 45: reference to external entity in attribute value
    …    near <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5090, Column 45: reference to entity "who" for which no system identifier could be generated
    …    near <a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5090, Column 189: reference not terminated by REFC delimiter
    …z/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" class="city">Cambridge</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 5090, Column 189: reference to external entity in attribute value
    …z/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" class="city">Cambridge</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 5090, Column 189: reference to entity "geonames_reg" for which no system identifier could be generated
    …z/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" class="city">Cambridge</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 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Error Line 5100, Column 6: document type does not allow element "tr" here
      <tr><td class="cell" style="vertical-align: top; text-align: center"><td clas…

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

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

  • Error Line 5100, Column 113: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5103, Column 56: cannot generate system identifier for general entity "picid"
    …tp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAf…

    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 5103, Column 56: general entity "picid" not defined and no default entity
    …tp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAf…

    This is usually a cascading error caused by 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 5103, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAfLgQAH…

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

  • Warning Line 5103, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAfLgQAH…

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

  • Error Line 5103, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAfLgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5103, Column 124: cannot generate system identifier for general entity "hr"
    …bEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targe…

    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 5103, Column 124: general entity "hr" not defined and no default entity
    …bEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targe…

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

  • Warning Line 5103, Column 126: reference not terminated by REFC delimiter
    …ADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5103, Column 126: reference to external entity in attribute value
    …ADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5103, Column 126: reference to entity "hr" for which no system identifier could be generated
    …ADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5103, Column 128: cannot generate system identifier for general entity "looking_for_person"
    …u3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_…

    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 5103, Column 128: general entity "looking_for_person" not defined and no default entity
    …u3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_…

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

  • Warning Line 5103, Column 146: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5103, Column 146: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5103, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5103, Column 149: cannot generate system identifier for general entity "show"
    …FO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_…

    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 5103, Column 149: general entity "show" not defined and no default entity
    …FO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_…

    This is usually a cascading error caused by 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 5103, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5103, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5103, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5107, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAfLgQAH…

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

  • Warning Line 5107, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAfLgQAH…

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

  • Error Line 5107, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoAfLgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5107, Column 146: reference not terminated by REFC delimiter
    …ADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5107, Column 146: reference to external entity in attribute value
    …ADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5107, Column 146: reference to entity "hr" for which no system identifier could be generated
    …ADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5107, Column 166: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Won0427</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 5107, Column 166: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Won0427</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 5107, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Won0427</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 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5107, Column 173: reference not terminated by REFC delimiter
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Won0427</a></div>

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

  • Warning Line 5107, Column 173: reference to external entity in attribute value
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Won0427</a></div>

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

  • Error Line 5107, Column 173: reference to entity "show" for which no system identifier could be generated
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Won0427</a></div>

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5113, Column 117: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5116, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1Gwlq8v4RsQADpaBwDu3AoAfLgQAH…

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

  • Warning Line 5116, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1Gwlq8v4RsQADpaBwDu3AoAfLgQAH…

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

  • Error Line 5116, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1Gwlq8v4RsQADpaBwDu3AoAfLgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5116, Column 126: reference not terminated by REFC delimiter
    …wDu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5116, Column 126: reference to external entity in attribute value
    …wDu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5116, Column 126: reference to entity "hr" for which no system identifier could be generated
    …wDu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5116, Column 146: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5116, Column 146: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5116, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5116, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5116, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5116, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5120, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1Gwlq8v4RsQADpaBwDu3AoAfLgQAH…

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

  • Warning Line 5120, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1Gwlq8v4RsQADpaBwDu3AoAfLgQAH…

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

  • Error Line 5120, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1Gwlq8v4RsQADpaBwDu3AoAfLgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5120, Column 146: reference not terminated by REFC delimiter
    …wDu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5120, Column 146: reference to external entity in attribute value
    …wDu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5120, Column 146: reference to entity "hr" for which no system identifier could be generated
    …wDu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5120, Column 166: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">epicureangal…

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

  • Warning Line 5120, Column 166: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">epicureangal…

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

  • Error Line 5120, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">epicureangal…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5120, Column 173: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">epicureangal</a></d…

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

  • Warning Line 5120, Column 173: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">epicureangal</a></d…

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

  • Error Line 5120, Column 173: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">epicureangal</a></d…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5126, Column 107: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5129, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HrQqgh7twKAOEbEAA6WgcAfLgQAH…

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

  • Warning Line 5129, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HrQqgh7twKAOEbEAA6WgcAfLgQAH…

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

  • Error Line 5129, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HrQqgh7twKAOEbEAA6WgcAfLgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5129, Column 126: reference not terminated by REFC delimiter
    …AA6WgcAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5129, Column 126: reference to external entity in attribute value
    …AA6WgcAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5129, Column 126: reference to entity "hr" for which no system identifier could be generated
    …AA6WgcAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5129, Column 146: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5129, Column 146: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5129, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5129, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5129, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5129, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5133, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HrQqgh7twKAOEbEAA6WgcAfLgQAH…

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

  • Warning Line 5133, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HrQqgh7twKAOEbEAA6WgcAfLgQAH…

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

  • Error Line 5133, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HrQqgh7twKAOEbEAA6WgcAfLgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5133, Column 146: reference not terminated by REFC delimiter
    …AA6WgcAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5133, Column 146: reference to external entity in attribute value
    …AA6WgcAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5133, Column 146: reference to entity "hr" for which no system identifier could be generated
    …AA6WgcAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5133, Column 166: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aa050109</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 5133, Column 166: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aa050109</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 5133, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aa050109</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 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5133, Column 173: reference not terminated by REFC delimiter
    …0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aa050109</a></div>

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

  • Warning Line 5133, Column 173: reference to external entity in attribute value
    …0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aa050109</a></div>

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

  • Error Line 5133, Column 173: reference to entity "show" for which no system identifier could be generated
    …0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aa050109</a></div>

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5139, Column 117: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5142, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EMSWQ5fLgQAO7cCgDhGxAAOloHAH…

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

  • Warning Line 5142, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EMSWQ5fLgQAO7cCgDhGxAAOloHAH…

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

  • Error Line 5142, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EMSWQ5fLgQAO7cCgDhGxAAOloHAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5142, Column 126: reference not terminated by REFC delimiter
    …gDhGxAAOloHAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5142, Column 126: reference to external entity in attribute value
    …gDhGxAAOloHAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5142, Column 126: reference to entity "hr" for which no system identifier could be generated
    …gDhGxAAOloHAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5142, Column 146: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5142, Column 146: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5142, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5142, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5142, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5142, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5146, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EMSWQ5fLgQAO7cCgDhGxAAOloHAH…

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

  • Warning Line 5146, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EMSWQ5fLgQAO7cCgDhGxAAOloHAH…

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

  • Error Line 5146, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EMSWQ5fLgQAO7cCgDhGxAAOloHAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5146, Column 146: reference not terminated by REFC delimiter
    …gDhGxAAOloHAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5146, Column 146: reference to external entity in attribute value
    …gDhGxAAOloHAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5146, Column 146: reference to entity "hr" for which no system identifier could be generated
    …gDhGxAAOloHAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5146, Column 166: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">MB2187</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 5146, Column 166: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">MB2187</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 5146, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">MB2187</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 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5146, Column 173: reference not terminated by REFC delimiter
    …FO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">MB2187</a></div>

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

  • Warning Line 5146, Column 173: reference to external entity in attribute value
    …FO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">MB2187</a></div>

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

  • Error Line 5146, Column 173: reference to entity "show" for which no system identifier could be generated
    …FO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">MB2187</a></div>

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5152, Column 107: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5155, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HHdcEAcbgQAHy4EADu3AoA4RsQAD…

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

  • Warning Line 5155, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HHdcEAcbgQAHy4EADu3AoA4RsQAD…

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

  • Error Line 5155, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HHdcEAcbgQAHy4EADu3AoA4RsQAD…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5155, Column 126: reference not terminated by REFC delimiter
    …ADu3AoA4RsQADpaBwDs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5155, Column 126: reference to external entity in attribute value
    …ADu3AoA4RsQADpaBwDs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5155, Column 126: reference to entity "hr" for which no system identifier could be generated
    …ADu3AoA4RsQADpaBwDs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5155, Column 146: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5155, Column 146: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5155, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5155, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5155, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5155, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5159, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HHdcEAcbgQAHy4EADu3AoA4RsQAD…

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

  • Warning Line 5159, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HHdcEAcbgQAHy4EADu3AoA4RsQAD…

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

  • Error Line 5159, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1HHdcEAcbgQAHy4EADu3AoA4RsQAD…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5159, Column 146: reference not terminated by REFC delimiter
    …ADu3AoA4RsQADpaBwDs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5159, Column 146: reference to external entity in attribute value
    …ADu3AoA4RsQADpaBwDs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5159, Column 146: reference to entity "hr" for which no system identifier could be generated
    …ADu3AoA4RsQADpaBwDs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5159, Column 166: reference not terminated by REFC delimiter
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aqua828</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 5159, Column 166: reference to external entity in attribute value
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aqua828</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 5159, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aqua828</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 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5159, Column 173: reference not terminated by REFC delimiter
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aqua828</a></div>

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

  • Warning Line 5159, Column 173: reference to external entity in attribute value
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aqua828</a></div>

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

  • Error Line 5159, Column 173: reference to entity "show" for which no system identifier could be generated
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">aqua828</a></div>

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5165, Column 117: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5168, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1FFp/kF7NwKAHG4EAB8uBAA7twKAO…

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

  • Warning Line 5168, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1FFp/kF7NwKAHG4EAB8uBAA7twKAO…

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

  • Error Line 5168, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1FFp/kF7NwKAHG4EAB8uBAA7twKAO…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5168, Column 126: reference not terminated by REFC delimiter
    …AB8uBAA7twKAOEbEAA6WgcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5168, Column 126: reference to external entity in attribute value
    …AB8uBAA7twKAOEbEAA6WgcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5168, Column 126: reference to entity "hr" for which no system identifier could be generated
    …AB8uBAA7twKAOEbEAA6WgcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5168, Column 146: reference not terminated by REFC delimiter
    …gcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5168, Column 146: reference to external entity in attribute value
    …gcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5168, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …gcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5168, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5168, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5168, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5172, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1FFp/kF7NwKAHG4EAB8uBAA7twKAO…

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

  • Warning Line 5172, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1FFp/kF7NwKAHG4EAB8uBAA7twKAO…

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

  • Error Line 5172, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1FFp/kF7NwKAHG4EAB8uBAA7twKAO…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5172, Column 146: reference not terminated by REFC delimiter
    …AB8uBAA7twKAOEbEAA6WgcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5172, Column 146: reference to external entity in attribute value
    …AB8uBAA7twKAOEbEAA6WgcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5172, Column 146: reference to entity "hr" for which no system identifier could be generated
    …AB8uBAA7twKAOEbEAA6WgcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5172, Column 166: reference not terminated by REFC delimiter
    …gcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Jae0427</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 5172, Column 166: reference to external entity in attribute value
    …gcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Jae0427</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 5172, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …gcAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Jae0427</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 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5172, Column 173: reference not terminated by REFC delimiter
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Jae0427</a></div>

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

  • Warning Line 5172, Column 173: reference to external entity in attribute value
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Jae0427</a></div>

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

  • Error Line 5172, Column 173: reference to entity "show" for which no system identifier could be generated
    …O0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">Jae0427</a></div>

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5178, Column 107: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5181, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1GPdI4iFO0QAOzcCgBxuBAAfLgQAO…

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

  • Warning Line 5181, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1GPdI4iFO0QAOzcCgBxuBAAfLgQAO…

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

  • Error Line 5181, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1GPdI4iFO0QAOzcCgBxuBAAfLgQAO…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5181, Column 126: reference not terminated by REFC delimiter
    …gBxuBAAfLgQAO7cCgDhGxAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5181, Column 126: reference to external entity in attribute value
    …gBxuBAAfLgQAO7cCgDhGxAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5181, Column 126: reference to entity "hr" for which no system identifier could be generated
    …gBxuBAAfLgQAO7cCgDhGxAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5181, Column 146: reference not terminated by REFC delimiter
    …xAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5181, Column 146: reference to external entity in attribute value
    …xAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5181, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …xAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5181, Column 153: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5181, Column 153: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5181, Column 153: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5185, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1GPdI4iFO0QAOzcCgBxuBAAfLgQAO…

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

  • Warning Line 5185, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1GPdI4iFO0QAOzcCgBxuBAAfLgQAO…

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

  • Error Line 5185, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1GPdI4iFO0QAOzcCgBxuBAAfLgQAO…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5185, Column 146: reference not terminated by REFC delimiter
    …gBxuBAAfLgQAO7cCgDhGxAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5185, Column 146: reference to external entity in attribute value
    …gBxuBAAfLgQAO7cCgDhGxAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5185, Column 146: reference to entity "hr" for which no system identifier could be generated
    …gBxuBAAfLgQAO7cCgDhGxAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5185, Column 166: reference not terminated by REFC delimiter
    …xAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">applejuicjgi…

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

  • Warning Line 5185, Column 166: reference to external entity in attribute value
    …xAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">applejuicjgi…

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

  • Error Line 5185, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …xAAOloHAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">applejuicjgi…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5185, Column 173: reference not terminated by REFC delimiter
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">applejuicjgirl</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 5185, Column 173: reference to external entity in attribute value
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">applejuicjgirl</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 5185, Column 173: reference to entity "show" for which no system identifier could be generated
    …AHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self">applejuicjgirl</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 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5191, Column 117: document type does not allow element "td" here
    …ical-align: top; text-align: center"><td class="piclist_thumbs" align="center">

    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 5194, Column 61: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1G2uqUTdNYQABTtEADs3AoAcbgQAH…

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

  • Warning Line 5194, Column 61: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1G2uqUTdNYQABTtEADs3AoAcbgQAH…

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

  • Error Line 5194, Column 61: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1G2uqUTdNYQABTtEADs3AoAcbgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5194, Column 126: reference not terminated by REFC delimiter
    …ADs3AoAcbgQAHy4EADu3AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5194, Column 126: reference to external entity in attribute value
    …ADs3AoAcbgQAHy4EADu3AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5194, Column 126: reference to entity "hr" for which no system identifier could be generated
    …ADs3AoAcbgQAHy4EADu3AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5194, Column 146: reference not terminated by REFC delimiter
    …AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Warning Line 5194, Column 146: reference to external entity in attribute value
    …AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Error Line 5194, Column 146: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self" class="picli…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5194, Column 153: reference not terminated by REFC delimiter
    …ADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Warning Line 5194, Column 153: reference to external entity in attribute value
    …ADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Error Line 5194, Column 153: reference to entity "show" for which no system identifier could be generated
    …ADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist_thum…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Warning Line 5198, Column 81: reference not terminated by REFC delimiter
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1G2uqUTdNYQABTtEADs3AoAcbgQAH…

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

  • Warning Line 5198, Column 81: reference to external entity in attribute value
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1G2uqUTdNYQABTtEADs3AoAcbgQAH…

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

  • Error Line 5198, Column 81: reference to entity "picid" for which no system identifier could be generated
    …getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1G2uqUTdNYQABTtEADs3AoAcbgQAH…

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

  • Info Line 5103, Column 55: entity was defined here
    …ttp://getiton.com/go/p112+reg?hostpid=&picid=2QTQegOqgL1EI4lAkOloHAOEbEADu3AoA…
  • Warning Line 5198, Column 146: reference not terminated by REFC delimiter
    …ADs3AoAcbgQAHy4EADu3AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Warning Line 5198, Column 146: reference to external entity in attribute value
    …ADs3AoAcbgQAHy4EADu3AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Error Line 5198, Column 146: reference to entity "hr" for which no system identifier could be generated
    …ADs3AoAcbgQAHy4EADu3AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target=…

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

  • Info Line 5103, Column 123: entity was defined here
    …EbEADu3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" targ…
  • Warning Line 5198, Column 166: reference not terminated by REFC delimiter
    …AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self">hannibalQ26<…

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

  • Warning Line 5198, Column 166: reference to external entity in attribute value
    …AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self">hannibalQ26<…

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

  • Error Line 5198, Column 166: reference to entity "looking_for_person" for which no system identifier could be generated
    …AoA4RsQADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self">hannibalQ26<…

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

  • Info Line 5103, Column 127: entity was defined here
    …Du3AoAfLgQAHG4EADs3AoAFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="…
  • Warning Line 5198, Column 173: reference not terminated by REFC delimiter
    …ADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self">hannibalQ26</a></di…

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

  • Warning Line 5198, Column 173: reference to external entity in attribute value
    …ADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self">hannibalQ26</a></di…

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

  • Error Line 5198, Column 173: reference to entity "show" for which no system identifier could be generated
    …ADpaBwA-&hr=&looking_for_person=2&show=f-m" target="_self">hannibalQ26</a></di…

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

  • Info Line 5103, Column 148: entity was defined here
    …AFO0QAHTWEAA-&hr=&looking_for_person=2&show=f-m" target="_self" class="piclist…
  • Error Line 5205, Column 7: end tag for "tr" which is not finished
      </tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 5216, Column 69: reference not terminated by REFC delimiter
    …="rcIE9"><a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5216, Column 69: reference to external entity in attribute value
    …="rcIE9"><a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5216, Column 69: reference to entity "who" for which no system identifier could be generated
    …="rcIE9"><a href="/p/register.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5216, Column 213: reference not terminated by REFC delimiter
    …xKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" id="findbestmatchbtn" class="bigredb…

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

  • Warning Line 5216, Column 213: reference to external entity in attribute value
    …xKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" id="findbestmatchbtn" class="bigredb…

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

  • Error Line 5216, Column 213: reference to entity "geonames_reg" for which no system identifier could be generated
    …xKkJAC/57PSZqKev0VvL244kE&geonames_reg=1" id="findbestmatchbtn" class="bigredb…

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

  • Info Line 4681, Column 193: entity was defined here
    …xKkJAC/57PSZqKev0VvL244kE&from=hotlist&geonames_reg=1&origin=hotlist&topwsid="…
  • Warning Line 5247, Column 61: reference not terminated by REFC delimiter
    …go/page/mobile_download_apps.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5247, Column 61: reference to external entity in attribute value
    …go/page/mobile_download_apps.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5247, Column 61: reference to entity "who" for which no system identifier could be generated
    …go/page/mobile_download_apps.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5250, Column 46: reference not terminated by REFC delimiter
    …   <a href="/go/page/privacy.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5250, Column 46: reference to external entity in attribute value
    …   <a href="/go/page/privacy.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5250, Column 46: reference to entity "who" for which no system identifier could be generated
    …   <a href="/go/page/privacy.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5251, Column 51: reference not terminated by REFC delimiter
    … href="/go/page/terms_of_use.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5251, Column 51: reference to external entity in attribute value
    … href="/go/page/terms_of_use.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5251, Column 51: reference to entity "who" for which no system identifier could be generated
    … href="/go/page/terms_of_use.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5254, Column 36: reference not terminated by REFC delimiter
              <a href="/p/help.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Warning Line 5254, Column 36: reference to external entity in attribute value
              <a href="/p/help.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Error Line 5254, Column 36: reference to entity "who" for which no system identifier could be generated
              <a href="/p/help.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5258, Column 44: reference not terminated by REFC delimiter
    …     <a href="/go/page/abuse.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5258, Column 44: reference to external entity in attribute value
    …     <a href="/go/page/abuse.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5258, Column 44: reference to entity "who" for which no system identifier could be generated
    …     <a href="/go/page/abuse.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Warning Line 5258, Column 176: cannot generate system identifier for general entity "abuse_fromip"
    …Jz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_re…

    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 5258, Column 176: general entity "abuse_fromip" not defined and no default entity
    …Jz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_re…

    This is usually a cascading error caused by 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 5258, Column 188: reference not terminated by REFC delimiter
    …xKkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&ab…

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

  • Warning Line 5258, Column 188: reference to external entity in attribute value
    …xKkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&ab…

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

  • Error Line 5258, Column 188: reference to entity "abuse_fromip" for which no system identifier could be generated
    …xKkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&ab…

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

  • Info Line 5258, Column 175: entity was defined here
    …JJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_r…
  • Warning Line 5258, Column 190: cannot generate system identifier for general entity "abuse_pwsid"
    …kJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abus…

    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 5258, Column 190: general entity "abuse_pwsid" not defined and no default entity
    …kJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abus…

    This is usually a cascading error caused by 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 5258, Column 201: reference not terminated by REFC delimiter
    …Kev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abus…

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

  • Warning Line 5258, Column 201: reference to external entity in attribute value
    …Kev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abus…

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

  • Error Line 5258, Column 201: reference to entity "abuse_pwsid" for which no system identifier could be generated
    …Kev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abus…

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

  • Info Line 5258, Column 189: entity was defined here
    …KkJAC/57PSZqKev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abu…
  • Warning Line 5258, Column 203: cannot generate system identifier for general entity "abuse_date_registered"
    …v0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_…

    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 5258, Column 203: general entity "abuse_date_registered" not defined and no default entity
    …v0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_…

    This is usually a cascading error caused by 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 5258, Column 224: reference not terminated by REFC delimiter
    …ip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=…

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

  • Warning Line 5258, Column 224: reference to external entity in attribute value
    …ip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=…

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

  • Error Line 5258, Column 224: reference to entity "abuse_date_registered" for which no system identifier could be generated
    …ip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=…

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

  • Info Line 5258, Column 202: entity was defined here
    …ev0VvL244kE&abuse_fromip=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse…
  • Warning Line 5258, Column 226: cannot generate system identifier for general entity "abuse_pid"
    …=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&a…

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

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

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

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

  • Error Line 5258, Column 226: general entity "abuse_pid" not defined and no default entity
    …=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&a…

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

  • Warning Line 5258, Column 235: reference not terminated by REFC delimiter
    …wsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_leve…

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

  • Warning Line 5258, Column 235: reference to external entity in attribute value
    …wsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_leve…

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

  • Error Line 5258, Column 235: reference to entity "abuse_pid" for which no system identifier could be generated
    …wsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_leve…

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

  • Info Line 5258, Column 225: entity was defined here
    …p=&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&…
  • Warning Line 5258, Column 237: cannot generate system identifier for general entity "abuse_handle"
    …id=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=…

    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 5258, Column 237: general entity "abuse_handle" not defined and no default entity
    …id=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=…

    This is usually a cascading error caused by 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 5258, Column 249: reference not terminated by REFC delimiter
    …te_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_t…

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

  • Warning Line 5258, Column 249: reference to external entity in attribute value
    …te_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_t…

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

  • Error Line 5258, Column 249: reference to entity "abuse_handle" for which no system identifier could be generated
    …te_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_t…

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

  • Info Line 5258, Column 236: entity was defined here
    …sid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level…
  • Warning Line 5258, Column 251: cannot generate system identifier for general entity "abuse_status"
    …_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top…

    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 5258, Column 251: general entity "abuse_status" not defined and no default entity
    …_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top…

    This is usually a cascading error caused by 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 5258, Column 263: reference not terminated by REFC delimiter
    …&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abu…

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

  • Warning Line 5258, Column 263: reference to external entity in attribute value
    …&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abu…

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

  • Error Line 5258, Column 263: reference to entity "abuse_status" for which no system identifier could be generated
    …&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abu…

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

  • Info Line 5258, Column 250: entity was defined here
    …e_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_to…
  • Warning Line 5258, Column 265: cannot generate system identifier for general entity "abuse_level"
    …buse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abuse…

    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 5258, Column 265: general entity "abuse_level" not defined and no default entity
    …buse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abuse…

    This is usually a cascading error caused by 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 5258, Column 276: reference not terminated by REFC delimiter
    …buse_handle=&abuse_status=&abuse_level=" target="_top">Report Abuse or Sexuall…

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

  • Warning Line 5258, Column 276: reference to external entity in attribute value
    …buse_handle=&abuse_status=&abuse_level=" target="_top">Report Abuse or Sexuall…

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

  • Error Line 5258, Column 276: reference to entity "abuse_level" for which no system identifier could be generated
    …buse_handle=&abuse_status=&abuse_level=" target="_top">Report Abuse or Sexuall…

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

  • Info Line 5258, Column 264: entity was defined here
    …abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abus…
  • Warning Line 5261, Column 76: reference not terminated by REFC delimiter
    …" href="/go/page/2257_notice.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5261, Column 76: reference to external entity in attribute value
    …" href="/go/page/2257_notice.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5261, Column 76: reference to entity "who" for which no system identifier could be generated
    …" href="/go/page/2257_notice.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Error Line 5273, Column 13: end tag for element "br" which is not open
            </br>

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

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

  • Warning Line 5387, Column 65: reference not terminated by REFC delimiter
    … href="/go/page/protect_kids.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Warning Line 5387, Column 65: reference to external entity in attribute value
    … href="/go/page/protect_kids.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Error Line 5387, Column 65: reference to entity "who" for which no system identifier could be generated
    … href="/go/page/protect_kids.html?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/…

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

  • Info Line 4326, Column 32: entity was defined here
          var popurl="/p/video.cgi?&who=r,JM8_QibIewxxGX74gZJvd3pv1CCy0HwAdtVV/KZbx…
  • Error Line 5475, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
      </body>

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

  • Info Line 4868, Column 9: start tag was here
            <div id="canvas">
  • Error Line 5475, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
      </body>

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

  • Info Line 4867, Column 11: start tag was here
              <div id="english">
  • Error Line 5475, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
      </body>

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

  • Info Line 4866, Column 3: start tag was here
      <div >
  • Error Line 5476, Column 9: 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 4209, Column 1: start tag was here
    <script language="javascript">
  • Error Line 5486, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

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

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

  • Error Line 5496, Column 62: document type does not allow element "script" here
    </script><script language="javascript" type="text/javascript"><!--

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

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

  • Error Line 5504, Column 10: document type does not allow element "noscript" here
    <noscript><img src="https://glean.pop6.com/images/common/glean.gif?rand=7513&si…

    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 5504, Column 82: reference not terminated by REFC delimiter
    …images/common/glean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+136207…

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

  • Warning Line 5504, Column 82: reference to external entity in attribute value
    …images/common/glean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+136207…

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

  • Error Line 5504, Column 82: reference to entity "site" for which no system identifier could be generated
    …images/common/glean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+136207…

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

  • Info Line 4329, Column 199: entity was defined here
    …JJz/DLdYRwqUjxKkJAC/57PSZqKev0VvL244kE&site=getiton&form_only=0&origin=member&…
  • Warning Line 5504, Column 91: cannot generate system identifier for general entity "session"
    …mmon/glean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+1362075881+128.…

    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 5504, Column 91: general entity "session" not defined and no default entity
    …mmon/glean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+1362075881+128.…

    This is usually a cascading error caused by 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 5504, Column 98: reference not terminated by REFC delimiter
    …ean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+1362075881+128.30.52.6…

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

  • Warning Line 5504, Column 98: reference to external entity in attribute value
    …ean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+1362075881+128.30.52.6…

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

  • Error Line 5504, Column 98: reference to entity "session" for which no system identifier could be generated
    …ean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+1362075881+128.30.52.6…

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

  • Info Line 5504, Column 90: entity was defined here
    …ommon/glean.gif?rand=7513&site=getiton&session=k%5EROIcI%3ESOei+1362075881+128…
  • Warning Line 5504, Column 141: cannot generate system identifier for general entity "pwsid"
    …ROIcI%3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=reg…

    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 5504, Column 141: general entity "pwsid" not defined and no default entity
    …ROIcI%3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=reg…

    This is usually a cascading error caused by 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 5504, Column 146: reference not terminated by REFC delimiter
    …%3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&…

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

  • Warning Line 5504, Column 146: reference to external entity in attribute value
    …%3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&…

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

  • Error Line 5504, Column 146: reference to entity "pwsid" for which no system identifier could be generated
    …%3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&…

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

  • Info Line 5504, Column 140: entity was defined here
    …EROIcI%3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=re…
  • Warning Line 5504, Column 148: cannot generate system identifier for general entity "pagename"
    …ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&co…

    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 5504, Column 148: general entity "pagename" not defined and no default entity
    …ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&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.

  • Warning Line 5504, Column 156: reference not terminated by REFC delimiter
    …62075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=Un…

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

  • Warning Line 5504, Column 156: reference to external entity in attribute value
    …62075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=Un…

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

  • Error Line 5504, Column 156: reference to entity "pagename" for which no system identifier could be generated
    …62075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=Un…

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

  • Info Line 5504, Column 147: entity was defined here
    …3ESOei+1362075881+128.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&c…
  • Warning Line 5504, Column 168: cannot generate system identifier for general entity "pagestate"
    ….30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States&…

    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 5504, Column 168: general entity "pagestate" not defined and no default entity
    ….30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States&…

    This is usually a cascading error caused by 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 5504, Column 177: reference not terminated by REFC delimiter
    …+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lan…

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

  • Warning Line 5504, Column 177: reference to external entity in attribute value
    …+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lan…

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

  • Error Line 5504, Column 177: reference to entity "pagestate" for which no system identifier could be generated
    …+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lan…

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

  • Info Line 5504, Column 167: entity was defined here
    …8.30.52.65+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States…
  • Warning Line 5504, Column 186: cannot generate system identifier for general entity "country"
    …pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lang=english…

    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 5504, Column 186: general entity "country" not defined and no default entity
    …pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lang=english…

    This is usually a cascading error caused by 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 5504, Column 193: reference not terminated by REFC delimiter
    …e=%2Funknown&pagestate=regtest&country=United+States&city=&lang=english&level=…

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

  • Warning Line 5504, Column 193: reference to external entity in attribute value
    …e=%2Funknown&pagestate=regtest&country=United+States&city=&lang=english&level=…

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

  • Error Line 5504, Column 193: reference to entity "country" for which no system identifier could be generated
    …e=%2Funknown&pagestate=regtest&country=United+States&city=&lang=english&level=…

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

  • Info Line 5504, Column 185: entity was defined here
    …&pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lang=englis…
  • Warning Line 5504, Column 208: cannot generate system identifier for general entity "city"
    …gestate=regtest&country=United+States&city=&lang=english&level=&gpid=g1087777&…

    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 5504, Column 208: general entity "city" not defined and no default entity
    …gestate=regtest&country=United+States&city=&lang=english&level=&gpid=g1087777&…

    This is usually a cascading error caused by 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 5504, Column 212: reference not terminated by REFC delimiter
    …ate=regtest&country=United+States&city=&lang=english&level=&gpid=g1087777&pid=…

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

  • Warning Line 5504, Column 212: reference to external entity in attribute value
    …ate=regtest&country=United+States&city=&lang=english&level=&gpid=g1087777&pid=…

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

  • Error Line 5504, Column 212: reference to entity "city" for which no system identifier could be generated
    …ate=regtest&country=United+States&city=&lang=english&level=&gpid=g1087777&pid=…

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

  • Info Line 5504, Column 207: entity was defined here
    …agestate=regtest&country=United+States&city=&lang=english&level=&gpid=g1087777…
  • Warning Line 5504, Column 218: reference not terminated by REFC delimiter
    …gtest&country=United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" …

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

  • Warning Line 5504, Column 227: cannot generate system identifier for general entity "level"
    …ntry=United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 h…

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

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

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

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

  • Error Line 5504, Column 227: general entity "level" not defined and no default entity
    …ntry=United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 h…

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

  • Warning Line 5504, Column 232: reference not terminated by REFC delimiter
    …United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height…

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

  • Warning Line 5504, Column 232: reference to external entity in attribute value
    …United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height…

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

  • Error Line 5504, Column 232: reference to entity "level" for which no system identifier could be generated
    …United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height…

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

  • Info Line 5504, Column 226: entity was defined here
    …untry=United+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 …
  • Warning Line 5504, Column 234: cannot generate system identifier for general entity "gpid"
    …ited+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1…

    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 5504, Column 234: general entity "gpid" not defined and no default entity
    …ited+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1…

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

  • Warning Line 5504, Column 238: reference not terminated by REFC delimiter
    …+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 bor…

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

  • Warning Line 5504, Column 238: reference to external entity in attribute value
    …+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 bor…

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

  • Error Line 5504, Column 238: reference to entity "gpid" for which no system identifier could be generated
    …+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 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.

  • Info Line 5504, Column 233: entity was defined here
    …nited+States&city=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=…
  • Warning Line 5504, Column 248: cannot generate system identifier for general entity "pid"
    …ty=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></no…

    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 5504, Column 248: general entity "pid" not defined and no default entity
    …ty=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></no…

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

  • Warning Line 5504, Column 251: reference not terminated by REFC delimiter
    …&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscr…

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

  • Warning Line 5504, Column 251: reference to external entity in attribute value
    …&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscr…

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

  • Error Line 5504, Column 251: reference to entity "pid" for which no system identifier could be generated
    …&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscr…

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

  • Info Line 5504, Column 247: entity was defined here
    …ity=&lang=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></n…
  • Error Line 5504, Column 264: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ng=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscript>
  • Error Line 5504, Column 273: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ng=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscript>
  • Error Line 5504, Column 282: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ng=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscript>
  • Error Line 5504, Column 283: required attribute "alt" not specified
    …ng=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscript>

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

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

  • Error Line 5504, Column 294: end tag for "img" omitted, but OMITTAG NO was specified
    …ng=english&level=&gpid=g1087777&pid=p112" width=1 height=1 border=0></noscript>

    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 5504, Column 11: start tag was here
    <noscript><img src="https://glean.pop6.com/images/common/glean.gif?rand=7513&si…

Visitor Analysis

Daily Visitor
  • 10.733 visits