citysex.com

citysex.com has Alexa Rank 22.692 and Google Page Rank is 3

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 04:19:18  (update).

Overview Info

  • Domain Name
    citysex.com
  • Favicon
  • Alexa Rank
    #22692
  • Google Page Rank
    PR 3
  • Ip Address
    207.178.140.254
  • Page Size
    29.9 KB
  • Images
    1 GIF, 16 JPG, 14 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 0 0

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    207.178.140.254
  • Domain Age
    14 Years, 8 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache
  • vary: Accept-Encoding
  • cache-control: no-store, no-cache, must-revalidate
  • content-type: text/html; charset=iso-8859-1
  • content-encoding: gzip
  • date: Sun, 15 Sep 2013 16:19:12 GMT
  • expires: Thu, 01 Dec 2003 16:00:00 GMT
  • pragma: no-cache
  • x-cache-info: not cacheable; response specified "Cache-Control: no-store"
  • content-length: 7213
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for citysex.com

DNS Analysis


DNS servers
dns5.tncservers.net
dns6.tncservers.net


DNS Records

Answer records
citysex.com SOA
server: dns5.tncservers.net
email: admin@tncservers.net
serial: 2012042302
refresh: 3600
retry: 900
expire: 604800
minimum ttl: 300
300s
citysex.com NS  dns5.tncservers.net 300s
citysex.com NS  dns6.tncservers.net 300s
citysex.com A 207.178.140.254 300s
citysex.com MX
preference: 10
exchange: mail.citysex.com
300s
citysex.com TXT v=spf1 include:_a.2pf.net include:_b.2pf.net ~all 300s

Authority records

Additional records
dns5.tncservers.net A 207.178.141.250 7200s
dns6.tncservers.net A 207.178.143.122 7200s
mail.citysex.com A 207.178.151.25 300s

IP 207.178.140.254 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Calabasas
  • Continent Code
    91302
  • Latitude
    818
  • Longitude
    803
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 207.178.140.254"
    #
    # Use "?" to get help.
    #

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

    Trade News Corporation ISWT-207-178-140-0 (NET-207-178-140-0-1) 207.178.140.0 - 207.178.140.255
    Internet Specialties West ISWEST-BLK-1 (NET-207-178-128-0-1) 207.178.128.0 - 207.178.255.255


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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 504 Errors
  • 208 Warnings
Ratio Text/Html
  • 0.7177830003916961
