On myFlirt you can flirt and find new people in your area. Everything is for free. Just sign up now. ...

myflirt.com
  • Domain Name
    myflirt.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #62444
  • Page Size
    30.6 KB
  • Ip Address
    62.116.130.8
  • Heading
    H1: 2, H2: 0, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    16 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    ♥ myFlirt: flirt, chat, find friends - everything for free
  • Meta Keyword
    Online dating, Flirt, Personal ads, Singles, Online dating agency
  • Meta Description
    On myFlirt you can flirt and find new people in your area. Everything is for free. Just sign up now.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    62.116.130.8
  • Domain Age
    13 Years, 0 Months, 29 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • date: Fri, 22 Feb 2013 08:42:10 GMT
  • server: Apache
  • vary: Accept-Encoding
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
%
% =============
% PSI-USA, Inc.
% =============
%
% This is the PSI-USA, Inc. WHOIS server.
%
% All requests are logged.
%
% Requesting IP: 149.47.64.164
% Requesting URL: http://whois.psi-usa.info
% Requesting Object: domain myflirt.com
% Timestamp: 2012-09-10 02:28:21
%
% You can see the policy that you agree by submitting a query to this server:
% whois -h whois.psi-usa.info POLICY


domain: myflirt.com
status: LOCK
owner-c: LULU-9394897
admin-c: LULU-9394898
tech-c: LULU-10716011
zone-c: LULU-10716011
nserver: a.ns14.net
nserver: b.ns14.net
nserver: c.ns14.net
nserver: d.ns14.net
created: 2000-02-02 07:02:13
expire: 2013-02-02 07:02:13 (registry time)
changed: 2012-06-16 07:40:34

[owner-c] handle: 9394897
[owner-c] type: ORG
[owner-c] title:
[owner-c] fname: myFlirt
[owner-c] lname: GmbH
[owner-c] org: myFlirt GmbH
[owner-c] address: An den Treptowers 1
[owner-c] city: Berlin
[owner-c] pcode: 12435
[owner-c] country: DE
[owner-c] state: Berlin
[owner-c] phone: +49-700-63836743
[owner-c] fax: +49-700-63836743
[owner-c] email: email
[owner-c] protection: B
[owner-c] updated: 2012-02-27 16:16:31

[admin-c] handle: 9394898
[admin-c] type: PERSON
[admin-c] title:
[admin-c] fname: Christian
[admin-c] lname: Ermel
[admin-c] org: myFlirt GmbH
[admin-c] address: An den Treptowers 1
[admin-c] city: Berlin
[admin-c] pcode: 12435
[admin-c] country: DE
[admin-c] state: Berlin
[admin-c] phone: +49-700-63836743
[admin-c] fax: +49-700-63836743
[admin-c] email: email
[admin-c] protection: B
[admin-c] remarks: (Tel./Fax. 12,6 Cent/Min. aus dem Festnetz der Deutschen Telekom)
[admin-c] updated: 2010-10-22 14:56:46

[tech-c] handle: 10716011
[tech-c] type: ROLE
[tech-c] title:
[tech-c] fname: myFlirt
[tech-c] lname: Hostmaster
[tech-c] org: myFlirt GmbH
[tech-c] address: An den Treptowers 1
[tech-c] city: Berlin
[tech-c] pcode: 12435
[tech-c] country: DE
[tech-c] state: DE
[tech-c] phone: +49-700-63836743
[tech-c] fax: +49-700-63836743
[tech-c] email: email
[tech-c] protection: B
[tech-c] remarks: (Tel./Fax. 12,6 Cent/Min. aus dem Festnetz der Deutschen Telekom, Mobilfunk abweichend)
[tech-c] updated: 2012-02-27 16:16:31

[zone-c] handle: 10716011
[zone-c] type: ROLE
[zone-c] title:
[zone-c] fname: myFlirt
[zone-c] lname: Hostmaster
[zone-c] org: myFlirt GmbH
[zone-c] address: An den Treptowers 1
[zone-c] city: Berlin
[zone-c] pcode: 12435
[zone-c] country: DE
[zone-c] state: DE
[zone-c] phone: +49-700-63836743
[zone-c] fax: +49-700-63836743
[zone-c] email: email
[zone-c] protection: B
[zone-c] remarks: (Tel./Fax. 12,6 Cent/Min. aus dem Festnetz der Deutschen Telekom, Mobilfunk abweichend)
[zone-c] updated: 2012-02-27 16:16:31

DNS Analysis


DNS servers
a.ns14.net [62.116.131.31]
b.ns14.net [217.160.113.32]
c.ns14.net [195.34.161.195]
d.ns14.net [74.208.164.110]


DNS Records

Answer records
myflirt.com NS  a.ns14.net 86400s
myflirt.com TXT v=spf1 include:emailsrvr.com -all 86400s
myflirt.com MX
preference: 10
exchange: mx1.emailsrvr.com
1800s
myflirt.com MX
preference: 20
exchange: mx2.emailsrvr.com
1800s
myflirt.com A 62.116.130.8 600s
myflirt.com NS  d.ns14.net 86400s
myflirt.com TXT spf2.0/pra include:emailsrvr.com -all 86400s
myflirt.com SOA
server: a.ns14.net
email: noc@myflirt.com
serial: 2012112001
refresh: 39940
retry: 14400
expire: 604800
minimum ttl: 86400
86400s
myflirt.com NS  b.ns14.net 86400s
myflirt.com NS  c.ns14.net 86400s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 226 Errors
  • 215 Warnings
Ratio Text/Html
  • 0.8066347687400319
