123any.com - gallery search engine. Movies portal, video post,adult directory. ...

123any.com
  • Domain Name
    123any.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #137034
  • Page Size
    56.9 KB
  • Ip Address
    67.213.218.40
  • Heading
    H1: 0, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 25 JPG, 1 PNG

Website Meta Analysis

  • Title
    123any.com - the ultimate sex search engine.
  • Meta Keyword
    ,tube,flash movie,sex movies,porn,movies,adult videos,amateur movies, videos,home tapes,free movies,xxx movies,sex,free sex,free porn,livecam,free videos,webcams, adult directory,123any,123any.com
  • Meta Description
    123any.com - gallery search engine. Movies portal, video post,adult directory.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    67.213.218.40
  • Domain Age
    6 Years, 5 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Thu, 26 Sep 2013 23:01:37 GMT
  • content-type: text/html
  • connection: keep-alive
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for 123any.com

DNS Analysis


DNS servers
ns1.alpha-space.com [67.213.218.40]
ns2.alpha-space.com [67.228.16.147]
ns1.onyx7.com [67.213.218.41]
ns2.onyx7.com [173.193.245.95]


DNS Records

Answer records
123any.com SOA
server: ns1.alpha-space.com
email: hostmaster@alpha-space.com
serial: 2008090980
refresh: 28800
retry: 7200
expire: 2592000
minimum ttl: 86400
86400s
123any.com NS  ns2.onyx7.com 86400s
123any.com NS  ns2.alpha-space.com 86400s
123any.com NS  ns1.onyx7.com 86400s
123any.com NS  ns1.alpha-space.com 86400s
123any.com A 67.213.218.40 86400s
123any.com MX
preference: 10
exchange: mail.alpha-space.com
86400s

Authority records

Additional records
ns1.onyx7.com A 67.213.218.41 3600s
ns1.alpha-space.com A 67.213.218.40 3600s
ns2.onyx7.com A 173.193.245.95 86400s
ns2.alpha-space.com A 67.228.16.147 86400s
mail.alpha-space.com A 174.37.222.49 86400s

IP 67.213.218.40 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Providence
  • Continent Code
    84332
  • Latitude
    435
  • Longitude
    770
  • No whois ip data for 67.213.218.40

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 161 Errors
  • 293 Warnings
Ratio Text/Html
  • 0.5761082306081104