Message Error
  • Error Line 17, Column 101: required attribute "alt" not specified
    …ogo"><img src="/images/CitySex/header1-logo.png" width="194" height="61" /></a>

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

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

  • Error Line 44, Column 77: required attribute "alt" not specified
    					  <img src="/images/CitySex/header1-menu.png" width="940" height="31" />

    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 46, Column 104: required attribute "alt" not specified
    …img src="/images/CitySex/header1-menu1.png" width="258" height="31" /></a></li>

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

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

  • Warning Line 47, Column 40: cannot generate system identifier for general entity "topmenu"
    …					  <li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySe…

    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 47, Column 40: general entity "topmenu" not defined and no default entity
    …					  <li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySe…

    This is usually a cascading error caused by 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 47, Column 47: reference not terminated by REFC delimiter
    …<li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySex/heade…

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

  • Warning Line 47, Column 47: reference to external entity in attribute value
    …<li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySex/heade…

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

  • Error Line 47, Column 47: reference to entity "topmenu" for which no system identifier could be generated
    …<li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySex/heade…

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

  • Info Line 47, Column 39: entity was defined here
    						  <li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySe…
  • Error Line 47, Column 126: required attribute "alt" not specified
    …img src="/images/CitySex/header1-menu2.png" width="173" height="31" /></a></li>

    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 48, Column 113: required attribute "alt" not specified
    …img src="/images/CitySex/header1-menu3.png" width="221" height="31" /></a></li>

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

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

  • Warning Line 49, Column 45: reference not terminated by REFC delimiter
    …  <li><a href="/?page=register&topmenu=free"><img src="/images/CitySex/header1…

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

  • Warning Line 49, Column 45: reference to external entity in attribute value
    …  <li><a href="/?page=register&topmenu=free"><img src="/images/CitySex/header1…

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

  • Error Line 49, Column 45: reference to entity "topmenu" for which no system identifier could be generated
    …  <li><a href="/?page=register&topmenu=free"><img src="/images/CitySex/header1…

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

  • Info Line 47, Column 39: entity was defined here
    						  <li><a href="/?page=s_result_j&topmenu=search"><img src="/images/CitySe…
  • Error Line 49, Column 122: required attribute "alt" not specified
    …img src="/images/CitySex/header1-menu4.png" width="288" height="31" /></a></li>

    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 57, Column 75: required attribute "alt" not specified
    			<img src="/images/CitySex/cities/boston.jpg" width="649" height="324" />

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

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

  • Warning Line 58, Column 28: cannot generate system identifier for general entity "home"
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…

    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 58, Column 28: general entity "home" not defined and no default entity
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…

    This is usually a cascading error caused by 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 58, Column 32: reference not terminated by REFC delimiter
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…

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

  • Warning Line 58, Column 32: reference to external entity in attribute value
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…

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

  • Error Line 58, Column 32: reference to entity "home" for which no system identifier could be generated
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Error Line 58, Column 134: required attribute "alt" not specified
    …"><img src="/images/CitySex/home-start1-bt1.png" width="240" height="32" /></a>

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

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

  • Error Line 66, Column 99: required attribute "alt" not specified
    …mg src="/images/CitySex/home-search-title.gif" width="244" height="14" /></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 67, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					<form name=preF method=post action='?home=search_b'>
  • Error Line 67, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					<form name=preF method=post action='?home=search_b'>
  • Error Line 68, Column 23: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    										<input type=hidden name='page' value='s_result_j' />
  • Error Line 72, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    							<option value=11>Couple</option><option value=10>Female</option><option …
  • Error Line 72, Column 54: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=11>Couple</option><option value=10>Female</option><option value=12>Femal…
  • Error Line 72, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=10>Female</option><option value=12>Female Couple</option><option value=9…
  • Error Line 72, Column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …2>Female Couple</option><option value=9 selected>Male</option><option value=13…
  • Error Line 72, Column 135: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …ouple</option><option value=9 selected>Male</option><option value=13>Male Coup…

    "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 72, Column 163: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=9 selected>Male</option><option value=13>Male Couple</option>							</select>
  • Error Line 76, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    							<option value=34>Couple</option><option value=33 selected>Female</option…
  • Error Line 76, Column 54: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=34>Couple</option><option value=33 selected>Female</option><option value…
  • Error Line 76, Column 65: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …uple</option><option value=33 selected>Female</option><option value=32>Male</o…

    "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 76, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=33 selected>Female</option><option value=32>Male</option>							</select>
  • Error Line 82, Column 25: document type does not allow element "div" here; assuming missing "li" start-tag
    						<div class="clear"></div>
  • Error Line 83, Column 22: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    						<li class="li5">

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

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

  • Error Line 85, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    							<option value=248>AALAND ISLANDS</option><option value=4>AFGHANISTAN</op…
  • Error Line 85, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>AALAND ISLANDS</option><option value=4>AFGHANISTAN</option><option value=8>AL…
  • Error Line 85, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=4>AFGHANISTAN</option><option value=8>ALBANIA</option><option value=12>ALGER…
  • Error Line 85, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=8>ALBANIA</option><option value=12>ALGERIA</option><option value=16>AMER…
  • Error Line 85, Column 164: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=12>ALGERIA</option><option value=16>AMERICAN SAMOA</option><option value=…
  • Error Line 85, Column 204: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>AMERICAN SAMOA</option><option value=20>ANDORRA</option><option value=24>ANGO…
  • Error Line 85, Column 237: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=20>ANDORRA</option><option value=24>ANGOLA</option><option value=660>ANGU…
  • Error Line 85, Column 269: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=24>ANGOLA</option><option value=660>ANGUILLA</option><option value=10>AN…
  • Error Line 85, Column 304: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=660>ANGUILLA</option><option value=10>ANTARCTICA</option><option value=28>A…
  • Error Line 85, Column 340: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=10>ANTARCTICA</option><option value=28>ANTIGUA AND BARBUDA</option><option v…
  • Error Line 85, Column 385: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …GUA AND BARBUDA</option><option value=32>ARGENTINA</option><option value=51>AR…
  • Error Line 85, Column 420: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=32>ARGENTINA</option><option value=51>ARMENIA</option><option value=533>ARU…
  • Error Line 85, Column 453: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=51>ARMENIA</option><option value=533>ARUBA</option><option value=36>AUSTR…
  • Error Line 85, Column 485: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=533>ARUBA</option><option value=36>AUSTRALIA</option><option value=40>AU…
  • Error Line 85, Column 520: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=36>AUSTRALIA</option><option value=40>AUSTRIA</option><option value=31>AZER…
  • Error Line 85, Column 553: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=40>AUSTRIA</option><option value=31>AZERBAIJAN</option><option value=44>B…
  • Error Line 85, Column 589: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=31>AZERBAIJAN</option><option value=44>BAHAMAS</option><option value=48>BAHR…
  • Error Line 85, Column 622: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=44>BAHAMAS</option><option value=48>BAHRAIN</option><option value=50>BANG…
  • Error Line 85, Column 655: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=48>BAHRAIN</option><option value=50>BANGLADESH</option><option value=52>B…
  • Error Line 85, Column 691: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=50>BANGLADESH</option><option value=52>BARBADOS</option><option value=112>BE…
  • Error Line 85, Column 725: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=52>BARBADOS</option><option value=112>BELARUS</option><option value=56>BEL…
  • Error Line 85, Column 759: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=112>BELARUS</option><option value=56>BELGIUM</option><option value=84>BELI…
  • Error Line 85, Column 792: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=56>BELGIUM</option><option value=84>BELIZE</option><option value=204>BENI…
  • Error Line 85, Column 824: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=84>BELIZE</option><option value=204>BENIN</option><option value=60>BERMU…
  • Error Line 85, Column 856: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=204>BENIN</option><option value=60>BERMUDA</option><option value=64>BHUT…
  • Error Line 85, Column 889: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=60>BERMUDA</option><option value=64>BHUTAN</option><option value=68>BOLIV…
  • Error Line 85, Column 921: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=64>BHUTAN</option><option value=68>BOLIVIA</option><option value=70>BOSN…
  • Error Line 85, Column 954: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=68>BOLIVIA</option><option value=70>BOSNIA AND HERZEGOWINA</option><optio…
  • Error Line 85, Column 1002: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AND HERZEGOWINA</option><option value=72>BOTSWANA</option><option value=74>BOU…
  • Error Line 85, Column 1036: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=72>BOTSWANA</option><option value=74>BOUVET ISLAND</option><option value=7…
  • Error Line 85, Column 1075: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4>BOUVET ISLAND</option><option value=76>BRAZIL</option><option value=86>BRITI…
  • Error Line 85, Column 1107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=76>BRAZIL</option><option value=86>BRITISH INDIAN OCEAN TERRITORY</optio…
  • Error Line 85, Column 1163: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …OCEAN TERRITORY</option><option value=96>BRUNEI DARUSSALAM</option><option val…
  • Error Line 85, Column 1206: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …UNEI DARUSSALAM</option><option value=100>BULGARIA</option><option value=854>B…
  • Error Line 85, Column 1241: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=100>BULGARIA</option><option value=854>BURKINA FASO</option><option value=1…
  • Error Line 85, Column 1280: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …54>BURKINA FASO</option><option value=108>BURUNDI</option><option value=116>CA…
  • Error Line 85, Column 1314: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=108>BURUNDI</option><option value=116>CAMBODIA</option><option value=120>C…
  • Error Line 85, Column 1349: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=116>CAMBODIA</option><option value=120>CAMEROON</option><option value=124>C…
  • Error Line 85, Column 1384: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=120>CAMEROON</option><option value=124>CANADA</option><option value=132>CAP…
  • Error Line 85, Column 1417: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=124>CANADA</option><option value=132>CAPE VERDE</option><option value=136…
  • Error Line 85, Column 1454: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=132>CAPE VERDE</option><option value=136>CAYMAN ISLANDS</option><option value…
  • Error Line 85, Column 1495: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>CAYMAN ISLANDS</option><option value=140>CENTRAL AFRICAN REPUBLIC</option><op…
  • Error Line 85, Column 1546: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …FRICAN REPUBLIC</option><option value=148>CHAD</option><option value=152>CHILE…
  • Error Line 85, Column 1577: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=148>CHAD</option><option value=152>CHILE</option><option value=156>CHIN…
  • Error Line 85, Column 1609: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=152>CHILE</option><option value=156>CHINA</option><option value=162>CHRI…
  • Error Line 85, Column 1641: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=156>CHINA</option><option value=162>CHRISTMAS ISLAND</option><option val…
  • Error Line 85, Column 1684: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …HRISTMAS ISLAND</option><option value=166>COCOS (KEELING) ISLANDS</option><opt…
  • Error Line 85, Column 1734: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EELING) ISLANDS</option><option value=170>COLOMBIA</option><option value=174>C…
  • Error Line 85, Column 1769: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=170>COLOMBIA</option><option value=174>COMOROS</option><option value=180>CO…
  • Error Line 85, Column 1803: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=174>COMOROS</option><option value=180>CONGO, Democratic Republic of (was Z…
  • Error Line 85, Column 1871: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … of (was Zaire)</option><option value=178>CONGO, Republic of</option><option v…
  • Error Line 85, Column 1916: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …GO, Republic of</option><option value=184>COOK ISLANDS</option><option value=1…
  • Error Line 85, Column 1955: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …84>COOK ISLANDS</option><option value=188>COSTA RICA</option><option value=384…
  • Error Line 85, Column 1992: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=188>COSTA RICA</option><option value=384>COTE D`IVOIRE</option><option value=…
  • Error Line 85, Column 2032: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4>COTE D`IVOIRE</option><option value=191>CROATIA (local name: Hrvatska)</opti…
  • Error Line 85, Column 2089: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …name: Hrvatska)</option><option value=192>CUBA</option><option value=196>CYPRU…
  • Error Line 85, Column 2120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=192>CUBA</option><option value=196>CYPRUS</option><option value=203>CZE…
  • Error Line 85, Column 2153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=196>CYPRUS</option><option value=203>CZECH REPUBLIC</option><option value…
  • Error Line 85, Column 2194: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>CZECH REPUBLIC</option><option value=208>DENMARK</option><option value=262>DJ…
  • Error Line 85, Column 2228: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=208>DENMARK</option><option value=262>DJIBOUTI</option><option value=212>D…
  • Error Line 85, Column 2263: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=262>DJIBOUTI</option><option value=212>DOMINICA</option><option value=214>D…
  • Error Line 85, Column 2298: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=212>DOMINICA</option><option value=214>DOMINICAN REPUBLIC</option><option v…
  • Error Line 85, Column 2343: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …INICAN REPUBLIC</option><option value=218>ECUADOR</option><option value=818>EG…
  • Error Line 85, Column 2377: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=218>ECUADOR</option><option value=818>EGYPT</option><option value=222>EL S…
  • Error Line 85, Column 2409: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=818>EGYPT</option><option value=222>EL SALVADOR</option><option value=22…
  • Error Line 85, Column 2447: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …222>EL SALVADOR</option><option value=226>EQUATORIAL GUINEA</option><option va…
  • Error Line 85, Column 2491: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …UATORIAL GUINEA</option><option value=232>ERITREA</option><option value=233>ES…
  • Error Line 85, Column 2525: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=232>ERITREA</option><option value=233>ESTONIA</option><option value=231>ET…
  • Error Line 85, Column 2559: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=233>ESTONIA</option><option value=231>ETHIOPIA</option><option value=238>F…
  • Error Line 85, Column 2594: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=231>ETHIOPIA</option><option value=238>FALKLAND ISLANDS (MALVINAS)</option>…
  • Error Line 85, Column 2648: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ANDS (MALVINAS)</option><option value=234>FAROE ISLANDS</option><option value=…
  • Error Line 85, Column 2688: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4>FAROE ISLANDS</option><option value=242>FIJI</option><option value=246>FINLA…
  • Error Line 85, Column 2719: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=242>FIJI</option><option value=246>FINLAND</option><option value=250>FR…
  • Error Line 85, Column 2753: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=246>FINLAND</option><option value=250>FRANCE</option><option value=254>FRE…
  • Error Line 85, Column 2786: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=250>FRANCE</option><option value=254>FRENCH GUIANA</option><option value=…
  • Error Line 85, Column 2826: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4>FRENCH GUIANA</option><option value=258>FRENCH POLYNESIA</option><option val…
  • Error Line 85, Column 2869: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …RENCH POLYNESIA</option><option value=260>FRENCH SOUTHERN TERRITORIES</option>…
  • Error Line 85, Column 2923: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ERN TERRITORIES</option><option value=266>GABON</option><option value=270>GAMB…
  • Error Line 85, Column 2955: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=266>GABON</option><option value=270>GAMBIA</option><option value=268>GEO…
  • Error Line 85, Column 2988: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=270>GAMBIA</option><option value=268>GEORGIA</option><option value=276>GE…
  • Error Line 85, Column 3022: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=268>GEORGIA</option><option value=276>GERMANY</option><option value=288>GH…
  • Error Line 85, Column 3056: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=276>GERMANY</option><option value=288>GHANA</option><option value=292>GIBR…
  • Error Line 85, Column 3088: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=288>GHANA</option><option value=292>GIBRALTAR</option><option value=300>…
  • Error Line 85, Column 3124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=292>GIBRALTAR</option><option value=300>GREECE</option><option value=304>GRE…
  • Error Line 85, Column 3157: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=300>GREECE</option><option value=304>GREENLAND</option><option value=308>…
  • Error Line 85, Column 3193: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=304>GREENLAND</option><option value=308>GRENADA</option><option value=312>GU…
  • Error Line 85, Column 3227: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=308>GRENADA</option><option value=312>GUADELOUPE</option><option value=316…
  • Error Line 85, Column 3264: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=312>GUADELOUPE</option><option value=316>GUAM</option><option value=320>GUATE…
  • Error Line 85, Column 3295: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=316>GUAM</option><option value=320>GUATEMALA</option><option value=324>…
  • Error Line 85, Column 3331: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=320>GUATEMALA</option><option value=324>GUINEA</option><option value=624>GUI…
  • Error Line 85, Column 3364: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=324>GUINEA</option><option value=624>GUINEA-BISSAU</option><option value=…
  • Error Line 85, Column 3404: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4>GUINEA-BISSAU</option><option value=328>GUYANA</option><option value=332>HAI…
  • Error Line 85, Column 3437: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=328>GUYANA</option><option value=332>HAITI</option><option value=334>HEAR…
  • Error Line 85, Column 3469: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=332>HAITI</option><option value=334>HEARD AND MC DONALD ISLANDS</option>…
  • Error Line 85, Column 3523: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … DONALD ISLANDS</option><option value=340>HONDURAS</option><option value=344>H…
  • Error Line 85, Column 3558: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=340>HONDURAS</option><option value=344>HONG KONG</option><option value=348>…
  • Error Line 85, Column 3594: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=344>HONG KONG</option><option value=348>HUNGARY</option><option value=352>IC…
  • Error Line 85, Column 3628: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=348>HUNGARY</option><option value=352>ICELAND</option><option value=356>IN…
  • Error Line 85, Column 3662: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=352>ICELAND</option><option value=356>INDIA</option><option value=360>INDO…
  • Error Line 85, Column 3694: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=356>INDIA</option><option value=360>INDONESIA</option><option value=364>…
  • Error Line 85, Column 3730: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=360>INDONESIA</option><option value=364>IRAN (ISLAMIC REPUBLIC OF)</option><…
  • Error Line 85, Column 3783: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …IC REPUBLIC OF)</option><option value=368>IRAQ</option><option value=372>IRELA…
  • Error Line 85, Column 3814: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=368>IRAQ</option><option value=372>IRELAND</option><option value=376>IS…
  • Error Line 85, Column 3848: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=372>IRELAND</option><option value=376>ISRAEL</option><option value=380>ITA…
  • Error Line 85, Column 3881: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=376>ISRAEL</option><option value=380>ITALY</option><option value=388>JAMA…
  • Error Line 85, Column 3913: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=380>ITALY</option><option value=388>JAMAICA</option><option value=392>JA…
  • Error Line 85, Column 3947: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=388>JAMAICA</option><option value=392>JAPAN</option><option value=400>JORD…
  • Error Line 85, Column 3979: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=392>JAPAN</option><option value=400>JORDAN</option><option value=398>KAZ…
  • Error Line 85, Column 4012: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=400>JORDAN</option><option value=398>KAZAKHSTAN</option><option value=404…
  • Error Line 85, Column 4049: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=398>KAZAKHSTAN</option><option value=404>KENYA</option><option value=296>KIRI…
  • Error Line 85, Column 4081: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=404>KENYA</option><option value=296>KIRIBATI</option><option value=408>K…
  • Error Line 85, Column 4116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=296>KIRIBATI</option><option value=408>KOREA, (north)</option><option value…
  • Error Line 85, Column 4157: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>KOREA, (north)</option><option value=410>KOREA, (south)</option><option value…
  • Error Line 85, Column 4198: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>KOREA, (south)</option><option value=414>KUWAIT</option><option value=417>KYR…
  • Error Line 85, Column 4231: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=414>KUWAIT</option><option value=417>KYRGYZSTAN</option><option value=418…
  • Error Line 85, Column 4268: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=417>KYRGYZSTAN</option><option value=418>LAO DEMOCRATIC REPUBLIC</option><opt…
  • Error Line 85, Column 4318: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …CRATIC REPUBLIC</option><option value=428>LATVIA</option><option value=422>LEB…
  • Error Line 85, Column 4351: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=428>LATVIA</option><option value=422>LEBANON</option><option value=426>LE…
  • Error Line 85, Column 4385: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=422>LEBANON</option><option value=426>LESOTHO</option><option value=430>LI…
  • Error Line 85, Column 4419: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=426>LESOTHO</option><option value=430>LIBERIA</option><option value=434>LI…
  • Error Line 85, Column 4453: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=430>LIBERIA</option><option value=434>LIBYAN ARAB JAMAHIRIYA</option><opti…
  • Error Line 85, Column 4502: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARAB JAMAHIRIYA</option><option value=438>LIECHTENSTEIN</option><option value=…
  • Error Line 85, Column 4542: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …8>LIECHTENSTEIN</option><option value=440>LITHUANIA</option><option value=442>…
  • Error Line 85, Column 4578: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=440>LITHUANIA</option><option value=442>LUXEMBOURG</option><option value=446…
  • Error Line 85, Column 4615: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=442>LUXEMBOURG</option><option value=446>MACAU</option><option value=807>MACE…
  • Error Line 85, Column 4647: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=446>MACAU</option><option value=807>MACEDONIA, FORMER YUGOSLAV</option><…
  • Error Line 85, Column 4700: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …FORMER YUGOSLAV</option><option value=450>MADAGASCAR</option><option value=454…
  • Error Line 85, Column 4737: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=450>MADAGASCAR</option><option value=454>MALAWI</option><option value=458>MAL…
  • Error Line 85, Column 4770: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=454>MALAWI</option><option value=458>MALAYSIA</option><option value=462>M…
  • Error Line 85, Column 4805: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=458>MALAYSIA</option><option value=462>MALDIVES</option><option value=466>M…
  • Error Line 85, Column 4840: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=462>MALDIVES</option><option value=466>MALI</option><option value=470>MALTA…
  • Error Line 85, Column 4871: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=466>MALI</option><option value=470>MALTA</option><option value=584>MARS…
  • Error Line 85, Column 4903: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=470>MALTA</option><option value=584>MARSHALL ISLANDS</option><option val…
  • Error Line 85, Column 4946: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARSHALL ISLANDS</option><option value=474>MARTINIQUE</option><option value=478…
  • Error Line 85, Column 4983: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=474>MARTINIQUE</option><option value=478>MAURITANIA</option><option value=480…
  • Error Line 85, Column 5020: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=478>MAURITANIA</option><option value=480>MAURITIUS</option><option value=175>…
  • Error Line 85, Column 5056: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=480>MAURITIUS</option><option value=175>MAYOTTE</option><option value=484>ME…
  • Error Line 85, Column 5090: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=175>MAYOTTE</option><option value=484>MEXICO</option><option value=583>MIC…
  • Error Line 85, Column 5123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=484>MEXICO</option><option value=583>MICRONESIA, FEDERATED STATES OF</opt…
  • Error Line 85, Column 5181: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …RATED STATES OF</option><option value=498>MOLDOVA, REPUBLIC OF</option><option…
  • Error Line 85, Column 5228: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …VA, REPUBLIC OF</option><option value=492>MONACO</option><option value=496>MON…
  • Error Line 85, Column 5261: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=492>MONACO</option><option value=496>MONGOLIA</option><option value=500>M…
  • Error Line 85, Column 5296: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=496>MONGOLIA</option><option value=500>MONTSERRAT</option><option value=504…
  • Error Line 85, Column 5333: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=500>MONTSERRAT</option><option value=504>MOROCCO</option><option value=508>MO…
  • Error Line 85, Column 5367: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=504>MOROCCO</option><option value=508>MOZAMBIQUE</option><option value=104…
  • Error Line 85, Column 5404: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=508>MOZAMBIQUE</option><option value=104>MYANMAR</option><option value=516>NA…
  • Error Line 85, Column 5438: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=104>MYANMAR</option><option value=516>NAMIBIA</option><option value=520>NA…
  • Error Line 85, Column 5472: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=516>NAMIBIA</option><option value=520>NAURU</option><option value=524>NEPA…
  • Error Line 85, Column 5504: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=520>NAURU</option><option value=524>NEPAL</option><option value=528>NETH…
  • Error Line 85, Column 5536: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=524>NEPAL</option><option value=528>NETHERLANDS</option><option value=53…
  • Error Line 85, Column 5574: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …528>NETHERLANDS</option><option value=530>NETHERLANDS ANTILLES</option><option…
  • Error Line 85, Column 5621: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …RLANDS ANTILLES</option><option value=540>NEW CALEDONIA</option><option value=…
  • Error Line 85, Column 5661: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0>NEW CALEDONIA</option><option value=554>NEW ZEALAND</option><option value=55…
  • Error Line 85, Column 5699: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …554>NEW ZEALAND</option><option value=558>NICARAGUA</option><option value=562>…
  • Error Line 85, Column 5735: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=558>NICARAGUA</option><option value=562>NIGER</option><option value=566>NIGE…
  • Error Line 85, Column 5767: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=562>NIGER</option><option value=566>NIGERIA</option><option value=570>NI…
  • Error Line 85, Column 5801: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=566>NIGERIA</option><option value=570>NIUE</option><option value=574>NORFO…
  • Error Line 85, Column 5832: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=570>NIUE</option><option value=574>NORFOLK ISLAND</option><option value…
  • Error Line 85, Column 5873: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>NORFOLK ISLAND</option><option value=580>NORTHERN MARIANA ISLANDS</option><op…
  • Error Line 85, Column 5924: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MARIANA ISLANDS</option><option value=578>NORWAY</option><option value=512>OMA…
  • Error Line 85, Column 5957: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=578>NORWAY</option><option value=512>OMAN</option><option value=586>PAKIS…
  • Error Line 85, Column 5988: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=512>OMAN</option><option value=586>PAKISTAN</option><option value=585>P…
  • Error Line 85, Column 6023: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=586>PAKISTAN</option><option value=585>PALAU</option><option value=275>PALE…
  • Error Line 85, Column 6055: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=585>PALAU</option><option value=275>PALESTINIAN TERRITORY, Occupied</opt…
  • Error Line 85, Column 6113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ITORY, Occupied</option><option value=591>PANAMA</option><option value=598>PAP…
  • Error Line 85, Column 6146: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=591>PANAMA</option><option value=598>PAPUA NEW GUINEA</option><option val…
  • Error Line 85, Column 6189: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …APUA NEW GUINEA</option><option value=600>PARAGUAY</option><option value=604>P…
  • Error Line 85, Column 6224: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=600>PARAGUAY</option><option value=604>PERU</option><option value=608>PHILI…
  • Error Line 85, Column 6255: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=604>PERU</option><option value=608>PHILIPPINES</option><option value=61…
  • Error Line 85, Column 6293: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …608>PHILIPPINES</option><option value=612>PITCAIRN</option><option value=616>P…
  • Error Line 85, Column 6328: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=612>PITCAIRN</option><option value=616>POLAND</option><option value=620>POR…
  • Error Line 85, Column 6361: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=616>POLAND</option><option value=620>PORTUGAL</option><option value=630>P…
  • Error Line 85, Column 6396: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=620>PORTUGAL</option><option value=630>PUERTO RICO</option><option value=63…
  • Error Line 85, Column 6434: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …630>PUERTO RICO</option><option value=634>QATAR</option><option value=638>REUN…
  • Error Line 85, Column 6466: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=634>QATAR</option><option value=638>REUNION</option><option value=642>RO…
  • Error Line 85, Column 6500: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=638>REUNION</option><option value=642>ROMANIA</option><option value=643>RU…
  • Error Line 85, Column 6534: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=642>ROMANIA</option><option value=643>RUSSIAN FEDERATION</option><option v…
  • Error Line 85, Column 6579: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …SIAN FEDERATION</option><option value=646>RWANDA</option><option value=654>SAI…
  • Error Line 85, Column 6612: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=646>RWANDA</option><option value=654>SAINT HELENA</option><option value=6…
  • Error Line 85, Column 6651: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …54>SAINT HELENA</option><option value=659>SAINT KITTS AND NEVIS</option><optio…
  • Error Line 85, Column 6699: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …KITTS AND NEVIS</option><option value=662>SAINT LUCIA</option><option value=66…
  • Error Line 85, Column 6737: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …662>SAINT LUCIA</option><option value=666>SAINT PIERRE AND MIQUELON</option><o…
  • Error Line 85, Column 6789: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …RE AND MIQUELON</option><option value=670>SAINT VINCENT AND THE GRENADINES</op…
  • Error Line 85, Column 6848: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … THE GRENADINES</option><option value=882>SAMOA</option><option value=674>SAN …
  • Error Line 85, Column 6880: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=882>SAMOA</option><option value=674>SAN MARINO</option><option value=678…
  • Error Line 85, Column 6917: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=674>SAN MARINO</option><option value=678>SAO TOME AND PRINCIPE</option><optio…
  • Error Line 85, Column 6965: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ME AND PRINCIPE</option><option value=682>SAUDI ARABIA</option><option value=6…
  • Error Line 85, Column 7004: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …82>SAUDI ARABIA</option><option value=686>SENEGAL</option><option value=891>SE…
  • Error Line 85, Column 7038: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=686>SENEGAL</option><option value=891>SERBIA AND MONTENEGRO</option><optio…
  • Error Line 85, Column 7086: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … AND MONTENEGRO</option><option value=690>SEYCHELLES</option><option value=694…
  • Error Line 85, Column 7123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=690>SEYCHELLES</option><option value=694>SIERRA LEONE</option><option value=7…
  • Error Line 85, Column 7162: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …94>SIERRA LEONE</option><option value=702>SINGAPORE</option><option value=703>…
  • Error Line 85, Column 7198: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=702>SINGAPORE</option><option value=703>SLOVAKIA</option><option value=705>S…
  • Error Line 85, Column 7233: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=703>SLOVAKIA</option><option value=705>SLOVENIA</option><option value=90>SO…
  • Error Line 85, Column 7268: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=705>SLOVENIA</option><option value=90>SOLOMON ISLANDS</option><option value…
  • Error Line 85, Column 7309: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …SOLOMON ISLANDS</option><option value=706>SOMALIA</option><option value=710>SO…
  • Error Line 85, Column 7343: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=706>SOMALIA</option><option value=710>SOUTH AFRICA</option><option value=2…
  • Error Line 85, Column 7382: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …10>SOUTH AFRICA</option><option value=239>SOUTH GEORGIA AND THE SOUTH SANDWICH…
  • Error Line 85, Column 7453: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ANDWICH ISLANDS</option><option value=724>SPAIN</option><option value=144>SRI …
  • Error Line 85, Column 7485: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=724>SPAIN</option><option value=144>SRI LANKA</option><option value=736>…
  • Error Line 85, Column 7521: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=144>SRI LANKA</option><option value=736>SUDAN</option><option value=740>SURI…
  • Error Line 85, Column 7553: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=736>SUDAN</option><option value=740>SURINAME</option><option value=744>S…
  • Error Line 85, Column 7588: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=740>SURINAME</option><option value=744>SVALBARD AND JAN MAYEN ISLANDS</opti…
  • Error Line 85, Column 7645: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …N MAYEN ISLANDS</option><option value=748>SWAZILAND</option><option value=752>…
  • Error Line 85, Column 7681: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=748>SWAZILAND</option><option value=752>SWEDEN</option><option value=756>SWI…
  • Error Line 85, Column 7714: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=752>SWEDEN</option><option value=756>SWITZERLAND</option><option value=76…
  • Error Line 85, Column 7752: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …756>SWITZERLAND</option><option value=760>SYRIAN ARAB REPUBLIC</option><option…
  • Error Line 85, Column 7799: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …N ARAB REPUBLIC</option><option value=158>TAIWAN</option><option value=762>TAJ…
  • Error Line 85, Column 7832: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=158>TAIWAN</option><option value=762>TAJIKISTAN</option><option value=834…
  • Error Line 85, Column 7869: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=762>TAJIKISTAN</option><option value=834>TANZANIA, UNITED REPUBLIC OF</option…
  • Error Line 85, Column 7924: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …TED REPUBLIC OF</option><option value=764>THAILAND</option><option value=626>T…
  • Error Line 85, Column 7959: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=764>THAILAND</option><option value=626>TIMOR-LESTE</option><option value=76…
  • Error Line 85, Column 7997: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …626>TIMOR-LESTE</option><option value=768>TOGO</option><option value=772>TOKEL…
  • Error Line 85, Column 8028: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … value=768>TOGO</option><option value=772>TOKELAU</option><option value=776>TO…
  • Error Line 85, Column 8062: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=772>TOKELAU</option><option value=776>TONGA</option><option value=780>TRIN…
  • Error Line 85, Column 8094: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=776>TONGA</option><option value=780>TRINIDAD AND TOBAGO</option><option …
  • Error Line 85, Column 8140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …IDAD AND TOBAGO</option><option value=788>TUNISIA</option><option value=792>TU…
  • Error Line 85, Column 8174: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=788>TUNISIA</option><option value=792>TURKEY</option><option value=795>TUR…
  • Error Line 85, Column 8207: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=792>TURKEY</option><option value=795>TURKMENISTAN</option><option value=7…
  • Error Line 85, Column 8246: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …95>TURKMENISTAN</option><option value=796>TURKS AND CAICOS ISLANDS</option><op…
  • Error Line 85, Column 8297: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … CAICOS ISLANDS</option><option value=798>TUVALU</option><option value=800>UGA…
  • Error Line 85, Column 8330: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=798>TUVALU</option><option value=800>UGANDA</option><option value=804>UKR…
  • Error Line 85, Column 8363: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=800>UGANDA</option><option value=804>UKRAINE</option><option value=784>UN…
  • Error Line 85, Column 8397: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=804>UKRAINE</option><option value=784>UNITED ARAB EMIRATES</option><option…
  • Error Line 85, Column 8444: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …D ARAB EMIRATES</option><option value=826>UNITED KINGDOM</option><option value…
  • Error Line 85, Column 8485: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>UNITED KINGDOM</option><option value=840 selected>UNITED STATES</option><opti…
  • Error Line 85, Column 8497: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …DOM</option><option value=840 selected>UNITED STATES</option><option value=858…

    "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 85, Column 8534: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …d>UNITED STATES</option><option value=858>URUGUAY</option><option value=860>UZ…
  • Error Line 85, Column 8568: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=858>URUGUAY</option><option value=860>UZBEKISTAN</option><option value=548…
  • Error Line 85, Column 8605: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=860>UZBEKISTAN</option><option value=548>VANUATU</option><option value=336>VA…
  • Error Line 85, Column 8639: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lue=548>VANUATU</option><option value=336>VATICAN CITY STATE (HOLY SEE)</optio…
  • Error Line 85, Column 8695: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …TATE (HOLY SEE)</option><option value=862>VENEZUELA</option><option value=704>…
  • Error Line 85, Column 8731: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=862>VENEZUELA</option><option value=704>VIET NAM</option><option value=92>VI…
  • Error Line 85, Column 8766: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=704>VIET NAM</option><option value=92>VIRGIN ISLANDS (BRITISH)</option><opt…
  • Error Line 85, Column 8816: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …LANDS (BRITISH)</option><option value=850>VIRGIN ISLANDS (U.S.)</option><optio…
  • Error Line 85, Column 8864: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … ISLANDS (U.S.)</option><option value=876>WALLIS AND FUTUNA ISLANDS</option><o…
  • Error Line 85, Column 8916: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … FUTUNA ISLANDS</option><option value=732>WESTERN SAHARA</option><option value…
  • Error Line 85, Column 8957: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …>WESTERN SAHARA</option><option value=887>YEMEN</option><option value=894>ZAMB…
  • Error Line 85, Column 8989: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …value=887>YEMEN</option><option value=894>ZAMBIA</option><option value=716>ZIM…
  • Error Line 85, Column 9022: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=894>ZAMBIA</option><option value=716>ZIMBABWE</option><option value=688>S…
  • Error Line 85, Column 9057: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ue=716>ZIMBABWE</option><option value=688>SERBIA</option><option value=499>MON…
  • Error Line 85, Column 9090: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue=688>SERBIA</option><option value=499>MONTENEGRO</option><option value=833…
  • Error Line 85, Column 9127: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=499>MONTENEGRO</option><option value=833>ISLE OF MAN</option><option value=83…
  • Error Line 85, Column 9165: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …833>ISLE OF MAN</option><option value=831>GUERNSEY</option><option value=832>J…
  • Error Line 85, Column 9200: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …on value=831>GUERNSEY</option><option value=832>JERSEY</option>							</select>
  • Error Line 87, Column 22: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    						<li class="li6">

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

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

  • Error Line 90, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    															<option value=5 >5 miles</option>
  • Error Line 91, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					            <option value=10 >10 miles</option>
  • Error Line 92, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					            <option value=25 selected>25 miles</option>
  • Error Line 92, Column 43: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    					            <option value=25 selected>25 miles</option>

    "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 93, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					            <option value=50 >50 miles</option>
  • Error Line 94, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					            <option value=100 >100 miles</option>
  • Error Line 95, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					            <option value=250 >250 miles</option>
  • Error Line 98, Column 22: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    						<li class="li7">

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

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

  • Error Line 101, Column 22: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    						<li class="li8">

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

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

  • Error Line 103, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    								<input type=image src="/images/CitySex/home-search-bt1.gif" />
  • Error Line 106, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
    					</ul>

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

  • Info Line 82, Column 7: start tag was here
    						<div class="clear"></div>
  • Warning Line 124, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="pers…

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

  • Warning Line 124, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="pers…

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

  • Error Line 124, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="pers…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 124, Column 44: cannot generate system identifier for general entity "model"
    …	<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person">…

    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 124, Column 44: general entity "model" not defined and no default entity
    …	<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person">…

    This is usually a cascading error caused by 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 124, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"><img …

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

  • Warning Line 124, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"><img …

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

  • Error Line 124, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"><img …

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 124, Column 58: cannot generate system identifier for general entity "id"
    …e=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/ima…

    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 124, Column 58: general entity "id" not defined and no default entity
    …e=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/ima…

    This is usually a cascading error caused by 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 124, Column 60: reference not terminated by REFC delimiter
    …register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/image…

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

  • Warning Line 124, Column 60: reference to external entity in attribute value
    …register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/image…

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

  • Error Line 124, Column 60: reference to entity "id" for which no system identifier could be generated
    …register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 124, Column 162: required attribute "alt" not specified
    … src="/images/CitySex/prof/set2/Not2Shy_25.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 126, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 2…

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

  • Warning Line 126, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 2…

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

  • Error Line 126, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 2…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 126, Column 50: reference not terminated by REFC delimiter
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 25</a>

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

  • Warning Line 126, Column 50: reference to external entity in attribute value
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 25</a>

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

  • Error Line 126, Column 50: reference to entity "model" for which no system identifier could be generated
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 25</a>

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 126, Column 61: reference not terminated by REFC delimiter
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 25</a>

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

  • Warning Line 126, Column 61: reference to external entity in attribute value
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 25</a>

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

  • Error Line 126, Column 61: reference to entity "id" for which no system identifier could be generated
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624">Not2Shy, 25</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 132, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=TrueLove&id=24215" class="pers…

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

  • Warning Line 132, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=TrueLove&id=24215" class="pers…

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

  • Error Line 132, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=TrueLove&id=24215" class="pers…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 132, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=TrueLove&id=24215" class="person"><img …

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

  • Warning Line 132, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=TrueLove&id=24215" class="person"><img …

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

  • Error Line 132, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=TrueLove&id=24215" class="person"><img …

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 132, Column 61: reference not terminated by REFC delimiter
    …egister2&home=newest&model=TrueLove&id=24215" class="person"><img src="/images…

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

  • Warning Line 132, Column 61: reference to external entity in attribute value
    …egister2&home=newest&model=TrueLove&id=24215" class="person"><img src="/images…

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

  • Error Line 132, Column 61: reference to entity "id" for which no system identifier could be generated
    …egister2&home=newest&model=TrueLove&id=24215" class="person"><img src="/images…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 132, Column 163: required attribute "alt" not specified
    …src="/images/CitySex/prof/set2/TrueLove_23.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 134, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, …

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

  • Warning Line 134, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, …

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

  • Error Line 134, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, …

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 134, Column 50: reference not terminated by REFC delimiter
    …	<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, 23</a>

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

  • Warning Line 134, Column 50: reference to external entity in attribute value
    …	<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, 23</a>

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

  • Error Line 134, Column 50: reference to entity "model" for which no system identifier could be generated
    …	<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, 23</a>

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 134, Column 62: reference not terminated by REFC delimiter
    …	<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, 23</a>

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

  • Warning Line 134, Column 62: reference to external entity in attribute value
    …	<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, 23</a>

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

  • Error Line 134, Column 62: reference to entity "id" for which no system identifier could be generated
    …	<a href="?page=register2&home=newest&model=TrueLove&id=24215">TrueLove, 23</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 140, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=svet_v_toneli&id=116860" class…

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

  • Warning Line 140, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=svet_v_toneli&id=116860" class…

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

  • Error Line 140, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=svet_v_toneli&id=116860" class…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 140, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=svet_v_toneli&id=116860" class="person"…

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

  • Warning Line 140, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=svet_v_toneli&id=116860" class="person"…

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

  • Error Line 140, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=svet_v_toneli&id=116860" class="person"…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 140, Column 66: reference not terminated by REFC delimiter
    …er2&home=newest&model=svet_v_toneli&id=116860" class="person"><img src="/image…

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

  • Warning Line 140, Column 66: reference to external entity in attribute value
    …er2&home=newest&model=svet_v_toneli&id=116860" class="person"><img src="/image…

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

  • Error Line 140, Column 66: reference to entity "id" for which no system identifier could be generated
    …er2&home=newest&model=svet_v_toneli&id=116860" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 140, Column 174: required attribute "alt" not specified
    …/images/CitySex/prof/set2/svet_v_toneli_24.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 142, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=svet_v_toneli&id=116860">svet…

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

  • Warning Line 142, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=svet_v_toneli&id=116860">svet…

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

  • Error Line 142, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=svet_v_toneli&id=116860">svet…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 142, Column 50: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=svet_v_toneli&id=116860">svet_v_toneli,…

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

  • Warning Line 142, Column 50: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=svet_v_toneli&id=116860">svet_v_toneli,…

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

  • Error Line 142, Column 50: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=svet_v_toneli&id=116860">svet_v_toneli,…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 142, Column 67: reference not terminated by REFC delimiter
    …page=register2&home=newest&model=svet_v_toneli&id=116860">svet_v_toneli, 24</a>

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

  • Warning Line 142, Column 67: reference to external entity in attribute value
    …page=register2&home=newest&model=svet_v_toneli&id=116860">svet_v_toneli, 24</a>

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

  • Error Line 142, Column 67: reference to entity "id" for which no system identifier could be generated
    …page=register2&home=newest&model=svet_v_toneli&id=116860">svet_v_toneli, 24</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 148, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=accablez&id=109928" class="per…

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

  • Warning Line 148, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=accablez&id=109928" class="per…

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

  • Error Line 148, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=accablez&id=109928" class="per…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 148, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=accablez&id=109928" class="person"><img…

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

  • Warning Line 148, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=accablez&id=109928" class="person"><img…

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

  • Error Line 148, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=accablez&id=109928" class="person"><img…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 148, Column 61: reference not terminated by REFC delimiter
    …egister2&home=newest&model=accablez&id=109928" class="person"><img src="/image…

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

  • Warning Line 148, Column 61: reference to external entity in attribute value
    …egister2&home=newest&model=accablez&id=109928" class="person"><img src="/image…

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

  • Error Line 148, Column 61: reference to entity "id" for which no system identifier could be generated
    …egister2&home=newest&model=accablez&id=109928" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 148, Column 164: required attribute "alt" not specified
    …src="/images/CitySex/prof/set2/accablez_27.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 150, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=accablez&id=109928">accablez,…

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

  • Warning Line 150, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=accablez&id=109928">accablez,…

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

  • Error Line 150, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=accablez&id=109928">accablez,…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 150, Column 50: reference not terminated by REFC delimiter
    …<a href="?page=register2&home=newest&model=accablez&id=109928">accablez, 27</a>

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

  • Warning Line 150, Column 50: reference to external entity in attribute value
    …<a href="?page=register2&home=newest&model=accablez&id=109928">accablez, 27</a>

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

  • Error Line 150, Column 50: reference to entity "model" for which no system identifier could be generated
    …<a href="?page=register2&home=newest&model=accablez&id=109928">accablez, 27</a>

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 150, Column 62: reference not terminated by REFC delimiter
    …<a href="?page=register2&home=newest&model=accablez&id=109928">accablez, 27</a>

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

  • Warning Line 150, Column 62: reference to external entity in attribute value
    …<a href="?page=register2&home=newest&model=accablez&id=109928">accablez, 27</a>

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

  • Error Line 150, Column 62: reference to entity "id" for which no system identifier could be generated
    …<a href="?page=register2&home=newest&model=accablez&id=109928">accablez, 27</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 156, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=ThinAndCurvy&id=108525" class=…

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

  • Warning Line 156, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=ThinAndCurvy&id=108525" class=…

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

  • Error Line 156, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=ThinAndCurvy&id=108525" class=…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 156, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=ThinAndCurvy&id=108525" class="person">…

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

  • Warning Line 156, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=ThinAndCurvy&id=108525" class="person">…

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

  • Error Line 156, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=ThinAndCurvy&id=108525" class="person">…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 156, Column 65: reference not terminated by REFC delimiter
    …ter2&home=newest&model=ThinAndCurvy&id=108525" class="person"><img src="/image…

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

  • Warning Line 156, Column 65: reference to external entity in attribute value
    …ter2&home=newest&model=ThinAndCurvy&id=108525" class="person"><img src="/image…

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

  • Error Line 156, Column 65: reference to entity "id" for which no system identifier could be generated
    …ter2&home=newest&model=ThinAndCurvy&id=108525" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 156, Column 172: required attribute "alt" not specified
    …"/images/CitySex/prof/set2/ThinAndCurvy_25.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 158, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinA…

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

  • Warning Line 158, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinA…

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

  • Error Line 158, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinA…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 158, Column 50: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinAndCurvy, 2…

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

  • Warning Line 158, Column 50: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinAndCurvy, 2…

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

  • Error Line 158, Column 50: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinAndCurvy, 2…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 158, Column 66: reference not terminated by REFC delimiter
    …"?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinAndCurvy, 25</a>

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

  • Warning Line 158, Column 66: reference to external entity in attribute value
    …"?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinAndCurvy, 25</a>

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

  • Error Line 158, Column 66: reference to entity "id" for which no system identifier could be generated
    …"?page=register2&home=newest&model=ThinAndCurvy&id=108525">ThinAndCurvy, 25</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 164, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=abusingsilence&id=110355" 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 164, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=abusingsilence&id=110355" 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 164, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=abusingsilence&id=110355" 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 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 164, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=abusingsilence&id=110355" class="person…

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

  • Warning Line 164, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=abusingsilence&id=110355" class="person…

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

  • Error Line 164, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=abusingsilence&id=110355" class="person…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 164, Column 67: reference not terminated by REFC delimiter
    …r2&home=newest&model=abusingsilence&id=110355" class="person"><img src="/image…

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

  • Warning Line 164, Column 67: reference to external entity in attribute value
    …r2&home=newest&model=abusingsilence&id=110355" class="person"><img src="/image…

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

  • Error Line 164, Column 67: reference to entity "id" for which no system identifier could be generated
    …r2&home=newest&model=abusingsilence&id=110355" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 164, Column 176: required attribute "alt" not specified
    …images/CitySex/prof/set2/abusingsilence_25.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 166, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=abusingsilence&id=110355">abu…

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

  • Warning Line 166, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=abusingsilence&id=110355">abu…

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

  • Error Line 166, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=abusingsilence&id=110355">abu…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 166, Column 50: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=abusingsilence&id=110355">abusingsilenc…

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

  • Warning Line 166, Column 50: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=abusingsilence&id=110355">abusingsilenc…

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

  • Error Line 166, Column 50: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=abusingsilence&id=110355">abusingsilenc…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 166, Column 68: reference not terminated by REFC delimiter
    …ge=register2&home=newest&model=abusingsilence&id=110355">abusingsilence, 25</a>

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

  • Warning Line 166, Column 68: reference to external entity in attribute value
    …ge=register2&home=newest&model=abusingsilence&id=110355">abusingsilence, 25</a>

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

  • Error Line 166, Column 68: reference to entity "id" for which no system identifier could be generated
    …ge=register2&home=newest&model=abusingsilence&id=110355">abusingsilence, 25</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 172, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=HornyHannah&id=109613" class="…

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

  • Warning Line 172, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=HornyHannah&id=109613" class="…

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

  • Error Line 172, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=HornyHannah&id=109613" class="…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 172, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=HornyHannah&id=109613" class="person"><…

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

  • Warning Line 172, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=HornyHannah&id=109613" class="person"><…

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

  • Error Line 172, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=HornyHannah&id=109613" class="person"><…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 172, Column 64: reference not terminated by REFC delimiter
    …ster2&home=newest&model=HornyHannah&id=109613" class="person"><img src="/image…

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

  • Warning Line 172, Column 64: reference to external entity in attribute value
    …ster2&home=newest&model=HornyHannah&id=109613" class="person"><img src="/image…

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

  • Error Line 172, Column 64: reference to entity "id" for which no system identifier could be generated
    …ster2&home=newest&model=HornyHannah&id=109613" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 172, Column 170: required attribute "alt" not specified
    …="/images/CitySex/prof/set2/HornyHannah_27.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 174, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=HornyHannah&id=109613">HornyH…

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

  • Warning Line 174, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=HornyHannah&id=109613">HornyH…

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

  • Error Line 174, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=HornyHannah&id=109613">HornyH…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 174, Column 50: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=HornyHannah&id=109613">HornyHannah, 27<…

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

  • Warning Line 174, Column 50: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=HornyHannah&id=109613">HornyHannah, 27<…

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

  • Error Line 174, Column 50: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=HornyHannah&id=109613">HornyHannah, 27<…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 174, Column 65: reference not terminated by REFC delimiter
    …f="?page=register2&home=newest&model=HornyHannah&id=109613">HornyHannah, 27</a>

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

  • Warning Line 174, Column 65: reference to external entity in attribute value
    …f="?page=register2&home=newest&model=HornyHannah&id=109613">HornyHannah, 27</a>

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

  • Error Line 174, Column 65: reference to entity "id" for which no system identifier could be generated
    …f="?page=register2&home=newest&model=HornyHannah&id=109613">HornyHannah, 27</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 180, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=SportsFan&id=39130" class="per…

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

  • Warning Line 180, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=SportsFan&id=39130" class="per…

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

  • Error Line 180, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=SportsFan&id=39130" class="per…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 180, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=SportsFan&id=39130" class="person"><img…

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

  • Warning Line 180, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=SportsFan&id=39130" class="person"><img…

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

  • Error Line 180, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=SportsFan&id=39130" class="person"><img…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 180, Column 62: reference not terminated by REFC delimiter
    …gister2&home=newest&model=SportsFan&id=39130" class="person"><img src="/images…

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

  • Warning Line 180, Column 62: reference to external entity in attribute value
    …gister2&home=newest&model=SportsFan&id=39130" class="person"><img src="/images…

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

  • Error Line 180, Column 62: reference to entity "id" for which no system identifier could be generated
    …gister2&home=newest&model=SportsFan&id=39130" class="person"><img src="/images…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 180, Column 165: required attribute "alt" not specified
    …rc="/images/CitySex/prof/set2/SportsFan_29.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 182, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan…

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

  • Warning Line 182, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan…

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

  • Error Line 182, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 182, Column 50: reference not terminated by REFC delimiter
    …a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan, 29</a>

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

  • Warning Line 182, Column 50: reference to external entity in attribute value
    …a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan, 29</a>

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

  • Error Line 182, Column 50: reference to entity "model" for which no system identifier could be generated
    …a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan, 29</a>

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 182, Column 63: reference not terminated by REFC delimiter
    …a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan, 29</a>

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

  • Warning Line 182, Column 63: reference to external entity in attribute value
    …a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan, 29</a>

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

  • Error Line 182, Column 63: reference to entity "id" for which no system identifier could be generated
    …a href="?page=register2&home=newest&model=SportsFan&id=39130">SportsFan, 29</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 188, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=nova_love_dr&id=650783" class=…

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

  • Warning Line 188, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=nova_love_dr&id=650783" class=…

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

  • Error Line 188, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=nova_love_dr&id=650783" class=…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 188, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=nova_love_dr&id=650783" class="person">…

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

  • Warning Line 188, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=nova_love_dr&id=650783" class="person">…

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

  • Error Line 188, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=nova_love_dr&id=650783" class="person">…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 188, Column 65: reference not terminated by REFC delimiter
    …ter2&home=newest&model=nova_love_dr&id=650783" class="person"><img src="/image…

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

  • Warning Line 188, Column 65: reference to external entity in attribute value
    …ter2&home=newest&model=nova_love_dr&id=650783" class="person"><img src="/image…

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

  • Error Line 188, Column 65: reference to entity "id" for which no system identifier could be generated
    …ter2&home=newest&model=nova_love_dr&id=650783" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 188, Column 172: required attribute "alt" not specified
    …"/images/CitySex/prof/set2/nova_love_dr_25.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 190, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=nova_love_dr&id=650783">nova_…

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

  • Warning Line 190, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=nova_love_dr&id=650783">nova_…

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

  • Error Line 190, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=nova_love_dr&id=650783">nova_…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 190, Column 50: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=nova_love_dr&id=650783">nova_love_dr, 2…

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

  • Warning Line 190, Column 50: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=nova_love_dr&id=650783">nova_love_dr, 2…

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

  • Error Line 190, Column 50: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=nova_love_dr&id=650783">nova_love_dr, 2…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 190, Column 66: reference not terminated by REFC delimiter
    …"?page=register2&home=newest&model=nova_love_dr&id=650783">nova_love_dr, 25</a>

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

  • Warning Line 190, Column 66: reference to external entity in attribute value
    …"?page=register2&home=newest&model=nova_love_dr&id=650783">nova_love_dr, 25</a>

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

  • Error Line 190, Column 66: reference to entity "id" for which no system identifier could be generated
    …"?page=register2&home=newest&model=nova_love_dr&id=650783">nova_love_dr, 25</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 196, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=newest&model=SmallnSweet&id=108520" class="…

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

  • Warning Line 196, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=newest&model=SmallnSweet&id=108520" class="…

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

  • Error Line 196, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=newest&model=SmallnSweet&id=108520" class="…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 196, Column 49: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=SmallnSweet&id=108520" class="person"><…

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

  • Warning Line 196, Column 49: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=SmallnSweet&id=108520" class="person"><…

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

  • Error Line 196, Column 49: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=SmallnSweet&id=108520" class="person"><…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 196, Column 64: reference not terminated by REFC delimiter
    …ster2&home=newest&model=SmallnSweet&id=108520" class="person"><img src="/image…

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

  • Warning Line 196, Column 64: reference to external entity in attribute value
    …ster2&home=newest&model=SmallnSweet&id=108520" class="person"><img src="/image…

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

  • Error Line 196, Column 64: reference to entity "id" for which no system identifier could be generated
    …ster2&home=newest&model=SmallnSweet&id=108520" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 196, Column 170: required attribute "alt" not specified
    …="/images/CitySex/prof/set2/SmallnSweet_22.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 198, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=newest&model=SmallnSweet&id=108520">Smalln…

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

  • Warning Line 198, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=newest&model=SmallnSweet&id=108520">Smalln…

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

  • Error Line 198, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=newest&model=SmallnSweet&id=108520">Smalln…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 198, Column 50: reference not terminated by REFC delimiter
    …ref="?page=register2&home=newest&model=SmallnSweet&id=108520">SmallnSweet, 22<…

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

  • Warning Line 198, Column 50: reference to external entity in attribute value
    …ref="?page=register2&home=newest&model=SmallnSweet&id=108520">SmallnSweet, 22<…

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

  • Error Line 198, Column 50: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=newest&model=SmallnSweet&id=108520">SmallnSweet, 22<…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 198, Column 65: reference not terminated by REFC delimiter
    …f="?page=register2&home=newest&model=SmallnSweet&id=108520">SmallnSweet, 22</a>

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

  • Warning Line 198, Column 65: reference to external entity in attribute value
    …f="?page=register2&home=newest&model=SmallnSweet&id=108520">SmallnSweet, 22</a>

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

  • Error Line 198, Column 65: reference to entity "id" for which no system identifier could be generated
    …f="?page=register2&home=newest&model=SmallnSweet&id=108520">SmallnSweet, 22</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 202, Column 28: document type does not allow element "div" here; assuming missing "li" start-tag
    									<div class="clear"></div>
  • Error Line 203, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    				</ul>

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

  • Info Line 202, Column 10: start tag was here
    									<div class="clear"></div>
  • Warning Line 204, Column 33: reference not terminated by REFC delimiter
    				<a href="?page=register&home=newest&model=all" class="viewall">View All &gt…

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

  • Warning Line 204, Column 33: reference to external entity in attribute value
    				<a href="?page=register&home=newest&model=all" class="viewall">View All &gt…

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

  • Error Line 204, Column 33: reference to entity "home" for which no system identifier could be generated
    				<a href="?page=register&home=newest&model=all" class="viewall">View All &gt…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 204, Column 46: reference not terminated by REFC delimiter
    …href="?page=register&home=newest&model=all" class="viewall">View All &gt;&gt;<…

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

  • Warning Line 204, Column 46: reference to external entity in attribute value
    …href="?page=register&home=newest&model=all" class="viewall">View All &gt;&gt;<…

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

  • Error Line 204, Column 46: reference to entity "model" for which no system identifier could be generated
    …href="?page=register&home=newest&model=all" class="viewall">View All &gt;&gt;<…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 218, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=recentOL&model=BitoniXXX&id=109602" class="…

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

  • Warning Line 218, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=recentOL&model=BitoniXXX&id=109602" class="…

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

  • Error Line 218, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=recentOL&model=BitoniXXX&id=109602" class="…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 218, Column 51: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=BitoniXXX&id=109602" class="person"><im…

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

  • Warning Line 218, Column 51: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=BitoniXXX&id=109602" class="person"><im…

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

  • Error Line 218, Column 51: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=BitoniXXX&id=109602" class="person"><im…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 218, Column 64: reference not terminated by REFC delimiter
    …ster2&home=recentOL&model=BitoniXXX&id=109602" class="person"><img src="/image…

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

  • Warning Line 218, Column 64: reference to external entity in attribute value
    …ster2&home=recentOL&model=BitoniXXX&id=109602" class="person"><img src="/image…

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

  • Error Line 218, Column 64: reference to entity "id" for which no system identifier could be generated
    …ster2&home=recentOL&model=BitoniXXX&id=109602" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 218, Column 168: required attribute "alt" not specified
    …rc="/images/CitySex/prof/set2/BitoniXXX_23.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 220, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=recentOL&model=BitoniXXX&id=109602">Bitoni…

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

  • Warning Line 220, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=recentOL&model=BitoniXXX&id=109602">Bitoni…

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

  • Error Line 220, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=recentOL&model=BitoniXXX&id=109602">Bitoni…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 220, Column 52: reference not terminated by REFC delimiter
    …ref="?page=register2&home=recentOL&model=BitoniXXX&id=109602">BitoniXXX, 23</a>

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

  • Warning Line 220, Column 52: reference to external entity in attribute value
    …ref="?page=register2&home=recentOL&model=BitoniXXX&id=109602">BitoniXXX, 23</a>

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

  • Error Line 220, Column 52: reference to entity "model" for which no system identifier could be generated
    …ref="?page=register2&home=recentOL&model=BitoniXXX&id=109602">BitoniXXX, 23</a>

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 220, Column 65: reference not terminated by REFC delimiter
    …ref="?page=register2&home=recentOL&model=BitoniXXX&id=109602">BitoniXXX, 23</a>

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

  • Warning Line 220, Column 65: reference to external entity in attribute value
    …ref="?page=register2&home=recentOL&model=BitoniXXX&id=109602">BitoniXXX, 23</a>

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

  • Error Line 220, Column 65: reference to entity "id" for which no system identifier could be generated
    …ref="?page=register2&home=recentOL&model=BitoniXXX&id=109602">BitoniXXX, 23</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 224, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=recentOL&model=jackspromise&id=110951" 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 224, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=recentOL&model=jackspromise&id=110951" 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 224, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=recentOL&model=jackspromise&id=110951" 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 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 224, Column 51: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=jackspromise&id=110951" class="person">…

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

  • Warning Line 224, Column 51: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=jackspromise&id=110951" class="person">…

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

  • Error Line 224, Column 51: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=jackspromise&id=110951" class="person">…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 224, Column 67: reference not terminated by REFC delimiter
    …r2&home=recentOL&model=jackspromise&id=110951" class="person"><img src="/image…

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

  • Warning Line 224, Column 67: reference to external entity in attribute value
    …r2&home=recentOL&model=jackspromise&id=110951" class="person"><img src="/image…

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

  • Error Line 224, Column 67: reference to entity "id" for which no system identifier could be generated
    …r2&home=recentOL&model=jackspromise&id=110951" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 224, Column 174: required attribute "alt" not specified
    …"/images/CitySex/prof/set2/jackspromise_25.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 226, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=recentOL&model=jackspromise&id=110951">jac…

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

  • Warning Line 226, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=recentOL&model=jackspromise&id=110951">jac…

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

  • Error Line 226, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=recentOL&model=jackspromise&id=110951">jac…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 226, Column 52: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=jackspromise&id=110951">jackspromise, 2…

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

  • Warning Line 226, Column 52: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=jackspromise&id=110951">jackspromise, 2…

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

  • Error Line 226, Column 52: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=jackspromise&id=110951">jackspromise, 2…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 226, Column 68: reference not terminated by REFC delimiter
    …page=register2&home=recentOL&model=jackspromise&id=110951">jackspromise, 25</a>

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

  • Warning Line 226, Column 68: reference to external entity in attribute value
    …page=register2&home=recentOL&model=jackspromise&id=110951">jackspromise, 25</a>

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

  • Error Line 226, Column 68: reference to entity "id" for which no system identifier could be generated
    …page=register2&home=recentOL&model=jackspromise&id=110951">jackspromise, 25</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 230, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=recentOL&model=WILDHottie&id=109637" class=…

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

  • Warning Line 230, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=recentOL&model=WILDHottie&id=109637" class=…

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

  • Error Line 230, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=recentOL&model=WILDHottie&id=109637" class=…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 230, Column 51: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637" class="person"><i…

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

  • Warning Line 230, Column 51: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637" class="person"><i…

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

  • Error Line 230, Column 51: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637" class="person"><i…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 230, Column 65: reference not terminated by REFC delimiter
    …ter2&home=recentOL&model=WILDHottie&id=109637" class="person"><img src="/image…

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

  • Warning Line 230, Column 65: reference to external entity in attribute value
    …ter2&home=recentOL&model=WILDHottie&id=109637" class="person"><img src="/image…

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

  • Error Line 230, Column 65: reference to entity "id" for which no system identifier could be generated
    …ter2&home=recentOL&model=WILDHottie&id=109637" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 230, Column 170: required attribute "alt" not specified
    …c="/images/CitySex/prof/set2/WILDHottie_26.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 232, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDH…

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

  • Warning Line 232, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDH…

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

  • Error Line 232, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDH…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 232, Column 52: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDHottie, 26</a…

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

  • Warning Line 232, Column 52: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDHottie, 26</a…

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

  • Error Line 232, Column 52: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDHottie, 26</a…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 232, Column 66: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDHottie, 26</a>

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

  • Warning Line 232, Column 66: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDHottie, 26</a>

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

  • Error Line 232, Column 66: reference to entity "id" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=WILDHottie&id=109637">WILDHottie, 26</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 236, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503" 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 236, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503" 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 236, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503" 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 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 236, Column 51: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503" class="perso…

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

  • Warning Line 236, Column 51: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503" class="perso…

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

  • Error Line 236, Column 51: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503" class="perso…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 236, Column 70: reference not terminated by REFC delimiter
    …home=recentOL&model=BrainsAndBeauty&id=108503" class="person"><img src="/image…

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

  • Warning Line 236, Column 70: reference to external entity in attribute value
    …home=recentOL&model=BrainsAndBeauty&id=108503" class="person"><img src="/image…

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

  • Error Line 236, Column 70: reference to entity "id" for which no system identifier could be generated
    …home=recentOL&model=BrainsAndBeauty&id=108503" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 236, Column 180: required attribute "alt" not specified
    …mages/CitySex/prof/set2/BrainsAndBeauty_24.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 238, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503">…

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

  • Warning Line 238, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503">…

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

  • Error Line 238, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503">…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 238, Column 52: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503">BrainsAndBea…

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

  • Warning Line 238, Column 52: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503">BrainsAndBea…

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

  • Error Line 238, Column 52: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=BrainsAndBeauty&id=108503">BrainsAndBea…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 238, Column 71: reference not terminated by REFC delimiter
    …egister2&home=recentOL&model=BrainsAndBeauty&id=108503">BrainsAndBeauty, 24</a>

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

  • Warning Line 238, Column 71: reference to external entity in attribute value
    …egister2&home=recentOL&model=BrainsAndBeauty&id=108503">BrainsAndBeauty, 24</a>

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

  • Error Line 238, Column 71: reference to entity "id" for which no system identifier could be generated
    …egister2&home=recentOL&model=BrainsAndBeauty&id=108503">BrainsAndBeauty, 24</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Warning Line 242, Column 36: reference not terminated by REFC delimiter
    						<a href="?page=register2&home=recentOL&model=hannahsamsen&id=110322" 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 242, Column 36: reference to external entity in attribute value
    						<a href="?page=register2&home=recentOL&model=hannahsamsen&id=110322" 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 242, Column 36: reference to entity "home" for which no system identifier could be generated
    						<a href="?page=register2&home=recentOL&model=hannahsamsen&id=110322" 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 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 242, Column 51: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=hannahsamsen&id=110322" class="person">…

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

  • Warning Line 242, Column 51: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=hannahsamsen&id=110322" class="person">…

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

  • Error Line 242, Column 51: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=hannahsamsen&id=110322" class="person">…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 242, Column 67: reference not terminated by REFC delimiter
    …r2&home=recentOL&model=hannahsamsen&id=110322" class="person"><img src="/image…

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

  • Warning Line 242, Column 67: reference to external entity in attribute value
    …r2&home=recentOL&model=hannahsamsen&id=110322" class="person"><img src="/image…

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

  • Error Line 242, Column 67: reference to entity "id" for which no system identifier could be generated
    …r2&home=recentOL&model=hannahsamsen&id=110322" class="person"><img src="/image…

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 242, Column 174: required attribute "alt" not specified
    …"/images/CitySex/prof/set2/hannahsamsen_25.jpg" width="172" height="147" /></a>

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

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

  • Warning Line 244, Column 37: reference not terminated by REFC delimiter
    							<a href="?page=register2&home=recentOL&model=hannahsamsen&id=110322">han…

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

  • Warning Line 244, Column 37: reference to external entity in attribute value
    							<a href="?page=register2&home=recentOL&model=hannahsamsen&id=110322">han…

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

  • Error Line 244, Column 37: reference to entity "home" for which no system identifier could be generated
    							<a href="?page=register2&home=recentOL&model=hannahsamsen&id=110322">han…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 244, Column 52: reference not terminated by REFC delimiter
    …f="?page=register2&home=recentOL&model=hannahsamsen&id=110322">hannahsamsen, 2…

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

  • Warning Line 244, Column 52: reference to external entity in attribute value
    …f="?page=register2&home=recentOL&model=hannahsamsen&id=110322">hannahsamsen, 2…

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

  • Error Line 244, Column 52: reference to entity "model" for which no system identifier could be generated
    …f="?page=register2&home=recentOL&model=hannahsamsen&id=110322">hannahsamsen, 2…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 244, Column 68: reference not terminated by REFC delimiter
    …page=register2&home=recentOL&model=hannahsamsen&id=110322">hannahsamsen, 25</a>

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

  • Warning Line 244, Column 68: reference to external entity in attribute value
    …page=register2&home=recentOL&model=hannahsamsen&id=110322">hannahsamsen, 25</a>

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

  • Error Line 244, Column 68: reference to entity "id" for which no system identifier could be generated
    …page=register2&home=recentOL&model=hannahsamsen&id=110322">hannahsamsen, 25</a>

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

  • Info Line 124, Column 57: entity was defined here
    …ge=register2&home=newest&model=Not2Shy&id=109624" class="person"><img src="/im…
  • Error Line 247, Column 28: document type does not allow element "div" here; assuming missing "li" start-tag
    									<div class="clear"></div>
  • Error Line 248, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    				</ul>

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

  • Info Line 247, Column 10: start tag was here
    									<div class="clear"></div>
  • Warning Line 249, Column 33: reference not terminated by REFC delimiter
    				<a href="?page=register&home=recentOL&model=all" class="viewall">View All &…

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

  • Warning Line 249, Column 33: reference to external entity in attribute value
    				<a href="?page=register&home=recentOL&model=all" class="viewall">View All &…

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

  • Error Line 249, Column 33: reference to entity "home" for which no system identifier could be generated
    				<a href="?page=register&home=recentOL&model=all" class="viewall">View All &…

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

  • Info Line 58, Column 27: entity was defined here
    			<a href="?page=register&home=geo_img" class="bt1 bthover"><img src="/images/…
  • Warning Line 249, Column 48: reference not terminated by REFC delimiter
    …ef="?page=register&home=recentOL&model=all" class="viewall">View All &gt;&gt;<…

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

  • Warning Line 249, Column 48: reference to external entity in attribute value
    …ef="?page=register&home=recentOL&model=all" class="viewall">View All &gt;&gt;<…

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

  • Error Line 249, Column 48: reference to entity "model" for which no system identifier could be generated
    …ef="?page=register&home=recentOL&model=all" class="viewall">View All &gt;&gt;<…

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

  • Info Line 124, Column 43: entity was defined here
    …		<a href="?page=register2&home=newest&model=Not2Shy&id=109624" class="person"…
  • Warning Line 276, Column 29: cannot generate system identifier for general entity "prefoot"
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…

    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 276, Column 29: general entity "prefoot" not defined and no default entity
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…

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

  • Warning Line 276, Column 36: reference not terminated by REFC delimiter
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…

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

  • Warning Line 276, Column 36: reference to external entity in attribute value
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…

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

  • Error Line 276, Column 36: reference to entity "prefoot" for which no system identifier could be generated
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…

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

  • Info Line 276, Column 28: entity was defined here
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…
  • Error Line 284, Column 83: required attribute "alt" not specified
    …<img src="/images/CitySex/prefooter-col1-1.png" width="351" height="22" /></h1>

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

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

  • Error Line 286, Column 81: required attribute "alt" not specified
    …				<img src="/images/CitySex/prefooter-col1-2.png" width="367" height="249" />

    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 303, Column 95: required attribute "alt" not specified
    …img src="/images/CitySex/prefooter-col2-1.png" width="459" height="19" /></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 305, Column 95: required attribute "alt" not specified
    …img src="/images/CitySex/prefooter-col2-2.png" width="452" height="56" /></div>

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

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

  • Warning Line 307, Column 39: reference not terminated by REFC delimiter
    						<a href="/?page=register&prefoot=button" class="bthover"><img src="/image…

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

  • Warning Line 307, Column 39: reference to external entity in attribute value
    						<a href="/?page=register&prefoot=button" class="bthover"><img src="/image…

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

  • Error Line 307, Column 39: reference to entity "prefoot" for which no system identifier could be generated
    						<a href="/?page=register&prefoot=button" class="bthover"><img src="/image…

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

  • Info Line 276, Column 28: entity was defined here
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…
  • Error Line 307, Column 139: required attribute "alt" not specified
    …img src="/images/CitySex/prefooter-col2-bt1.png" width="185" height="47" /></a>

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

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

  • Error Line 308, Column 119: required attribute "alt" not specified
    …img src="/images/CitySex/prefooter-col2-bt2.png" width="185" height="47" /></a>

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

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

  • Warning Line 319, Column 97: reference not terminated by REFC delimiter
    …sp;|&nbsp; <a href="/?page=register&prefoot=b_s_link">Search</a> &nbsp;|&nbsp; 

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

  • Warning Line 319, Column 97: reference to external entity in attribute value
    …sp;|&nbsp; <a href="/?page=register&prefoot=b_s_link">Search</a> &nbsp;|&nbsp; 

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

  • Error Line 319, Column 97: reference to entity "prefoot" for which no system identifier could be generated
    …sp;|&nbsp; <a href="/?page=register&prefoot=b_s_link">Search</a> &nbsp;|&nbsp; 

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

  • Info Line 276, Column 28: entity was defined here
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…
  • Warning Line 321, Column 100: reference not terminated by REFC delimiter
    … &nbsp;|&nbsp; <a href="/?page=register&prefoot=b_r_link">Register for FREE</a>

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

  • Warning Line 321, Column 100: reference to external entity in attribute value
    … &nbsp;|&nbsp; <a href="/?page=register&prefoot=b_r_link">Register for FREE</a>

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

  • Error Line 321, Column 100: reference to entity "prefoot" for which no system identifier could be generated
    … &nbsp;|&nbsp; <a href="/?page=register&prefoot=b_r_link">Register for FREE</a>

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

  • Info Line 276, Column 28: entity was defined here
    			<a href="/?page=register&prefoot=top">View all of our profiles for free, <sp…
  • Error Line 326, Column 9: required attribute "type" not specified
    	<script>

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

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

  • Error Line 332, Column 97: required attribute "alt" not specified
    …ogo"><img src="/images/CitySex/header1-logo.png" width="194" height="61" /></a>

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

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

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

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

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

  • Error Line 348, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 54, Column 1: start tag was here
    <div class="main">

Visitor Analysis

Daily Visitor
  • 4.317 visits

In Page Analysis