Message Error
  • Error Line 1, Column 185: element "TITLE" undefined
    …w.w3.org/1999/xhtml"> <head>    <TITLE>&#9829; myFlirt: flirt, chat, find frie…

    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 1, Column 278: there is no attribute "property"
    …g for free</TITLE>     <meta property="fb:app_id" content="179174265430387">  …

    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 1, Column 316: end tag for "meta" omitted, but OMITTAG NO was specified
    …"fb:app_id" content="179174265430387">      <meta property="og:type" content="…

    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 1, Column 263: start tag was here
    …nds - everything for free</TITLE>     <meta property="fb:app_id" content="1791…
  • Error Line 1, Column 365: end tag for "meta" omitted, but OMITTAG NO was specified
    … property="og:type" content="website">      <meta property="og:title" content=…

    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 1, Column 322: start tag was here
    …p_id" content="179174265430387">      <meta property="og:type" content="websit…
  • Error Line 1, Column 472: end tag for "meta" omitted, but OMITTAG NO was specified
    …, find friends - everything for free">     <meta property="og:description" con…

    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 1, Column 371: start tag was here
    …rty="og:type" content="website">      <meta property="og:title" content="&#982…
  • Error Line 1, Column 620: end tag for "meta" omitted, but OMITTAG NO was specified
    …thing is for free. Just sign up now.">     <meta property="og:url" content="ht…

    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 1, Column 477: start tag was here
    …d friends - everything for free">     <meta property="og:description" content=…
  • Error Line 1, Column 686: end tag for "meta" omitted, but OMITTAG NO was specified
    … content="http://www.myflirt.com/en/">   <meta name="robots" content="NOODP"> …

    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 1, Column 625: start tag was here
    … is for free. Just sign up now.">     <meta property="og:url" content="http://…
  • Error Line 1, Column 725: end tag for "meta" omitted, but OMITTAG NO was specified
    …  <meta name="robots" content="NOODP">  <meta name="google-site-verification" …

    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 1, Column 689: start tag was here
    …ntent="http://www.myflirt.com/en/">   <meta name="robots" content="NOODP">  <m…
  • Error Line 1, Column 1010: end tag for "meta" omitted, but OMITTAG NO was specified
    …, find friends - everything for free">  <meta name="description" content="On m…

    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 1, Column 916: start tag was here
    ….com/v6/grafik/myflirt200x200.png"/>  <meta name="title" content="&#9829; myFl…
  • Error Line 1, Column 1148: end tag for "meta" omitted, but OMITTAG NO was specified
    …thing is for free. Just sign up now.">  <meta name="keywords" content="Online …

    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 1, Column 1012: start tag was here
    …find friends - everything for free">  <meta name="description" content="On myF…
  • Error Line 1, Column 1248: end tag for "meta" omitted, but OMITTAG NO was specified
    …l ads, Singles, Online dating agency"> <link rel="SHORTCUT ICON" HREF="http://…

    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 1, Column 1150: start tag was here
    …ing is for free. Just sign up now.">  <meta name="keywords" content="Online da…
  • Error Line 1, Column 1280: there is no attribute "HREF"
    …ency"> <link rel="SHORTCUT ICON" HREF="http://i.myflirt.com/v6/grafik/favicon.…

    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 1, Column 1342: end tag for "link" omitted, but OMITTAG NO was specified
    …/grafik/favicon.ico" type="image/ico">  <meta http-equiv="Content-Type" conten…

    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 1, Column 1249: start tag was here
    … ads, Singles, Online dating agency"> <link rel="SHORTCUT ICON" HREF="http://i…
  • Error Line 1, Column 1411: end tag for "meta" omitted, but OMITTAG NO was specified
    …e" content="text/html; charset=UTF-8">  <meta http-equiv="content-language" co…

    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 1, Column 1344: start tag was here
    …rafik/favicon.ico" type="image/ico">  <meta http-equiv="Content-Type" content=…
  • Error Line 1, Column 1512: end tag for "meta" omitted, but OMITTAG NO was specified
    … name="robots" content="index,follow">  <link rel="stylesheet" type="text/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 1, Column 1469: start tag was here
    …content-language" content="de" />     <meta name="robots" content="index,follo…
  • Error Line 1, Column 1606: end tag for "link" omitted, but OMITTAG NO was specified
    …myflirt.com/v6/css/bootstrap.min.css"> <link rel="stylesheet" type="text/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 1, Column 1514: start tag was here
    …ame="robots" content="index,follow">  <link rel="stylesheet" type="text/css" h…
  • Error Line 1, Column 1712: end tag for "link" omitted, but OMITTAG NO was specified
    …6/css/jquery-ui-1.8.23.custom_v4.css"> <link rel="stylesheet" type="text/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 1, Column 1607: start tag was here
    …yflirt.com/v6/css/bootstrap.min.css"> <link rel="stylesheet" type="text/css" h…
  • Error Line 1, Column 1803: end tag for "link" omitted, but OMITTAG NO was specified
    …i.myflirt.com/v6/css/myflirt_v15.css"> <link rel="stylesheet" type="text/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 1, Column 1713: start tag was here
    …/css/jquery-ui-1.8.23.custom_v4.css"> <link rel="stylesheet" type="text/css" h…
  • Error Line 1, Column 1892: end tag for "link" omitted, but OMITTAG NO was specified
    …//i.myflirt.com/v6/multi/en/lang.css"> <style>.userliste .content {cursor:defa…

    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 1, Column 1804: start tag was here
    ….myflirt.com/v6/css/myflirt_v15.css"> <link rel="stylesheet" type="text/css" h…
  • Error Line 1, Column 1899: required attribute "type" not specified
    …lirt.com/v6/multi/en/lang.css"> <style>.userliste .content {cursor:default}</s…

    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 1, Column 1964: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …r:default}</style>   <script language=JavaScript src="http://i.myflirt.com/v6/…
  • Error Line 1, Column 2024: required attribute "type" not specified
    …/i.myflirt.com/v6/multi/en/lang_v1.js"></script>     <script language=JavaScri…

    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 1, Column 2056: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …v1.js"></script>     <script language=JavaScript src="http://i.myflirt.com/v6/…
  • Error Line 1, Column 2119: required attribute "type" not specified
    …myflirt.com/v6/js/jquery-1.7.2.min.js"></script>     <script language=JavaScri…

    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 1, Column 2151: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …in.js"></script>     <script language=JavaScript src="http://i.myflirt.com/v6/…
  • Error Line 1, Column 2228: required attribute "type" not specified
    …/js/jquery-ui-1.8.23.custom.min_v3.js"></script>     <script language=JavaScri…

    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 1, Column 2260: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …v3.js"></script>     <script language=JavaScript src="http://i.myflirt.com/v6/…
  • Error Line 1, Column 2320: required attribute "type" not specified
    …/i.myflirt.com/v6/js/bootstrap.min.js"></script>  <script>   staticurl = 'http…

    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 1, Column 2339: required attribute "type" not specified
    …s/bootstrap.min.js"></script>  <script>   staticurl = 'http://i.myflirt.com/v6…

    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 1, Column 2855: document type does not allow element "br" here
    …notfound = 'The city was not found.<br>&nbsp;Please choose a city from the lis…

    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 1, Column 2856: end tag for "br" omitted, but OMITTAG NO was specified
    …otfound = 'The city was not found.<br>&nbsp;Please choose a city from the list…

    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 1, Column 2852: start tag was here
    …itynotfound = 'The city was not found.<br>&nbsp;Please choose a city from the …
  • Warning Line 1, Column 3486: cannot generate system identifier for general entity "mode"
    ….com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + sessioni…

    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 1, Column 3486: general entity "mode" not defined and no default entity
    ….com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + sessioni…

    This is usually a cascading error caused by 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 1, Column 3490: reference not terminated by REFC delimiter
    …' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + sessionidful…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1, Column 3490: reference to entity "mode" for which no system identifier could be generated
    …' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + sessionidful…

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

  • Info Line 1, Column 3485: entity was defined here
    …t.com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + session…
  • Warning Line 1, Column 3894: cannot generate system identifier for general entity "loadsound"
    … == 1) {        jQuery.get('/n/inc_js&loadsound=1', function(data){           …

    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 1, Column 3894: general entity "loadsound" not defined and no default entity
    … == 1) {        jQuery.get('/n/inc_js&loadsound=1', function(data){           …

    This is usually a cascading error caused by 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 1, Column 3903: reference not terminated by REFC delimiter
    …       jQuery.get('/n/inc_js&loadsound=1', function(data){            jQuery('…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1, Column 3903: reference to entity "loadsound" for which no system identifier could be generated
    …       jQuery.get('/n/inc_js&loadsound=1', function(data){            jQuery('…

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

  • Info Line 1, Column 3893: entity was defined here
    …d == 1) {        jQuery.get('/n/inc_js&loadsound=1', function(data){          …
  • Error Line 1, Column 4220: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …;});  </script>      <script language=JavaScript src="http://i.myflirt.com/v6/…
  • Error Line 1, Column 4278: required attribute "type" not specified
    …://i.myflirt.com/v6/js/myflirt_v11.js"></SCRIPT>      <script type='text/javas…

    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 1, Column 4287: end tag for element "SCRIPT" which is not open
    …irt.com/v6/js/myflirt_v11.js"></SCRIPT>      <script type='text/javascript' sr…

    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 1, Column 4391: document type does not allow element "script" here
    …services.com/gampad/google_service.js'>  </script>  <script type='text/javascr…

    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 1, Column 4435: document type does not allow element "script" here
    …cript>  <script type='text/javascript'>  GS_googleAddAdSenseService("ca-pub-34…

    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 1, Column 4566: document type does not allow element "script" here
    …cript>  <script type='text/javascript'>  GA_googleAddSlot("ca-pub-348598695965…

    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 1, Column 4768: document type does not allow element "script" here
    …cript>  <script type='text/javascript'>  GA_googleFetchAds();  </script>      …

    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 1, Column 4842: document type does not allow element "script" here
    …        <script type="text/javascript">  var _gaq = _gaq || [];  _gaq.push(['_…

    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 1, Column 5410: end tag for "script" omitted, but OMITTAG NO was specified
    …fore(ga, s);   })();  </script> </head> <body> <div id="jQFZ"></div> <!-- nav …

    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 1, Column 4203: start tag was here
    …n() {searchlink();});  </script>      <script language=JavaScript src="http://…
  • Error Line 1, Column 5410: end tag for "head" which is not finished
    …fore(ga, s);   })();  </script> </head> <body> <div id="jQFZ"></div> <!-- nav …

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1, Column 5866: end tag for "img" omitted, but OMITTAG NO was specified
    …t" border="0" style="padding:10px"></a></div>         <div style="float:right"…

    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 1, Column 5739: start tag was here
    …/www.myflirt.com/en/" title="myFlirt"><img src="http://i.myflirt.com/v6/grafik…
  • Error Line 1, Column 5939: there is no attribute "onSubmit"
    …ight">                 <form onSubmit="login('/n/dummy&mode=profil/json/login'…

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

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

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

  • Warning Line 1, Column 5960: reference not terminated by REFC delimiter
    …  <form onSubmit="login('/n/dummy&mode=profil/json/login');return false;" clas…

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

  • Warning Line 1, Column 5960: reference to external entity in attribute value
    …  <form onSubmit="login('/n/dummy&mode=profil/json/login');return false;" clas…

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

  • Error Line 1, Column 5960: reference to entity "mode" for which no system identifier could be generated
    …  <form onSubmit="login('/n/dummy&mode=profil/json/login');return false;" clas…

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

  • Info Line 1, Column 3485: entity was defined here
    …t.com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + session…
  • Error Line 1, Column 6073: required attribute "action" not specified
    …"post" id="formlogin" name="formlogin">                 <table>               …

    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 1, Column 6316: there is no attribute "placeholder"
    …18px; margin-bottom:0px;" placeholder="Username"><br />        <input type="ch…

    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 1, Column 6327: end tag for "input" omitted, but OMITTAG NO was specified
    …n-bottom:0px;" placeholder="Username"><br />        <input type="checkbox" nam…

    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 1, Column 6198: start tag was here
    …idth:140px">                          <input type="text" name="username" class…
  • Error Line 1, Column 6391: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …"checkbox" name="al" value="1" checked> Keep me logged in       </td>         …

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 1, Column 6392: end tag for "input" omitted, but OMITTAG NO was specified
    …checkbox" name="al" value="1" checked> Keep me logged in       </td>          …

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

  • Info Line 1, Column 6341: start tag was here
    … placeholder="Username"><br />        <input type="checkbox" name="al" value="…
  • Error Line 1, Column 6630: end tag for "input" omitted, but OMITTAG NO was specified
    …n-bottom:0px;" placeholder="Password"><br />        <a href="/en/login_pass.ht…

    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 1, Column 6497: start tag was here
    …idth:120px">                          <input type="password" name="password" c…
  • Error Line 1, Column 6932: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …      <td><li class="divider-vertical"></li></td>       <td style="width:5px">…

    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 1, Column 7104: cannot generate system identifier for general entity "redirect_uri"
    …ialog/oauth?client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb…

    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 1, Column 7104: general entity "redirect_uri" not defined and no default entity
    …ialog/oauth?client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb…

    This is usually a cascading error caused by 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 1, Column 7116: reference not terminated by REFC delimiter
    …client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb_login&scope…

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

  • Warning Line 1, Column 7116: reference to external entity in attribute value
    …client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb_login&scope…

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

  • Error Line 1, Column 7116: reference to entity "redirect_uri" for which no system identifier could be generated
    …client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb_login&scope…

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

  • Info Line 1, Column 7103: entity was defined here
    …dialog/oauth?client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/f…
  • Warning Line 1, Column 7151: cannot generate system identifier for general entity "scope"
    …uri=http://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me&…

    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 1, Column 7151: general entity "scope" not defined and no default entity
    …uri=http://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me&…

    This is usually a cascading error caused by 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 1, Column 7156: reference not terminated by REFC delimiter
    …ttp://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me&respo…

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

  • Warning Line 1, Column 7156: reference to external entity in attribute value
    …ttp://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me&respo…

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

  • Error Line 1, Column 7156: reference to entity "scope" for which no system identifier could be generated
    …ttp://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me&respo…

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

  • Info Line 1, Column 7150: entity was defined here
    …_uri=http://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me…
  • Warning Line 1, Column 7191: cannot generate system identifier for general entity "response_type"
    …ope=email,user_birthday,user_about_me&response_type=token&display=popup', '450…

    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 1, Column 7191: general entity "response_type" not defined and no default entity
    …ope=email,user_birthday,user_about_me&response_type=token&display=popup', '450…

    This is usually a cascading error caused by 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 1, Column 7204: reference not terminated by REFC delimiter
    …r_birthday,user_about_me&response_type=token&display=popup', '450', '300');" c…

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

  • Warning Line 1, Column 7204: reference to external entity in attribute value
    …r_birthday,user_about_me&response_type=token&display=popup', '450', '300');" c…

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

  • Error Line 1, Column 7204: reference to entity "response_type" for which no system identifier could be generated
    …r_birthday,user_about_me&response_type=token&display=popup', '450', '300');" c…

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

  • Info Line 1, Column 7190: entity was defined here
    …cope=email,user_birthday,user_about_me&response_type=token&display=popup', '45…
  • Warning Line 1, Column 7211: cannot generate system identifier for general entity "display"
    …day,user_about_me&response_type=token&display=popup', '450', '300');" class="b…

    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 1, Column 7211: general entity "display" not defined and no default entity
    …day,user_about_me&response_type=token&display=popup', '450', '300');" class="b…

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

  • Warning Line 1, Column 7218: reference not terminated by REFC delimiter
    …r_about_me&response_type=token&display=popup', '450', '300');" class="btn-fb 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 1, Column 7218: reference to external entity in attribute value
    …r_about_me&response_type=token&display=popup', '450', '300');" class="btn-fb 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 1, Column 7218: reference to entity "display" for which no system identifier could be generated
    …r_about_me&response_type=token&display=popup', '450', '300');" class="btn-fb 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 1, Column 7210: entity was defined here
    …hday,user_about_me&response_type=token&display=popup', '450', '300');" class="…
  • Error Line 1, Column 7436: there is no attribute "data-toggle"
    …" class="dropdown-toggle" data-toggle="dropdown">Language<b class="caret"></b>…

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

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

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

  • Warning Line 1, Column 7606: cannot generate system identifier for general entity "pid"
    …                <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>        …

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

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

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

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

  • Error Line 1, Column 7606: general entity "pid" not defined and no default entity
    …                <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>        …

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

  • Warning Line 1, Column 7609: reference not terminated by REFC delimiter
    …             <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>           …

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

  • Warning Line 1, Column 7609: reference to external entity in attribute value
    …             <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>           …

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

  • Error Line 1, Column 7609: reference to entity "pid" for which no system identifier could be generated
    …             <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>           …

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 7611: cannot generate system identifier for general entity "kid"
    …           <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>             …

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

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

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

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

  • Error Line 1, Column 7611: general entity "kid" not defined and no default entity
    …           <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>             …

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

  • Warning Line 1, Column 7614: reference not terminated by REFC delimiter
    …        <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                …

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

  • Warning Line 1, Column 7614: reference to external entity in attribute value
    …        <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                …

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

  • Error Line 1, Column 7614: reference to entity "kid" for which no system identifier could be generated
    …        <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                …

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 7616: cannot generate system identifier for general entity "lid"
    …      <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                  …

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

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

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

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

  • Error Line 1, Column 7616: general entity "lid" not defined and no default entity
    …      <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                  …

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

  • Warning Line 1, Column 7619: reference not terminated by REFC delimiter
    …   <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                     …

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

  • Warning Line 1, Column 7619: reference to external entity in attribute value
    …   <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                     …

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

  • Error Line 1, Column 7619: reference to entity "lid" for which no system identifier could be generated
    …   <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                     …

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

  • Info Line 1, Column 7615: entity was defined here
    …       <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                 …
  • Warning Line 1, Column 7704: reference not terminated by REFC delimiter
    …             <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>          …

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

  • Warning Line 1, Column 7704: reference to external entity in attribute value
    …             <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>          …

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

  • Error Line 1, Column 7704: reference to entity "pid" for which no system identifier could be generated
    …             <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>          …

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 7709: reference not terminated by REFC delimiter
    …        <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>               …

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

  • Warning Line 1, Column 7709: reference to external entity in attribute value
    …        <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>               …

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

  • Error Line 1, Column 7709: reference to entity "kid" for which no system identifier could be generated
    …        <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>               …

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 7714: reference not terminated by REFC delimiter
    …   <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>                    …

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

  • Warning Line 1, Column 7714: reference to external entity in attribute value
    …   <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>                    …

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

  • Error Line 1, Column 7714: reference to entity "lid" for which no system identifier could be generated
    …   <li><a href="/n/index&pid=&kid=&lid=2">English</a></li>                    …

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

  • Info Line 1, Column 7615: entity was defined here
    …       <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                 …
  • Error Line 1, Column 8143: required attribute "type" not specified
    …tive -->  <!-- versions -->     <style>  .index_gast_content {   background-im…

    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 1, Column 8143: document type does not allow element "style" here
    …tive -->  <!-- versions -->     <style>  .index_gast_content {   background-im…

    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 1, Column 8742: reference not terminated by REFC delimiter
    …client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb_signup&scop…

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

  • Warning Line 1, Column 8742: reference to external entity in attribute value
    …client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb_signup&scop…

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

  • Error Line 1, Column 8742: reference to entity "redirect_uri" for which no system identifier could be generated
    …client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/fb_signup&scop…

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

  • Info Line 1, Column 7103: entity was defined here
    …dialog/oauth?client_id=179174265430387&redirect_uri=http://www.myflirt.com/n/f…
  • Warning Line 1, Column 8783: reference not terminated by REFC delimiter
    …tp://www.myflirt.com/n/fb_signup&scope=email,publish_actions,user_birthday,use…

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

  • Warning Line 1, Column 8783: reference to external entity in attribute value
    …tp://www.myflirt.com/n/fb_signup&scope=email,publish_actions,user_birthday,use…

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

  • Error Line 1, Column 8783: reference to entity "scope" for which no system identifier could be generated
    …tp://www.myflirt.com/n/fb_signup&scope=email,publish_actions,user_birthday,use…

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

  • Info Line 1, Column 7150: entity was defined here
    …_uri=http://www.myflirt.com/n/fb_login&scope=email,user_birthday,user_about_me…
  • Warning Line 1, Column 8847: reference not terminated by REFC delimiter
    …r_birthday,user_about_me&response_type=token&display=popup', '450', '300');" c…

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

  • Warning Line 1, Column 8847: reference to external entity in attribute value
    …r_birthday,user_about_me&response_type=token&display=popup', '450', '300');" c…

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

  • Error Line 1, Column 8847: reference to entity "response_type" for which no system identifier could be generated
    …r_birthday,user_about_me&response_type=token&display=popup', '450', '300');" c…

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

  • Info Line 1, Column 7190: entity was defined here
    …cope=email,user_birthday,user_about_me&response_type=token&display=popup', '45…
  • Warning Line 1, Column 8861: reference not terminated by REFC delimiter
    …r_about_me&response_type=token&display=popup', '450', '300');" class="btn-fb">…

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

  • Warning Line 1, Column 8861: reference to external entity in attribute value
    …r_about_me&response_type=token&display=popup', '450', '300');" class="btn-fb">…

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

  • Error Line 1, Column 8861: reference to entity "display" for which no system identifier could be generated
    …r_about_me&response_type=token&display=popup', '450', '300');" class="btn-fb">…

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

  • Info Line 1, Column 7210: entity was defined here
    …hday,user_about_me&response_type=token&display=popup', '450', '300');" class="…
  • Warning Line 1, Column 9141: reference not terminated by REFC delimiter
    … <form onSubmit="signup('/n/dummy&mode=profil/json/signup');return false;" cla…

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

  • Warning Line 1, Column 9141: reference to external entity in attribute value
    … <form onSubmit="signup('/n/dummy&mode=profil/json/signup');return false;" cla…

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

  • Error Line 1, Column 9141: reference to entity "mode" for which no system identifier could be generated
    … <form onSubmit="signup('/n/dummy&mode=profil/json/signup');return false;" cla…

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

  • Info Line 1, Column 3485: entity was defined here
    …t.com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + session…
  • Error Line 1, Column 9241: required attribute "action" not specified
    …d="formsignupurl" name="formsignupurl">           <input type="hidden" name="k…

    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 1, Column 9572: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>                         <input type=text name="username" style="width:232px"…
  • Error Line 1, Column 9641: there is no attribute "data-content"
    …th:232px" maxlength="20" data-content="Required<br>(no special character)" dat…

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

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

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

  • Warning Line 1, Column 9650: character "<" is the first character of a delimiter but occurred as data
    … maxlength="20" data-content="Required<br>(no special character)" data-content…

    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 1, Column 9705: there is no attribute "data-content-usernameexist"
    …haracter)" data-content-usernameexist="This username already exists" rel="popo…

    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 1, Column 9740: there is no attribute "rel"
    …st="This username already exists" rel="popover" id="username">                …

    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 1, Column 9764: end tag for "input" omitted, but OMITTAG NO was specified
    …y exists" rel="popover" id="username">                     </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 1, Column 9560: start tag was here
    …rols signup">                         <input type=text name="username" style="…
  • Error Line 1, Column 10047: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>                         <input type=password name="password" style="width:23…
  • Warning Line 1, Column 10129: character "<" is the first character of a delimiter but occurred as data
    … maxlength="20" data-content="Required<br>(at least 6 characters)" data-conten…

    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 1, Column 10194: there is no attribute "data-content-failusernameeqpassword"
    …" data-content-failusernameeqpassword="The password and your username must not…

    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 1, Column 10277: end tag for "input" omitted, but OMITTAG NO was specified
    …he same!" rel="popover" id="password">                     </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 1, Column 10035: start tag was here
    …rols signup">                         <input type=password name="password" sty…
  • Error Line 1, Column 10557: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>                         <input type=text name="email" style="width:232px" ma…
  • Warning Line 1, Column 10633: character "<" is the first character of a delimiter but occurred as data
    …maxlength="250" data-content="Required<br>(valid email address)" data-content-…

    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 1, Column 10689: there is no attribute "data-content-failemailexists"
    …ddress)" data-content-failemailexists="The email address is not allowed (anymo…

    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 1, Column 10760: end tag for "input" omitted, but OMITTAG NO was specified
    … (anymore)!" rel="popover" id="email">                     </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 1, Column 10545: start tag was here
    …rols signup">                         <input type=text name="email" style="wid…
  • Error Line 1, Column 11068: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>                         <input type=text name="firstname" style="width:232px…
  • Error Line 1, Column 11179: end tag for "input" omitted, but OMITTAG NO was specified
    …equired" rel="popover" id="firstname">                     </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 1, Column 11056: start tag was here
    …rols signup">                         <input type=text name="firstname" style=…
  • Error Line 1, Column 11771: end tag for "input" omitted, but OMITTAG NO was specified
    …data-content="Required" rel="popover">                          <br />&nbsp;<s…

    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 1, Column 11658: start tag was here
    …" value="" />                         <input type="text" name="city" id="inser…
  • Error Line 1, Column 12342: there is no attribute "data-content"
    …e="width:68px" id="bday" data-content="Required" rel="popover">               …

    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 1, Column 12357: there is no attribute "rel"
    …id="bday" data-content="Required" rel="popover">                             <…

    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 1, Column 14170: there is no attribute "data-content-failage"
    …ntent="Required" data-content-failage="You must be at least 16 years old for s…

    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 1, Column 17595: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                          <input type=radio name="gender" value="1" style="mar…
  • Error Line 1, Column 17668: end tag for "input" omitted, but OMITTAG NO was specified
    …="margin-top:0px; margin-left:-17px;"> <span class="icon_form user">Man</span>…

    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 1, Column 17583: start tag was here
    … signup">                             <input type=radio name="gender" value="1…
  • Error Line 1, Column 17836: there is no attribute "data-content"
    …gnup" id="genderpopover" data-content="Required" rel="popover">               …

    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 1, Column 17851: there is no attribute "rel"
    …rpopover" data-content="Required" rel="popover">                             <…

    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 1, Column 17902: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                          <input type=radio name="gender" value="2" style="mar…
  • Error Line 1, Column 17955: end tag for "input" omitted, but OMITTAG NO was specified
    …der" value="2" style="margin-top:0px"> <span class="icon_form girl">Women</spa…

    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 1, Column 17890: start tag was here
    …popover">                             <input type=radio name="gender" value="2…
  • Error Line 1, Column 18409: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                          <input type=radio name="category" value="2" style="m…
  • Error Line 1, Column 18484: end tag for "input" omitted, but OMITTAG NO was specified
    …="margin-top:0px; margin-left:-17px;"> <span class="icon_form user">Man</span>…

    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 1, Column 18397: start tag was here
    … signup">                             <input type=radio name="category" value=…
  • Error Line 1, Column 18720: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                          <input type=radio name="category" value="1" style="m…
  • Error Line 1, Column 18776: end tag for "input" omitted, but OMITTAG NO was specified
    …ry" value="1" style="margin-top:0px;"> <span class="icon_form girl">Women</spa…

    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 1, Column 18708: start tag was here
    …popover">                             <input type=radio name="category" value=…
  • Error Line 1, Column 19897: end tag for "input" omitted, but OMITTAG NO was specified
    …lass="btn btn-success btn-large"></div>                     <div class="none" …

    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 1, Column 19788: start tag was here
    …               <div id="button_step1"><input type="button" onclick="validate_s…
  • Error Line 1, Column 20084: end tag for "input" omitted, but OMITTAG NO was specified
    …lass="btn btn-success btn-large"></div>                                 <div c…

    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 1, Column 19955: start tag was here
    …  <div class="none" id="button_step2"><input type="button" onclick="validate_s…
  • Warning Line 1, Column 20776: cannot generate system identifier for general entity "profil"
    …64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCo…

    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 1, Column 20776: general entity "profil" not defined and no default entity
    …64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCo…

    This is usually a cascading error caused by 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 1, Column 20782: reference not terminated by REFC delimiter
    …5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('…

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

  • Warning Line 1, Column 20782: reference to external entity in attribute value
    …5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('…

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

  • Error Line 1, Column 20782: reference to entity "profil" for which no system identifier could be generated
    …5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 20794: reference not terminated by REFC delimiter
    …href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda6…

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

  • Warning Line 1, Column 20794: reference to external entity in attribute value
    …href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda6…

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

  • Error Line 1, Column 20794: reference to entity "kid" for which no system identifier could be generated
    …href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda6…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 20799: reference not terminated by REFC delimiter
    …"/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda69', (…

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

  • Warning Line 1, Column 20799: reference to external entity in attribute value
    …"/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda69', (…

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

  • Error Line 1, Column 20799: reference to entity "pid" for which no system identifier could be generated
    …"/n/profil_off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda69', (…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Error Line 1, Column 20810: there is no attribute "onClick"
    …off&profil=linda69&kid=&pid=" onClick="SetCookie('lp', 'linda69', (1000 * 3600…

    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 1, Column 20876: there is no attribute "onMouseOver"
    …(1000 * 3600 * 24 * 7));" onMouseOver="jQOL('<b>linda69</b>, 30 Jahre<br><img …

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

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

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

  • Warning Line 1, Column 20883: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>linda69</b>, 30 Jahre<br><img src=htt…

    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 1, Column 20893: character "<" is the first character of a delimiter but occurred as data
    … * 7));" onMouseOver="jQOL('<b>linda69</b>, 30 Jahre<br><img src=http://i.myfl…

    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 1, Column 20907: character "<" is the first character of a delimiter but occurred as data
    …seOver="jQOL('<b>linda69</b>, 30 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 20911: character "<" is the first character of a delimiter but occurred as data
    …er="jQOL('<b>linda69</b>, 30 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 21143: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 21160: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 21164: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 21069: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 21389: reference not terminated by REFC delimiter
    …7.jpg);"><a href="/n/profil_off&profil=smilewink32&kid=&pid=" onClick="SetCook…

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

  • Warning Line 1, Column 21389: reference to external entity in attribute value
    …7.jpg);"><a href="/n/profil_off&profil=smilewink32&kid=&pid=" onClick="SetCook…

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

  • Error Line 1, Column 21389: reference to entity "profil" for which no system identifier could be generated
    …7.jpg);"><a href="/n/profil_off&profil=smilewink32&kid=&pid=" onClick="SetCook…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 21405: reference not terminated by REFC delimiter
    …="/n/profil_off&profil=smilewink32&kid=&pid=" onClick="SetCookie('lp', 'smilew…

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

  • Warning Line 1, Column 21405: reference to external entity in attribute value
    …="/n/profil_off&profil=smilewink32&kid=&pid=" onClick="SetCookie('lp', 'smilew…

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

  • Error Line 1, Column 21405: reference to entity "kid" for which no system identifier could be generated
    …="/n/profil_off&profil=smilewink32&kid=&pid=" onClick="SetCookie('lp', 'smilew…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 21410: reference not terminated by REFC delimiter
    …profil_off&profil=smilewink32&kid=&pid=" onClick="SetCookie('lp', 'smilewink32…

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

  • Warning Line 1, Column 21410: reference to external entity in attribute value
    …profil_off&profil=smilewink32&kid=&pid=" onClick="SetCookie('lp', 'smilewink32…

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

  • Error Line 1, Column 21410: reference to entity "pid" for which no system identifier could be generated
    …profil_off&profil=smilewink32&kid=&pid=" onClick="SetCookie('lp', 'smilewink32…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 21498: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>smilewink32</b>, 33 Jahre<br><img src…

    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 1, Column 21512: character "<" is the first character of a delimiter but occurred as data
    …));" onMouseOver="jQOL('<b>smilewink32</b>, 33 Jahre<br><img src=http://i.myfl…

    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 1, Column 21526: character "<" is the first character of a delimiter but occurred as data
    …er="jQOL('<b>smilewink32</b>, 33 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 21530: character "<" is the first character of a delimiter but occurred as data
    …jQOL('<b>smilewink32</b>, 33 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 21762: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 21779: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 21783: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 21688: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 22008: reference not terminated by REFC delimiter
    …4.jpg);"><a href="/n/profil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCoo…

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

  • Warning Line 1, Column 22008: reference to external entity in attribute value
    …4.jpg);"><a href="/n/profil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCoo…

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

  • Error Line 1, Column 22008: reference to entity "profil" for which no system identifier could be generated
    …4.jpg);"><a href="/n/profil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCoo…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 22025: reference not terminated by REFC delimiter
    …"/n/profil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCookie('lp', 'unique…

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

  • Warning Line 1, Column 22025: reference to external entity in attribute value
    …"/n/profil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCookie('lp', 'unique…

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

  • Error Line 1, Column 22025: reference to entity "kid" for which no system identifier could be generated
    …"/n/profil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCookie('lp', 'unique…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 22030: reference not terminated by REFC delimiter
    …rofil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCookie('lp', 'uniquejulie…

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

  • Warning Line 1, Column 22030: reference to external entity in attribute value
    …rofil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCookie('lp', 'uniquejulie…

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

  • Error Line 1, Column 22030: reference to entity "pid" for which no system identifier could be generated
    …rofil_off&profil=uniquejuliet&kid=&pid=" onClick="SetCookie('lp', 'uniquejulie…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 22119: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>uniquejuliet</b>, 32 Jahre<br><img sr…

    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 1, Column 22134: character "<" is the first character of a delimiter but occurred as data
    …);" onMouseOver="jQOL('<b>uniquejuliet</b>, 32 Jahre<br><img src=http://i.myfl…

    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 1, Column 22148: character "<" is the first character of a delimiter but occurred as data
    …r="jQOL('<b>uniquejuliet</b>, 32 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 22152: character "<" is the first character of a delimiter but occurred as data
    …QOL('<b>uniquejuliet</b>, 32 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 22384: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 22401: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 22405: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 22310: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 22630: reference not terminated by REFC delimiter
    …3.jpg);"><a href="/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('…

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

  • Warning Line 1, Column 22630: reference to external entity in attribute value
    …3.jpg);"><a href="/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('…

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

  • Error Line 1, Column 22630: reference to entity "profil" for which no system identifier could be generated
    …3.jpg);"><a href="/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 22642: reference not terminated by REFC delimiter
    …href="/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('lp', 'faithm…

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

  • Warning Line 1, Column 22642: reference to external entity in attribute value
    …href="/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('lp', 'faithm…

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

  • Error Line 1, Column 22642: reference to entity "kid" for which no system identifier could be generated
    …href="/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('lp', 'faithm…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 22647: reference not terminated by REFC delimiter
    …"/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('lp', 'faithm2', (…

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

  • Warning Line 1, Column 22647: reference to external entity in attribute value
    …"/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('lp', 'faithm2', (…

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

  • Error Line 1, Column 22647: reference to entity "pid" for which no system identifier could be generated
    …"/n/profil_off&profil=faithm2&kid=&pid=" onClick="SetCookie('lp', 'faithm2', (…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 22731: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>faithm2</b>, 27 Jahre<br><img src=htt…

    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 1, Column 22741: character "<" is the first character of a delimiter but occurred as data
    … * 7));" onMouseOver="jQOL('<b>faithm2</b>, 27 Jahre<br><img src=http://i.myfl…

    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 1, Column 22755: character "<" is the first character of a delimiter but occurred as data
    …seOver="jQOL('<b>faithm2</b>, 27 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 22759: character "<" is the first character of a delimiter but occurred as data
    …er="jQOL('<b>faithm2</b>, 27 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 22991: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 23008: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 23012: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 22917: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 23237: reference not terminated by REFC delimiter
    …E.jpg);"><a href="/n/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 23237: reference to external entity in attribute value
    …E.jpg);"><a href="/n/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 23237: reference to entity "profil" for which no system identifier could be generated
    …E.jpg);"><a href="/n/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 23252: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCookie('lp', 'rosema…

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

  • Warning Line 1, Column 23252: reference to external entity in attribute value
    …f="/n/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCookie('lp', 'rosema…

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

  • Error Line 1, Column 23252: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCookie('lp', 'rosema…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 23257: reference not terminated by REFC delimiter
    …/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCookie('lp', 'rosemary62'…

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

  • Warning Line 1, Column 23257: reference to external entity in attribute value
    …/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCookie('lp', 'rosemary62'…

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

  • Error Line 1, Column 23257: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=rosemary62&kid=&pid=" onClick="SetCookie('lp', 'rosemary62'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 23344: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>rosemary62</b>, 27 Jahre<br><img src=…

    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 1, Column 23357: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>rosemary62</b>, 27 Jahre<br><img src=http://i.myfl…

    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 1, Column 23371: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>rosemary62</b>, 27 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 23375: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>rosemary62</b>, 27 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 23607: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 23624: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 23628: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 23533: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 23853: reference not terminated by REFC delimiter
    …6.jpg);"><a href="/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie(…

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

  • Warning Line 1, Column 23853: reference to external entity in attribute value
    …6.jpg);"><a href="/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie(…

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

  • Error Line 1, Column 23853: reference to entity "profil" for which no system identifier could be generated
    …6.jpg);"><a href="/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie(…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 23866: reference not terminated by REFC delimiter
    …ref="/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie('lp', 'jslove…

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

  • Warning Line 1, Column 23866: reference to external entity in attribute value
    …ref="/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie('lp', 'jslove…

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

  • Error Line 1, Column 23866: reference to entity "kid" for which no system identifier could be generated
    …ref="/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie('lp', 'jslove…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 23871: reference not terminated by REFC delimiter
    …/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie('lp', 'jslove06', …

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

  • Warning Line 1, Column 23871: reference to external entity in attribute value
    …/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie('lp', 'jslove06', …

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

  • Error Line 1, Column 23871: reference to entity "pid" for which no system identifier could be generated
    …/n/profil_off&profil=jslove06&kid=&pid=" onClick="SetCookie('lp', 'jslove06', …

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 23956: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>jslove06</b>, 31 Jahre<br><img src=ht…

    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 1, Column 23967: character "<" is the first character of a delimiter but occurred as data
    …* 7));" onMouseOver="jQOL('<b>jslove06</b>, 31 Jahre<br><img src=http://i.myfl…

    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 1, Column 23981: character "<" is the first character of a delimiter but occurred as data
    …eOver="jQOL('<b>jslove06</b>, 31 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 23985: character "<" is the first character of a delimiter but occurred as data
    …r="jQOL('<b>jslove06</b>, 31 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 24217: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 24234: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 24238: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 24143: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 24463: reference not terminated by REFC delimiter
    …C.jpg);"><a href="/n/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 24463: reference to external entity in attribute value
    …C.jpg);"><a href="/n/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 24463: reference to entity "profil" for which no system identifier could be generated
    …C.jpg);"><a href="/n/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 24478: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCookie('lp', 'sofia1…

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

  • Warning Line 1, Column 24478: reference to external entity in attribute value
    …f="/n/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCookie('lp', 'sofia1…

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

  • Error Line 1, Column 24478: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCookie('lp', 'sofia1…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 24483: reference not terminated by REFC delimiter
    …/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCookie('lp', 'sofia11111'…

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

  • Warning Line 1, Column 24483: reference to external entity in attribute value
    …/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCookie('lp', 'sofia11111'…

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

  • Error Line 1, Column 24483: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=sofia11111&kid=&pid=" onClick="SetCookie('lp', 'sofia11111'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 24570: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>sofia11111</b>, 27 Jahre<br><img src=…

    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 1, Column 24583: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>sofia11111</b>, 27 Jahre<br><img src=http://i.myfl…

    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 1, Column 24597: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>sofia11111</b>, 27 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 24601: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>sofia11111</b>, 27 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 24833: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 24850: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 24854: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 24759: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 25079: reference not terminated by REFC delimiter
    …8.jpg);"><a href="/n/profil_off&profil=cassandra2012&kid=&pid=" onClick="SetCo…

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

  • Warning Line 1, Column 25079: reference to external entity in attribute value
    …8.jpg);"><a href="/n/profil_off&profil=cassandra2012&kid=&pid=" onClick="SetCo…

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

  • Error Line 1, Column 25079: reference to entity "profil" for which no system identifier could be generated
    …8.jpg);"><a href="/n/profil_off&profil=cassandra2012&kid=&pid=" onClick="SetCo…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 25097: reference not terminated by REFC delimiter
    …/n/profil_off&profil=cassandra2012&kid=&pid=" onClick="SetCookie('lp', 'cassan…

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

  • Warning Line 1, Column 25097: reference to external entity in attribute value
    …/n/profil_off&profil=cassandra2012&kid=&pid=" onClick="SetCookie('lp', 'cassan…

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

  • Error Line 1, Column 25097: reference to entity "kid" for which no system identifier could be generated
    …/n/profil_off&profil=cassandra2012&kid=&pid=" onClick="SetCookie('lp', 'cassan…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 25102: reference not terminated by REFC delimiter
    …ofil_off&profil=cassandra2012&kid=&pid=" onClick="SetCookie('lp', 'cassandra20…

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

  • Warning Line 1, Column 25102: reference to external entity in attribute value
    …ofil_off&profil=cassandra2012&kid=&pid=" onClick="SetCookie('lp', 'cassandra20…

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

  • Error Line 1, Column 25102: reference to entity "pid" for which no system identifier could be generated
    …ofil_off&profil=cassandra2012&kid=&pid=" onClick="SetCookie('lp', 'cassandra20…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 25192: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>cassandra2012</b>, 34 Jahre<br><img s…

    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 1, Column 25208: character "<" is the first character of a delimiter but occurred as data
    …;" onMouseOver="jQOL('<b>cassandra2012</b>, 34 Jahre<br><img src=http://i.myfl…

    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 1, Column 25222: character "<" is the first character of a delimiter but occurred as data
    …="jQOL('<b>cassandra2012</b>, 34 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 25226: character "<" is the first character of a delimiter but occurred as data
    …OL('<b>cassandra2012</b>, 34 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 25458: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 25475: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 25479: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 25384: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 25704: reference not terminated by REFC delimiter
    …B.jpg);"><a href="/n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie…

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

  • Warning Line 1, Column 25704: reference to external entity in attribute value
    …B.jpg);"><a href="/n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie…

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

  • Error Line 1, Column 25704: reference to entity "profil" for which no system identifier could be generated
    …B.jpg);"><a href="/n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 25718: reference not terminated by REFC delimiter
    …ef="/n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie('lp', 'carlos…

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

  • Warning Line 1, Column 25718: reference to external entity in attribute value
    …ef="/n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie('lp', 'carlos…

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

  • Error Line 1, Column 25718: reference to entity "kid" for which no system identifier could be generated
    …ef="/n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie('lp', 'carlos…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 25723: reference not terminated by REFC delimiter
    …n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie('lp', 'carlostan',…

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

  • Warning Line 1, Column 25723: reference to external entity in attribute value
    …n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie('lp', 'carlostan',…

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

  • Error Line 1, Column 25723: reference to entity "pid" for which no system identifier could be generated
    …n/profil_off&profil=carlostan&kid=&pid=" onClick="SetCookie('lp', 'carlostan',…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 25809: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>carlostan</b>, 58 Jahre<br><img src=h…

    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 1, Column 25821: character "<" is the first character of a delimiter but occurred as data
    … 7));" onMouseOver="jQOL('<b>carlostan</b>, 58 Jahre<br><img src=http://i.myfl…

    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 1, Column 25835: character "<" is the first character of a delimiter but occurred as data
    …Over="jQOL('<b>carlostan</b>, 58 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 25839: character "<" is the first character of a delimiter but occurred as data
    …="jQOL('<b>carlostan</b>, 58 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 26071: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 26088: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 26092: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 25997: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 26317: reference not terminated by REFC delimiter
    …B.jpg);"><a href="/n/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 26317: reference to external entity in attribute value
    …B.jpg);"><a href="/n/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 26317: reference to entity "profil" for which no system identifier could be generated
    …B.jpg);"><a href="/n/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 26332: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCookie('lp', 'Aarona…

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

  • Warning Line 1, Column 26332: reference to external entity in attribute value
    …f="/n/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCookie('lp', 'Aarona…

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

  • Error Line 1, Column 26332: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCookie('lp', 'Aarona…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 26337: reference not terminated by REFC delimiter
    …/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCookie('lp', 'Aaronadams'…

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

  • Warning Line 1, Column 26337: reference to external entity in attribute value
    …/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCookie('lp', 'Aaronadams'…

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

  • Error Line 1, Column 26337: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=Aaronadams&kid=&pid=" onClick="SetCookie('lp', 'Aaronadams'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 26424: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>Aaronadams</b>, 48 Jahre<br><img src=…

    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 1, Column 26437: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>Aaronadams</b>, 48 Jahre<br><img src=http://i.myfl…

    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 1, Column 26451: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>Aaronadams</b>, 48 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 26455: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>Aaronadams</b>, 48 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 26687: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 26704: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 26708: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 26613: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 26933: reference not terminated by REFC delimiter
    …A.jpg);"><a href="/n/profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCook…

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

  • Warning Line 1, Column 26933: reference to external entity in attribute value
    …A.jpg);"><a href="/n/profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCook…

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

  • Error Line 1, Column 26933: reference to entity "profil" for which no system identifier could be generated
    …A.jpg);"><a href="/n/profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCook…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 26949: reference not terminated by REFC delimiter
    …="/n/profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCookie('lp', 'aarona…

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

  • Warning Line 1, Column 26949: reference to external entity in attribute value
    …="/n/profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCookie('lp', 'aarona…

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

  • Error Line 1, Column 26949: reference to entity "kid" for which no system identifier could be generated
    …="/n/profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCookie('lp', 'aarona…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 26954: reference not terminated by REFC delimiter
    …profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCookie('lp', 'aaronadams1…

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

  • Warning Line 1, Column 26954: reference to external entity in attribute value
    …profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCookie('lp', 'aaronadams1…

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

  • Error Line 1, Column 26954: reference to entity "pid" for which no system identifier could be generated
    …profil_off&profil=aaronadams1&kid=&pid=" onClick="SetCookie('lp', 'aaronadams1…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 27042: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>aaronadams1</b>, 48 Jahre<br><img src…

    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 1, Column 27056: character "<" is the first character of a delimiter but occurred as data
    …));" onMouseOver="jQOL('<b>aaronadams1</b>, 48 Jahre<br><img src=http://i.myfl…

    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 1, Column 27070: character "<" is the first character of a delimiter but occurred as data
    …er="jQOL('<b>aaronadams1</b>, 48 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 27074: character "<" is the first character of a delimiter but occurred as data
    …jQOL('<b>aaronadams1</b>, 48 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 27306: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 27323: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 27327: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 27232: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 27552: reference not terminated by REFC delimiter
    …B.jpg);"><a href="/n/profil_off&profil=morris9959&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 27552: reference to external entity in attribute value
    …B.jpg);"><a href="/n/profil_off&profil=morris9959&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 27552: reference to entity "profil" for which no system identifier could be generated
    …B.jpg);"><a href="/n/profil_off&profil=morris9959&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 27567: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=morris9959&kid=&pid=" onClick="SetCookie('lp', 'morris…

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

  • Warning Line 1, Column 27567: reference to external entity in attribute value
    …f="/n/profil_off&profil=morris9959&kid=&pid=" onClick="SetCookie('lp', 'morris…

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

  • Error Line 1, Column 27567: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=morris9959&kid=&pid=" onClick="SetCookie('lp', 'morris…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 27572: reference not terminated by REFC delimiter
    …/profil_off&profil=morris9959&kid=&pid=" onClick="SetCookie('lp', 'morris9959'…

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

  • Warning Line 1, Column 27572: reference to external entity in attribute value
    …/profil_off&profil=morris9959&kid=&pid=" onClick="SetCookie('lp', 'morris9959'…

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

  • Error Line 1, Column 27572: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=morris9959&kid=&pid=" onClick="SetCookie('lp', 'morris9959'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 27659: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>morris9959</b>, 42 Jahre<br><img src=…

    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 1, Column 27672: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>morris9959</b>, 42 Jahre<br><img src=http://i.myfl…

    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 1, Column 27686: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>morris9959</b>, 42 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 27690: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>morris9959</b>, 42 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 27922: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 27939: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 27943: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 27848: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 28168: reference not terminated by REFC delimiter
    …F.jpg);"><a href="/n/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 28168: reference to external entity in attribute value
    …F.jpg);"><a href="/n/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 28168: reference to entity "profil" for which no system identifier could be generated
    …F.jpg);"><a href="/n/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 28183: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCookie('lp', 'joewat…

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

  • Warning Line 1, Column 28183: reference to external entity in attribute value
    …f="/n/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCookie('lp', 'joewat…

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

  • Error Line 1, Column 28183: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCookie('lp', 'joewat…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 28188: reference not terminated by REFC delimiter
    …/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCookie('lp', 'joewatkins'…

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

  • Warning Line 1, Column 28188: reference to external entity in attribute value
    …/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCookie('lp', 'joewatkins'…

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

  • Error Line 1, Column 28188: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=joewatkins&kid=&pid=" onClick="SetCookie('lp', 'joewatkins'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 28275: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>joewatkins</b>, 48 Jahre<br><img src=…

    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 1, Column 28288: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>joewatkins</b>, 48 Jahre<br><img src=http://i.myfl…

    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 1, Column 28302: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>joewatkins</b>, 48 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 28306: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>joewatkins</b>, 48 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 28538: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 28555: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 28559: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 28464: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 28784: reference not terminated by REFC delimiter
    …C.jpg);"><a href="/n/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 28784: reference to external entity in attribute value
    …C.jpg);"><a href="/n/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 28784: reference to entity "profil" for which no system identifier could be generated
    …C.jpg);"><a href="/n/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 28799: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCookie('lp', 'david4…

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

  • Warning Line 1, Column 28799: reference to external entity in attribute value
    …f="/n/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCookie('lp', 'david4…

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

  • Error Line 1, Column 28799: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCookie('lp', 'david4…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 28804: reference not terminated by REFC delimiter
    …/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCookie('lp', 'david4kyle'…

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

  • Warning Line 1, Column 28804: reference to external entity in attribute value
    …/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCookie('lp', 'david4kyle'…

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

  • Error Line 1, Column 28804: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=david4kyle&kid=&pid=" onClick="SetCookie('lp', 'david4kyle'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 28891: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>david4kyle</b>, 45 Jahre<br><img src=…

    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 1, Column 28904: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>david4kyle</b>, 45 Jahre<br><img src=http://i.myfl…

    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 1, Column 28918: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>david4kyle</b>, 45 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 28922: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>david4kyle</b>, 45 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 29154: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 29171: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 29175: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 29080: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 29400: reference not terminated by REFC delimiter
    …9.jpg);"><a href="/n/profil_off&profil=garrisonmoores&kid=&pid=" onClick="SetC…

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

  • Warning Line 1, Column 29400: reference to external entity in attribute value
    …9.jpg);"><a href="/n/profil_off&profil=garrisonmoores&kid=&pid=" onClick="SetC…

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

  • Error Line 1, Column 29400: reference to entity "profil" for which no system identifier could be generated
    …9.jpg);"><a href="/n/profil_off&profil=garrisonmoores&kid=&pid=" onClick="SetC…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 29419: reference not terminated by REFC delimiter
    …n/profil_off&profil=garrisonmoores&kid=&pid=" onClick="SetCookie('lp', 'garris…

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

  • Warning Line 1, Column 29419: reference to external entity in attribute value
    …n/profil_off&profil=garrisonmoores&kid=&pid=" onClick="SetCookie('lp', 'garris…

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

  • Error Line 1, Column 29419: reference to entity "kid" for which no system identifier could be generated
    …n/profil_off&profil=garrisonmoores&kid=&pid=" onClick="SetCookie('lp', 'garris…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 29424: reference not terminated by REFC delimiter
    …fil_off&profil=garrisonmoores&kid=&pid=" onClick="SetCookie('lp', 'garrisonmoo…

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

  • Warning Line 1, Column 29424: reference to external entity in attribute value
    …fil_off&profil=garrisonmoores&kid=&pid=" onClick="SetCookie('lp', 'garrisonmoo…

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

  • Error Line 1, Column 29424: reference to entity "pid" for which no system identifier could be generated
    …fil_off&profil=garrisonmoores&kid=&pid=" onClick="SetCookie('lp', 'garrisonmoo…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 29515: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>garrisonmoores</b>, 54 Jahre<br><img …

    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 1, Column 29532: character "<" is the first character of a delimiter but occurred as data
    …" onMouseOver="jQOL('<b>garrisonmoores</b>, 54 Jahre<br><img src=http://i.myfl…

    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 1, Column 29546: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>garrisonmoores</b>, 54 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 29550: character "<" is the first character of a delimiter but occurred as data
    …L('<b>garrisonmoores</b>, 54 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 29782: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 29799: required attribute "alt" not specified
    … height="100" border=0 class="userpic"></a></div>              <div class="ind…

    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 1, Column 29803: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="100" border=0 class="userpic"></a></div>              <div class="index_g…

    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 1, Column 29708: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Warning Line 1, Column 30028: reference not terminated by REFC delimiter
    …5.jpg);"><a href="/n/profil_off&profil=robert2435&kid=&pid=" onClick="SetCooki…

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

  • Warning Line 1, Column 30028: reference to external entity in attribute value
    …5.jpg);"><a href="/n/profil_off&profil=robert2435&kid=&pid=" onClick="SetCooki…

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

  • Error Line 1, Column 30028: reference to entity "profil" for which no system identifier could be generated
    …5.jpg);"><a href="/n/profil_off&profil=robert2435&kid=&pid=" onClick="SetCooki…

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

  • Info Line 1, Column 20775: entity was defined here
    …B64677C5.jpg);"><a href="/n/profil_off&profil=linda69&kid=&pid=" onClick="SetC…
  • Warning Line 1, Column 30043: reference not terminated by REFC delimiter
    …f="/n/profil_off&profil=robert2435&kid=&pid=" onClick="SetCookie('lp', 'robert…

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

  • Warning Line 1, Column 30043: reference to external entity in attribute value
    …f="/n/profil_off&profil=robert2435&kid=&pid=" onClick="SetCookie('lp', 'robert…

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

  • Error Line 1, Column 30043: reference to entity "kid" for which no system identifier could be generated
    …f="/n/profil_off&profil=robert2435&kid=&pid=" onClick="SetCookie('lp', 'robert…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Warning Line 1, Column 30048: reference not terminated by REFC delimiter
    …/profil_off&profil=robert2435&kid=&pid=" onClick="SetCookie('lp', 'robert2435'…

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

  • Warning Line 1, Column 30048: reference to external entity in attribute value
    …/profil_off&profil=robert2435&kid=&pid=" onClick="SetCookie('lp', 'robert2435'…

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

  • Error Line 1, Column 30048: reference to entity "pid" for which no system identifier could be generated
    …/profil_off&profil=robert2435&kid=&pid=" onClick="SetCookie('lp', 'robert2435'…

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

  • Info Line 1, Column 7605: entity was defined here
    …                 <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>       …
  • Warning Line 1, Column 30135: character "<" is the first character of a delimiter but occurred as data
    … 3600 * 24 * 7));" onMouseOver="jQOL('<b>robert2435</b>, 50 Jahre<br><img src=…

    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 1, Column 30148: character "<" is the first character of a delimiter but occurred as data
    …7));" onMouseOver="jQOL('<b>robert2435</b>, 50 Jahre<br><img src=http://i.myfl…

    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 1, Column 30162: character "<" is the first character of a delimiter but occurred as data
    …ver="jQOL('<b>robert2435</b>, 50 Jahre<br><img src=http://i.myflirt.com/pics/p…

    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 1, Column 30166: character "<" is the first character of a delimiter but occurred as data
    …"jQOL('<b>robert2435</b>, 50 Jahre<br><img src=http://i.myflirt.com/pics/previ…

    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 1, Column 30398: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….gif" width="100" height="100" border=0 class="userpic"></a></div>            …
  • Error Line 1, Column 30415: required attribute "alt" not specified
    …gif" width="100" height="100" border=0 class="userpic"></a></div>              

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

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

  • Error Line 1, Column 30419: end tag for "img" omitted, but OMITTAG NO was specified
    …gif" width="100" height="100" border=0 class="userpic"></a></div>              

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

  • Info Line 1, Column 30324: start tag was here
    …205 height=205 border=0>');" rel="jF"><img src="http://i.myflirt.com/v6/px.gif…
  • Error Line 2, Column 222: there is no attribute "data-dismiss"
    …e="button" class="close" data-dismiss="modal">×</button>    <h3 id="chooseCity…

    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 2, Column 481: name character invalid: only S separators and TAGC allowed here
    …:left" id="geoback"></div>      </div -->  </div> <!-- countrylist -->  <!-- f…
  • Error Line 2, Column 615: end tag for element "div" which is not open
    …p"></div> <div id="foot2"></div> </div> <div id="foot3">  <div id="foot3conten…

    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 2, Column 876: end tag for "br" omitted, but OMITTAG NO was specified
    …n/support_mail.html">Contact</a>  <br><br>   &copy; 2013 myFlirt GmbH</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 2, Column 872: start tag was here
    …="/en/support_mail.html">Contact</a>  <br><br>   &copy; 2013 myFlirt GmbH</div…
  • Error Line 2, Column 880: end tag for "br" omitted, but OMITTAG NO was specified
    …pport_mail.html">Contact</a>  <br><br>   &copy; 2013 myFlirt GmbH</div> </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 2, Column 876: start tag was here
    …n/support_mail.html">Contact</a>  <br><br>   &copy; 2013 myFlirt GmbH</div> </…
  • Warning Line 2, Column 1078: reference not terminated by REFC delimiter
    …ang cookie --> <img src="/n/dummy&mode=profil/langcookie/set&lid=2" width=1 he…

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

  • Warning Line 2, Column 1078: reference to external entity in attribute value
    …ang cookie --> <img src="/n/dummy&mode=profil/langcookie/set&lid=2" width=1 he…

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

  • Error Line 2, Column 1078: reference to entity "mode" for which no system identifier could be generated
    …ang cookie --> <img src="/n/dummy&mode=profil/langcookie/set&lid=2" width=1 he…

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

  • Info Line 1, Column 3485: entity was defined here
    …t.com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + session…
  • Warning Line 2, Column 1104: reference not terminated by REFC delimiter
    …n/dummy&mode=profil/langcookie/set&lid=2" width=1 height=1> <!-- lang cookie -…

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

  • Warning Line 2, Column 1104: reference to external entity in attribute value
    …n/dummy&mode=profil/langcookie/set&lid=2" width=1 height=1> <!-- lang cookie -…

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

  • Error Line 2, Column 1104: reference to entity "lid" for which no system identifier could be generated
    …n/dummy&mode=profil/langcookie/set&lid=2" width=1 height=1> <!-- lang cookie -…

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

  • Info Line 1, Column 7615: entity was defined here
    …       <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>                 …
  • Error Line 2, Column 1114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …de=profil/langcookie/set&lid=2" width=1 height=1> <!-- lang cookie -->  <!-- k…
  • Error Line 2, Column 1123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/langcookie/set&lid=2" width=1 height=1> <!-- lang cookie -->  <!-- kid tracki…
  • Error Line 2, Column 1124: required attribute "alt" not specified
    …langcookie/set&lid=2" width=1 height=1> <!-- lang cookie -->  <!-- kid trackin…

    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 2, Column 1125: end tag for "img" omitted, but OMITTAG NO was specified
    …angcookie/set&lid=2" width=1 height=1> <!-- lang cookie -->  <!-- kid tracking…

    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 2, Column 1055: start tag was here
    …statistiken -->  <!-- lang cookie --> <img src="/n/dummy&mode=profil/langcooki…
  • Warning Line 2, Column 1200: reference not terminated by REFC delimiter
    …ing cookie --> <img src="/n/dummy&mode=orders/kidcookie/set&kid=" width=1 heig…

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

  • Warning Line 2, Column 1200: reference to external entity in attribute value
    …ing cookie --> <img src="/n/dummy&mode=orders/kidcookie/set&kid=" width=1 heig…

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

  • Error Line 2, Column 1200: reference to entity "mode" for which no system identifier could be generated
    …ing cookie --> <img src="/n/dummy&mode=orders/kidcookie/set&kid=" width=1 heig…

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

  • Info Line 1, Column 3485: entity was defined here
    …t.com' });    jQuery.getJSON("/n/dummy&mode=tele/json/newmail_check" + session…
  • Warning Line 2, Column 1225: reference not terminated by REFC delimiter
    …/n/dummy&mode=orders/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking c…

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

  • Warning Line 2, Column 1225: reference to external entity in attribute value
    …/n/dummy&mode=orders/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking c…

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

  • Error Line 2, Column 1225: reference to entity "kid" for which no system identifier could be generated
    …/n/dummy&mode=orders/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking c…

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

  • Info Line 1, Column 7610: entity was defined here
    …            <li><a href="/n/index&pid=&kid=&lid=1">German</a></li>            …
  • Error Line 2, Column 1234: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mode=orders/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking cookie -->…
  • Error Line 2, Column 1243: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rs/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking cookie -->  <!-- CO…
  • Error Line 2, Column 1244: required attribute "alt" not specified
    …s/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking cookie -->  <!-- COU…

    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 2, Column 1245: end tag for "img" omitted, but OMITTAG NO was specified
    …/kidcookie/set&kid=" width=1 height=1> <!-- kid tracking cookie -->  <!-- COUN…

    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 2, Column 1177: start tag was here
    …kie -->  <!-- kid tracking cookie --> <img src="/n/dummy&mode=orders/kidcookie…

Visitor Analysis

Daily Visitor
  • 1.820 visits
Daily Visitor