Message Error
  • Error Line 11, Column 79: required attribute "type" not specified
    …src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>

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

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

  • Error Line 15, Column 15: there is no attribute "target"
    	<base target="_self" />

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

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

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

  • Error Line 15, Column 24: required attribute "href" not specified
    	<base target="_self" />

    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 18, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 18, Column 8: document type does not allow element "script" here; assuming missing "body" start-tag
    <script>
  • Warning Line 23, Column 27: character "<" is the first character of a delimiter but occurred as data
     if ( $(document).width() < 1150 ) { maxlist = 4; }  

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 25, Column 47: there is no attribute "target"
    … list + '<a href="'+linkurl+'" target="_blank" onclick="tr('+docid+',\'FHG\');…

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

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

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

  • Error Line 25, Column 88: document type does not allow element "a" here
    …ref="'+linkurl+'" target="_blank" onclick="tr('+docid+',\'FHG\');"><img src="' 

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

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

  • Error Line 26, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
         + prefix + i + '.jpg" width=160 height=200 /></a>'; 
  • Error Line 26, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
         + prefix + i + '.jpg" width=160 height=200 /></a>'; 
  • Error Line 26, Column 50: required attribute "alt" not specified
         + prefix + i + '.jpg" width=160 height=200 /></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 94, Column 6: document type does not allow element "body" here
    <body>

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

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

  • Error Line 104, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    				<li><a target=_blank title='tube video' href="http://altaporn.com/">Tube Vi…
  • Error Line 120, Column 95: there is no attribute "autocomplete"
    …t" class="text" name="q" autocomplete="off" value="" id="inputString" onkeyup=…

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

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

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

  • Error Line 123, Column 97: end tag for "img" omitted, but OMITTAG NO was specified
    …upArrow.png" style="position: relative; top: -12px; left: 30px;" alt="upArrow">

    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 123, Column 7: start tag was here
    						<img src="/upArrow.png" style="position: relative; top: -12px; left: 30px…
  • Warning Line 151, Column 1268: character "&" is the first character of a delimiter but occurred as data
    …SET FOR MEMBERS ONLY. GET FULL ACCESS & ENJOY THE MOST BEAUTIFUL GIRLS  198,18…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 151, Column 1444: character "&" is the first character of a delimiter but occurred as data
    …US SETS, DVD DOWNLOAD, 3D ... ALL SETS & VIDEOS JOIN...</div></div></div><br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 154, Column 1301: character "&" is the first character of a delimiter but occurred as data
    …SET FOR MEMBERS ONLY. GET FULL ACCESS & ENJOY THE MOST BEAUTIFUL GIRLS  198,18…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 157, Column 1269: character "&" is the first character of a delimiter but occurred as data
    …SET FOR MEMBERS ONLY. GET FULL ACCESS & ENJOY THE MOST BEAUTIFUL GIRLS  198,18…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 157, Column 1445: character "&" is the first character of a delimiter but occurred as data
    …S SETS, DVD DOWNLOAD, 3D ... ALL SETS & VIDEOS JOIN NOW  ...</div></div></div>…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 160, Column 1293: character "&" is the first character of a delimiter but occurred as data
    …SET FOR MEMBERS ONLY. GET FULL ACCESS & ENJOY THE MOST BEAUTIFUL GIRLS  198,18…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 160, Column 1469: character "&" is the first character of a delimiter but occurred as data
    …D BONUS SETS, DVD DOWNLOAD, 3D ... ALL SETS & VIDEOS...</div></div></div><br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 163, Column 1241: character "&" is the first character of a delimiter but occurred as data
    …SET FOR MEMBERS ONLY. GET FULL ACCESS & ENJOY THE MOST BEAUTIFUL GIRLS  198,18…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 163, Column 1417: character "&" is the first character of a delimiter but occurred as data
    …S SETS, DVD DOWNLOAD, 3D ... ALL SETS & VIDEOS JOIN NOW  TODAYS GALLER...</div…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 166, Column 1255: character "&" is the first character of a delimiter but occurred as data
    …SET FOR MEMBERS ONLY. GET FULL ACCESS & ENJOY THE MOST BEAUTIFUL GIRLS  198,18…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 166, Column 1431: character "&" is the first character of a delimiter but occurred as data
    …S SETS, DVD DOWNLOAD, 3D ... ALL SETS & VIDEOS JOIN NOW  ...</div></div></div>…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 169, Column 160: cannot generate system identifier for general entity "page"
    …=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='Ga…

    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 169, Column 160: general entity "page" not defined and no default entity
    …=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='Ga…

    This is usually a cascading error caused by 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 169, Column 164: reference not terminated by REFC delimiter
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='Gabrie…

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

  • Warning Line 169, Column 164: reference to external entity in attribute value
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='Gabrie…

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

  • Error Line 169, Column 164: reference to entity "page" for which no system identifier could be generated
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='Gabrie…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 169, Column 395: reference not terminated by REFC delimiter
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Warning Line 169, Column 395: reference to external entity in attribute value
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Error Line 169, Column 395: reference to entity "page" for which no system identifier could be generated
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 169, Column 773: reference not terminated by REFC delimiter
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Warning Line 169, Column 773: reference to external entity in attribute value
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Error Line 169, Column 773: reference to entity "page" for which no system identifier could be generated
    …yNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 172, Column 159: reference not terminated by REFC delimiter
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php' target='_blank' title='Jazmin…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another 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 159: reference to external entity in attribute value
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php' target='_blank' title='Jazmin…

    This is generally the sign of an ampersand that was not 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 159: reference to entity "page" for which no system identifier could be generated
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php' target='_blank' title='Jazmin…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 172, Column 390: reference not terminated by REFC delimiter
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another 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 390: reference to external entity in attribute value
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

    This is generally the sign of an ampersand that was not 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 390: reference to entity "page" for which no system identifier could be generated
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 172, Column 768: reference not terminated by REFC delimiter
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php' target='_blank' rel='nofollow…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another 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 768: reference to external entity in attribute value
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php' target='_blank' rel='nofollow…

    This is generally the sign of an ampersand that was not 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 768: reference to entity "page" for which no system identifier could be generated
    …yNzQ4NC4yLjUuNS4xLjcwMDU0MzUuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 175, Column 158: reference not terminated by REFC delimiter
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php' target='_blank' title='Desira…

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

  • Warning Line 175, Column 158: reference to external entity in attribute value
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php' target='_blank' title='Desira…

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

  • Error Line 175, Column 158: reference to entity "page" for which no system identifier could be generated
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php' target='_blank' title='Desira…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 175, Column 381: reference not terminated by REFC delimiter
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Warning Line 175, Column 381: reference to external entity in attribute value
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Error Line 175, Column 381: reference to entity "page" for which no system identifier could be generated
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 175, Column 751: reference not terminated by REFC delimiter
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Warning Line 175, Column 751: reference to external entity in attribute value
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Error Line 175, Column 751: reference to entity "page" for which no system identifier could be generated
    …=MTIyNzQ4NC4yLjIyLjIyLjEuNTcuMC4w&page=main.php' target='_blank' rel='nofollow…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 211, Column 1291: character "&" is the first character of a delimiter but occurred as data
    …e Housewives, Mature Pleasure, Nudism & Outdoors	Are you looking for Gorgeous …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 214, Column 167: reference not terminated by REFC delimiter
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php' target='_blank' title='Big bo…

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

  • Warning Line 214, Column 167: reference to external entity in attribute value
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php' target='_blank' title='Big bo…

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

  • Error Line 214, Column 167: reference to entity "page" for which no system identifier could be generated
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php' target='_blank' title='Big bo…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 214, Column 421: reference not terminated by REFC delimiter
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Warning Line 214, Column 421: reference to external entity in attribute value
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Error Line 214, Column 421: reference to entity "page" for which no system identifier could be generated
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php','http://67.213.218.43/dbi/84/…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Warning Line 214, Column 821: reference not terminated by REFC delimiter
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php' target='_blank' rel='nofollow…

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

  • Warning Line 214, Column 821: reference to external entity in attribute value
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php' target='_blank' rel='nofollow…

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

  • Error Line 214, Column 821: reference to entity "page" for which no system identifier could be generated
    …Q4NC4yLjEwLjEwLjEuNzAwNTk1Mi4wLjA&page=main.php' target='_blank' rel='nofollow…

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

  • Info Line 169, Column 159: entity was defined here
    …s=MTIyNzQ4NC4yLjIuMi4wLjcwMDU5OTUuMC4w&page=main.php' target='_blank' title='G…
  • Error Line 245, Column 27: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    //]]>--></script><noscript><a href='http://openx.altaporn.com/www/delivery/ck.p…

    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 245, Column 127: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …78d8&amp;cb=523452345' target='_blank'><img src='http://openx.altaporn.com/www…

    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 245, Column 232: there is no attribute "border"
    …php?zoneid=3&amp;cb=5234524&amp;n=a09778d8' border='0' alt='' /></a></noscript>

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

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

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

  • Warning Line 256, Column 41: cannot generate system identifier for general entity "vm"
    …		 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href=…

    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 256, Column 41: general entity "vm" not defined and no default entity
    …		 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href=…

    This is usually a cascading error caused by 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 256, Column 43: reference not terminated by REFC delimiter
    … <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 43: reference to external entity in attribute value
    … <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/…

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

  • Error Line 256, Column 43: reference to entity "vm" for which no system identifier could be generated
    … <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 46: cannot generate system identifier for general entity "sm"
    …l><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=…

    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 256, Column 46: general entity "sm" not defined and no default entity
    …l><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=…

    This is usually a cascading error caused by 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 256, Column 48: reference not terminated by REFC delimiter
    …<li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 48: reference to external entity in attribute value
    …<li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 48: reference to entity "sm" for which no system identifier could be generated
    …<li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 51: cannot generate system identifier for general entity "pn"
    …> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=C…

    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 256, Column 51: general entity "pn" not defined and no default entity
    …> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=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.

  • Warning Line 256, Column 53: reference not terminated by REFC delimiter
    …1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 53: reference to external entity in attribute value
    …1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 53: reference to entity "pn" for which no system identifier could be generated
    …1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 89: reference not terminated by REFC delimiter
    …pn=2'>2</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 89: reference to external entity in attribute value
    …pn=2'>2</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/…

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

  • Error Line 256, Column 89: reference to entity "vm" for which no system identifier could be generated
    …pn=2'>2</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 94: reference not terminated by REFC delimiter
    …>2</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 94: reference to external entity in attribute value
    …>2</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 94: reference to entity "sm" for which no system identifier could be generated
    …>2</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 99: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 99: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 99: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=3'>3</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 135: reference not terminated by REFC delimiter
    …pn=3'>3</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 135: reference to external entity in attribute value
    …pn=3'>3</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/…

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

  • Error Line 256, Column 135: reference to entity "vm" for which no system identifier could be generated
    …pn=3'>3</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 140: reference not terminated by REFC delimiter
    …>3</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 140: reference to external entity in attribute value
    …>3</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 140: reference to entity "sm" for which no system identifier could be generated
    …>3</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 145: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 145: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 145: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=4'>4</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 181: reference not terminated by REFC delimiter
    …pn=4'>4</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 181: reference to external entity in attribute value
    …pn=4'>4</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/…

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

  • Error Line 256, Column 181: reference to entity "vm" for which no system identifier could be generated
    …pn=4'>4</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 186: reference not terminated by REFC delimiter
    …>4</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 186: reference to external entity in attribute value
    …>4</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 186: reference to entity "sm" for which no system identifier could be generated
    …>4</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 191: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 191: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 191: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=5'>5</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 227: reference not terminated by REFC delimiter
    …pn=5'>5</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 227: reference to external entity in attribute value
    …pn=5'>5</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/…

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

  • Error Line 256, Column 227: reference to entity "vm" for which no system identifier could be generated
    …pn=5'>5</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 232: reference not terminated by REFC delimiter
    …>5</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 232: reference to external entity in attribute value
    …>5</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 232: reference to entity "sm" for which no system identifier could be generated
    …>5</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 237: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 237: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 237: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=6'>6</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 273: reference not terminated by REFC delimiter
    …pn=6'>6</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 273: reference to external entity in attribute value
    …pn=6'>6</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/…

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

  • Error Line 256, Column 273: reference to entity "vm" for which no system identifier could be generated
    …pn=6'>6</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 278: reference not terminated by REFC delimiter
    …>6</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 278: reference to external entity in attribute value
    …>6</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 278: reference to entity "sm" for which no system identifier could be generated
    …>6</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 283: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 283: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 283: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=7'>7</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 319: reference not terminated by REFC delimiter
    …pn=7'>7</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 319: reference to external entity in attribute value
    …pn=7'>7</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/…

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

  • Error Line 256, Column 319: reference to entity "vm" for which no system identifier could be generated
    …pn=7'>7</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 324: reference not terminated by REFC delimiter
    …>7</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 324: reference to external entity in attribute value
    …>7</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 324: reference to entity "sm" for which no system identifier could be generated
    …>7</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 329: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 329: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 329: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=8'>8</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 365: reference not terminated by REFC delimiter
    …pn=8'>8</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/…

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

  • Warning Line 256, Column 365: reference to external entity in attribute value
    …pn=8'>8</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/…

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

  • Error Line 256, Column 365: reference to entity "vm" for which no system identifier could be generated
    …pn=8'>8</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 370: reference not terminated by REFC delimiter
    …>8</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/?q=&v…

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

  • Warning Line 256, Column 370: reference to external entity in attribute value
    …>8</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/?q=&v…

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

  • Error Line 256, Column 370: reference to entity "sm" for which no system identifier could be generated
    …>8</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/?q=&v…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 375: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Warning Line 256, Column 375: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Error Line 256, Column 375: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=9'>9</a> </li><li> <a href='/?q=&vm=C&s…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 411: reference not terminated by REFC delimiter
    …pn=9'>9</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href=…

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

  • Warning Line 256, Column 411: reference to external entity in attribute value
    …pn=9'>9</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href=…

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

  • Error Line 256, Column 411: reference to entity "vm" for which no system identifier could be generated
    …pn=9'>9</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 416: reference not terminated by REFC delimiter
    …>9</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 416: reference to external entity in attribute value
    …>9</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 416: reference to entity "sm" for which no system identifier could be generated
    …>9</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 421: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href='/?q=&vm=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 256, Column 421: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href='/?q=&vm=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 256, Column 421: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=10'>10</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 459: reference not terminated by REFC delimiter
    …=10'>10</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href=…

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

  • Warning Line 256, Column 459: reference to external entity in attribute value
    …=10'>10</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href=…

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

  • Error Line 256, Column 459: reference to entity "vm" for which no system identifier could be generated
    …=10'>10</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 464: reference not terminated by REFC delimiter
    …10</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 464: reference to external entity in attribute value
    …10</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 464: reference to entity "sm" for which no system identifier could be generated
    …10</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 469: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href='/?q=&vm=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 256, Column 469: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href='/?q=&vm=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 256, Column 469: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=11'>11</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 507: reference not terminated by REFC delimiter
    …=11'>11</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href=…

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

  • Warning Line 256, Column 507: reference to external entity in attribute value
    …=11'>11</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href=…

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

  • Error Line 256, Column 507: reference to entity "vm" for which no system identifier could be generated
    …=11'>11</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 512: reference not terminated by REFC delimiter
    …11</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 512: reference to external entity in attribute value
    …11</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 512: reference to entity "sm" for which no system identifier could be generated
    …11</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 517: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href='/?q=&vm=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 256, Column 517: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href='/?q=&vm=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 256, Column 517: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=12'>12</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 555: reference not terminated by REFC delimiter
    …=12'>12</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href=…

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

  • Warning Line 256, Column 555: reference to external entity in attribute value
    …=12'>12</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href=…

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

  • Error Line 256, Column 555: reference to entity "vm" for which no system identifier could be generated
    …=12'>12</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 560: reference not terminated by REFC delimiter
    …12</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 560: reference to external entity in attribute value
    …12</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 560: reference to entity "sm" for which no system identifier could be generated
    …12</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 565: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href='/?q=&vm=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 256, Column 565: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href='/?q=&vm=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 256, Column 565: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=13'>13</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 603: reference not terminated by REFC delimiter
    …=13'>13</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href=…

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

  • Warning Line 256, Column 603: reference to external entity in attribute value
    …=13'>13</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href=…

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

  • Error Line 256, Column 603: reference to entity "vm" for which no system identifier could be generated
    …=13'>13</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 608: reference not terminated by REFC delimiter
    …13</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 608: reference to external entity in attribute value
    …13</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 608: reference to entity "sm" for which no system identifier could be generated
    …13</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 613: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href='/?q=&vm=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 256, Column 613: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href='/?q=&vm=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 256, Column 613: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=14'>14</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 651: reference not terminated by REFC delimiter
    …=14'>14</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href=…

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

  • Warning Line 256, Column 651: reference to external entity in attribute value
    …=14'>14</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href=…

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

  • Error Line 256, Column 651: reference to entity "vm" for which no system identifier could be generated
    …=14'>14</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 656: reference not terminated by REFC delimiter
    …14</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 656: reference to external entity in attribute value
    …14</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 656: reference to entity "sm" for which no system identifier could be generated
    …14</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 661: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href='/?q=&vm=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 256, Column 661: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href='/?q=&vm=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 256, Column 661: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=15'>15</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 699: reference not terminated by REFC delimiter
    …=15'>15</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href=…

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

  • Warning Line 256, Column 699: reference to external entity in attribute value
    …=15'>15</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href=…

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

  • Error Line 256, Column 699: reference to entity "vm" for which no system identifier could be generated
    …=15'>15</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 704: reference not terminated by REFC delimiter
    …15</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 704: reference to external entity in attribute value
    …15</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 704: reference to entity "sm" for which no system identifier could be generated
    …15</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 709: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href='/?q=&vm=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 256, Column 709: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href='/?q=&vm=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 256, Column 709: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=16'>16</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 747: reference not terminated by REFC delimiter
    …=16'>16</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href=…

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

  • Warning Line 256, Column 747: reference to external entity in attribute value
    …=16'>16</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href=…

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

  • Error Line 256, Column 747: reference to entity "vm" for which no system identifier could be generated
    …=16'>16</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 752: reference not terminated by REFC delimiter
    …16</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 752: reference to external entity in attribute value
    …16</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 752: reference to entity "sm" for which no system identifier could be generated
    …16</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 757: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href='/?q=&vm=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 256, Column 757: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href='/?q=&vm=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 256, Column 757: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=17'>17</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 795: reference not terminated by REFC delimiter
    …=17'>17</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href=…

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

  • Warning Line 256, Column 795: reference to external entity in attribute value
    …=17'>17</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href=…

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

  • Error Line 256, Column 795: reference to entity "vm" for which no system identifier could be generated
    …=17'>17</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 800: reference not terminated by REFC delimiter
    …17</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 800: reference to external entity in attribute value
    …17</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 800: reference to entity "sm" for which no system identifier could be generated
    …17</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 805: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href='/?q=&vm=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 256, Column 805: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href='/?q=&vm=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 256, Column 805: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=18'>18</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 843: reference not terminated by REFC delimiter
    …=18'>18</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href=…

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

  • Warning Line 256, Column 843: reference to external entity in attribute value
    …=18'>18</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href=…

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

  • Error Line 256, Column 843: reference to entity "vm" for which no system identifier could be generated
    …=18'>18</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href=…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 848: reference not terminated by REFC delimiter
    …18</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href='/?q=…

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

  • Warning Line 256, Column 848: reference to external entity in attribute value
    …18</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href='/?q=…

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

  • Error Line 256, Column 848: reference to entity "sm" for which no system identifier could be generated
    …18</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href='/?q=…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 853: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href='/?q=&vm=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 256, Column 853: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href='/?q=&vm=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 256, Column 853: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=19'>19</a> </li><li> <a href='/?q=&vm=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 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 891: reference not terminated by REFC delimiter
    …=19'>19</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li…

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

  • Warning Line 256, Column 891: reference to external entity in attribute value
    …=19'>19</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li…

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

  • Error Line 256, Column 891: reference to entity "vm" for which no system identifier could be generated
    …=19'>19</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 896: reference not terminated by REFC delimiter
    …19</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li><a h…

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

  • Warning Line 256, Column 896: reference to external entity in attribute value
    …19</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li><a h…

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

  • Error Line 256, Column 896: reference to entity "sm" for which no system identifier could be generated
    …19</a> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li><a h…

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

  • Info Line 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 901: reference not terminated by REFC delimiter
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li><a href='…

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

  • Warning Line 256, Column 901: reference to external entity in attribute value
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li><a href='…

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

  • Error Line 256, Column 901: reference to entity "pn" for which no system identifier could be generated
    …> </li><li> <a href='/?q=&vm=C&sm=t&pn=20'>20</a> </li><li> ... </li><a href='…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Warning Line 256, Column 948: reference not terminated by REFC delimiter
    …a> </li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div cla…

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

  • Warning Line 256, Column 948: reference to external entity in attribute value
    …a> </li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div cla…

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

  • Error Line 256, Column 948: reference to entity "vm" for which no system identifier could be generated
    …a> </li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div cla…

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

  • Info Line 256, Column 40: entity was defined here
    …			 <ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href…
  • Warning Line 256, Column 953: reference not terminated by REFC delimiter
    …li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="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 256, Column 953: reference to external entity in attribute value
    …li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="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 256, Column 953: reference to entity "sm" for which no system identifier could be generated
    …li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="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 256, Column 45: entity was defined here
    …ul><li> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q…
  • Warning Line 256, Column 958: reference not terminated by REFC delimiter
    …i> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="clear"…

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

  • Warning Line 256, Column 958: reference to external entity in attribute value
    …i> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="clear"…

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

  • Error Line 256, Column 958: reference to entity "pn" for which no system identifier could be generated
    …i> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="clear"…

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

  • Info Line 256, Column 50: entity was defined here
    …i> 1 </li><li> <a href='/?q=&vm=C&sm=t&pn=2'>2</a> </li><li> <a href='/?q=&vm=…
  • Error Line 256, Column 961: document type does not allow element "a" here; assuming missing "li" start-tag
    …... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="clear"></…
  • Error Line 256, Column 977: end tag for "li" omitted, but OMITTAG NO was specified
    … </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a></ul>		<div class="clear"></div>

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

  • Info Line 256, Column 932: start tag was here
    …sm=t&pn=20'>20</a> </li><li> ... </li><a href='/?q=&vm=C&sm=t&pn=2'>Next >></a…
  • Error Line 260, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ntact.php?src=123any-illegal-content' target=_blank>Report Illegal Content</a> 
  • Error Line 279, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

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

  • Info Line 18, Column 1: start tag was here
    <script>

Visitor Analysis

Daily Visitor
  • 1.178 visits