Meet and chat online with people from everywhere... Share your ideas not your identity! News,Ideas,photos,music, chat, buy and sell, list your websites... A Social network that respects your privacy ...

whzon.com
  • Domain Name
    whzon.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #45451
  • Page Size
    53.9 KB
  • Ip Address
    204.225.48.65
  • Heading
    H1: 4, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 4 PNG

Website Meta Analysis

  • Title
    WhzOn.Com - Chat Online And Make New Friends
  • Meta Keyword
    Talk,Talking,talk about,chat, chatting,chat about
  • Meta Description
    Meet and chat online with people from everywhere... Share your ideas not your identity! News,Ideas,photos,music, chat, buy and sell, list your websites... A Social network that respects your privacy

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    204.225.48.65
  • Domain Age
    3 Years, 7 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache
  • pragma: no-cache
  • content-length: 53361
  • content-type: text/html
  • expires: Fri, 08 Feb 2013 18:45:30 GMT
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • date: Fri, 08 Feb 2013 18:46:30 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for whzon.com

DNS Analysis


DNS servers
ns.sentex.ca
ns.naviss.com [204.225.48.34]


DNS Records

Answer records
whzon.com SOA
server: image.whzon.com
email: admin@icdirect.com
serial: 16
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
whzon.com NS  image.whzon.com 3600s
whzon.com A 204.225.48.65 3600s
whzon.com MX
preference: 10
exchange: image.whzon.com
3600s
whzon.com TXT v=spf1 ip4:204.225.48.0/24 a mx ptr include:smtp1.sympatico.ca ~all 3600s

Authority records

Additional records
image.whzon.com A 204.225.48.69 3600s

