SexMatchBook Free Dating Exposed ...

sexmatchbook.com
  • Domain Name
    sexmatchbook.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #27541
  • Page Size
    118.9 KB
  • Ip Address
    208.88.180.72
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 3 JPG, 2 PNG

Website Meta Analysis

  • Title
    SexMatchBook
  • Meta Keyword
    SexMatchBook Sex Personals SexPersonals Dating Exposed
  • Meta Description
    SexMatchBook Free Dating Exposed

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    208.88.180.72
  • Domain Age
    1 Years, 9 Months, 4 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 26 Jun 2013 23:42:52 GMT
  • server: Apache
  • etag: TESTBED
  • p3p: CP="DSP LAW"
  • x-apacheserver: ii85-27.friendfinderinc.com
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 24248
  • content-type: text/html;charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for sexmatchbook.com

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 357 Errors
  • 349 Warnings
Ratio Text/Html
  • 0.31417281435354816
Message Error
  • Error Line 15, Column 137: end tag for "link" omitted, but OMITTAG NO was specified
    …ics.pop6.com/css/live_cd/ffadult/english/31351/global_facelift-1358193646.css">

    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 15, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://graphics.pop6.com/css/live_…
  • Error Line 16, Column 135: end tag for "link" omitted, but OMITTAG NO was specified
    …phics.pop6.com/css/live_cd/ffadult/english/31351/jquery_custom-1358193646.css">

    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 16, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://graphics.pop6.com/css/live_…
  • Error Line 17, Column 134: end tag for "link" omitted, but OMITTAG NO was specified
    …aphics.pop6.com/css/live_cd/ffadult/english/31351/notification-1358193646.css">

    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 17, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://graphics.pop6.com/css/live_…
  • Error Line 19, Column 7: document type does not allow element "title" here
    <title>SexMatchBook</title>

    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 273, 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 286, Column 7: document type does not allow element "title" here
    <title>SexMatchBook</title>

    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 287, 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 315, 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 321, 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 372, Column 31: document type does not allow element "script" here; assuming missing "body" start-tag
    <script type="text/javascript"><!--
  • Error Line 464, Column 71: invalid comment declaration: found name start character outside comment but inside comment declaration
    …i; j = parseInt(Math.random() * i), --i, x = arr[i], arr[i] = arr[j], arr[j] =…
  • Info Line 372, Column 32: comment declaration started here
    <script type="text/javascript"><!--
  • Error Line 475, Column 54: document type does not allow element "a" here
    …e('<a href="' + udLink + '" target="_"><img src="' + userInfo[randIDX].imgPath…

    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 475, Column 158: required attribute "alt" not specified
    …imgPath + '" border="0" width="' + width + '" height="' + height + '" /></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 481, Column 54: document type does not allow element "a" here
    …te('<a href="' + udLink + '" target="_">' + userInfo[randIDX].handle + '</a>');

    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 489, Column 54: document type does not allow element "a" here
    …e('<a href="' + udLink + '" target="_"><img src="' + userInfo[randIDX].imgPath…

    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 489, Column 158: required attribute "alt" not specified
    …DX].imgPath + '" border="0" width="' + width + '" height="' + height + '" />');

    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 499, Column 54: document type does not allow element "a" here
    …e('<a href="' + udLink + '" target="_"><img src="' + userInfo[randIDX].imgPath…

    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 499, Column 158: required attribute "alt" not specified
    …DX].imgPath + '" border="0" width="' + width + '" height="' + height + '" />');

    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 502, Column 84: document type does not allow element "br" here
    …+ '/' + userInfo[randIDX].sex + '<br />' + userInfo[randIDX].city + ',' + user…

    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 502, Column 151: document type does not allow element "br" here
    …X].city + ',' + userInfo[randIDX].state + '<br/>' + userInfo[randIDX].country);

    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 574, Column 35: cannot generate system identifier for general entity "who"
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…

    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 574, Column 35: general entity "who" not defined and no default entity
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…

    This is usually a cascading error caused by 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 574, Column 38: reference not terminated by REFC delimiter
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…

    If you meant to include an entity that starts with "&", then you should terminate it 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 574, Column 38: reference to entity "who" for which no system identifier could be generated
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 574, Column 234: cannot generate system identifier for general entity "dcb"
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';

    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 574, Column 234: general entity "dcb" not defined and no default entity
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';

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

  • Warning Line 574, Column 237: reference not terminated by REFC delimiter
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';

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

  • Error Line 574, Column 237: reference to entity "dcb" for which no system identifier could be generated
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Error Line 578, Column 67: document type does not allow element "a" here
    …="piclist_image" href="' + udLink + '"><img src="' + userInfo[randIDX].imgPath…

    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 578, Column 171: required attribute "alt" not specified
    …imgPath + '" border="0" width="' + width + '" height="' + height + '" /></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 579, Column 69: document type does not allow element "a" here
    …piclist_profile" href="' + udLink + '"><span class="piclist_handle piclist_pro…

    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 580, Column 68: document type does not allow element "a" here
        document.write('<a class="piclist_online" href="' + udLink + '"></a>');

    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 590, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript">

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

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

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

  • Error Line 590, Column 30: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript">

    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 652, Column 81: required attribute "type" not specified
    …="http://graphics.pop6.com/images/common/js/jquery/jquery-1.7.min.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 653, Column 83: required attribute "type" not specified
    …http://graphics.pop6.com/images/common/js/handlebars-1.0.0.beta.6.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 654, Column 76: required attribute "type" not specified
    …t src="http://graphics.pop6.com/images/common/js/underscore_1.3.3.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 655, Column 73: required attribute "type" not specified
    …ript src="http://graphics.pop6.com/images/common/js/jquery.cookie.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 665, Column 36: there is no attribute "type"
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

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

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

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

  • Error Line 665, Column 53: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

    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 687, Column 56: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript1.1" type="text/javascript">

    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 709, Column 53: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

    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 759, Column 12: 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 810, 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 828, Column 57: reference not terminated by REFC delimiter
    …nager_url = '/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 828, Column 57: reference to entity "who" for which no system identifier could be generated
    …nager_url = '/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 828, Column 256: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_vi…

    If you meant to include an entity that starts with "&", then you should terminate it 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 828, Column 256: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_vi…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 828, Column 274: cannot generate system identifier for general entity "action"
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_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 828, Column 274: general entity "action" not defined and no default entity
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_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 828, Column 280: reference not terminated by REFC delimiter
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';

    If you meant to include an entity that starts with "&", then you should terminate it 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 828, Column 280: reference to entity "action" for which no system identifier could be generated
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_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.

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 829, Column 55: reference not terminated by REFC delimiter
    …hotos_url = '/p/manage_photos.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 829, Column 55: reference to entity "who" for which no system identifier could be generated
    …hotos_url = '/p/manage_photos.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 829, Column 254: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_…

    If you meant to include an entity that starts with "&", then you should terminate it 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 829, Column 254: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 829, Column 272: cannot generate system identifier for general entity "do"
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_page';

    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 829, Column 272: general entity "do" not defined and no default entity
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_page';

    This is usually a cascading error caused by 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 829, Column 274: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_page';

    If you meant to include an entity that starts with "&", then you should terminate it 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 829, Column 274: reference to entity "do" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_page';

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

  • Info Line 829, Column 271: entity was defined here
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&do=show_profile_photo_page';
  • Warning Line 830, Column 55: reference not terminated by REFC delimiter
    …tos_url   = '/p/manage_photos.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 830, Column 55: reference to entity "who" for which no system identifier could be generated
    …tos_url   = '/p/manage_photos.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 830, Column 254: reference not terminated by REFC delimiter
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';

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

  • Error Line 830, Column 254: reference to entity "dcb" for which no system identifier could be generated
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 842, Column 270: cannot generate system identifier for general entity "site"
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",

    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 842, Column 270: general entity "site" not defined and no default entity
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",

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

  • Warning Line 842, Column 274: reference not terminated by REFC delimiter
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",

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

  • Error Line 842, Column 274: reference to entity "site" for which no system identifier could be generated
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 842, Column 286: reference not terminated by REFC delimiter
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",

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

  • Error Line 842, Column 286: reference to entity "dcb" for which no system identifier could be generated
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 843, Column 279: reference not terminated by REFC delimiter
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=win…

    If you meant to include an entity that starts with "&", then you should terminate it 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 843, Column 279: reference to entity "site" for which no system identifier could be generated
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=win…

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 843, Column 291: reference not terminated by REFC delimiter
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",

    If you meant to include an entity that starts with "&", then you should terminate it 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 843, Column 291: reference to entity "dcb" for which no system identifier could be generated
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 843, Column 309: cannot generate system identifier for general entity "origin"
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",

    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 843, Column 309: general entity "origin" not defined and no default entity
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",

    This is usually a cascading error caused by 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 843, Column 315: reference not terminated by REFC delimiter
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",

    If you meant to include an entity that starts with "&", then you should terminate it 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 843, Column 315: reference to entity "origin" for which no system identifier could be generated
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 844, Column 281: reference not terminated by REFC delimiter
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=mem…

    If you meant to include an entity that starts with "&", then you should terminate it 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 844, Column 281: reference to entity "site" for which no system identifier could be generated
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=mem…

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 844, Column 293: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=member",

    If you meant to include an entity that starts with "&", then you should terminate it 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 844, Column 293: reference to entity "dcb" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=member",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 844, Column 317: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=member",

    If you meant to include an entity that starts with "&", then you should terminate it 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 844, Column 317: reference to entity "origin" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=member",

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 845, Column 281: reference not terminated by REFC delimiter
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=inv…

    If you meant to include an entity that starts with "&", then you should terminate it 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 845, Column 281: reference to entity "site" for which no system identifier could be generated
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=inv…

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 845, Column 293: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=invite",

    If you meant to include an entity that starts with "&", then you should terminate it 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 845, Column 293: reference to entity "dcb" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=invite",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 845, Column 317: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=invite",

    If you meant to include an entity that starts with "&", then you should terminate it 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 845, Column 317: reference to entity "origin" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=invite",

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 846, Column 283: reference not terminated by REFC delimiter
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=lik…

    If you meant to include an entity that starts with "&", then you should terminate it 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 846, Column 283: reference to entity "site" for which no system identifier could be generated
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=lik…

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 846, Column 295: reference not terminated by REFC delimiter
    …NlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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 846, Column 295: reference to entity "dcb" for which no system identifier could be generated
    …NlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 846, Column 319: reference not terminated by REFC delimiter
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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 846, Column 319: reference to entity "origin" for which no system identifier could be generated
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 846, Column 328: cannot generate system identifier for general entity "p_pwsid"
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&p_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 846, Column 328: general entity "p_pwsid" not defined and no default entity
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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.

  • Warning Line 846, Column 335: reference not terminated by REFC delimiter
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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 846, Column 335: reference to entity "p_pwsid" for which no system identifier could be generated
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&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 846, Column 327: entity was defined here
    …mtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=likebox&p_pwsid=",
  • Warning Line 847, Column 35: reference not terminated by REFC delimiter
          'mlink': "/p/member.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyDdcP…

    If you meant to include an entity that starts with "&", then you should terminate it 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 847, Column 35: reference to entity "who" for which no system identifier could be generated
          'mlink': "/p/member.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyDdcP…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 847, Column 234: reference not terminated by REFC delimiter
    …qvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&",

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

  • Error Line 847, Column 234: reference to entity "dcb" for which no system identifier could be generated
    …qvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 847, Column 251: character "&" is the first character of a delimiter but occurred as data
    …qvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&",

    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 851, Column 52: reference not terminated by REFC delimiter
    …ount_update_link': "/p/update.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 851, Column 52: reference to entity "who" for which no system identifier could be generated
    …ount_update_link': "/p/update.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 851, Column 251: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cu…

    If you meant to include an entity that starts with "&", then you should terminate it 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 851, Column 251: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cu…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 851, Column 269: cannot generate system identifier for general entity "p"
    …tRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cupid_preferences",

    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 851, Column 269: general entity "p" not defined and no default entity
    …tRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cupid_preferences",

    This is usually a cascading error caused by 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 851, Column 270: reference not terminated by REFC delimiter
    …tRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cupid_preferences",

    If you meant to include an entity that starts with "&", then you should terminate it 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 851, Column 270: reference to entity "p" for which no system identifier could be generated
    …tRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cupid_preferences",

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

  • Info Line 851, Column 268: entity was defined here
    …tRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cupid_preferences",
  • Warning Line 862, Column 51: reference not terminated by REFC delimiter
    …t_abuse_url':"/go/page/abuse.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 862, Column 51: reference to entity "who" for which no system identifier could be generated
    …t_abuse_url':"/go/page/abuse.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 862, Column 250: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_pw…

    If you meant to include an entity that starts with "&", then you should terminate it 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 862, Column 250: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_pw…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 862, Column 268: cannot generate system identifier for general entity "abuse_handle"
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 268: general entity "abuse_handle" not defined and no default entity
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 280: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 280: reference to entity "abuse_handle" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 267: entity was defined here
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_pwsid=",
  • Warning Line 862, Column 282: cannot generate system identifier for general entity "abuse_pwsid"
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 282: general entity "abuse_pwsid" not defined and no default entity
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 293: reference not terminated by REFC delimiter
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 293: reference to entity "abuse_pwsid" for which no system identifier could be generated
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_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 862, Column 281: entity was defined here
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_pwsid=",
  • Warning Line 897, Column 19: character "&" is the first character of a delimiter but occurred as data
        if (!a.mytype && a.myurl) {

    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 897, Column 20: character "&" is the first character of a delimiter but occurred as data
        if (!a.mytype && a.myurl) {

    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 903, Column 19: character "&" is the first character of a delimiter but occurred as data
        if (a.no_ajax && a.resp) {

    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 903, Column 20: character "&" is the first character of a delimiter but occurred as data
        if (a.no_ajax && a.resp) {

    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 935, Column 31: cannot generate system identifier for general entity "ajax_xml"
            ajax.send(a.myurl + '&ajax_xml=1', function (r) {

    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 935, Column 31: general entity "ajax_xml" not defined and no default entity
            ajax.send(a.myurl + '&ajax_xml=1', function (r) {

    This is usually a cascading error caused by 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 935, Column 39: reference not terminated by REFC delimiter
            ajax.send(a.myurl + '&ajax_xml=1', function (r) {

    If you meant to include an entity that starts with "&", then you should terminate it 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 935, Column 39: reference to entity "ajax_xml" for which no system identifier could be generated
            ajax.send(a.myurl + '&ajax_xml=1', function (r) {

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

  • Info Line 935, Column 30: entity was defined here
            ajax.send(a.myurl + '&ajax_xml=1', function (r) {
  • Warning Line 955, Column 69: reference not terminated by REFC delimiter
    …blog_view_more': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 955, Column 69: reference to entity "who" for which no system identifier could be generated
    …blog_view_more': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 955, Column 268: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_popula…

    If you meant to include an entity that starts with "&", then you should terminate it 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 955, Column 268: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_popula…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 955, Column 292: reference not terminated by REFC delimiter
    …cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_popular_blogs"

    If you meant to include an entity that starts with "&", then you should terminate it 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 955, Column 292: reference to entity "action" for which no system identifier could be generated
    …cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_popular_blogs"

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 960, Column 70: reference not terminated by REFC delimiter
    …blog_view_more': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 960, Column 70: reference to entity "who" for which no system identifier could be generated
    …blog_view_more': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 960, Column 269: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=v…

    If you meant to include an entity that starts with "&", then you should terminate it 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 960, Column 269: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=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.

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 960, Column 287: cannot generate system identifier for general entity "phandle"
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    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 960, Column 287: general entity "phandle" not defined and no default entity
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    This is usually a cascading error caused by 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 960, Column 294: reference not terminated by REFC delimiter
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    If you meant to include an entity that starts with "&", then you should terminate it 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 960, Column 294: reference to entity "phandle" for which no system identifier could be generated
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

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

  • Info Line 960, Column 286: entity was defined here
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",
  • Warning Line 960, Column 296: cannot generate system identifier for general entity "oid"
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    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 960, Column 296: general entity "oid" not defined and no default entity
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    This is usually a cascading error caused by 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 960, Column 299: reference not terminated by REFC delimiter
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    If you meant to include an entity that starts with "&", then you should terminate it 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 960, Column 299: reference to entity "oid" for which no system identifier could be generated
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

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

  • Info Line 960, Column 295: entity was defined here
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",
  • Warning Line 960, Column 307: reference not terminated by REFC delimiter
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    If you meant to include an entity that starts with "&", then you should terminate it 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 960, Column 307: reference to entity "action" for which no system identifier could be generated
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 961, Column 63: reference not terminated by REFC delimiter
    …'stuff_my_blog': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 961, Column 63: reference to entity "who" for which no system identifier could be generated
    …'stuff_my_blog': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 961, Column 262: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=v…

    If you meant to include an entity that starts with "&", then you should terminate it 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 961, Column 262: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=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.

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 961, Column 287: reference not terminated by REFC delimiter
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    If you meant to include an entity that starts with "&", then you should terminate it 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 961, Column 287: reference to entity "phandle" for which no system identifier could be generated
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

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

  • Info Line 960, Column 286: entity was defined here
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",
  • Warning Line 961, Column 292: reference not terminated by REFC delimiter
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    If you meant to include an entity that starts with "&", then you should terminate it 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 961, Column 292: reference to entity "oid" for which no system identifier could be generated
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

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

  • Info Line 960, Column 295: entity was defined here
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",
  • Warning Line 961, Column 300: reference not terminated by REFC delimiter
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

    If you meant to include an entity that starts with "&", then you should terminate it 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 961, Column 300: reference to entity "action" for which no system identifier could be generated
    …h0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&phandle=&oid=&action=view_blog",

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 962, Column 61: reference not terminated by REFC delimiter
    …  'create_blog': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 962, Column 61: reference to entity "who" for which no system identifier could be generated
    …  'create_blog': "/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 962, Column 260: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=bl…

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

  • Error Line 962, Column 260: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=bl…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 962, Column 284: reference not terminated by REFC delimiter
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"

    If you meant to include an entity that starts with "&", then you should terminate it 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 962, Column 284: reference to entity "action" for which no system identifier could be generated
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 962, Column 293: cannot generate system identifier for general entity "type"
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"

    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 962, Column 293: general entity "type" not defined and no default entity
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"

    This is usually a cascading error caused by 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 962, Column 297: reference not terminated by REFC delimiter
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"

    If you meant to include an entity that starts with "&", then you should terminate it 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 962, Column 297: reference to entity "type" for which no system identifier could be generated
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"

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

  • Info Line 962, Column 292: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"
  • Warning Line 967, Column 91: reference not terminated by REFC delimiter
    …tgroups/aclist_active_groups.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 967, Column 91: reference to entity "who" for which no system identifier could be generated
    …tgroups/aclist_active_groups.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 967, Column 290: reference not terminated by REFC delimiter
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Error Line 967, Column 290: reference to entity "dcb" for which no system identifier could be generated
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 972, Column 87: reference not terminated by REFC delimiter
    …og/index.html?dcb=sexmatchbook.com&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 972, Column 87: reference to entity "who" for which no system identifier could be generated
    …og/index.html?dcb=sexmatchbook.com&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 977, Column 74: reference not terminated by REFC delimiter
    …iew_more': "/p/imc/view_video.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 977, Column 74: reference to entity "who" for which no system identifier could be generated
    …iew_more': "/p/imc/view_video.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 977, Column 273: reference not terminated by REFC delimiter
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Error Line 977, Column 273: reference to entity "dcb" for which no system identifier could be generated
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 982, Column 86: reference not terminated by REFC delimiter
    … "/go/page/social_networking.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 982, Column 86: reference to entity "who" for which no system identifier could be generated
    … "/go/page/social_networking.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 982, Column 285: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hotte…

    If you meant to include an entity that starts with "&", then you should terminate it 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 982, Column 285: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hotte…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 982, Column 303: cannot generate system identifier for general entity "item"
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"

    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 982, Column 303: general entity "item" not defined and no default entity
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"

    This is usually a cascading error caused by 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 982, Column 307: reference not terminated by REFC delimiter
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 982, Column 307: reference to entity "item" for which no system identifier could be generated
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"

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

  • Info Line 982, Column 302: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"
  • Warning Line 982, Column 319: reference not terminated by REFC delimiter
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 982, Column 319: reference to entity "type" for which no system identifier could be generated
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"

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

  • Info Line 962, Column 292: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"
  • Warning Line 987, Column 83: reference not terminated by REFC delimiter
    …_view_more': "/p/quick_search.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 987, Column 83: reference to entity "who" for which no system identifier could be generated
    …_view_more': "/p/quick_search.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 987, Column 282: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_ra…

    If you meant to include an entity that starts with "&", then you should terminate it 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 987, Column 282: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_ra…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 987, Column 300: cannot generate system identifier for general entity "page_type"
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_pa…

    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 987, Column 300: general entity "page_type" not defined and no default entity
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_pa…

    This is usually a cascading error caused by 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 987, Column 309: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 309: reference to entity "page_type" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 299: entity was defined here
    …RohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_p…
  • Warning Line 987, Column 314: cannot generate system identifier for general entity "match_race"
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 314: general entity "match_race" not defined and no default entity
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 324: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 324: reference to entity "match_race" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 313: entity was defined here
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=1"
  • Warning Line 987, Column 327: cannot generate system identifier for general entity "from_cover_page"
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 327: general entity "from_cover_page" not defined and no default entity
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 342: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 342: reference to entity "from_cover_page" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=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 987, Column 326: entity was defined here
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&page_type=won&match_race=1&from_cover_page=1"
  • Warning Line 992, Column 95: reference not terminated by REFC delimiter
    … "/go/page/social_networking.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 992, Column 95: reference to entity "who" for which no system identifier could be generated
    … "/go/page/social_networking.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 992, Column 294: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottes…

    If you meant to include an entity that starts with "&", then you should terminate it 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 992, Column 294: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottes…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 992, Column 312: cannot generate system identifier for general entity "sort"
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&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 992, Column 312: general entity "sort" not defined and no default entity
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&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 992, Column 316: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hot…

    If you meant to include an entity that starts with "&", then you should terminate it 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 992, Column 316: reference to entity "sort" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hot…

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

  • Info Line 992, Column 311: entity was defined here
    …RohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&typ…
  • Warning Line 992, Column 327: reference not terminated by REFC delimiter
    …TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 992, Column 327: reference to entity "action" for which no system identifier could be generated
    …TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hottest"

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 992, Column 340: reference not terminated by REFC delimiter
    …TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 992, Column 340: reference to entity "item" for which no system identifier could be generated
    …TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hottest"

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

  • Info Line 982, Column 302: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"
  • Warning Line 992, Column 352: reference not terminated by REFC delimiter
    …TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 992, Column 352: reference to entity "type" for which no system identifier could be generated
    …TgPj3OK4&dcb=sexmatchbook.com&sort=top&action=hottest&item=photos&type=hottest"

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

  • Info Line 962, Column 292: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"
  • Warning Line 997, Column 96: reference not terminated by REFC delimiter
    … "/go/page/social_networking.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 997, Column 96: reference to entity "who" for which no system identifier could be generated
    … "/go/page/social_networking.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 997, Column 295: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=members&type=hott…

    If you meant to include an entity that starts with "&", then you should terminate it 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 997, Column 295: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=members&type=hott…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 997, Column 317: reference not terminated by REFC delimiter
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=members&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 997, Column 317: reference to entity "item" for which no system identifier could be generated
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=members&type=hottest"

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

  • Info Line 982, Column 302: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"
  • Warning Line 997, Column 330: reference not terminated by REFC delimiter
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=members&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 997, Column 330: reference to entity "type" for which no system identifier could be generated
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=members&type=hottest"

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

  • Info Line 962, Column 292: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"
  • Warning Line 1002, Column 81: reference not terminated by REFC delimiter
    …iew_more': "/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1002, Column 81: reference to entity "who" for which no system identifier could be generated
    …iew_more': "/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1002, Column 280: reference not terminated by REFC delimiter
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com",

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

  • Error Line 1002, Column 280: reference to entity "dcb" for which no system identifier could be generated
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1003, Column 75: reference not terminated by REFC delimiter
    …hat_room': "/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1003, Column 75: reference to entity "who" for which no system identifier could be generated
    …hat_room': "/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1003, Column 274: reference not terminated by REFC delimiter
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1003, Column 274: reference to entity "dcb" for which no system identifier could be generated
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1003, Column 292: cannot generate system identifier for general entity "room"
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"

    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 1003, Column 292: general entity "room" not defined and no default entity
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"

    This is usually a cascading error caused by 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 1003, Column 296: reference not terminated by REFC delimiter
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1003, Column 296: reference to entity "room" for which no system identifier could be generated
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"

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

  • Info Line 1003, Column 291: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&room=interest"
  • Warning Line 1008, Column 84: reference not terminated by REFC delimiter
    …view_more': "/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1008, Column 84: reference to entity "who" for which no system identifier could be generated
    …view_more': "/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1008, Column 283: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&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.

  • Error Line 1008, Column 283: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&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 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1008, Column 301: cannot generate system identifier for general entity "order_by"
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&date_range=7_day&it…

    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 1008, Column 301: general entity "order_by" not defined and no default entity
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&date_range=7_day&it…

    This is usually a cascading error caused by 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 1008, Column 309: reference not terminated by REFC delimiter
    …TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&date_range=7_day&item=video…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1008, Column 309: reference to entity "order_by" for which no system identifier could be generated
    …TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&date_range=7_day&item=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.

  • Info Line 1008, Column 300: entity was defined here
    …RohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&order_by=user_rating&date_range=7_day&i…
  • Warning Line 1008, Column 322: cannot generate system identifier for general entity "date_range"
    …sexmatchbook.com&order_by=user_rating&date_range=7_day&item=videos&action=soci…

    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 1008, Column 322: general entity "date_range" not defined and no default entity
    …sexmatchbook.com&order_by=user_rating&date_range=7_day&item=videos&action=soci…

    This is usually a cascading error caused by 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 1008, Column 332: reference not terminated by REFC delimiter
    …ok.com&order_by=user_rating&date_range=7_day&item=videos&action=social_videos&…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1008, Column 332: reference to entity "date_range" for which no system identifier could be generated
    …ok.com&order_by=user_rating&date_range=7_day&item=videos&action=social_videos&…

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

  • Info Line 1008, Column 321: entity was defined here
    …=sexmatchbook.com&order_by=user_rating&date_range=7_day&item=videos&action=soc…
  • Warning Line 1008, Column 343: reference not terminated by REFC delimiter
    …r_by=user_rating&date_range=7_day&item=videos&action=social_videos&type=hottes…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1008, Column 343: reference to entity "item" for which no system identifier could be generated
    …r_by=user_rating&date_range=7_day&item=videos&action=social_videos&type=hottes…

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

  • Info Line 982, Column 302: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&item=albums&type=hottest"
  • Warning Line 1008, Column 357: reference not terminated by REFC delimiter
    …_by=user_rating&date_range=7_day&item=videos&action=social_videos&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1008, Column 357: reference to entity "action" for which no system identifier could be generated
    …_by=user_rating&date_range=7_day&item=videos&action=social_videos&type=hottest"

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 1008, Column 376: reference not terminated by REFC delimiter
    …_by=user_rating&date_range=7_day&item=videos&action=social_videos&type=hottest"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1008, Column 376: reference to entity "type" for which no system identifier could be generated
    …_by=user_rating&date_range=7_day&item=videos&action=social_videos&type=hottest"

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

  • Info Line 962, Column 292: entity was defined here
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=addform&type=blog"
  • Warning Line 1013, Column 80: reference not terminated by REFC delimiter
    …chat_view_more': "/p/cams_videos/?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1013, Column 80: reference to entity "who" for which no system identifier could be generated
    …chat_view_more': "/p/cams_videos/?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1013, Column 279: reference not terminated by REFC delimiter
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=whos_online_page"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1013, Column 279: reference to entity "dcb" for which no system identifier could be generated
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=whos_online_page"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1013, Column 298: reference not terminated by REFC delimiter
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=whos_online_page"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1013, Column 298: reference to entity "p" for which no system identifier could be generated
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=whos_online_page"

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

  • Info Line 851, Column 268: entity was defined here
    …tRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&p=my_account_update_cupid_preferences",
  • Warning Line 1018, Column 72: reference not terminated by REFC delimiter
    …iends_view_more': "/p/network.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1018, Column 72: reference to entity "who" for which no system identifier could be generated
    …iends_view_more': "/p/network.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1018, Column 271: reference not terminated by REFC delimiter
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Error Line 1018, Column 271: reference to entity "dcb" for which no system identifier could be generated
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1023, Column 74: reference not terminated by REFC delimiter
    …lists_view_more': "/p/hotlist.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1023, Column 74: reference to entity "who" for which no system identifier could be generated
    …lists_view_more': "/p/hotlist.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1023, Column 273: reference not terminated by REFC delimiter
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Error Line 1023, Column 273: reference to entity "dcb" for which no system identifier could be generated
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1028, Column 79: reference not terminated by REFC delimiter
    …_photos_view_more': "/p/photo.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1028, Column 79: reference to entity "who" for which no system identifier could be generated
    …_photos_view_more': "/p/photo.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1028, Column 278: reference not terminated by REFC delimiter
    …coyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=favorites"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1028, Column 278: reference to entity "dcb" for which no system identifier could be generated
    …coyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=favorites"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1028, Column 302: reference not terminated by REFC delimiter
    …coyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=favorites"

    If you meant to include an entity that starts with "&", then you should terminate it 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 1028, Column 302: reference to entity "action" for which no system identifier could be generated
    …coyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=favorites"

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 1033, Column 94: reference not terminated by REFC delimiter
    …intgroups/acview_member_main.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1033, Column 94: reference to entity "who" for which no system identifier could be generated
    …intgroups/acview_member_main.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1033, Column 293: reference not terminated by REFC delimiter
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com",

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

  • Error Line 1033, Column 293: reference to entity "dcb" for which no system identifier could be generated
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1034, Column 87: reference not terminated by REFC delimiter
    …ups/aclist_all_recent_groups.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1034, Column 87: reference to entity "who" for which no system identifier could be generated
    …ups/aclist_all_recent_groups.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1034, Column 286: reference not terminated by REFC delimiter
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",

    If you meant to include an entity that starts with "&", then you should terminate it 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 1034, Column 286: reference to entity "dcb" for which no system identifier could be generated
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1034, Column 304: cannot generate system identifier for general entity "qtype"
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",

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

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

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

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

  • Error Line 1034, Column 304: general entity "qtype" not defined and no default entity
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",

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

  • Warning Line 1034, Column 309: reference not terminated by REFC delimiter
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",

    If you meant to include an entity that starts with "&", then you should terminate it 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 1034, Column 309: reference to entity "qtype" for which no system identifier could be generated
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",

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

  • Info Line 1034, Column 303: entity was defined here
    …2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&qtype=text",
  • Warning Line 1035, Column 109: reference not terminated by REFC delimiter
    …create_new_group_instruction.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1035, Column 109: reference to entity "who" for which no system identifier could be generated
    …create_new_group_instruction.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1035, Column 308: reference not terminated by REFC delimiter
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Error Line 1035, Column 308: reference to entity "dcb" for which no system identifier could be generated
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1040, Column 78: reference not terminated by REFC delimiter
    …albums_view_more': "/p/albums.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1040, Column 78: reference to entity "who" for which no system identifier could be generated
    …albums_view_more': "/p/albums.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1040, Column 277: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_friend…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1040, Column 277: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_friend…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1040, Column 301: reference not terminated by REFC delimiter
    …r7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1040, Column 301: reference to entity "action" for which no system identifier could be generated
    …r7TgPj3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min…

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 1040, Column 319: cannot generate system identifier for general entity "show_sex"
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    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 1040, Column 319: general entity "show_sex" not defined and no default entity
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    This is usually a cascading error caused by 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 1040, Column 327: reference not terminated by REFC delimiter
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    If you meant to include an entity that starts with "&", then you should terminate it 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 1040, Column 327: reference to entity "show_sex" for which no system identifier could be generated
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

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

  • Info Line 1040, Column 318: entity was defined here
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="
  • Warning Line 1040, Column 329: cannot generate system identifier for general entity "max_age"
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    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 1040, Column 329: general entity "max_age" not defined and no default entity
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    This is usually a cascading error caused by 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 1040, Column 336: reference not terminated by REFC delimiter
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    If you meant to include an entity that starts with "&", then you should terminate it 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 1040, Column 336: reference to entity "max_age" for which no system identifier could be generated
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

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

  • Info Line 1040, Column 328: entity was defined here
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="
  • Warning Line 1040, Column 338: cannot generate system identifier for general entity "min_age"
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    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 1040, Column 338: general entity "min_age" not defined and no default entity
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    This is usually a cascading error caused by 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 1040, Column 345: reference not terminated by REFC delimiter
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

    If you meant to include an entity that starts with "&", then you should terminate it 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 1040, Column 345: reference to entity "min_age" for which no system identifier could be generated
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="

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

  • Info Line 1040, Column 337: entity was defined here
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="
  • Error Line 1077, Column 60: character ";" not allowed in attribute specification list
                        for (i=0;i<xmlOptions.childNodes.length;i++){
  • Error Line 1077, Column 60: element "xmlOptions.childNodes.length" undefined
                        for (i=0;i<xmlOptions.childNodes.length;i++){

    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 1099, Column 9: end tag for "xmlOptions.childNodes.length" 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 1077, Column 31: start tag was here
                        for (i=0;i<xmlOptions.childNodes.length;i++){
  • Error Line 1112, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <script type=text/javascript src="http://graphics.pop6.com/images/js/AjaxRequ…
  • Error Line 1112, Column 21: NET-enabling start-tag not immediately followed by null end-tag
      <script type=text/javascript src="http://graphics.pop6.com/images/js/AjaxRequ…

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

  • Error Line 1112, Column 104: end tag for element "script" which is not open
    …cript src="http://graphics.pop6.com/images/js/AjaxRequest-compact.js"></script>

    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 1121, 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 1121, 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 1121, Column 196: delimiter "'" invalid: only S separators and TAGC allowed here
    …s.com/confirm18.js?site=ffadult') + '" defer="defer"></scr' + 'ipt>');</script>
  • Error Line 1126, 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 1271, Column 102: required attribute "type" not specified
    …6.com/css/live_cd/ffadult/english/31351/infoicon_beta1-1358193646.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>.

  • Warning Line 1288, Column 23: character "<" is the first character of a delimiter but occurred as data
            for(var i=0;i < ca.length;i++) {

    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 1343, Column 40: reference not terminated by REFC delimiter
    …     var ajaxurl = "/p/member.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1343, Column 40: reference to entity "who" for which no system identifier could be generated
    …     var ajaxurl = "/p/member.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1343, Column 239: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member;aj…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1343, Column 239: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member;aj…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1343, Column 263: reference not terminated by REFC delimiter
    …r7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member;ajax=1;mid="+pwsid+';times…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1343, Column 263: reference to entity "origin" for which no system identifier could be generated
    …r7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member;ajax=1;mid="+pwsid+';times…

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1360, Column 49: reference not terminated by REFC delimiter
    …  var profileurl = '/p/member.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1360, Column 49: reference to entity "who" for which no system identifier could be generated
    …  var profileurl = '/p/member.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1360, Column 248: reference not terminated by REFC delimiter
    …xwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1360, Column 248: reference to entity "dcb" for which no system identifier could be generated
    …xwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member'

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1360, Column 272: reference not terminated by REFC delimiter
    …xwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1360, Column 272: reference to entity "origin" for which no system identifier could be generated
    …xwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_member'

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1361, Column 280: reference not terminated by REFC delimiter
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=iic…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1361, Column 280: reference to entity "site" for which no system identifier could be generated
    …iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=iic…

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 1361, Column 292: reference not terminated by REFC delimiter
    …0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=iicon_member'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1361, Column 292: reference to entity "dcb" for which no system identifier could be generated
    …0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=iicon_member'

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1361, Column 316: reference not terminated by REFC delimiter
    …0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=iicon_member'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1361, Column 316: reference to entity "origin" for which no system identifier could be generated
    …0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=iicon_member'

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1364, Column 43: reference not terminated by REFC delimiter
    …        var winkurl ='/p/wink.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1364, Column 43: reference to entity "who" for which no system identifier could be generated
    …        var winkurl ='/p/wink.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1364, Column 242: reference not terminated by REFC delimiter
    …oyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1364, Column 242: reference to entity "dcb" for which no system identifier could be generated
    …oyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink'

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1364, Column 266: reference not terminated by REFC delimiter
    …oyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1364, Column 266: reference to entity "origin" for which no system identifier could be generated
    …oyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink'

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1365, Column 51: reference not terminated by REFC delimiter
    …var registerurl ='/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1365, Column 51: reference to entity "who" for which no system identifier could be generated
    …var registerurl ='/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1365, Column 250: reference not terminated by REFC delimiter
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_refer'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1365, Column 250: reference to entity "dcb" for which no system identifier could be generated
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_refer'

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1365, Column 274: reference not terminated by REFC delimiter
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_refer'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1365, Column 274: reference to entity "origin" for which no system identifier could be generated
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_refer'

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1366, Column 64: reference not terminated by REFC delimiter
    …eurl = '/go/page/wink_upsale.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1366, Column 64: reference to entity "who" for which no system identifier could be generated
    …eurl = '/go/page/wink_upsale.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1366, Column 263: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink_upsa…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1366, Column 263: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink_upsa…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1366, Column 287: reference not terminated by REFC delimiter
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink_upsale'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1366, Column 287: reference to entity "origin" for which no system identifier could be generated
    …V8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_wink_upsale'

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1367, Column 50: reference not terminated by REFC delimiter
    … var hotlisturl = '/p/hotlist.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1367, Column 50: reference to entity "who" for which no system identifier could be generated
    … var hotlisturl = '/p/hotlist.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1367, Column 249: reference not terminated by REFC delimiter
    …wc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_hotlist'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1367, Column 249: reference to entity "dcb" for which no system identifier could be generated
    …wc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_hotlist'

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1367, Column 273: reference not terminated by REFC delimiter
    …wc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_hotlist'

    If you meant to include an entity that starts with "&", then you should terminate it 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 1367, Column 273: reference to entity "origin" for which no system identifier could be generated
    …wc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&origin=iicon_hotlist'

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

  • Info Line 843, Column 308: entity was defined here
    …8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com&origin=wink",
  • Warning Line 1368, Column 59: reference not terminated by REFC delimiter
    …mmendurl = '/p/recommendation.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1368, Column 59: reference to entity "who" for which no system identifier could be generated
    …mmendurl = '/p/recommendation.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1368, Column 258: reference not terminated by REFC delimiter
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com'

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

  • Error Line 1368, Column 258: reference to entity "dcb" for which no system identifier could be generated
    …tMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com'

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1376, 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 1376, 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 1393, 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 1433, 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 1433, 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 1454, Column 7: document type does not allow element "body" here
    <body >

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

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

  • Warning Line 1471, Column 53: reference not terminated by REFC delimiter
    …        <a href=" /p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

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

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

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

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1471, Column 252: reference not terminated by REFC delimiter
    …GtMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com

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

  • Warning Line 1471, Column 252: reference to external entity in attribute value
    …GtMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com

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

  • Error Line 1471, Column 252: reference to entity "dcb" for which no system identifier could be generated
    …GtMqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1489, Column 60: reference not terminated by REFC delimiter
    …me" class="br1" href="/p/page.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1489, Column 60: reference to external entity in attribute value
    …me" class="br1" href="/p/page.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1489, Column 60: reference to entity "who" for which no system identifier could be generated
    …me" class="br1" href="/p/page.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1489, Column 259: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="SexMatchBook">…

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

  • Warning Line 1489, Column 259: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="SexMatchBook">…

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

  • Error Line 1489, Column 259: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="SexMatchBook">…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1490, Column 68: reference not terminated by REFC delimiter
    …s="br1 yel" href="/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1490, Column 68: reference to external entity in attribute value
    …s="br1 yel" href="/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1490, Column 68: reference to entity "who" for which no system identifier could be generated
    …s="br1 yel" href="/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1490, Column 267: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title…

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

  • Warning Line 1490, Column 267: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title…

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

  • Error Line 1490, Column 267: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1490, Column 285: cannot generate system identifier for general entity "show"
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBoo…

    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 1490, Column 285: general entity "show" not defined and no default entity
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBoo…

    This is usually a cascading error caused by 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 1490, Column 289: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook no…

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

  • Warning Line 1490, Column 289: reference to external entity in attribute value
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook no…

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

  • Error Line 1490, Column 289: reference to entity "show" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook no…

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

  • Info Line 1490, Column 284: entity was defined here
    …RohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBo…
  • Warning Line 1490, Column 291: cannot generate system identifier for general entity "find_sex"
    …r7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now"…

    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 1490, Column 291: general entity "find_sex" not defined and no default entity
    …r7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now"…

    This is usually a cascading error caused by 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 1490, Column 299: reference not terminated by REFC delimiter
    …K4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now">JOIN NO…

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

  • Warning Line 1490, Column 299: reference to external entity in attribute value
    …K4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now">JOIN NO…

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

  • Error Line 1490, Column 299: reference to entity "find_sex" for which no system identifier could be generated
    …K4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now">JOIN NO…

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

  • Info Line 1490, Column 290: entity was defined here
    …Fr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now…
  • Warning Line 1491, Column 78: reference not terminated by REFC delimiter
    …ref="/go/page/standard_login.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1491, Column 78: reference to external entity in attribute value
    …ref="/go/page/standard_login.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1491, Column 78: reference to entity "who" for which no system identifier could be generated
    …ref="/go/page/standard_login.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1491, Column 277: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Members login …

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

  • Warning Line 1491, Column 277: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Members login …

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

  • Error Line 1491, Column 277: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Members login …

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1492, Column 59: reference not terminated by REFC delimiter
    …rowse" class="br1" href="/browse?=&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1492, Column 59: reference to external entity in attribute value
    …rowse" class="br1" href="/browse?=&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1492, Column 59: reference to entity "who" for which no system identifier could be generated
    …rowse" class="br1" href="/browse?=&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1492, Column 258: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Find local sex…

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

  • Warning Line 1492, Column 258: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Find local sex…

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

  • Error Line 1492, Column 258: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Find local sex…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1493, Column 86: reference not terminated by REFC delimiter
    …"br1" href="/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1493, Column 86: reference to external entity in attribute value
    …"br1" href="/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1493, Column 86: reference to entity "who" for which no system identifier could be generated
    …"br1" href="/p/chat/makerooms.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1493, Column 285: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Chat with over…

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

  • Warning Line 1493, Column 285: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Chat with over…

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

  • Error Line 1493, Column 285: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Chat with over…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1494, Column 85: reference not terminated by REFC delimiter
    …"br1" href="/magazine/index.html?=&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1494, Column 85: reference to external entity in attribute value
    …"br1" href="/magazine/index.html?=&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1494, Column 85: reference to entity "who" for which no system identifier could be generated
    …"br1" href="/magazine/index.html?=&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1494, Column 284: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Sex advice fro…

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

  • Warning Line 1494, Column 284: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Sex advice fro…

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

  • Error Line 1494, Column 284: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="Sex advice fro…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1495, Column 78: reference not terminated by REFC delimiter
    …="br1" href="/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1495, Column 78: reference to external entity in attribute value
    …="br1" href="/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1495, Column 78: reference to entity "who" for which no system identifier could be generated
    …="br1" href="/p/video/manager.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1495, Column 277: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&max_age=40&action=sort…

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

  • Warning Line 1495, Column 277: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&max_age=40&action=sort…

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

  • Error Line 1495, Column 277: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&max_age=40&action=sort…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1495, Column 302: reference not terminated by REFC delimiter
    …7TgPj3OK4&dcb=sexmatchbook.com&max_age=40&action=sort_score&date_range=30_day&…

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

  • Warning Line 1495, Column 302: reference to external entity in attribute value
    …7TgPj3OK4&dcb=sexmatchbook.com&max_age=40&action=sort_score&date_range=30_day&…

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

  • Error Line 1495, Column 302: reference to entity "max_age" for which no system identifier could be generated
    …7TgPj3OK4&dcb=sexmatchbook.com&max_age=40&action=sort_score&date_range=30_day&…

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

  • Info Line 1040, Column 328: entity was defined here
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="
  • Warning Line 1495, Column 312: reference not terminated by REFC delimiter
    …dcb=sexmatchbook.com&max_age=40&action=sort_score&date_range=30_day&min_age=18…

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

  • Warning Line 1495, Column 312: reference to external entity in attribute value
    …dcb=sexmatchbook.com&max_age=40&action=sort_score&date_range=30_day&min_age=18…

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

  • Error Line 1495, Column 312: reference to entity "action" for which no system identifier could be generated
    …dcb=sexmatchbook.com&max_age=40&action=sort_score&date_range=30_day&min_age=18…

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

  • Info Line 828, Column 273: entity was defined here
    …pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&action=view_indexed_video';
  • Warning Line 1495, Column 334: reference not terminated by REFC delimiter
    …ax_age=40&action=sort_score&date_range=30_day&min_age=18&show_sex=2&filter_sho…

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

  • Warning Line 1495, Column 334: reference to external entity in attribute value
    …ax_age=40&action=sort_score&date_range=30_day&min_age=18&show_sex=2&filter_sho…

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

  • Error Line 1495, Column 334: reference to entity "date_range" for which no system identifier could be generated
    …ax_age=40&action=sort_score&date_range=30_day&min_age=18&show_sex=2&filter_sho…

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

  • Info Line 1008, Column 321: entity was defined here
    …=sexmatchbook.com&order_by=user_rating&date_range=7_day&item=videos&action=soc…
  • Warning Line 1495, Column 349: reference not terminated by REFC delimiter
    …n=sort_score&date_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title=…

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

  • Warning Line 1495, Column 349: reference to external entity in attribute value
    …n=sort_score&date_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title=…

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

  • Error Line 1495, Column 349: reference to entity "min_age" for which no system identifier could be generated
    …n=sort_score&date_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title=…

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

  • Info Line 1040, Column 337: entity was defined here
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="
  • Warning Line 1495, Column 361: reference not terminated by REFC delimiter
    …&date_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy …

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

  • Warning Line 1495, Column 361: reference to external entity in attribute value
    …&date_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy …

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

  • Error Line 1495, Column 361: reference to entity "show_sex" for which no system identifier could be generated
    …&date_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy …

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

  • Info Line 1040, Column 318: entity was defined here
    …j3OK4&dcb=sexmatchbook.com&action=list_all_friends&show_sex=&max_age=&min_age="
  • Warning Line 1495, Column 364: cannot generate system identifier for general entity "filter_show_sex"
    …te_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy vid…

    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 1495, Column 364: general entity "filter_show_sex" not defined and no default entity
    …te_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy vid…

    This is usually a cascading error caused by 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 1495, Column 379: reference not terminated by REFC delimiter
    …&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy videos from real S…

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

  • Warning Line 1495, Column 379: reference to external entity in attribute value
    …&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy videos from real S…

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

  • Error Line 1495, Column 379: reference to entity "filter_show_sex" for which no system identifier could be generated
    …&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy videos from real S…

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

  • Info Line 1495, Column 363: entity was defined here
    …ate_range=30_day&min_age=18&show_sex=2&filter_show_sex=2" title="Watch sexy vi…
  • Warning Line 1496, Column 94: reference not terminated by REFC delimiter
    …og/index.html?dcb=sexmatchbook.com&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1496, Column 94: reference to external entity in attribute value
    …og/index.html?dcb=sexmatchbook.com&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1496, Column 94: reference to entity "who" for which no system identifier could be generated
    …og/index.html?dcb=sexmatchbook.com&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1497, Column 90: reference not terminated by REFC delimiter
    …class="br1" href="/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1497, Column 90: reference to external entity in attribute value
    …class="br1" href="/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1497, Column 90: reference to entity "who" for which no system identifier could be generated
    …class="br1" href="/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1497, Column 289: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title…

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

  • Warning Line 1497, Column 289: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title…

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

  • Error Line 1497, Column 289: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1497, Column 311: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join a group and mee…

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

  • Warning Line 1497, Column 311: reference to external entity in attribute value
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join a group and mee…

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

  • Error Line 1497, Column 311: reference to entity "show" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join a group and mee…

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

  • Info Line 1490, Column 284: entity was defined here
    …RohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBo…
  • Warning Line 1497, Column 321: reference not terminated by REFC delimiter
    …K4&dcb=sexmatchbook.com&show=&find_sex=" title="Join a group and meet people w…

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

  • Warning Line 1497, Column 321: reference to external entity in attribute value
    …K4&dcb=sexmatchbook.com&show=&find_sex=" title="Join a group and meet people w…

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

  • Error Line 1497, Column 321: reference to entity "find_sex" for which no system identifier could be generated
    …K4&dcb=sexmatchbook.com&show=&find_sex=" title="Join a group and meet people w…

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

  • Info Line 1490, Column 290: entity was defined here
    …Fr7TgPj3OK4&dcb=sexmatchbook.com&show=&find_sex=" title="Join SexMatchBook now…
  • Warning Line 1498, Column 84: reference not terminated by REFC delimiter
    …lp" class="br0" href="/p/help.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1498, Column 84: reference to external entity in attribute value
    …lp" class="br0" href="/p/help.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1498, Column 84: reference to entity "who" for which no system identifier could be generated
    …lp" class="br0" href="/p/help.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1498, Column 283: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="SexMatchBook h…

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

  • Warning Line 1498, Column 283: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="SexMatchBook h…

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

  • Error Line 1498, Column 283: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" title="SexMatchBook 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.

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1525, Column 50: 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 1525, Column 95: 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 1525, Column 105: 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 1525, Column 105: 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 1525, Column 114: 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 1525, Column 114: 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 1525, Column 104: entity was defined here
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');
  • Warning Line 1525, Column 135: 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.
  • Error Line 1531, Column 160: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …o' : 'suspended';"><div class="arrows">&nbsp;</div><div class="flag english">&…

    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 1531, Column 198: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …>&nbsp;</div><div class="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 1532, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'spanish');"><div class="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 1532, Column 191: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …g('french');"><div class="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 1532, Column 304: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …g('german');"><div class="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 1532, Column 415: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …apanese');"><div class="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 1532, Column 539: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …g('korean');"><div class="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 1532, Column 663: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …guese');"><div class="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 1532, Column 780: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'italian');"><div class="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 1532, Column 886: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ang('dutch');"><div class="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 1532, Column 998: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'swedish');"><div class="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 1532, Column 1107: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'chinese');"><div class="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>").

  • Warning Line 1539, Column 245: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Warning Line 1539, Column 245: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Error Line 1539, Column 245: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1540, Column 245: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Warning Line 1540, Column 245: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Error Line 1540, Column 245: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1541, Column 245: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Warning Line 1541, Column 245: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Error Line 1541, Column 245: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Error Line 1551, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <form method="post" action="/p/register.cgi" name=search_form >
  • Error Line 1554, Column 63: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="searchtype" value="photo_search">

    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 1554, Column 3: start tag was here
      <input type="hidden" name="searchtype" value="photo_search">
  • Error Line 1555, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="quick_search" value="1">

    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 1555, Column 3: start tag was here
      <input type="hidden" name="quick_search" value="1">
  • Error Line 1556, Column 49: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="hottest" value="1">

    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 1556, Column 3: start tag was here
      <input type="hidden" name="hottest" value="1">
  • Error Line 1557, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="prefill_from_cookie" value="1">

    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 1557, Column 3: start tag was here
      <input type="hidden" name="prefill_from_cookie" value="1">
  • Error Line 1558, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="photo_rating" value="30">

    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 1558, Column 3: start tag was here
      <input type="hidden" name="photo_rating" value="30">
  • Error Line 1559, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="bday_year" value="76">

    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 1559, Column 3: start tag was here
      <input type="hidden" name="bday_year" value="76">
  • Error Line 1560, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="hidden" name="looking_for_what" value="*">

    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 1560, Column 3: start tag was here
      <input type="hidden" name="looking_for_what" value="*">
  • Error Line 1609, Column 110: end tag for "input" omitted, but OMITTAG NO was specified
    …in_age" value="18" maxlength="2"></div><div id="form_text_age">&nbsp;and&nbsp;…

    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 1609, Column 37: start tag was here
          <div class="input_fields_age"><input type="text" size="2" name="min_age" …
  • Error Line 1609, Column 259: end tag for "input" omitted, but OMITTAG NO was specified
    …age"><input type="text" size="2" name="max_age" value="35" maxlength="2"></div>

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

  • Info Line 1609, Column 186: start tag was here
    …p;</div><div class="input_fields_age"><input type="text" size="2" name="max_ag…
  • Error Line 1616, Column 215: there is no attribute "cols"
    …><select name="country"  onchange="statedropdown(search_form)"  cols=20 size=1>

    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 1616, Column 215: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …><select name="country"  onchange="statedropdown(search_form)"  cols=20 size=1>
  • Error Line 1616, Column 223: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …><select name="country"  onchange="statedropdown(search_form)"  cols=20 size=1>
  • Error Line 1806, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …v id="form_field_state" class="form_input"><select name="state" cols=20 size=1>
  • Error Line 1806, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …v id="form_field_state" class="form_input"><select name="state" cols=20 size=1>
  • Warning Line 1875, Column 73: reference not terminated by REFC delimiter
    …"window.location='/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1875, Column 73: reference to external entity in attribute value
    …"window.location='/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1875, Column 73: reference to entity "who" for which no system identifier could be generated
    …"window.location='/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1875, Column 272: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" v…

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

  • Warning Line 1875, Column 272: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" v…

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

  • Error Line 1875, Column 272: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" 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.

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1875, Column 290: cannot generate system identifier for general entity "from"
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" value="Search" 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 1875, Column 290: general entity "from" not defined and no default entity
    …ohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" value="Search" 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 1875, Column 294: reference not terminated by REFC delimiter
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" value="Search" id="cove…

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

  • Warning Line 1875, Column 294: reference to external entity in attribute value
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" value="Search" id="cove…

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

  • Error Line 1875, Column 294: reference to entity "from" for which no system identifier could be generated
    …QFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" value="Search" id="cove…

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

  • Info Line 1875, Column 289: entity was defined here
    …RohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&from=cover_search';" value="Search" id=…
  • Warning Line 1885, Column 232: reference not terminated by REFC delimiter
    …rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">cta</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 1885, Column 232: reference to external entity in attribute value
    …rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">cta</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 1885, Column 232: reference to entity "dcb" for which no system identifier could be generated
    …rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">cta</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 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1888, Column 232: reference not terminated by REFC delimiter
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Join for FREE!</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 1888, Column 232: reference to external entity in attribute value
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Join for FREE!</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 1888, Column 232: reference to entity "dcb" for which no system identifier could be generated
    …yxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Join for FREE!</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 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1891, Column 232: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Warning Line 1891, Column 232: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Error Line 1891, Column 232: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Error Line 1891, Column 380: required attribute "alt" not specified
    …nd/sexmatchbook.com/btn_highlight.png" width="62" height="62" 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 1897, Column 245: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Real hookups near <sp…

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

  • Warning Line 1897, Column 245: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Real hookups near <sp…

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

  • Error Line 1897, Column 245: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Real hookups near <sp…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1898, Column 246: reference not terminated by REFC delimiter
    …c/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">View more members</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 1898, Column 246: reference to external entity in attribute value
    …c/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">View more members</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 1898, Column 246: reference to entity "dcb" for which no system identifier could be generated
    …c/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">View more members</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 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1917, Column 253: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Join for FREE!</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 1917, Column 253: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Join for FREE!</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 1917, Column 253: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com">Join for FREE!</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 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1918, Column 258: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Warning Line 1918, Column 258: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Error Line 1918, Column 258: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com"><img src="http://grap…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Error Line 1918, Column 406: required attribute "alt" not specified
    …matchbook.com/btn_highlight.png" width="62" height="62" border="0" /></a></div>

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

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

  • Warning Line 1959, Column 54: reference not terminated by REFC delimiter
    …iv><a href="/go/page/privacy.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1959, Column 54: reference to external entity in attribute value
    …iv><a href="/go/page/privacy.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1959, Column 54: reference to entity "who" for which no system identifier could be generated
    …iv><a href="/go/page/privacy.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1959, Column 253: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Privacy…

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

  • Warning Line 1959, Column 253: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Privacy…

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

  • Error Line 1959, Column 253: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Privacy…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1960, Column 46: reference not terminated by REFC delimiter
    … href="/go/page/terms_of_use.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1960, Column 46: reference to external entity in attribute value
    … href="/go/page/terms_of_use.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1960, Column 46: reference to entity "who" for which no system identifier could be generated
    … href="/go/page/terms_of_use.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1960, Column 245: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Terms o…

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

  • Warning Line 1960, Column 245: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Terms o…

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

  • Error Line 1960, Column 245: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Terms o…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1961, Column 47: reference not terminated by REFC delimiter
    … href="/go/page/protect_kids.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1961, Column 47: reference to external entity in attribute value
    … href="/go/page/protect_kids.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1961, Column 47: reference to entity "who" for which no system identifier could be generated
    … href="/go/page/protect_kids.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1961, Column 246: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Protect…

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

  • Warning Line 1961, Column 246: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Protect…

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

  • Error Line 1961, Column 246: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Protect…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1962, Column 39: reference not terminated by REFC delimiter
    	<li><a href="/go/page/abuse.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8ley…

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

  • Warning Line 1962, Column 39: reference to external entity in attribute value
    	<li><a href="/go/page/abuse.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8ley…

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

  • Error Line 1962, Column 39: reference to entity "who" for which no system identifier could be generated
    	<li><a href="/go/page/abuse.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8ley…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1962, Column 238: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_pwsid=&abuse_dat…

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

  • Warning Line 1962, Column 238: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_pwsid=&abuse_dat…

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

  • Error Line 1962, Column 238: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_pwsid=&abuse_dat…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1962, Column 267: reference not terminated by REFC delimiter
    …j3OK4&dcb=sexmatchbook.com&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 1962, Column 267: reference to external entity in attribute value
    …j3OK4&dcb=sexmatchbook.com&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 1962, Column 267: reference to entity "abuse_pwsid" for which no system identifier could be generated
    …j3OK4&dcb=sexmatchbook.com&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 862, Column 281: entity was defined here
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_pwsid=",
  • Warning Line 1962, Column 269: cannot generate system identifier for general entity "abuse_date_registered"
    …OK4&dcb=sexmatchbook.com&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 1962, Column 269: general entity "abuse_date_registered" not defined and no default entity
    …OK4&dcb=sexmatchbook.com&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 1962, Column 290: reference not terminated by REFC delimiter
    …com&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 1962, Column 290: reference to external entity in attribute value
    …com&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 1962, Column 290: reference to entity "abuse_date_registered" for which no system identifier could be generated
    …com&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 1962, Column 268: entity was defined here
    …3OK4&dcb=sexmatchbook.com&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse…
  • Warning Line 1962, Column 292: cannot generate system identifier for general entity "abuse_pid"
    …m&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 1962, Column 292: general entity "abuse_pid" not defined and no default entity
    …m&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 1962, Column 301: 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 1962, Column 301: 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 1962, Column 301: 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 1962, Column 291: entity was defined here
    …om&abuse_pwsid=&abuse_date_registered=&abuse_pid=&abuse_handle=&abuse_status=&…
  • Warning Line 1962, Column 315: 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 1962, Column 315: 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 1962, Column 315: 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 862, Column 267: entity was defined here
    …j6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com&abuse_handle=&abuse_pwsid=",
  • Warning Line 1962, Column 317: 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 1962, Column 317: 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 1962, Column 329: 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 1962, Column 329: 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 1962, Column 329: 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 1962, Column 316: entity was defined here
    …e_registered=&abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_to…
  • Warning Line 1962, Column 331: 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 1962, Column 331: 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 1962, Column 342: 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 1962, Column 342: 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 1962, Column 342: 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 1962, Column 330: entity was defined here
    …abuse_pid=&abuse_handle=&abuse_status=&abuse_level=" target="_top">Report Abus…
  • Warning Line 1964, Column 46: reference not terminated by REFC delimiter
    …a href="/go/page/2257_notice.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 1964, Column 46: reference to external entity in attribute value
    …a href="/go/page/2257_notice.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 1964, Column 46: reference to entity "who" for which no system identifier could be generated
    …a href="/go/page/2257_notice.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1964, Column 245: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">18 U.S.…

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

  • Warning Line 1964, Column 245: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">18 U.S.…

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

  • Error Line 1964, Column 245: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">18 U.S.…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 1967, Column 32: reference not terminated by REFC delimiter
    		<li><a href="/p/help.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyDdcPqHJ…

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

  • Warning Line 1967, Column 32: reference to external entity in attribute value
    		<li><a href="/p/help.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyDdcPqHJ…

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

  • Error Line 1967, Column 32: reference to entity "who" for which no system identifier could be generated
    		<li><a href="/p/help.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyDdcPqHJ…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 1967, Column 231: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Help / …

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

  • Warning Line 1967, Column 231: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Help / …

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

  • Error Line 1967, Column 231: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top">Help / …

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 2013, Column 75: reference not terminated by REFC delimiter
    …<a href="/go/page/panic_page.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 2013, Column 75: reference to external entity in attribute value
    …<a href="/go/page/panic_page.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 2013, Column 75: reference to entity "who" for which no system identifier could be generated
    …<a href="/go/page/panic_page.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 2013, Column 274: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" style="color:red;font…

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

  • Warning Line 2013, Column 274: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" style="color:red;font…

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

  • Error Line 2013, Column 274: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" style="color:red;font…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 2016, Column 43: reference not terminated by REFC delimiter
    … href="/go/page/protect_kids.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Warning Line 2016, Column 43: reference to external entity in attribute value
    … href="/go/page/protect_kids.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Error Line 2016, Column 43: reference to entity "who" for which no system identifier could be generated
    … href="/go/page/protect_kids.html?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8le…

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

  • Info Line 574, Column 34: entity was defined here
    var udLink    = '/p/register.cgi?&who=r,JU0yINvKi0kNPKvkAJB6as5nFhPlAF3eQg8leyD…
  • Warning Line 2016, Column 242: reference not terminated by REFC delimiter
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top"><img sr…

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

  • Warning Line 2016, Column 242: reference to external entity in attribute value
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top"><img sr…

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

  • Error Line 2016, Column 242: reference to entity "dcb" for which no system identifier could be generated
    …/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com" target="_top"><img sr…

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

  • Info Line 574, Column 233: entity was defined here
    …MqvFEv6rxot2NB2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&dcb=sexmatchbook.com';
  • Warning Line 2026, Column 50: 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 2026, Column 95: 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 2026, Column 114: 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 2026, Column 114: 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 1525, Column 104: entity was defined here
    …lang)=(\w+|\d+)/gi, '')+'&lang='+lang+'&show_lang='+lang).replace(/[\?&]/,'?');
  • Warning Line 2026, Column 135: 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.
  • Error Line 2031, Column 14: ID "lang_dd" already defined
        <div id="lang_dd" class="suspended">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1530, Column 14: ID "lang_dd" first defined here
        <div id="lang_dd" class="suspended">
  • Error Line 2032, Column 160: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …o' : 'suspended';"><div class="arrows">&nbsp;</div><div class="flag english">&…

    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 2032, Column 198: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …>&nbsp;</div><div class="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 2033, Column 79: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'spanish');"><div class="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 2033, Column 191: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …g('french');"><div class="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 2033, Column 304: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …g('german');"><div class="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 2033, Column 415: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …apanese');"><div class="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 2033, Column 539: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …g('korean');"><div class="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 2033, Column 663: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …guese');"><div class="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 2033, Column 780: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'italian');"><div class="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 2033, Column 886: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ang('dutch');"><div class="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 2033, Column 998: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'swedish');"><div class="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 2033, Column 1107: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …'chinese');"><div class="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 2061, Column 30: there is no attribute "data-lang"
    <div id="siteLang" data-lang="english"></div>

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

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

  • Info Line 372, Column 1: start tag was here
    <script type="text/javascript"><!--
  • Error Line 2069, Column 33: 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 2087, Column 53: document type does not allow element "script" here
    <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 2095, Column 10: document type does not allow element "noscript" here
    <noscript><img src="https://glean.pop6.com/images/common/glean.gif?rand=5333&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 2095, Column 82: reference not terminated by REFC delimiter
    …images/common/glean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360…

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

  • Warning Line 2095, Column 82: reference to external entity in attribute value
    …images/common/glean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360…

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

  • Error Line 2095, Column 82: reference to entity "site" for which no system identifier could be generated
    …images/common/glean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360…

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

  • Info Line 842, Column 269: entity was defined here
    …B2wcoyxwc/iV8pj6cBh0WeNlmtRohmJQFr7TgPj3OK4&site=ffadult&dcb=sexmatchbook.com",
  • Warning Line 2095, Column 91: cannot generate system identifier for general entity "session"
    …mmon/glean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360512688+12…

    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 2095, Column 91: general entity "session" not defined and no default entity
    …mmon/glean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360512688+12…

    This is usually a cascading error caused by 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 2095, Column 98: reference not terminated by REFC delimiter
    …ean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360512688+128.30.52…

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

  • Warning Line 2095, Column 98: reference to external entity in attribute value
    …ean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360512688+128.30.52…

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

  • Error Line 2095, Column 98: reference to entity "session" for which no system identifier could be generated
    …ean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360512688+128.30.52…

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

  • Info Line 2095, Column 90: entity was defined here
    …ommon/glean.gif?rand=5333&site=ffadult&session=CD7_%3AcOWZ0%5D%5C+1360512688+1…
  • Warning Line 2095, Column 143: cannot generate system identifier for general entity "pwsid"
    …AcOWZ0%5D%5C+1360512688+128.30.52.70+&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 2095, Column 143: general entity "pwsid" not defined and no default entity
    …AcOWZ0%5D%5C+1360512688+128.30.52.70+&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 2095, Column 148: reference not terminated by REFC delimiter
    …0%5D%5C+1360512688+128.30.52.70+&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 2095, Column 148: reference to external entity in attribute value
    …0%5D%5C+1360512688+128.30.52.70+&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 2095, Column 148: reference to entity "pwsid" for which no system identifier could be generated
    …0%5D%5C+1360512688+128.30.52.70+&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 2095, Column 142: entity was defined here
    …3AcOWZ0%5D%5C+1360512688+128.30.52.70+&pwsid=&pagename=%2Funknown&pagestate=re…
  • Warning Line 2095, Column 150: cannot generate system identifier for general entity "pagename"
    …5D%5C+1360512688+128.30.52.70+&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 2095, Column 150: general entity "pagename" not defined and no default entity
    …5D%5C+1360512688+128.30.52.70+&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 2095, Column 158: reference not terminated by REFC delimiter
    …60512688+128.30.52.70+&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 2095, Column 158: reference to external entity in attribute value
    …60512688+128.30.52.70+&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 2095, Column 158: reference to entity "pagename" for which no system identifier could be generated
    …60512688+128.30.52.70+&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 2095, Column 149: entity was defined here
    …%5D%5C+1360512688+128.30.52.70+&pwsid=&pagename=%2Funknown&pagestate=regtest&c…
  • Warning Line 2095, Column 170: cannot generate system identifier for general entity "pagestate"
    ….30.52.70+&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 2095, Column 170: general entity "pagestate" not defined and no default entity
    ….30.52.70+&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 2095, Column 179: 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 2095, Column 179: 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 2095, Column 179: 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 2095, Column 169: entity was defined here
    …8.30.52.70+&pwsid=&pagename=%2Funknown&pagestate=regtest&country=United+States…
  • Warning Line 2095, Column 188: 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 2095, Column 188: 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 2095, Column 195: 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 2095, Column 195: 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 2095, Column 195: 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 2095, Column 187: entity was defined here
    …&pagename=%2Funknown&pagestate=regtest&country=United+States&city=&lang=englis…
  • Warning Line 2095, Column 210: cannot generate system identifier for general entity "city"
    …gestate=regtest&country=United+States&city=&lang=english&level=&gpid=g547603&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 2095, Column 210: general entity "city" not defined and no default entity
    …gestate=regtest&country=United+States&city=&lang=english&level=&gpid=g547603&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 2095, Column 214: reference not terminated by REFC delimiter
    …ate=regtest&country=United+States&city=&lang=english&level=&gpid=g547603&pid=p…

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

  • Warning Line 2095, Column 214: reference to external entity in attribute value
    …ate=regtest&country=United+States&city=&lang=english&level=&gpid=g547603&pid=p…

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

  • Error Line 2095, Column 214: reference to entity "city" for which no system identifier could be generated
    …ate=regtest&country=United+States&city=&lang=english&level=&gpid=g547603&pid=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.

  • Info Line 2095, Column 209: entity was defined here
    …agestate=regtest&country=United+States&city=&lang=english&level=&gpid=g547603&…
  • Warning Line 2095, Column 220: reference not terminated by REFC delimiter
    …gtest&country=United+States&city=&lang=english&level=&gpid=g547603&pid=p143591…

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

  • Warning Line 2095, Column 229: cannot generate system identifier for general entity "level"
    …ntry=United+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexma…

    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 2095, Column 229: general entity "level" not defined and no default entity
    …ntry=United+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexma…

    This is usually a cascading error caused by 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 2095, Column 234: reference not terminated by REFC delimiter
    …United+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbo…

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

  • Warning Line 2095, Column 234: reference to external entity in attribute value
    …United+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbo…

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

  • Error Line 2095, Column 234: reference to entity "level" for which no system identifier could be generated
    …United+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbo…

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

  • Info Line 2095, Column 228: entity was defined here
    …untry=United+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexm…
  • Warning Line 2095, Column 236: cannot generate system identifier for general entity "gpid"
    …ited+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook…

    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 2095, Column 236: general entity "gpid" not defined and no default entity
    …ited+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook…

    This is usually a cascading error caused by 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 2095, Column 240: reference not terminated by REFC delimiter
    …+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" wi…

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

  • Warning Line 2095, Column 240: reference to external entity in attribute value
    …+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" wi…

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

  • Error Line 2095, Column 240: reference to entity "gpid" for which no system identifier could be generated
    …+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" wi…

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

  • Info Line 2095, Column 235: entity was defined here
    …nited+States&city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchboo…
  • Warning Line 2095, Column 249: cannot generate system identifier for general entity "pid"
    …ity=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" width=1 hei…

    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 2095, Column 249: general entity "pid" not defined and no default entity
    …ity=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" width=1 hei…

    This is usually a cascading error caused by 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 2095, Column 252: reference not terminated by REFC delimiter
    …=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" 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 2095, Column 252: reference to external entity in attribute value
    …=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" 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 2095, Column 252: reference to entity "pid" for which no system identifier could be generated
    …=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" 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 2095, Column 248: entity was defined here
    …city=&lang=english&level=&gpid=g547603&pid=p143591.subsexmatchbook" width=1 he…
  • Error Line 2095, Column 284: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gpid=g547603&pid=p143591.subsexmatchbook" width=1 height=1 border=0></noscript>
  • Error Line 2095, Column 293: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gpid=g547603&pid=p143591.subsexmatchbook" width=1 height=1 border=0></noscript>
  • Error Line 2095, Column 302: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gpid=g547603&pid=p143591.subsexmatchbook" width=1 height=1 border=0></noscript>
  • Error Line 2095, Column 303: required attribute "alt" not specified
    …gpid=g547603&pid=p143591.subsexmatchbook" 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 2095, Column 314: end tag for "img" omitted, but OMITTAG NO was specified
    …gpid=g547603&pid=p143591.subsexmatchbook" 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 2095, Column 11: start tag was here
    <noscript><img src="https://glean.pop6.com/images/common/glean.gif?rand=5333&si…

Visitor Analysis

Daily Visitor
  • 9.450 visits
Daily Visitor