Source to Download Free Games, Movies, Music, TV Shows, Applications, Ebooks, Magazines, Tutorials ...

downarchive.ws
  • Domain Name
    downarchive.ws
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #16083
  • Page Size
    48.2 KB
  • Ip Address
    83.167.226.125
  • Heading
    H1: 17, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 11 JPG, 16 PNG

Website Meta Analysis

  • Title
    DownArchive - Your Future Downloads
  • Meta Keyword
    Free Download, Rapidgator, Depositfiles. Zippyshare, Mediafire, Letitbit, Turbobit, Uploaded, Filefactory, Rapidshare, Torrent
  • Meta Description
    Source to Download Free Games, Movies, Music, TV Shows, Applications, Ebooks, Magazines, Tutorials

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    83.167.226.125
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from downarchive.ws.

HTML Analysis

  • server: nginx
  • date: Mon, 29 Apr 2013 23:42:03 GMT
  • content-type: text/html
  • content-length: 9600
  • connection: keep-alive
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA


Welcome to the .WS Whois Server

Use of this service for any purpose other
than determining the availability of a domain
in the .WS TLD to be registered is strictly
prohibited.

Domain Name: DOWNARCHIVE.WS

Registrant Name: Use registrar whois listed below
Registrant Email: Use registrar whois listed below

Administrative Contact Email: Use registrar whois listed below
Administrative Contact Telephone: Use registrar whois listed below

Registrar Name: eNom
Registrar Email: email
Registrar Telephone: 425-974-4500
Registrar Whois: whois.enom.com

Domain Created: 2012-07-07
Domain Last Updated: 2012-07-07
Domain Currently Expires: 2013-07-07

Current Nameservers:

dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com


DNS Analysis


DNS servers
dns5.name-services.com [98.124.196.1]
dns4.name-services.com [98.124.194.1]
dns2.name-services.com [98.124.197.1]
dns1.name-services.com [98.124.192.1]
dns3.name-services.com [98.124.193.1]


DNS Records

Answer records
downarchive.ws NS  dns2.name-services.com 3600s
downarchive.ws NS  dns1.name-services.com 3600s
downarchive.ws NS  dns5.name-services.com 3600s
downarchive.ws SOA
server: dns1.name-services.com
email: info@name-services.com
serial: 2002050701
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1800s
downarchive.ws NS  dns3.name-services.com 3600s
downarchive.ws A 83.167.226.125 1800s
downarchive.ws NS  dns4.name-services.com 3600s

Authority records

Additional records

IP 83.167.226.125 Analysis

  • Country Code
    CZ
  • Country Code3
    CZE
  • Country Name
    Czech Republic
  • City
    H�sting
  • Continent Code
    EU
  • Latitude
    49.0167
  • Longitude
    15.9.
  • No whois ip data for 83.167.226.125

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 223 Errors
  • 99 Warnings
Ratio Text/Html
  • 0.5963924934712634