IP 204.225.48.65 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 204.225.48.65

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 70 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.3795038928118776
Message Error
  • Error Line 3, Column 1: no document type declaration; will parse without validation
    <head>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 38, Column 75: cannot generate system identifier for general entity "wsID"
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></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 38, Column 75: general entity "wsID" not defined and no default entity
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></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.

  • Error Line 38, Column 79: reference to entity "wsID" for which no system identifier could be generated
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></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 38, Column 74: entity was defined here
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></script>
  • Warning Line 38, Column 82: cannot generate system identifier for general entity "pgID"
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></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 38, Column 82: general entity "pgID" not defined and no default entity
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></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.

  • Error Line 38, Column 86: reference to entity "pgID" for which no system identifier could be generated
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></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 38, Column 81: entity was defined here
    …teLOGz.whozontop.com/tracker/snapLTp.asp?ID=17621&wsID=5&pgID=581669'></script>
  • Warning Line 56, Column 68: cannot generate system identifier for general entity "fnewsID"
    …     var url="/whozon/newsTalkLT.asp?fwebsiteID=" + wsID + "&fnewsID=" + mapID;

    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 56, Column 68: general entity "fnewsID" not defined and no default entity
    …     var url="/whozon/newsTalkLT.asp?fwebsiteID=" + wsID + "&fnewsID=" + mapID;

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

  • Error Line 56, Column 75: reference to entity "fnewsID" for which no system identifier could be generated
    …     var url="/whozon/newsTalkLT.asp?fwebsiteID=" + wsID + "&fnewsID=" + mapID;

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

  • Info Line 56, Column 67: entity was defined here
    …     var url="/whozon/newsTalkLT.asp?fwebsiteID=" + wsID + "&fnewsID=" + mapID;
  • Error Line 116, Column 22: character ";" not allowed in attribute specification list
      for (var i=0; i<cnt; i++) { s += chr; }
  • Error Line 127, Column 34: character ";" not allowed in attribute specification list
      for (var i=0; i<BadWords.length; i++) {
  • Error Line 195, Column 17: document type does not allow element "BODY" here
    <body style=''  >

    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 237, Column 77: cannot generate system identifier for general entity "fwebsiteID"
    …/whzon.com/whozDev/frmQuickfan.asp?fwzUserID=" + fanID + "&fwebsiteID=" + wsID;

    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 237, Column 77: general entity "fwebsiteID" not defined and no default entity
    …/whzon.com/whozDev/frmQuickfan.asp?fwzUserID=" + fanID + "&fwebsiteID=" + wsID;

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

  • Error Line 237, Column 87: reference to entity "fwebsiteID" for which no system identifier could be generated
    …/whzon.com/whozDev/frmQuickfan.asp?fwzUserID=" + fanID + "&fwebsiteID=" + wsID;

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

  • Info Line 237, Column 76: entity was defined here
    …/whzon.com/whozDev/frmQuickfan.asp?fwzUserID=" + fanID + "&fwebsiteID=" + wsID;
  • Warning Line 330, Column 58: cannot generate system identifier for general entity "wzUserID"
      var URL="/whozon/vChat/vPhonet.asp?fname=" + fname + "&wzUserID=";

    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 330, Column 58: general entity "wzUserID" not defined and no default entity
      var URL="/whozon/vChat/vPhonet.asp?fname=" + fname + "&wzUserID=";

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

  • Error Line 330, Column 66: reference to entity "wzUserID" for which no system identifier could be generated
      var URL="/whozon/vChat/vPhonet.asp?fname=" + fname + "&wzUserID=";

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

  • Info Line 330, Column 57: entity was defined here
      var URL="/whozon/vChat/vPhonet.asp?fname=" + fname + "&wzUserID=";
  • Error Line 349, Column 80: reference to entity "wzUserID" for which no system identifier could be generated
    …tfor.asp?fname=" + VCname + "&wzUserID=&wzCallBackID=" + VCmbrID,350,200,450,1…

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

  • Info Line 330, Column 57: entity was defined here
      var URL="/whozon/vChat/vPhonet.asp?fname=" + fname + "&wzUserID=";
  • Warning Line 349, Column 82: cannot generate system identifier for general entity "wzCallBackID"
    …or.asp?fname=" + VCname + "&wzUserID=&wzCallBackID=" + VCmbrID,350,200,450,100…

    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 349, Column 82: general entity "wzCallBackID" not defined and no default entity
    …or.asp?fname=" + VCname + "&wzUserID=&wzCallBackID=" + VCmbrID,350,200,450,100…

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

  • Error Line 349, Column 94: reference to entity "wzCallBackID" for which no system identifier could be generated
    …r.asp?fname=" + VCname + "&wzUserID=&wzCallBackID=" + VCmbrID,350,200,450,100);

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

  • Info Line 349, Column 81: entity was defined here
    …for.asp?fname=" + VCname + "&wzUserID=&wzCallBackID=" + VCmbrID,350,200,450,10…
  • Warning Line 359, Column 75: cannot generate system identifier for general entity "fusername"
    …//image.whzon.com/vChat/2wvideochat.php?r=" + roomNbr + "&fusername=" + VCname;

    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 359, Column 75: general entity "fusername" not defined and no default entity
    …//image.whzon.com/vChat/2wvideochat.php?r=" + roomNbr + "&fusername=" + VCname;

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

  • Error Line 359, Column 84: reference to entity "fusername" for which no system identifier could be generated
    …//image.whzon.com/vChat/2wvideochat.php?r=" + roomNbr + "&fusername=" + VCname;

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

  • Info Line 359, Column 74: entity was defined here
    …//image.whzon.com/vChat/2wvideochat.php?r=" + roomNbr + "&fusername=" + VCname;
  • Error Line 406, Column 13: end tag for element "FONT" which is not open
          </font><font style='font-size:14px;font-weight:normal;color:#cb0051;'>Wor…

    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 430, Column 76: an attribute value must be a literal unless it contains only name characters
    …yle='color:#8ec634;font-size:14px;' href=javascript:wzGotoPage('/');>Home</a>  

    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.

  • Warning Line 571, Column 71: cannot generate system identifier for general entity "fwzUserId"
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>

    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 571, Column 71: general entity "fwzUserId" not defined and no default entity
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>

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

  • Error Line 571, Column 80: reference to entity "fwzUserId" for which no system identifier could be generated
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 574, Column 80: reference to entity "fwzUserId" for which no system identifier could be generated
    …ize:14px;' href='/whozon/myTown.asp?fmyMode=web&fwzUserId=315613'>Websites</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 575, Column 81: reference to entity "fwzUserId" for which no system identifier could be generated
    …4px;' href='/whozon/myTown.asp?fmyMode=class&fwzUserId=315613'>Classifieds</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 576, Column 80: reference to entity "fwzUserId" for which no system identifier could be generated
    …size:14px;' href='/whozon/myTown.asp?fmyMode=mbrs&fwzUserId=315613'>People</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 577, Column 81: reference to entity "fwzUserId" for which no system identifier could be generated
    …ize:14px;' href='/whozon/myTown.asp?fmyMode=event&fwzUserId=315613'>Events</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Warning Line 578, Column 73: cannot generate system identifier for general entity "fmyMode"
    …ef='/whozon/myTown.asp?fscope=myWorld&fmyMode=mBlog&fwzUserId=315613'>miniBlog…

    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 578, Column 73: general entity "fmyMode" not defined and no default entity
    …ef='/whozon/myTown.asp?fscope=myWorld&fmyMode=mBlog&fwzUserId=315613'>miniBlog…

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

  • Error Line 578, Column 80: reference to entity "fmyMode" for which no system identifier could be generated
    …whozon/myTown.asp?fscope=myWorld&fmyMode=mBlog&fwzUserId=315613'>miniBlogs</a> 

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

  • Info Line 578, Column 72: entity was defined here
    …ref='/whozon/myTown.asp?fscope=myWorld&fmyMode=mBlog&fwzUserId=315613'>miniBlo…
  • Error Line 578, Column 96: reference to entity "fwzUserId" for which no system identifier could be generated
    …whozon/myTown.asp?fscope=myWorld&fmyMode=mBlog&fwzUserId=315613'>miniBlogs</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 579, Column 80: reference to entity "fmyMode" for which no system identifier could be generated
    …='/whozon/myTown.asp?fscope=myWorld&fmyMode=photo&fwzUserId=315613'>Photos</a> 

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

  • Info Line 578, Column 72: entity was defined here
    …ref='/whozon/myTown.asp?fscope=myWorld&fmyMode=mBlog&fwzUserId=315613'>miniBlo…
  • Error Line 579, Column 96: reference to entity "fwzUserId" for which no system identifier could be generated
    …='/whozon/myTown.asp?fscope=myWorld&fmyMode=photo&fwzUserId=315613'>Photos</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 580, Column 81: reference to entity "fwzUserId" for which no system identifier could be generated
    …14px;' href='/whozon/myTown.asp?fmyMode=wNews&fwzUserId=315613'>World News</a> 

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Error Line 585, Column 272: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=34881…

    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 585, Column 610: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=26332…

    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 585, Column 950: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=20798…

    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 585, Column 1293: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=32933…

    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 585, Column 1641: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=28468…

    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 585, Column 1979: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=25973…

    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 585, Column 2319: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=12360…

    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 585, Column 2661: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=34457…

    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 585, Column 3007: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=35635…

    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 585, Column 3346: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=26525…

    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 585, Column 3684: an attribute value must be a literal unless it contains only name characters
    …Profile' href=javascript:wzOpenSiteLOG('/whozon/mbrProfile.asp?fwzUserID=19153…

    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.

  • Warning Line 607, Column 166: cannot generate system identifier for general entity "fqry"
    …dow' SRC='framTalkChannels.asp?newPg=&fqry='  SCROLLING='NO' FRAMEBORDER='NO' …

    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 607, Column 166: general entity "fqry" not defined and no default entity
    …dow' SRC='framTalkChannels.asp?newPg=&fqry='  SCROLLING='NO' FRAMEBORDER='NO' …

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

  • Error Line 607, Column 170: reference to entity "fqry" for which no system identifier could be generated
    … SRC='framTalkChannels.asp?newPg=&fqry='  SCROLLING='NO' FRAMEBORDER='NO' BORD…

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

  • Info Line 607, Column 165: entity was defined here
    …ndow' SRC='framTalkChannels.asp?newPg=&fqry='  SCROLLING='NO' FRAMEBORDER='NO'…
  • Error Line 616, Column 99: reference to entity "fwzUserId" for which no system identifier could be generated
    …whozon/myTown.asp?fmyMode=wNews&fwzUserId=315613'>More Recent News...</a></div>

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

  • Info Line 571, Column 70: entity was defined here
    …tyle='font-size:14px;' href='/whozon/myTown.asp?fmyMode=mosh&fwzUserId=315613'>
  • Warning Line 617, Column 55: cannot generate system identifier for general entity "fxmlSrc"
    …ipt src='/whozon/xmlFeed.asp?fxmlr=65&fxmlSrc=/whozon/smNewsFeedSrc.asp'></scr…

    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 617, Column 55: general entity "fxmlSrc" not defined and no default entity
    …ipt src='/whozon/xmlFeed.asp?fxmlr=65&fxmlSrc=/whozon/smNewsFeedSrc.asp'></scr…

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

  • Error Line 617, Column 62: reference to entity "fxmlSrc" for which no system identifier could be generated
    …='/whozon/xmlFeed.asp?fxmlr=65&fxmlSrc=/whozon/smNewsFeedSrc.asp'></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 617, Column 54: entity was defined here
    …ript src='/whozon/xmlFeed.asp?fxmlr=65&fxmlSrc=/whozon/smNewsFeedSrc.asp'></sc…
  • Warning Line 628, Column 137: cannot generate system identifier for general entity "fmode"
    …whozon/_framexmlActivity.asp?fboxID=9&fmode=yes' SCROLLING="vertical" FRAMEBOR…

    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 628, Column 137: general entity "fmode" not defined and no default entity
    …whozon/_framexmlActivity.asp?fboxID=9&fmode=yes' SCROLLING="vertical" FRAMEBOR…

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

  • Error Line 628, Column 142: reference to entity "fmode" for which no system identifier could be generated
    …n/_framexmlActivity.asp?fboxID=9&fmode=yes' SCROLLING="vertical" FRAMEBORDER="…

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

  • Info Line 628, Column 136: entity was defined here
    …/whozon/_framexmlActivity.asp?fboxID=9&fmode=yes' SCROLLING="vertical" FRAMEBO…
  • Warning Line 948, Column 45: NET-enabling start-tag requires SHORTTAG YES
        msg=msg.replace('wzIRTx','<img src=http://204.225.48.34/vChat/emoticons/');

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1121, Column 47: cannot generate system identifier for general entity "xm"
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;

    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 1121, Column 47: general entity "xm" not defined and no default entity
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;

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

  • Error Line 1121, Column 49: reference to entity "xm" for which no system identifier could be generated
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Error Line 1123, Column 48: reference to entity "xm" for which no system identifier could be generated
         URL = '/whozon/mods/muteSelf.asp?fpen=5&xm=' + ranTime;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Error Line 1175, Column 65: reference to entity "xm" for which no system identifier could be generated
              var url='sendChatOpt.asp?fshout=' + escape(msg) + "&xm=" + ranTime;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Error Line 1230, Column 46: reference to entity "xm" for which no system identifier could be generated
          var url='popChatEnd.asp?fmbrID=84941&xm=' + ranTime ;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Warning Line 1240, Column 17: cannot generate system identifier for general entity "msg"
       if ( msg!=""&msg!="0;") {

    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 1240, Column 17: general entity "msg" not defined and no default entity
       if ( msg!=""&msg!="0;") {

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

  • Error Line 1240, Column 20: reference to entity "msg" for which no system identifier could be generated
       if ( msg!=""&msg!="0;") {

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

  • Info Line 1240, Column 16: entity was defined here
       if ( msg!=""&msg!="0;") {
  • Warning Line 1243, Column 28: cannot generate system identifier for general entity "cptr.length"
         while (cptr.length>0&&cptr.length!=prevL) {

    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 1243, Column 28: general entity "cptr.length" not defined and no default entity
         while (cptr.length>0&&cptr.length!=prevL) {

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

  • Error Line 1243, Column 39: reference to entity "cptr.length" for which no system identifier could be generated
         while (cptr.length>0&&cptr.length!=prevL) {

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

  • Info Line 1243, Column 27: entity was defined here
         while (cptr.length>0&&cptr.length!=prevL) {
  • Warning Line 1254, Column 45: cannot generate system identifier for general entity "fanID"
       var url='blockUserAJ.asp?fwzUserID=17621&fanID=' + ID +'&xm=' + ranTime ;

    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 1254, Column 45: general entity "fanID" not defined and no default entity
       var url='blockUserAJ.asp?fwzUserID=17621&fanID=' + ID +'&xm=' + ranTime ;

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

  • Error Line 1254, Column 50: reference to entity "fanID" for which no system identifier could be generated
       var url='blockUserAJ.asp?fwzUserID=17621&fanID=' + ID +'&xm=' + ranTime ;

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

  • Info Line 1254, Column 44: entity was defined here
       var url='blockUserAJ.asp?fwzUserID=17621&fanID=' + ID +'&xm=' + ranTime ;
  • Error Line 1254, Column 63: reference to entity "xm" for which no system identifier could be generated
       var url='blockUserAJ.asp?fwzUserID=17621&fanID=' + ID +'&xm=' + ranTime ;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Error Line 1313, Column 44: reference to entity "xm" for which no system identifier could be generated
       var url='addSpotAdSrc.asp?fmode=NOsrc&xm=' + ranTime ;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Error Line 1338, Column 61: reference to entity "xm" for which no system identifier could be generated
       var url='popChatGetMsgV2.asp?flmsgID=' + lastMsgID + '&xm=' + ranTime ;

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

  • Info Line 1121, Column 46: entity was defined here
       var URL='/whozon/mods/muteSelf.asp?fpen=30&xm=' + ranTime;
  • Warning Line 1354, Column 21: cannot generate system identifier for general entity "msgs"
          if ( msgs!=""&msgs!="done!") {

    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 1354, Column 21: general entity "msgs" not defined and no default entity
          if ( msgs!=""&msgs!="done!") {

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

  • Error Line 1354, Column 25: reference to entity "msgs" for which no system identifier could be generated
          if ( msgs!=""&msgs!="done!") {

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

  • Info Line 1354, Column 20: entity was defined here
          if ( msgs!=""&msgs!="done!") {
  • Error Line 1357, Column 42: reference to entity "cptr.length" for which no system identifier could be generated
            while (cptr.length>0&&cptr.length!=prevL) {

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

  • Info Line 1243, Column 27: entity was defined here
         while (cptr.length>0&&cptr.length!=prevL) {
  • Error Line 1497, Column 24: character ";" not allowed in attribute specification list
      for (i=1;i<str.length;i++){
  • Error Line 1515, Column 7: end tag for element "HTML" which is not open
    </html>

    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.

Visitor Analysis

Daily Visitor
  • 3.733 visits
Daily Visitor