Message Error
  • Error Line 5, Column 83: required attribute "type" not specified
    …anguage="Javascript" src="http://code.jquery.com/jquery-1.8.3.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 25, Column 53: document type does not allow element "script" here; assuming missing "body" start-tag
    <script language="javascript" type="text/javascript">
  • Error Line 52, Column 30: required attribute "type" not specified
    <script language="Javascript">ShowOrHide('b-login');</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 53, Column 19: document type does not allow element "body" here
    <body id="wrapper">		

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

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

  • Warning Line 60, Column 223: cannot generate system identifier for general entity "blogurl"
    …s, Graphical, Hot Magazine, Templates&blogurl=http://www.downarchive.com/&rssu…

    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 60, Column 223: general entity "blogurl" not defined and no default entity
    …s, Graphical, Hot Magazine, Templates&blogurl=http://www.downarchive.com/&rssu…

    This is usually a cascading error caused by 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 60, Column 230: reference not terminated by REFC delimiter
    …hical, Hot Magazine, Templates&blogurl=http://www.downarchive.com/&rssurl=http…

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

  • Warning Line 60, Column 230: reference to external entity in attribute value
    …hical, Hot Magazine, Templates&blogurl=http://www.downarchive.com/&rssurl=http…

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

  • Error Line 60, Column 230: reference to entity "blogurl" for which no system identifier could be generated
    …hical, Hot Magazine, Templates&blogurl=http://www.downarchive.com/&rssurl=http…

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

  • Info Line 60, Column 222: entity was defined here
    …ts, Graphical, Hot Magazine, Templates&blogurl=http://www.downarchive.com/&rss…
  • Warning Line 60, Column 259: cannot generate system identifier for general entity "rssurl"
    …s&blogurl=http://www.downarchive.com/&rssurl=http://www.downarchive.com/rss.xm…

    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 60, Column 259: general entity "rssurl" not defined and no default entity
    …s&blogurl=http://www.downarchive.com/&rssurl=http://www.downarchive.com/rss.xm…

    This is usually a cascading error caused by 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 60, Column 265: reference not terminated by REFC delimiter
    …url=http://www.downarchive.com/&rssurl=http://www.downarchive.com/rss.xml&chk_…

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

  • Warning Line 60, Column 265: reference to external entity in attribute value
    …url=http://www.downarchive.com/&rssurl=http://www.downarchive.com/rss.xml&chk_…

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

  • Error Line 60, Column 265: reference to entity "rssurl" for which no system identifier could be generated
    …url=http://www.downarchive.com/&rssurl=http://www.downarchive.com/rss.xml&chk_…

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

  • Info Line 60, Column 258: entity was defined here
    …es&blogurl=http://www.downarchive.com/&rssurl=http://www.downarchive.com/rss.x…
  • Warning Line 60, Column 301: cannot generate system identifier for general entity "chk_weblogscom"
    …rl=http://www.downarchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_techn…

    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 60, Column 301: general entity "chk_weblogscom" not defined and no default entity
    …rl=http://www.downarchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_techn…

    This is usually a cascading error caused by 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 60, Column 315: reference not terminated by REFC delimiter
    …downarchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_f…

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

  • Warning Line 60, Column 315: reference to external entity in attribute value
    …downarchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_f…

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

  • Error Line 60, Column 315: reference to entity "chk_weblogscom" for which no system identifier could be generated
    …downarchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_f…

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

  • Info Line 60, Column 300: entity was defined here
    …url=http://www.downarchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_tech…
  • Warning Line 60, Column 319: cannot generate system identifier for general entity "chk_blogs"
    …archive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedb…

    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 60, Column 319: general entity "chk_blogs" not defined and no default entity
    …archive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedb…

    This is usually a cascading error caused by 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 60, Column 328: reference not terminated by REFC delimiter
    …om/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&…

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

  • Warning Line 60, Column 328: reference to external entity in attribute value
    …om/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&…

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

  • Error Line 60, Column 328: reference to entity "chk_blogs" for which no system identifier could be generated
    …om/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&…

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

  • Info Line 60, Column 318: entity was defined here
    …narchive.com/rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feed…
  • Warning Line 60, Column 332: cannot generate system identifier for general entity "chk_technorati"
    …ss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_…

    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 60, Column 332: general entity "chk_technorati" not defined and no default entity
    …ss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_…

    This is usually a cascading error caused by 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 60, Column 346: reference not terminated by REFC delimiter
    …logscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk…

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

  • Warning Line 60, Column 346: reference to external entity in attribute value
    …logscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk…

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

  • Error Line 60, Column 346: reference to entity "chk_technorati" for which no system identifier could be generated
    …logscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk…

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

  • Info Line 60, Column 331: entity was defined here
    …rss.xml&chk_weblogscom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk…
  • Warning Line 60, Column 350: cannot generate system identifier for general entity "chk_feedburner"
    …com=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_new…

    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 60, Column 350: general entity "chk_feedburner" not defined and no default entity
    …com=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_new…

    This is usually a cascading error caused by 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 60, Column 364: reference not terminated by REFC delimiter
    …gs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_…

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

  • Warning Line 60, Column 364: reference to external entity in attribute value
    …gs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_…

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

  • Error Line 60, Column 364: reference to entity "chk_feedburner" for which no system identifier could be generated
    …gs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_…

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

  • Info Line 60, Column 349: entity was defined here
    …scom=on&chk_blogs=on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_ne…
  • Warning Line 60, Column 368: cannot generate system identifier for general entity "chk_syndic8"
    …n&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myya…

    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 60, Column 368: general entity "chk_syndic8" not defined and no default entity
    …n&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myya…

    This is usually a cascading error caused by 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 60, Column 379: reference not terminated by REFC delimiter
    …orati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_…

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

  • Warning Line 60, Column 379: reference to external entity in attribute value
    …orati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_…

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

  • Error Line 60, Column 379: reference to entity "chk_syndic8" for which no system identifier could be generated
    …orati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_…

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

  • Info Line 60, Column 367: entity was defined here
    …on&chk_technorati=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myy…
  • Warning Line 60, Column 383: cannot generate system identifier for general entity "chk_newsgator"
    …i=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubs…

    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 60, Column 383: general entity "chk_newsgator" not defined and no default entity
    …i=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubs…

    This is usually a cascading error caused by 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 60, Column 396: reference not terminated by REFC delimiter
    …burner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_…

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

  • Warning Line 60, Column 396: reference to external entity in attribute value
    …burner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_…

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

  • Error Line 60, Column 396: reference to entity "chk_newsgator" for which no system identifier could be generated
    …burner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_…

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

  • Info Line 60, Column 382: entity was defined here
    …ti=on&chk_feedburner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pub…
  • Warning Line 60, Column 400: cannot generate system identifier for general entity "chk_myyahoo"
    …er=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blog…

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

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

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

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

  • Error Line 60, Column 400: general entity "chk_myyahoo" not defined and no default entity
    …er=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blog…

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

  • Warning Line 60, Column 411: reference not terminated by REFC delimiter
    …yndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&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 60, Column 411: reference to external entity in attribute value
    …yndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&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 60, Column 411: reference to entity "chk_myyahoo" for which no system identifier could be generated
    …yndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&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 60, Column 399: entity was defined here
    …ner=on&chk_syndic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blo…
  • Warning Line 60, Column 415: cannot generate system identifier for general entity "chk_pubsubcom"
    …c8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_b…

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

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

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

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

  • Error Line 60, Column 415: general entity "chk_pubsubcom" not defined and no default entity
    …c8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_b…

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

  • Warning Line 60, Column 428: reference not terminated by REFC delimiter
    …sgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&…

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

  • Warning Line 60, Column 428: reference to external entity in attribute value
    …sgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&…

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

  • Error Line 60, Column 428: reference to entity "chk_pubsubcom" for which no system identifier could be generated
    …sgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&…

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

  • Info Line 60, Column 414: entity was defined here
    …ic8=on&chk_newsgator=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_…
  • Warning Line 60, Column 432: cannot generate system identifier for general entity "chk_blogdigger"
    …or=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_…

    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 60, Column 432: general entity "chk_blogdigger" not defined and no default entity
    …or=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_…

    This is usually a cascading error caused by 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 60, Column 446: reference not terminated by REFC delimiter
    …hoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&ch…

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

  • Warning Line 60, Column 446: reference to external entity in attribute value
    …hoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&ch…

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

  • Error Line 60, Column 446: reference to entity "chk_blogdigger" for which no system identifier could be generated
    …hoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&ch…

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

  • Info Line 60, Column 431: entity was defined here
    …tor=on&chk_myyahoo=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk…
  • Warning Line 60, Column 450: cannot generate system identifier for general entity "chk_blogstreet"
    …on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_we…

    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 60, Column 450: general entity "chk_blogstreet" not defined and no default entity
    …on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_we…

    This is usually a cascading error caused by 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 60, Column 464: reference not terminated by REFC delimiter
    …om=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&ch…

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

  • Warning Line 60, Column 464: reference to external entity in attribute value
    …om=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&ch…

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

  • Error Line 60, Column 464: reference to entity "chk_blogstreet" for which no system identifier could be generated
    …om=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&ch…

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

  • Info Line 60, Column 449: entity was defined here
    …=on&chk_pubsubcom=on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_w…
  • Warning Line 60, Column 468: cannot generate system identifier for general entity "chk_moreover"
    …n&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_ic…

    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 60, Column 468: general entity "chk_moreover" not defined and no default entity
    …n&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_ic…

    This is usually a cascading error caused by 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 60, Column 480: reference not terminated by REFC delimiter
    …gger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&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 60, Column 480: reference to external entity in attribute value
    …gger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&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 60, Column 480: reference to entity "chk_moreover" for which no system identifier could be generated
    …gger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&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 60, Column 467: entity was defined here
    …on&chk_blogdigger=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_i…
  • Warning Line 60, Column 484: cannot generate system identifier for general entity "chk_weblogalot"
    …=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_n…

    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 60, Column 484: general entity "chk_weblogalot" not defined and no default entity
    …=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_n…

    This is usually a cascading error caused by 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 60, Column 498: reference not terminated by REFC delimiter
    …reet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&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 60, Column 498: reference to external entity in attribute value
    …reet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&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 60, Column 498: reference to entity "chk_weblogalot" for which no system identifier could be generated
    …reet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&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 60, Column 483: entity was defined here
    …r=on&chk_blogstreet=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_…
  • Warning Line 60, Column 502: cannot generate system identifier for general entity "chk_icerocket"
    …=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_t…

    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 60, Column 502: general entity "chk_icerocket" not defined and no default entity
    …=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_t…

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

  • Warning Line 60, Column 515: reference not terminated by REFC delimiter
    …ver=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=…

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

  • Warning Line 60, Column 515: reference to external entity in attribute value
    …ver=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=…

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

  • Error Line 60, Column 515: reference to entity "chk_icerocket" for which no system identifier could be generated
    …ver=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=…

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

  • Info Line 60, Column 501: entity was defined here
    …t=on&chk_moreover=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_…
  • Warning Line 60, Column 519: cannot generate system identifier for general entity "chk_newsisfree"
    …on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&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 60, Column 519: general entity "chk_newsisfree" not defined and no default entity
    …on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&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 60, Column 533: reference not terminated by REFC delimiter
    …lot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&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 60, Column 533: reference to external entity in attribute value
    …lot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&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 60, Column 533: reference to entity "chk_newsisfree" for which no system identifier could be generated
    …lot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&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 60, Column 518: entity was defined here
    …=on&chk_weblogalot=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&…
  • Warning Line 60, Column 537: cannot generate system identifier for general entity "chk_topicexchange"
    …on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_t…

    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 60, Column 537: general entity "chk_topicexchange" not defined and no default entity
    …on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_t…

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

  • Warning Line 60, Column 554: reference not terminated by REFC delimiter
    …on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bl…

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

  • Warning Line 60, Column 554: reference to external entity in attribute value
    …on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bl…

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

  • Error Line 60, Column 554: reference to entity "chk_topicexchange" for which no system identifier could be generated
    …on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bl…

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

  • Info Line 60, Column 536: entity was defined here
    …=on&chk_icerocket=on&chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_…
  • Warning Line 60, Column 558: cannot generate system identifier for general entity "chk_google"
    …hk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_blogli…

    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 60, Column 558: general entity "chk_google" not defined and no default entity
    …hk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_blogli…

    This is usually a cascading error caused by 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 60, Column 568: reference not terminated by REFC delimiter
    …ree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk…

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

  • Warning Line 60, Column 568: reference to external entity in attribute value
    …ree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk…

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

  • Error Line 60, Column 568: reference to entity "chk_google" for which no system identifier could be generated
    …ree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk…

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

  • Info Line 60, Column 557: entity was defined here
    …chk_newsisfree=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_blogl…
  • Warning Line 60, Column 572: cannot generate system identifier for general entity "chk_tailrank"
    …on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_pos…

    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 60, Column 572: general entity "chk_tailrank" not defined and no default entity
    …on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_pos…

    This is usually a cascading error caused by 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 60, Column 584: reference not terminated by REFC delimiter
    …exchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk…

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

  • Warning Line 60, Column 584: reference to external entity in attribute value
    …exchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk…

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

  • Error Line 60, Column 584: reference to entity "chk_tailrank" for which no system identifier could be generated
    …exchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk…

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

  • Info Line 60, Column 571: entity was defined here
    …=on&chk_topicexchange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_po…
  • Warning Line 60, Column 588: cannot generate system identifier for general entity "chk_bloglines"
    …ange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_sky…

    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 60, Column 588: general entity "chk_bloglines" not defined and no default entity
    …ange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_sky…

    This is usually a cascading error caused by 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 60, Column 601: reference not terminated by REFC delimiter
    …oogle=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_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 60, Column 601: reference to external entity in attribute value
    …oogle=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_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 60, Column 601: reference to entity "chk_bloglines" for which no system identifier could be generated
    …oogle=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_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 60, Column 587: entity was defined here
    …hange=on&chk_google=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_sk…
  • Warning Line 60, Column 605: cannot generate system identifier for general entity "chk_postrank"
    …e=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_colle…

    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 60, Column 605: general entity "chk_postrank" not defined and no default entity
    …e=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_colle…

    This is usually a cascading error caused by 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 60, Column 617: reference not terminated by REFC delimiter
    …lrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_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 60, Column 617: reference to external entity in attribute value
    …lrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_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 60, Column 617: reference to entity "chk_postrank" for which no system identifier could be generated
    …lrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_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 60, Column 604: entity was defined here
    …le=on&chk_tailrank=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_coll…
  • Warning Line 60, Column 621: cannot generate system identifier for general entity "chk_skygrid"
    …k=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_super…

    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 60, Column 621: general entity "chk_skygrid" not defined and no default entity
    …k=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_super…

    This is usually a cascading error caused by 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 60, Column 632: reference not terminated by REFC delimiter
    …oglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&ch…

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

  • Warning Line 60, Column 632: reference to external entity in attribute value
    …oglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&ch…

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

  • Error Line 60, Column 632: reference to entity "chk_skygrid" for which no system identifier could be generated
    …oglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&ch…

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

  • Info Line 60, Column 620: entity was defined here
    …nk=on&chk_bloglines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_supe…
  • Warning Line 60, Column 636: cannot generate system identifier for general entity "chk_collecta"
    …nes=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_au…

    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 60, Column 636: general entity "chk_collecta" not defined and no default entity
    …nes=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_au…

    This is usually a cascading error caused by 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 60, Column 648: reference not terminated by REFC delimiter
    …ostrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=o…

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

  • Warning Line 60, Column 648: reference to external entity in attribute value
    …ostrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=o…

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

  • Error Line 60, Column 648: reference to entity "chk_collecta" for which no system identifier could be generated
    …ostrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=o…

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

  • Info Line 60, Column 635: entity was defined here
    …ines=on&chk_postrank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_a…
  • Warning Line 60, Column 652: cannot generate system identifier for general entity "chk_superfeedr"
    …ank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&ch…

    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 60, Column 652: general entity "chk_superfeedr" not defined and no default entity
    …ank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&ch…

    This is usually a cascading error caused by 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 60, Column 666: reference not terminated by REFC delimiter
    …grid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&ch…

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

  • Warning Line 60, Column 666: reference to external entity in attribute value
    …grid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&ch…

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

  • Error Line 60, Column 666: reference to entity "chk_superfeedr" for which no system identifier could be generated
    …grid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&ch…

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

  • Info Line 60, Column 651: entity was defined here
    …rank=on&chk_skygrid=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&c…
  • Warning Line 60, Column 670: cannot generate system identifier for general entity "chk_audioweblogs"
    …=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_ge…

    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 60, Column 670: general entity "chk_audioweblogs" not defined and no default entity
    …=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_ge…

    This is usually a cascading error caused by 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 60, Column 686: reference not terminated by REFC delimiter
    …=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=…

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

  • Warning Line 60, Column 686: reference to external entity in attribute value
    …=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=…

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

  • Error Line 60, Column 686: reference to entity "chk_audioweblogs" for which no system identifier could be generated
    …=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=…

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

  • Info Line 60, Column 669: entity was defined here
    …d=on&chk_collecta=on&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_g…
  • Warning Line 60, Column 690: cannot generate system identifier for general entity "chk_rubhub"
    …chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&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 60, Column 690: general entity "chk_rubhub" not defined and no default entity
    …chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&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 60, Column 700: reference not terminated by REFC delimiter
    …eedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogsha…

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

  • Warning Line 60, Column 700: reference to external entity in attribute value
    …eedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogsha…

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

  • Error Line 60, Column 700: reference to entity "chk_rubhub" for which no system identifier could be generated
    …eedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogsha…

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

  • Info Line 60, Column 689: entity was defined here
    …&chk_superfeedr=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&…
  • Warning Line 60, Column 704: cannot generate system identifier for general entity "chk_geourl"
    …=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=…

    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 60, Column 704: general entity "chk_geourl" not defined and no default entity
    …=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=…

    This is usually a cascading error caused by 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 60, Column 714: reference not terminated by REFC delimiter
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Warning Line 60, Column 714: reference to external entity in attribute value
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Error Line 60, Column 714: reference to entity "chk_geourl" for which no system identifier could be generated
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Info Line 60, Column 703: entity was defined here
    …r=on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares…
  • Warning Line 60, Column 718: cannot generate system identifier for general entity "chk_a2b"
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

    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 60, Column 718: general entity "chk_a2b" not defined and no default entity
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

    This is usually a cascading error caused by 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 60, Column 725: reference not terminated by REFC delimiter
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Warning Line 60, Column 725: reference to external entity in attribute value
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Error Line 60, Column 725: reference to entity "chk_a2b" for which no system identifier could be generated
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Info Line 60, Column 717: entity was defined here
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on
  • Warning Line 60, Column 729: cannot generate system identifier for general entity "chk_blogshares"
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

    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 60, Column 729: general entity "chk_blogshares" not defined and no default entity
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

    This is usually a cascading error caused by 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 60, Column 743: reference not terminated by REFC delimiter
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Warning Line 60, Column 743: reference to external entity in attribute value
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Error Line 60, Column 743: reference to entity "chk_blogshares" for which no system identifier could be generated
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on

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

  • Info Line 60, Column 728: entity was defined here
    …on&chk_audioweblogs=on&chk_rubhub=on&chk_geourl=on&chk_a2b=on&chk_blogshares=on
  • Error Line 61, Column 9: duplicate specification of attribute "target"
    "target="_blank">Ping 1</a>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 85, Column 33: document type does not allow element "a" here; assuming missing "li" start-tag
            <a href="/" class="hlit"><img src="/templates/DAVLay/img/logoda.jpg" al…
  • Error Line 87, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
        </ul>

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

  • Info Line 85, Column 9: start tag was here
            <a href="/" class="hlit"><img src="/templates/DAVLay/img/logoda.jpg" al…
  • Error Line 102, Column 58: required attribute "action" not specified
    <form method="post" onsubmit="javascript:showBusyLayer()">

    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 102, Column 58: document type does not allow element "form" here; assuming missing "li" start-tag
    <form method="post" onsubmit="javascript:showBusyLayer()">
  • Error Line 106, Column 214: end tag for "input" omitted, but OMITTAG NO was specified
    …Here')this.value=''" onblur="if(this.value=='')this.value='Type It Here'"></td>

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

  • Info Line 106, Column 18: start tag was here
    		<td class="va"><input type="text" name="login_name" class="login" id="nameqwe…
  • Error Line 107, Column 6: document type does not allow element "br" here; missing one of "th", "td" start-tag
    <br />

    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 109, Column 217: end tag for "input" omitted, but OMITTAG NO was specified
    …d...')this.value=''" onblur="if(this.value=='')this.value='Password...'" ></td>

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

  • Info Line 109, Column 18: start tag was here
    		<td class="va"><input type="password" name="login_password" class="login" id=…
  • Error Line 111, Column 6: document type does not allow element "br" here; missing one of "th", "td" start-tag
    <br />

    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 113, Column 168: end tag for "input" omitted, but OMITTAG NO was specified
    …bmit" src="http://www.downarchive.com/templates/DAVLay/img/go.png" id="button">

    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 113, Column 26: start tag was here
    		<td class="va" id="go"><input type="image" name="submit" onclick="submit();" …
  • Error Line 114, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
            <input name="login" type="hidden" value="submit"></td>

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

  • Info Line 114, Column 9: start tag was here
            <input name="login" type="hidden" value="submit"></td>
  • Error Line 118, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
    </form></ul>

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

  • Info Line 102, Column 1: start tag was here
    <form method="post" onsubmit="javascript:showBusyLayer()">
  • Error Line 123, Column 21: document type does not allow element "p" here; assuming missing "li" start-tag
        <p class="top-r"><img src="/templates/DAVLay/img/tr.png" /></p>
  • Error Line 123, Column 63: required attribute "alt" not specified
        <p class="top-r"><img src="/templates/DAVLay/img/tr.png" /></p>

    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 128, Column 17: character data is not allowed here
              &rarr; <a href="/"><b>Homepage</b></a><br/>

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 128, Column 29: document type does not allow element "a" here; assuming missing "li" start-tag
              &rarr; <a href="/"><b>Homepage</b></a><br/>
  • Warning Line 137, Column 80: character "&" is the first character of a delimiter but occurred as data
    …l;&nbsp;<a href="/software/graphics__design/">&rarr;  Graphics & Design</a><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.
  • Error Line 137, Column 96: end tag for "br" omitted, but OMITTAG NO was specified
    …l;&nbsp;<a href="/software/graphics__design/">&rarr;  Graphics & Design</a><br>

    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 137, Column 92: start tag was here
    …l;&nbsp;<a href="/software/graphics__design/">&rarr;  Graphics & Design</a><br>
  • Error Line 138, Column 84: end tag for "br" omitted, but OMITTAG NO was specified
    …p;&nbsp;&bull;&nbsp;<a href="/software/downloaders/">&rarr; Downloaders</a><br>

    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 138, Column 80: start tag was here
    …p;&nbsp;&bull;&nbsp;<a href="/software/downloaders/">&rarr; Downloaders</a><br>
  • Error Line 139, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …bsp;&nbsp;&bull;&nbsp;<a href="/software/multimedia/">&rarr; MultiMedia</a><br>

    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 139, Column 78: start tag was here
    …bsp;&nbsp;&bull;&nbsp;<a href="/software/multimedia/">&rarr; MultiMedia</a><br>
  • Error Line 140, Column 102: end tag for "br" omitted, but OMITTAG NO was specified
    …p;<a href="/software/desktop_enhancements/">&rarr; Desktop Enhancements</a><br>

    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 140, Column 98: start tag was here
    …p;<a href="/software/desktop_enhancements/">&rarr; Desktop Enhancements</a><br>
  • Error Line 141, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/dvd_tools/">&rarr; DVD Tools</a><br>

    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 141, Column 76: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/dvd_tools/">&rarr; DVD Tools</a><br>
  • Warning Line 142, Column 85: character "&" is the first character of a delimiter but occurred as data
    …;<a href="/software/virtual_cd_cd_tools/">&rarr;  Virtual CD & CD Tools</a><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.
  • Error Line 142, Column 103: end tag for "br" omitted, but OMITTAG NO was specified
    …;<a href="/software/virtual_cd_cd_tools/">&rarr;  Virtual CD & CD Tools</a><br>

    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 142, Column 99: start tag was here
    …;<a href="/software/virtual_cd_cd_tools/">&rarr;  Virtual CD & CD Tools</a><br>
  • Error Line 143, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/office/">&rarr; Office</a><br>

    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 143, Column 70: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/office/">&rarr; Office</a><br>
  • Error Line 144, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …bsp;&nbsp;&bull;&nbsp;<a href="/software/file_tools/">&rarr; File Tools</a><br>

    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 144, Column 78: start tag was here
    …bsp;&nbsp;&bull;&nbsp;<a href="/software/file_tools/">&rarr; File Tools</a><br>
  • Error Line 145, Column 81: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/aio/">&rarr; All In One (AIO)</a><br>

    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 145, Column 77: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/aio/">&rarr; All In One (AIO)</a><br>
  • Error Line 147, Column 78: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/portable/">&rarr; Portable</a><br>

    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 147, Column 74: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/portable/">&rarr; Portable</a><br>
  • Error Line 148, Column 84: end tag for "br" omitted, but OMITTAG NO was specified
    …p;&nbsp;&bull;&nbsp;<a href="/software/programming/">&rarr; Programming</a><br>

    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 148, Column 80: start tag was here
    …p;&nbsp;&bull;&nbsp;<a href="/software/programming/">&rarr; Programming</a><br>
  • Error Line 149, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/others/">&rarr; Others</a><br>

    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 149, Column 70: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/others/">&rarr; Others</a><br>
  • Error Line 150, Column 78: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/macosx/">&rarr; For MacOSX</a><br>

    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 150, Column 74: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/software/macosx/">&rarr; For MacOSX</a><br>
  • Error Line 151, Column 41: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/script/">Script</a><br>

    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 151, Column 37: start tag was here
    &rarr; <a href="/script/">Script</a><br>
  • Error Line 152, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/music">Music</a><br>

    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 152, Column 34: start tag was here
    &rarr; <a href="/music">Music</a><br>
  • Error Line 153, Column 41: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/movies/">Movies</a><br>

    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 153, Column 37: start tag was here
    &rarr; <a href="/movies/">Movies</a><br>
  • Error Line 154, Column 75: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/movies/tvshows/">&rarr; Tv Shows</a><br>

    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 154, Column 71: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/movies/tvshows/">&rarr; Tv Shows</a><br>
  • Error Line 155, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …bsp;&nbsp;&bull;&nbsp;<a href="/movies/documentary/">&rarr; Documentary</a><br>

    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 155, Column 78: start tag was here
    …bsp;&nbsp;&bull;&nbsp;<a href="/movies/documentary/">&rarr; Documentary</a><br>
  • Error Line 156, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/pda_mobile/">PDA / Mobile</a><br>

    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 156, Column 47: start tag was here
    &rarr; <a href="/pda_mobile/">PDA / Mobile</a><br>
  • Error Line 157, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
    …&nbsp;&bull;&nbsp;<a href="/pda_mobile/application/">&rarr; Application</a><br>

    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 157, Column 82: start tag was here
    …&nbsp;&bull;&nbsp;<a href="/pda_mobile/application/">&rarr; Application</a><br>
  • Error Line 158, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/pda_mobile/game/">&rarr; Game</a><br>

    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 158, Column 68: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/pda_mobile/game/">&rarr; Game</a><br>
  • Error Line 159, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/pda_mobile/theme/">&rarr; Theme</a><br>

    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 159, Column 70: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/pda_mobile/theme/">&rarr; Theme</a><br>
  • Error Line 160, Column 42: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/ebooks/">E-Books</a><br>

    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 160, Column 38: start tag was here
    &rarr; <a href="/ebooks/">E-Books</a><br>
  • Error Line 161, Column 76: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/ebooks/magazine/">&rarr; Magazine</a><br>

    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 161, Column 72: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/ebooks/magazine/">&rarr; Magazine</a><br>
  • Error Line 162, Column 88: end tag for "br" omitted, but OMITTAG NO was specified
    …bsp;&bull;&nbsp;<a href="/ebooks/video_training/">&rarr; Video Training</a><br>

    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 162, Column 84: start tag was here
    …bsp;&bull;&nbsp;<a href="/ebooks/video_training/">&rarr; Video Training</a><br>
  • Error Line 163, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/games/"> Games</a><br>

    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 163, Column 36: start tag was here
    &rarr; <a href="/games/"> Games</a><br>
  • Error Line 164, Column 73: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/games/console/">&rarr; Console</a><br>

    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 164, Column 69: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/games/console/">&rarr; Console</a><br>
  • Error Line 165, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/games/portable-game/">&rarr; Portable</a><br>

    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 165, Column 76: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/games/portable-game/">&rarr; Portable</a><br>
  • Error Line 166, Column 45: end tag for "br" omitted, but OMITTAG NO was specified
    &rarr; <a href="/graphics/">Graphics</a><br>

    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 166, Column 41: start tag was here
    &rarr; <a href="/graphics/">Graphics</a><br>
  • Error Line 167, Column 78: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/graphics/template/">&rarr; Template</a><br>

    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 167, Column 74: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/graphics/template/">&rarr; Template</a><br>
  • Error Line 168, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …bsp;&nbsp;&bull;&nbsp;<a href="/graphics/wallpapers/">&rarr; Wallpapers</a><br>

    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 168, Column 78: start tag was here
    …bsp;&nbsp;&bull;&nbsp;<a href="/graphics/wallpapers/">&rarr; Wallpapers</a><br>
  • Error Line 169, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/graphics/icons/">&rarr; Icons</a><br>

    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 169, Column 68: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/graphics/icons/">&rarr; Icons</a><br>
  • Error Line 170, Column 76: end tag for "br" omitted, but OMITTAG NO was specified
    &nbsp;&nbsp;&bull;&nbsp;<a href="/graphics/vectors/">&rarr; Vectors</a><br>

    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 170, Column 72: start tag was here
    &nbsp;&nbsp;&bull;&nbsp;<a href="/graphics/vectors/">&rarr; Vectors</a><br>
  • Error Line 171, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …bsp;&nbsp;&bull;&nbsp;<a href="/graphics/graphic-others/">&rarr; Others</a><br>

    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 171, Column 78: start tag was here
    …bsp;&nbsp;&bull;&nbsp;<a href="/graphics/graphic-others/">&rarr; Others</a><br>
  • Error Line 173, Column 13: end tag for "li" omitted, but OMITTAG NO was specified
            </ul>

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

  • Info Line 128, Column 18: start tag was here
              &rarr; <a href="/"><b>Homepage</b></a><br/>
  • Error Line 176, Column 63: required attribute "alt" not specified
        <p class="bot-r"><img src="/templates/DAVLay/img/br.png" /></p>

    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 179, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
        	<div><br>

    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 179, Column 11: start tag was here
        	<div><br>
  • Error Line 183, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <table cellpadding=0 cellspacing=0 class=text>
  • Error Line 183, Column 42: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <table cellpadding=0 cellspacing=0 class=text>
  • Error Line 183, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <table cellpadding=0 cellspacing=0 class=text>
  • Error Line 184, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <tr><td colspan=2><b>Top Contributors:
  • Error Line 185, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
            </td></tr><tr>

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

  • Info Line 184, Column 27: start tag was here
            <tr><td colspan=2><b>Top Contributors:
  • Error Line 309, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width='90%' cellpadding=0 cellspacing=0 class=stext>
  • Error Line 309, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width='90%' cellpadding=0 cellspacing=0 class=stext>
  • Error Line 309, Column 54: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width='90%' cellpadding=0 cellspacing=0 class=stext>
  • Error Line 310, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <tr><td><br><br><b>

    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 310, Column 9: start tag was here
    <tr><td><br><br><b>
  • Error Line 310, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
    <tr><td><br><br><b>

    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 310, Column 13: start tag was here
    <tr><td><br><br><b>
  • Error Line 311, Column 14: end tag for "b" omitted, but OMITTAG NO was specified
    Articles:</td></tr>

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

  • Info Line 310, Column 17: start tag was here
    <tr><td><br><br><b>
  • Error Line 323, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
     <br><br>

    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 323, Column 2: start tag was here
     <br><br>
  • Error Line 323, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
     <br><br>

    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 323, Column 6: start tag was here
     <br><br>
  • Error Line 326, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width='90%' cellpadding=0 cellspacing=0 class=stext>
  • Error Line 326, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width='90%' cellpadding=0 cellspacing=0 class=stext>
  • Error Line 326, Column 54: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width='90%' cellpadding=0 cellspacing=0 class=stext>
  • Error Line 328, Column 38: end tag for "b" omitted, but OMITTAG NO was specified
                   <td><b>Membership:</td>

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

  • Info Line 328, Column 20: start tag was here
                   <td><b>Membership:</td>
  • Error Line 336, Column 6: document type does not allow element "br" here; assuming missing "li" start-tag
    <br />
  • Error Line 376, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 376, Column 1: start tag was here
    <br><br>
  • Error Line 376, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 376, Column 5: start tag was here
    <br><br>
  • Error Line 379, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …"http://www.downarchive.com/" onclick=window.open("http://cdn.attracta.com/bad…
  • Error Line 379, Column 58: an attribute value must be a literal unless it contains only name characters
    ….downarchive.com/" onclick=window.open("http://cdn.attracta.com/badge/verify/6…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 379, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
    …m" style="border:0px" src="http://cdn.attracta.com/badge/img/686668/2.png"></a>

    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 379, Column 128: start tag was here
    …verify/686668.html"); rel="nofollow" ><img alt="Increase your website traffic …
  • Error Line 381, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 381, Column 1: start tag was here
    <br><br>
  • Error Line 381, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 381, Column 5: start tag was here
    <br><br>
  • Error Line 383, Column 13: end tag for "li" omitted, but OMITTAG NO was specified
            </ul>

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

  • Info Line 336, Column 1: start tag was here
    <br />
  • Error Line 388, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
        </ul>

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

  • Info Line 123, Column 5: start tag was here
        <p class="top-r"><img src="/templates/DAVLay/img/tr.png" /></p>
  • Error Line 390, Column 38: document type does not allow element "div" here; assuming missing "li" start-tag
            <div class="rounded" id="ntf">            
  • Error Line 401, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Tv Shows</font> &#8594 <a href="http://ww…
  • Warning Line 401, Column 61: reference not terminated by REFC delimiter
    …ont class="cat">Tv Shows</font> &#8594 <a href="http://www.downarchive.ws/movi…

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

  • Error Line 404, Column 616: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 407, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751131'><div align="center"><…

    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 410, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 401, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Tv Shows</font> &#8594 <a href="http://ww…
  • Error Line 413, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Console</font> &#8594 <a href="http://www…
  • Warning Line 413, Column 60: reference not terminated by REFC delimiter
    …font class="cat">Console</font> &#8594 <a href="http://www.downarchive.ws/game…

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

  • Error Line 416, Column 617: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 419, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751130'><div align="center"><…

    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 422, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 413, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Console</font> &#8594 <a href="http://www…
  • Error Line 425, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Warning Line 425, Column 67: reference not terminated by REFC delimiter
    …ass="cat">Video Training</font> &#8594 <a href="http://www.downarchive.ws/eboo…

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

  • Error Line 428, Column 645: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 431, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751129'><div align="center"><…

    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 434, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 425, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Error Line 437, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Warning Line 437, Column 67: reference not terminated by REFC delimiter
    …ass="cat">Video Training</font> &#8594 <a href="http://www.downarchive.ws/eboo…

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

  • Error Line 440, Column 618: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 443, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751128'><div align="center"><…

    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 446, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 437, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Error Line 449, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="…
  • Warning Line 449, Column 48: character "&" is the first character of a delimiter but occurred as data
    …s="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="http://w…

    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 449, Column 70: reference not terminated by REFC delimiter
    …="cat">Graphics & Design</font> &#8594 <a href="http://www.downarchive.ws/soft…

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

  • Error Line 452, Column 643: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 455, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751127'><div align="center"><…

    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 458, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 449, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="…
  • Error Line 461, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="…
  • Warning Line 461, Column 48: character "&" is the first character of a delimiter but occurred as data
    …s="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="http://w…

    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 461, Column 70: reference not terminated by REFC delimiter
    …="cat">Graphics & Design</font> &#8594 <a href="http://www.downarchive.ws/soft…

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

  • Error Line 464, Column 642: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 467, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751126'><div align="center"><…

    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 470, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 461, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="…
  • Error Line 473, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Warning Line 473, Column 67: reference not terminated by REFC delimiter
    …ass="cat">Video Training</font> &#8594 <a href="http://www.downarchive.ws/eboo…

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

  • Error Line 476, Column 655: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 479, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751125'><div align="center"><…

    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 482, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 473, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Error Line 485, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="…
  • Warning Line 485, Column 48: character "&" is the first character of a delimiter but occurred as data
    …s="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="http://w…

    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 485, Column 70: reference not terminated by REFC delimiter
    …="cat">Graphics & Design</font> &#8594 <a href="http://www.downarchive.ws/soft…

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

  • Error Line 488, Column 671: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 491, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751124'><div align="center"><…

    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 494, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 485, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Graphics & Design</font> &#8594 <a href="…
  • Error Line 497, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Warning Line 497, Column 67: reference not terminated by REFC delimiter
    …ass="cat">Video Training</font> &#8594 <a href="http://www.downarchive.ws/eboo…

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

  • Warning Line 497, Column 230: character "&" is the first character of a delimiter but occurred as data
    …ic-training-1-2.html">Shaolin White Crane Gong Fu Basic Training 1 & 2</a></h1>

    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 500, Column 646: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 503, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751123'><div align="center"><…

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

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

  • Warning Line 503, Column 348: character "&" is the first character of a delimiter but occurred as data
    … White Crane Gong Fu Basic Training 1 & 2</b><br />XVID | English | 720x480 | …

    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 506, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 497, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Error Line 509, Column 20: document type does not allow element "h1" here; assuming missing "li" start-tag
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Warning Line 509, Column 67: reference not terminated by REFC delimiter
    …ass="cat">Video Training</font> &#8594 <a href="http://www.downarchive.ws/eboo…

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

  • Error Line 512, Column 634: required attribute "alt" not specified
    …ve.com/templates/DAVLay/img/com.png" />&nbsp;<font color="#3f8803">0</font></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 515, Column 33: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="con" style="margin:0"><div id='newsqid-751122'><div align="center"><…

    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 518, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 509, Column 2: start tag was here
    	<h1 class="ntitle"><font class="cat">Video Training</font> &#8594 <a href="htt…
  • Error Line 521, Column 88: required attribute "alt" not specified
    …ww.downarchive.com/templates/DAVLay/img/left.png" /> <span>Previous</span></li>

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

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

  • Error Line 522, Column 143: required attribute "alt" not specified
    …a> <img src="http://www.downarchive.com/templates/DAVLay/img/right.png" /></li>

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

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

  • Error Line 525, Column 22: document type does not allow element "div" here; assuming missing "li" start-tag
    <div align = "center">
  • Error Line 526, Column 37: required attribute "action" not specified
    <form name="go_on_page" method="get">

    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 530, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </ul></div></div>   

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

  • Info Line 525, Column 1: start tag was here
    <div align = "center">
  • Error Line 530, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul></div></div>   

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

  • Info Line 525, Column 1: start tag was here
    <div align = "center">
  • Error Line 533, Column 13: end tag for "div" omitted, but OMITTAG NO was specified
            </ul>

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

  • Info Line 532, Column 9: start tag was here
            <div id="n">
  • Error Line 533, Column 13: end tag for "li" omitted, but OMITTAG NO was specified
            </ul>

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

  • Info Line 390, Column 9: start tag was here
            <div class="rounded" id="ntf">            
  • Error Line 534, Column 18: ID "side" already defined
             <ul id="side">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 122, Column 13: ID "side" first defined here
        <ul id="side" style="float:left;">
  • Error Line 535, Column 30: document type does not allow element "div" here; assuming missing "li" start-tag
                <div id="b-about">
  • Error Line 536, Column 35: end tag for element "a" which is not open
                    <h1>Search</h1></a>

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

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

  • Error Line 538, Column 62: document type does not allow element "li" here
                        <li id="searchfield"  style="float:right">

    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 539, Column 64: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …            <form action="/?do=search"  method="GET" name="frmd2c" id="frmd2c">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 540, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
                            <input type="hidden" name="do" value="search">

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

  • Info Line 540, Column 25: start tag was here
                            <input type="hidden" name="do" value="search">
  • Error Line 541, Column 78: end tag for "input" omitted, but OMITTAG NO was specified
                            <input type="hidden" name="subaction" value="search">

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

  • Info Line 541, Column 25: start tag was here
                            <input type="hidden" name="subaction" value="search">
  • Error Line 542, Column 90: end tag for "input" omitted, but OMITTAG NO was specified
    …              <input name="story" maxlength="100" type="text" id="searchstyle">

    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 542, Column 25: start tag was here
                            <input name="story" maxlength="100" type="text" id="sea…
  • Error Line 552, Column 14: ID "b-about" already defined
        <div id="b-about">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 535, Column 22: ID "b-about" first defined here
                <div id="b-about">
  • Error Line 555, Column 14: there is no attribute "TYPE"
    <SCRIPT TYPE="text/javascript" SRC="http://adserving.cpxinteractive.com/st?ad_t…

    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 555, Column 36: there is no attribute "SRC"
    <SCRIPT TYPE="text/javascript" SRC="http://adserving.cpxinteractive.com/st?ad_t…

    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 555, Column 87: cannot generate system identifier for general entity "ad_size"
    …ving.cpxinteractive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=…

    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 555, Column 87: general entity "ad_size" not defined and no default entity
    …ving.cpxinteractive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=…

    This is usually a cascading error caused by 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 555, Column 94: reference not terminated by REFC delimiter
    …xinteractive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_U…

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

  • Warning Line 555, Column 94: reference to external entity in attribute value
    …xinteractive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_U…

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

  • Error Line 555, Column 94: reference to entity "ad_size" for which no system identifier could be generated
    …xinteractive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_U…

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

  • Info Line 555, Column 86: entity was defined here
    …rving.cpxinteractive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url…
  • Warning Line 555, Column 103: cannot generate system identifier for general entity "section"
    …ive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SC…

    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 555, Column 103: general entity "section" not defined and no default entity
    …ive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SC…

    This is usually a cascading error caused by 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 555, Column 110: reference not terminated by REFC delimiter
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

  • Warning Line 555, Column 110: reference to external entity in attribute value
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

  • Error Line 555, Column 110: reference to entity "section" for which no system identifier could be generated
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

  • Info Line 555, Column 102: entity was defined here
    …tive.com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></S…
  • Warning Line 555, Column 119: cannot generate system identifier for general entity "pub_url"
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

    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 555, Column 119: general entity "pub_url" not defined and no default entity
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

    This is usually a cascading error caused by 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 555, Column 126: reference not terminated by REFC delimiter
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

  • Warning Line 555, Column 126: reference to external entity in attribute value
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

  • Error Line 555, Column 126: reference to entity "pub_url" for which no system identifier could be generated
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

  • Info Line 555, Column 118: entity was defined here
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>
  • Error Line 555, Column 138: element "SCRIPT" undefined
    …com/st?ad_type=ad&ad_size=160x600&section=3384650&pub_url=${PUB_URL}"></SCRIPT>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 561, Column 83: end tag for "br" omitted, but OMITTAG NO was specified
    …o;&nbsp;<a href="http://www.downorange.com" target="_blank">DownOrage</a><br>  

    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 561, Column 79: start tag was here
    …o;&nbsp;<a href="http://www.downorange.com" target="_blank">DownOrage</a><br>  
  • Error Line 566, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 566, Column 1: start tag was here
    <br>
  • Error Line 567, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
    …index.php?do=feedback" rel="nofollow"><strong>Your Link Here ?</strong></a><br>

    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 567, Column 112: start tag was here
    …index.php?do=feedback" rel="nofollow"><strong>Your Link Here ?</strong></a><br>
  • Error Line 573, Column 56: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … href="/index.php?do=lastcomments" rel="nofollow"><h1>Last Comments</h1></a>   

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

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

  • Error Line 577, Column 63: required attribute "alt" not specified
    …<p class="top-r"><img src="/templates/DAVLay/img/tr.png" /></p>                

    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 578, Column 15: ID "b-nav" already defined
         <div id="b-nav">    				

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 125, Column 14: ID "b-nav" first defined here
        <div id="b-nav">
  • Error Line 581, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone>	

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 592, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
    </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 535, Column 13: start tag was here
                <div id="b-about">
  • Error Line 592, Column 6: end tag for "ul" omitted, but OMITTAG NO was specified
    </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 534, Column 10: start tag was here
             <ul id="side">
  • Error Line 594, Column 34: end tag for "ul" which is not finished
                <ul class="dash"></ul>			

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

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

  • Error Line 598, Column 43: there is no attribute "COLOR"
    …lign="center"><a href="/"><FONT COLOR="#449DDA"><strong>Homepage</strong></FON…

    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 598, Column 52: element "FONT" undefined
    …ter"><a href="/"><FONT COLOR="#449DDA"><strong>Homepage</strong></FONT></a> | …

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 598, Column 164: element "FONT" undefined
    …" rel="nofollow"><FONT COLOR="#449DDA"><strong>DMCA</strong></FONT></a> | <a h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 598, Column 335: element "FONT" undefined
    …,scrollbars=1')"><FONT COLOR="#449DDA"><strong>Privacy Policy</strong></FONT><…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 598, Column 450: element "FONT" undefined
    …" rel="nofollow"><FONT COLOR="#449DDA"><strong>Contact Us</strong></FONT></a> …

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 598, Column 540: element "FONT" undefined
    …" rel="nofollow"><FONT COLOR="#449DDA"><strong>Back to Top</strong></FONT></a>…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 614, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 614, Column 1: start tag was here
    <br>
  • Error Line 620, Column 84: required attribute "type" not specified
    …nguage="JavaScript" src="http://api.easyjquery.com/antispam/index.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 621, Column 34: required attribute "type" not specified
        <script language="Javascript">

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

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

  • Error Line 625, Column 14: end tag for "div" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 593, Column 9: start tag was here
            <div id="footer">			
  • Error Line 625, Column 14: end tag for "body" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 53, Column 1: start tag was here
    <body id="wrapper">		
  • Error Line 625, Column 14: end tag for "body" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 25, Column 1: start tag was here
    <script language="javascript" type="text/javascript">
  • Error Line 625, Column 14: end tag for "html" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 7.583 visits
Daily Visitor