Bonus pages

Joomla pages

It's not a joking. 514 bugs with Inoutscripts Shopping Cart

It's not a joking. 514 bugs with Inoutscripts Shopping Cart

Article Index

  1. Error Line 25, Column 37: required attribute "type" not specified 
    	<script src="/js/jquery-ui1.10.3.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>.

  2. Warning Line 88, Column 32: cannot generate system identifier for general entity "pro_qty" 
        data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

    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.

  3. Error Line 88, Column 32: general entity "pro_qty" not defined and no default entity 
     data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  4. Warning Line 88, Column 39: reference not terminated by REFC delimiter 
      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  5. Error Line 88, Column 39: reference to entity "pro_qty" for which no system identifier could be generated 
      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  6. Info Line 88, Column 31: entity was defined here 
       data: "cartid="+cartid+"&pro_qty="+pro_qty,
  7. Warning Line 105, Column 40: reference not terminated by REFC delimiter 
       data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

    ✉

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

  8. Error Line 105, Column 40: reference to entity "pro_qty" for which no system identifier could be generated 
      data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

    ✉

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

  9. Info Line 88, Column 31: entity was defined here 
       data: "cartid="+cartid+"&pro_qty="+pro_qty,
  10. Warning Line 105, Column 53: cannot generate system identifier for general entity "cartid" 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

    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.

  11. Error Line 105, Column 53: general entity "cartid" not defined and no default entity 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  12. Warning Line 105, Column 59: reference not terminated by REFC delimiter 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  13. Error Line 105, Column 59: reference to entity "cartid" for which no system identifier could be generated 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  14. Info Line 105, Column 52: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  15. Warning Line 105, Column 71: cannot generate system identifier for general entity "userid" 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

    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.

  16. Error Line 105, Column 71: general entity "userid" not defined and no default entity 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  17. Warning Line 105, Column 77: reference not terminated by REFC delimiter 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  18. Error Line 105, Column 77: reference to entity "userid" for which no system identifier could be generated 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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


  19. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  20. Warning Line 111, Column 22: character "&" is the first character of a delimiter but occurred as data 
     x=data.split("[&&]");

    ✉

    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.
  21. Warning Line 111, Column 23: character "&" is the first character of a delimiter but occurred as data 
     x=data.split("[&&]");

    ✉

    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.
  22. Error Line 129, Column 36: document type does not allow element "span" here 
     view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    ✉

    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).

  23. Error Line 134, Column 34: document type does not allow element "span" here 
    view1='<span class="grnSuc"><b>'+err+'</b></span>';

    ✉

    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).

  24. Error Line 141, Column 36: document type does not allow element "span" here 
    	view1 ='<span class="redEror"><b>'+error+'</b></span>';

    ✉

    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).

  25. Warning Line 185, Column 40: reference not terminated by REFC delimiter 
    … data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

    ✉

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

  26. Error Line 185, Column 40: reference to entity "pro_qty" for which no system identifier could be generated 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

    ✉

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

  27. Info Line 88, Column 31: entity was defined here 
     data: "cartid="+cartid+"&pro_qty="+pro_qty,
  28. Warning Line 185, Column 59: reference not terminated by REFC delimiter 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  29. Error Line 185, Column 59: reference to entity "cartid" for which no system identifier could be generated 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  30. Info Line 105, Column 52: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  31. Warning Line 185, Column 77: reference not terminated by REFC delimiter 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  32. Error Line 185, Column 77: reference to entity "userid" for which no system identifier could be generated 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    ✉

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

  33. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  34. Warning Line 189, Column 22: character "&" is the first character of a delimiter but occurred as data 
     x=data.split("[&&]");

    ✉

    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.
  35. Warning Line 189, Column 23: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  36. Error Line 209, Column 37: document type does not allow element "span" here 
    	view1 ='<span class="redEror"><b>'+view+'</b></span>';

    ✉

    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).

  37. Error Line 213, Column 39: document type does not allow element "span" here 
    	  view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    ✉

    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).

  38. Error Line 219, Column 34: document type does not allow element "span" here 
    	view1='<span class="grnSuc"><b>'+err+'</b></span>';

    ✉

    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).

  39. Error Line 226, Column 36: document type does not allow element "span" here 
    view1 ='<span class="redEror"><b>'+error+'</b></span>';

    ✉

    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).


  40. Warning Line 273, Column 39: reference not terminated by REFC delimiter 
       data: "cartid="+cartid+"&userid="+userid,

    ✉

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

  41. Error Line 273, Column 39: reference to entity "userid" for which no system identifier could be generated 
    	  data: "cartid="+cartid+"&userid="+userid,

    ✉

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

  42. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  43. Error Line 287, Column 36: document type does not allow element "span" here 
          view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    ✉

    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).

  44. Error Line 292, Column 34: document type does not allow element "span" here 
          view1='<span class="grnSuc"><b>'+err+'</b></span>';

    ✉

    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).

  45. Error Line 298, Column 36: document type does not allow element "span" here 
    	view1 ='<span class="redEror"><b>'+error+'</b></span>';

    ✉

    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).

  46. Warning Line 332, Column 39: reference not terminated by REFC delimiter 
    	 data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  47. Error Line 332, Column 39: reference to entity "pro_qty" for which no system identifier could be generated 
    	   data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  48. Info Line 88, Column 31: entity was defined here 
    	  data: "cartid="+cartid+"&pro_qty="+pro_qty,
  49. Warning Line 359, Column 40: reference not terminated by REFC delimiter 
    	  data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  50. Error Line 359, Column 40: reference to entity "pro_qty" for which no system identifier could be generated 
    	 data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  51. Info Line 88, Column 31: entity was defined here 
       data: "cartid="+cartid+"&pro_qty="+pro_qty,
  52. Warning Line 365, Column 22: character "&" is the first character of a delimiter but occurred as data 
     x=data.split("[&&]");

    ✉

    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.
  53. Warning Line 365, Column 23: character "&" is the first character of a delimiter but occurred as data 
     x=data.split("[&&]");

    ✉

    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.
  54. Error Line 384, Column 37: document type does not allow element "span" here 
    	view1 ='<span class="redEror"><b>'+view+'</b></span>';

    ✉

    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).

  55. Error Line 388, Column 36: document type does not allow element "span" here 
    	  view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    ✉

    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).

  56. Error Line 394, Column 34: document type does not allow element "span" here 
    	view1='<span class="grnSuc"><b>'+err+'</b></span>';

    ✉

    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).

  57. Error Line 401, Column 36: document type does not allow element "span" here 
    	view1 ='<span class="redEror"><b>'+error+'</b></span>';

    ✉

    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).

  58. Warning Line 440, Column 40: reference not terminated by REFC delimiter 
      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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

  59. Error Line 440, Column 40: reference to entity "pro_qty" for which no system identifier could be generated 
     data: "cartid="+cartid+"&pro_qty="+pro_qty,

    ✉

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


  60. Info Line 88, Column 31: entity was defined here 
    	   data: "cartid="+cartid+"&pro_qty="+pro_qty,
  61. Warning Line 444, Column 22: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  62. Warning Line 444, Column 23: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  63. Error Line 453, Column 36: document type does not allow element "span" here 
    	  view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    ✉

    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).

  64. Error Line 458, Column 34: document type does not allow element "span" here 
    	view1='<span class="grnSuc"><b>'+err+'</b></span>';

    ✉

    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).

  65. Error Line 465, Column 36: document type does not allow element "span" here 
    	view1 ='<span class="redEror"><b>'+error+'</b></span>';

    ✉

    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).

  66. Warning Line 556, Column 22: character "<" is the first character of a delimiter but occurred as data 
         if (topmenuTopPos < -100)

    ✉

    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.
  67. Warning Line 707, Column 93: cannot generate system identifier for general entity "keyword" 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

    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.

  68. Error Line 707, Column 93: general entity "keyword" not defined and no default entity 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  69. Warning Line 707, Column 100: reference not terminated by REFC delimiter 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  70. Error Line 707, Column 100: reference to entity "keyword" for which no system identifier could be generated 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  71. Info Line 707, Column 92: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid…
  72. Warning Line 707, Column 113: cannot generate system identifier for general entity "vendorid" 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

    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.

  73. Error Line 707, Column 113: general entity "vendorid" not defined and no default entity 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  74. Warning Line 707, Column 121: reference not terminated by REFC delimiter 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  75. Error Line 707, Column 121: reference to entity "vendorid" for which no system identifier could be generated 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  76. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  77. Warning Line 721, Column 100: reference not terminated by REFC delimiter 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  78. Error Line 721, Column 100: reference to entity "keyword" for which no system identifier could be generated 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  79. Info Line 707, Column 92: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid…
  80. Warning Line 721, Column 121: reference not terminated by REFC delimiter 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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

  81. Error Line 721, Column 121: reference to entity "vendorid" for which no system identifier could be generated 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    ✉

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


  82. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  83. Warning Line 770, Column 37: cannot generate system identifier for general entity "page" 
        data: "product_id="+pro_id+"&page="+pagestat,

    ✉

    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.

  84. Error Line 770, Column 37: general entity "page" not defined and no default entity 
        data: "product_id="+pro_id+"&page="+pagestat,

    ✉

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

  85. Warning Line 770, Column 41: reference not terminated by REFC delimiter 
      data: "product_id="+pro_id+"&page="+pagestat,

    ✉

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

  86. Error Line 770, Column 41: reference to entity "page" for which no system identifier could be generated 
       data: "product_id="+pro_id+"&page="+pagestat,

    ✉

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

  87. Info Line 770, Column 36: entity was defined here 
       data: "product_id="+pro_id+"&page="+pagestat,
  88. Warning Line 871, Column 24: character "<" is the first character of a delimiter but occurred as data 
         for(i=0;i<(selectcount-1);i++)

    ✉

    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.
  89. Error Line 891, Column 37: character ";" not allowed in attribute specification list 
       for(i=0;i<radiocount-1;i++)

    ✉

  90. Error Line 891, Column 37: element "radiocount-1" undefined 
          for(i=0;i<radiocount-1;i++)

    ✉

    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).
  91. Error Line 910, Column 40: character ";" not allowed in attribute specification list 
    	  for(i=0;i<checkboxcount-1;i++)

    ✉

  92. Error Line 910, Column 40: element "checkboxcount-1" undefined 
    	for(i=0;i<checkboxcount-1;i++)

    ✉

    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).
  93. Warning Line 931, Column 40: cannot generate system identifier for general entity "select" 
    …    data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid=…

    ✉

    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.

  94. Error Line 931, Column 40: general entity "select" not defined and no default entity 
    …     data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid=…

    ✉

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

  95. Warning Line 931, Column 46: reference not terminated by REFC delimiter 
    …   data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid="+sele…

    ✉

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

  96. Error Line 931, Column 46: reference to entity "select" for which no system identifier could be generated 
    …   data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid="+sele…

    ✉

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

  97. Info Line 931, Column 39: entity was defined here 
          data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid=…
  98. Warning Line 931, Column 71: cannot generate system identifier for general entity "selectid" 
    …d_id+"&select="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+r…

    ✉

    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.

  99. Error Line 931, Column 71: general entity "selectid" not defined and no default entity 
    …d_id+"&select="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+r…

    ✉

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


  100. Warning Line 931, Column 79: reference not terminated by REFC delimiter 
    …elect="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+radiofiel…

    ✉

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

  101. Error Line 931, Column 79: reference to entity "selectid" for which no system identifier could be generated 
    …elect="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+radiofiel…

    ✉

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

  102. Info Line 931, Column 70: entity was defined here 
    …rd_id+"&select="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+…
  103. Warning Line 931, Column 100: cannot generate system identifier for general entity "radioid" 
    …value1+"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+che…

    ✉

    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.

  104. Error Line 931, Column 100: general entity "radioid" not defined and no default entity 
    …value1+"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+che…

    ✉

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

  105. Warning Line 931, Column 107: reference not terminated by REFC delimiter 
    …"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfi…

    ✉

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

  106. Error Line 931, Column 107: reference to entity "radioid" for which no system identifier could be generated 
    …"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfi…

    ✉

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

  107. Info Line 931, Column 99: entity was defined here 
    …_value1+"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+ch…
  108. Warning Line 931, Column 127: cannot generate system identifier for general entity "checkid" 
    …ield_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+ra…

    ✉

    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.

  109. Error Line 931, Column 127: general entity "checkid" not defined and no default entity 
    …ield_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+ra…

    ✉

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

  110. Warning Line 931, Column 134: reference not terminated by REFC delimiter 
    …s+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofiel…

    ✉

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

  111. Error Line 931, Column 134: reference to entity "checkid" for which no system identifier could be generated 
    …s+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofiel…

    ✉

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

  112. Info Line 931, Column 126: entity was defined here 
    …field_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+r…
  113. Warning Line 931, Column 157: cannot generate system identifier for general entity "radio" 
    …d_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="+…

    ✉

    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.

  114. Error Line 931, Column 157: general entity "radio" not defined and no default entity 
    …d_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="+…

    ✉

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

  115. Warning Line 931, Column 162: reference not terminated by REFC delimiter 
    …+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="+check…

    ✉

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

  116. Error Line 931, Column 162: reference to entity "radio" for which no system identifier could be generated 
    …+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="+check…

    ✉

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

  117. Info Line 931, Column 156: entity was defined here 
    …ld_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="…
  118. Warning Line 931, Column 186: cannot generate system identifier for general entity "checkbox" 
    …ld_ids+"&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vendo…

    ✉

    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.

  119. Error Line 931, Column 186: general entity "checkbox" not defined and no default entity 
    …ld_ids+"&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vendo…

    ✉

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

  120. Warning Line 931, Column 194: reference not terminated by REFC delimiter 
    …&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vendorid="+ve…

    ✉

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


  121. Error Line 931, Column 194: reference to entity "checkbox" for which no system identifier could be generated 
    …&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vendorid="+ve…

    ✉

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

  122. Info Line 931, Column 185: entity was defined here 
    …eld_ids+"&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vend…
  123. Warning Line 931, Column 229: reference not terminated by REFC delimiter 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  124. Error Line 931, Column 229: reference to entity "vendorid" for which no system identifier could be generated 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  125. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  126. Warning Line 931, Column 243: cannot generate system identifier for general entity "click" 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

    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.

  127. Error Line 931, Column 243: general entity "click" not defined and no default entity 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  128. Warning Line 931, Column 248: reference not terminated by REFC delimiter 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  129. Error Line 931, Column 248: reference to entity "click" for which no system identifier could be generated 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  130. Info Line 931, Column 242: entity was defined here 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,
  131. Warning Line 944, Column 22: character "&" is the first character of a delimiter but occurred as data 
       x=d.split("[&&]");

    ✉

    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.
  132. Warning Line 944, Column 23: character "&" is the first character of a delimiter but occurred as data 
        x=d.split("[&&]");

    ✉

    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.
  133. Warning Line 1037, Column 30: cannot generate system identifier for general entity "color" 
        data: "pro_id="+pro_id+"&color="+color,

    ✉

    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.

  134. Error Line 1037, Column 30: general entity "color" not defined and no default entity 
        data: "pro_id="+pro_id+"&color="+color,

    ✉

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

  135. Warning Line 1037, Column 35: reference not terminated by REFC delimiter 
        data: "pro_id="+pro_id+"&color="+color,

    ✉

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

  136. Error Line 1037, Column 35: reference to entity "color" for which no system identifier could be generated 
        data: "pro_id="+pro_id+"&color="+color,

    ✉

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

  137. Info Line 1037, Column 29: entity was defined here 
        data: "pro_id="+pro_id+"&color="+color,
  138. Warning Line 1084, Column 24: character "<" is the first character of a delimiter but occurred as data 
        for(i=0;i<(selectcount-1);i++)

    ✉

    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.
  139. Error Line 1104, Column 37: character ";" not allowed in attribute specification list 
          for(i=0;i<radiocount-1;i++)

    ✉

  140. Error Line 1104, Column 37: element "radiocount-1" undefined 
          for(i=0;i<radiocount-1;i++)

    ✉

    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).
  141. Error Line 1123, Column 40: character ";" not allowed in attribute specification list 
    	 for(i=0;i<checkboxcount-1;i++)

    ✉

  142. Error Line 1123, Column 40: element "checkboxcount-1" undefined 
    	 for(i=0;i<checkboxcount-1;i++)

    ✉

    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).
  143. Warning Line 1144, Column 46: reference not terminated by REFC delimiter 
    …   data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid="+sele…

    ✉

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

  144. Error Line 1144, Column 46: reference to entity "select" for which no system identifier could be generated 
    …   data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid="+sele…

    ✉

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

  145. Info Line 931, Column 39: entity was defined here 
        	  data: "product_id="+prd_id+"&select="+selectfields_value1+"&selectid=…
  146. Warning Line 1144, Column 79: reference not terminated by REFC delimiter 
    …elect="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+radiofiel…

    ✉

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

  147. Error Line 1144, Column 79: reference to entity "selectid" for which no system identifier could be generated 
    …elect="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+radiofiel…

    ✉

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

  148. Info Line 931, Column 70: entity was defined here 
    …rd_id+"&select="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+…
  149. Warning Line 1144, Column 107: reference not terminated by REFC delimiter 
    …"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfi…

    ✉

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

  150. Error Line 1144, Column 107: reference to entity "radioid" for which no system identifier could be generated 
    …"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfi…

    ✉

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

  151. Info Line 931, Column 99: entity was defined here 
    …_value1+"&selectid="+selectfield_ids+"&radioid="+radiofield_ids+"&checkid="+ch…
  152. Warning Line 1144, Column 134: reference not terminated by REFC delimiter 
    …s+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofiel…

    ✉

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

  153. Error Line 1144, Column 134: reference to entity "checkid" for which no system identifier could be generated 
    …s+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofiel…

    ✉

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

  154. Info Line 931, Column 126: entity was defined here 
    …field_ids+"&radioid="+radiofield_ids+"&checkid="+checkboxfield_ids+"&radio="+r…
  155. Warning Line 1144, Column 162: reference not terminated by REFC delimiter 
    …+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="+check…

    ✉

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

  156. Error Line 1144, Column 162: reference to entity "radio" for which no system identifier could be generated 
    …+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="+check…

    ✉

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

  157. Info Line 931, Column 156: entity was defined here 
    …ld_ids+"&checkid="+checkboxfield_ids+"&radio="+radiofields_value1+"&checkbox="…
  158. Warning Line 1144, Column 194: reference not terminated by REFC delimiter 
    …&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vendorid="+ve…

    ✉

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

  159. Error Line 1144, Column 194: reference to entity "checkbox" for which no system identifier could be generated 
    …&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vendorid="+ve…

    ✉

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

  160. Info Line 931, Column 185: entity was defined here 
    …eld_ids+"&radio="+radiofields_value1+"&checkbox="+checkboxfields_value1+"&vend…
  161. Warning Line 1144, Column 229: reference not terminated by REFC delimiter 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  162. Error Line 1144, Column 229: reference to entity "vendorid" for which no system identifier could be generated 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  163. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  164. Warning Line 1144, Column 248: reference not terminated by REFC delimiter 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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

  165. Error Line 1144, Column 248: reference to entity "click" for which no system identifier could be generated 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,

    ✉

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


  166. Info Line 931, Column 242: entity was defined here 
    …alue1+"&checkbox="+checkboxfields_value1+"&vendorid="+vendorid+"&click="+click,
  167. Warning Line 1155, Column 22: character "&" is the first character of a delimiter but occurred as data 
        	 x=d.split("[&&]");

    ✉

    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.
  168. Warning Line 1155, Column 23: character "&" is the first character of a delimiter but occurred as data 
        	 x=d.split("[&&]");

    ✉

    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.
  169. Error Line 1306, Column 18: character "+" not allowed in attribute specification list 
    	 for(var j=0;j<n+1;j++)

    ✉

  170. Error Line 1306, Column 18: element "n" undefined 
    	 for(var j=0;j<n+1;j++)

    ✉

    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).
  171. Warning Line 1321, Column 57: reference not terminated by REFC delimiter 
    	data: "company_plan_id="+company_plan_id+"&cartid="+cartid,

    ✉

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

  172. Error Line 1321, Column 57: reference to entity "cartid" for which no system identifier could be generated 
    	data: "company_plan_id="+company_plan_id+"&cartid="+cartid,

    ✉

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

  173. Info Line 105, Column 52: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  174. Warning Line 1355, Column 37: cannot generate system identifier for general entity "pro_price" 
    	  data: "colour="+colour+"&pro_price="+pro_price,

    ✉

    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.

  175. Error Line 1355, Column 37: general entity "pro_price" not defined and no default entity 
    	  data: "colour="+colour+"&pro_price="+pro_price,

    ✉

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

  176. Warning Line 1355, Column 46: reference not terminated by REFC delimiter 
    	   data: "colour="+colour+"&pro_price="+pro_price,

    ✉

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

  177. Error Line 1355, Column 46: reference to entity "pro_price" for which no system identifier could be generated 
    	   data: "colour="+colour+"&pro_price="+pro_price,

    ✉

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

  178. Info Line 1355, Column 36: entity was defined here 
    	  data: "colour="+colour+"&pro_price="+pro_price,
  179. Warning Line 1367, Column 11: character "<" is the first character of a delimiter but occurred as data 
     for(i=1;i<=singleValues;i++)

    ✉

    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.
  180. Warning Line 1376, Column 12: character "<" is the first character of a delimiter but occurred as data 
      for(i=1;i<=singleValues;i++)

    ✉

    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.
  181. Warning Line 1382, Column 13: character "<" is the first character of a delimiter but occurred as data 
       for(i=1;i<=singleValues;i++)

    ✉

    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.
  182. Warning Line 1392, Column 32: cannot generate system identifier for general entity "vote" 
      data: "displayurl="+url+"&vote="+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.

  183. Error Line 1392, Column 32: general entity "vote" not defined and no default entity 
    	  data: "displayurl="+url+"&vote="+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.

  184. Warning Line 1392, Column 36: reference not terminated by REFC delimiter 
    	 data: "displayurl="+url+"&vote="+t,

    ✉

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

  185. Error Line 1392, Column 36: reference to entity "vote" for which no system identifier could be generated 
    	   data: "displayurl="+url+"&vote="+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.

  186. Info Line 1392, Column 31: entity was defined here 
    	   data: "displayurl="+url+"&vote="+t,
  187. Warning Line 1396, Column 25: character "&" is the first character of a delimiter but occurred as data 
    	  var aa=data.split("&&");

    ✉

    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.
  188. Warning Line 1396, Column 26: character "&" is the first character of a delimiter but occurred as data 
    	  var aa=data.split("&&");

    ✉

    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.
  189. Warning Line 1412, Column 11: character "<" is the first character of a delimiter but occurred as data 
     for(i=1;i<=singleValues;i++)

    ✉

    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.
  190. Error Line 1418, Column 9: end tag for "n" 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 ">".


  191. Info Line 1306, Column 16: start tag was here 
    	 for(var j=0;j<n+1;j++)
  192. Error Line 1418, Column 9: end tag for "checkboxcount-1" 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 ">".

  193. Info Line 1123, Column 24: start tag was here 
    	    for(i=0;i<checkboxcount-1;i++)
  194. Error Line 1418, Column 9: end tag for "radiocount-1" 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 ">".

  195. Info Line 1104, Column 24: start tag was here 
           for(i=0;i<radiocount-1;i++)
  196. Error Line 1418, Column 9: end tag for "checkboxcount-1" 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 ">".

  197. Info Line 910, Column 24: start tag was here 
    	   for(i=0;i<checkboxcount-1;i++)
  198. Error Line 1418, Column 9: end tag for "radiocount-1" 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 ">".

  199. Info Line 891, Column 24: start tag was here 
          	 for(i=0;i<radiocount-1;i++)
  200. Warning Line 1508, Column 32: character "&" is the first character of a delimiter but occurred as data 
    	   var aa=data.split("&&");

    ✉

    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.
  201. Warning Line 1508, Column 33: character "&" is the first character of a delimiter but occurred as data 
    	    var aa=data.split("&&");

    ✉

    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.
  202. Error Line 1517, Column 106: document type does not allow element "div" here 
    …erHTML='<div class="noresult" style="height:200px;"><b>No Products</b></div>';

    ✉

    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).

  203. Error Line 1539, Column 25: character ";" not allowed in attribute specification list 
    	 for(i=0;i<brand_len-1;i++)

    ✉

  204. Error Line 1539, Column 25: element "brand_len-1" undefined 
    	 for(i=0;i<brand_len-1;i++)

    ✉

    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).
  205. Error Line 1561, Column 25: character ";" not allowed in attribute specification list 
    	for(i=0;i<brand_len-1;i++)

    ✉

  206. Error Line 1561, Column 25: element "brand_len-1" undefined 
    	for(i=0;i<brand_len-1;i++)

    ✉

    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).
  207. Error Line 1605, Column 29: character ";" not allowed in attribute specification list 
    for (i=0;i<ARRcookies.length;i++)

    ✉

  208. Error Line 1605, Column 29: element "ARRcookies.length" undefined 
    for (i=0;i<ARRcookies.length;i++)

    ✉

    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).
  209. Error Line 1628, Column 11: end tag for "ARRcookies.length" 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 ">".

  210. Info Line 1605, Column 11: start tag was here 
    for (i=0;i<ARRcookies.length;i++)
  211. Error Line 1628, Column 11: end tag for "brand_len-1" 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 ">".

  212. Info Line 1561, Column 13: start tag was here 
    	for(i=0;i<brand_len-1;i++)
  213. Error Line 1628, Column 11: end tag for "brand_len-1" 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 ">".

  214. Info Line 1539, Column 13: start tag was here 
    		 for(i=0;i<brand_len-1;i++)
  215. Warning Line 1786, Column 36: cannot generate system identifier for general entity "search_cat" 
    	data: "searchword="+searchbox+"&search_cat="+search_cat,

    ✉

    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.


  216. Error Line 1786, Column 36: general entity "search_cat" not defined and no default entity 
    		data: "searchword="+searchbox+"&search_cat="+search_cat,

    ✉

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

  217. Warning Line 1786, Column 46: reference not terminated by REFC delimiter 
    	data: "searchword="+searchbox+"&search_cat="+search_cat,

    ✉

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

  218. Error Line 1786, Column 46: reference to entity "search_cat" for which no system identifier could be generated 
    	data: "searchword="+searchbox+"&search_cat="+search_cat,

    ✉

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

  219. Info Line 1786, Column 35: entity was defined here 
    	data: "searchword="+searchbox+"&search_cat="+search_cat,
  220. Error Line 1876, Column 64: document type does not allow element "font" here 
    …ent.getElementById("error1").innerHTML="<font color='red'>"+errormsg+"</font>";

    ✉

    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).

  221. Error Line 1888, Column 64: document type does not allow element "font" here 
    …t.getElementById("error1").innerHTML="<font color='red'>"+emailerror+"</font>";

    ✉

    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).

  222. Warning Line 1902, Column 12: character "<" is the first character of a delimiter but occurred as data 
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

    ✉

    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.
  223. Error Line 1902, Column 30: character "+" not allowed in attribute specification list 
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

    ✉

  224. Error Line 1902, Column 30: element "atpos" undefined 
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

    ✉

    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).
  225. Warning Line 1930, Column 26: character "<" is the first character of a delimiter but occurred as data 
    	 for (i = 0 ; i < f_mobile.length ; i++)

    ✉

    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.
  226. Warning Line 1932, Column 36: character "<" is the first character of a delimiter but occurred as data 
    	  if ((f_mobile.charAt(i) < '0') || (f_mobile.charAt(i) > '9'))

    ✉

    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.
  227. Warning Line 1963, Column 36: cannot generate system identifier for general entity "f_email" 
    	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_…

    ✉

    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.

  228. Error Line 1963, Column 36: general entity "f_email" not defined and no default entity 
    	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&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.

  229. Warning Line 1963, Column 43: reference not terminated by REFC delimiter 
    …data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_fea…

    ✉

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

  230. Error Line 1963, Column 43: reference to entity "f_email" for which no system identifier could be generated 
    …	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_fea…

    ✉

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

  231. Info Line 1963, Column 35: entity was defined here 
    	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_…
  232. Warning Line 1963, Column 56: cannot generate system identifier for general entity "f_mobile" 
    …f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_fea…

    ✉

    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.

  233. Error Line 1963, Column 56: general entity "f_mobile" not defined and no default entity 
    …f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_fea…

    ✉

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

  234. Warning Line 1963, Column 64: reference not terminated by REFC delimiter 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  235. Error Line 1963, Column 64: reference to entity "f_mobile" for which no system identifier could be generated 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  236. Info Line 1963, Column 55: entity was defined here 
    …"f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_fe…
  237. Warning Line 1963, Column 78: cannot generate system identifier for general entity "f_feadback" 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

    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.

  238. Error Line 1963, Column 78: general entity "f_feadback" not defined and no default entity 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  239. Warning Line 1963, Column 88: reference not terminated by REFC delimiter 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  240. Error Line 1963, Column 88: reference to entity "f_feadback" for which no system identifier could be generated 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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


  241. Info Line 1963, Column 77: entity was defined here 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,
  242. Warning Line 2036, Column 12: character "<" is the first character of a delimiter but occurred as data 
    		if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

    ✉

    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.
  243. Error Line 2036, Column 30: character "+" not allowed in attribute specification list 
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

    ✉

  244. Error Line 2036, Column 30: element "atpos" undefined 
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

    ✉

    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).
  245. Warning Line 2065, Column 26: character "<" is the first character of a delimiter but occurred as data 
    	 for (i = 0 ; i < f_mobile.length ; i++)

    ✉

    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.
  246. Warning Line 2067, Column 37: character "<" is the first character of a delimiter but occurred as data 
    	  if ((f_mobile.charAt(i) < '0') || (f_mobile.charAt(i) > '9'))

    ✉

    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.
  247. Warning Line 2104, Column 43: reference not terminated by REFC delimiter 
    …	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_fea…

    ✉

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

  248. Error Line 2104, Column 43: reference to entity "f_email" for which no system identifier could be generated 
    …	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_fea…

    ✉

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

  249. Info Line 1963, Column 35: entity was defined here 
    	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_…
  250. Warning Line 2104, Column 64: reference not terminated by REFC delimiter 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  251. Error Line 2104, Column 64: reference to entity "f_mobile" for which no system identifier could be generated 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  252. Info Line 1963, Column 55: entity was defined here 
    …"f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_fe…
  253. Warning Line 2104, Column 88: reference not terminated by REFC delimiter 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  254. Error Line 2104, Column 88: reference to entity "f_feadback" for which no system identifier could be generated 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,

    ✉

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

  255. Info Line 1963, Column 77: entity was defined here 
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,
  256. Error Line 2138, Column 9: end tag for "atpos" 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 ">".

  257. Info Line 2036, Column 24: start tag was here 
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)
  258. Error Line 2138, Column 9: end tag for "atpos" 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 ">".

  259. Info Line 1902, Column 24: start tag was here 
    if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)
  260. Error Line 2142, Column 30: 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>.

  261. Error Line 2167, Column 30: 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>.

  262. Error Line 2176, Column 30: 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>.

  263. Error Line 2192, Column 30: 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>.

  264. Warning Line 2202, Column 22: character "&" is the first character of a delimiter but occurred as data 
    	 if (errorids!=null && errorids!="")

    ✉

    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.
  265. Warning Line 2202, Column 23: character "&" is the first character of a delimiter but occurred as data 
    	 if (errorids!=null && errorids!="")

    ✉

    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.
  266. Warning Line 2207, Column 24: character "<" is the first character of a delimiter but occurred as data 
    		    for(var i = 0; i < str_array.length-1; i++)

    ✉

    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.
  267. Warning Line 2230, Column 40: cannot generate system identifier for general entity "status" 
    …	    data: "product_id="+product_id+"&status="+status+"&cart_id="+cartid+"&car…

    ✉

    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.

  268. Error Line 2230, Column 40: general entity "status" not defined and no default entity 
    …	    data: "product_id="+product_id+"&status="+status+"&cart_id="+cartid+"&car…

    ✉

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

  269. Warning Line 2230, Column 46: reference not terminated by REFC delimiter 
    …ata: "product_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype=…

    ✉

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

  270. Error Line 2230, Column 46: reference to entity "status" for which no system identifier could be generated 
    …ata: "product_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype=…

    ✉

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


  271. Info Line 2230, Column 39: entity was defined here 
    		    data: "product_id="+product_id+"&status="+status+"&cart_id="+cartid+"&car…
  272. Warning Line 2230, Column 58: cannot generate system identifier for general entity "cart_id" 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

    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.

  273. Error Line 2230, Column 58: general entity "cart_id" not defined and no default entity 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

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

  274. Warning Line 2230, Column 65: reference not terminated by REFC delimiter 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

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

  275. Error Line 2230, Column 65: reference to entity "cart_id" for which no system identifier could be generated 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

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

  276. Info Line 2230, Column 57: entity was defined here 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,
  277. Warning Line 2230, Column 77: cannot generate system identifier for general entity "carttype" 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

    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.

  278. Error Line 2230, Column 77: general entity "carttype" not defined and no default entity 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

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

  279. Warning Line 2230, Column 85: reference not terminated by REFC delimiter 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

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

  280. Error Line 2230, Column 85: reference to entity "carttype" for which no system identifier could be generated 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,

    ✉

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

  281. Info Line 2230, Column 76: entity was defined here 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,
  282. Warning Line 2233, Column 27: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  283. Warning Line 2233, Column 28: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  284. Warning Line 2270, Column 21: character "&" is the first character of a delimiter but occurred as data 
    	if (errorids!=null && errorids!="")

    ✉

    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.
  285. Warning Line 2270, Column 22: character "&" is the first character of a delimiter but occurred as data 
    	if (errorids!=null && errorids!="")

    ✉

    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.
  286. Warning Line 2275, Column 24: character "<" is the first character of a delimiter but occurred as data 
    	 for(var i = 0; i < str_array.length-1; i++)

    ✉

    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.
  287. Warning Line 2305, Column 47: reference not terminated by REFC delimiter 
    …ata: "product_id="+product_id+"&status="+status+"&carttype="+carttype+"&cart_i…

    ✉

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

  288. Error Line 2305, Column 47: reference to entity "status" for which no system identifier could be generated 
    …ata: "product_id="+product_id+"&status="+status+"&carttype="+carttype+"&cart_i…

    ✉

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

  289. Info Line 2230, Column 39: entity was defined here 
    	  data: "product_id="+product_id+"&status="+status+"&cart_id="+cartid+"&car…
  290. Warning Line 2305, Column 67: reference not terminated by REFC delimiter 
    …uct_id="+product_id+"&status="+status+"&carttype="+carttype+"&cart_id="+cartid,

    ✉

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

  291. Error Line 2305, Column 67: reference to entity "carttype" for which no system identifier could be generated 
    …uct_id="+product_id+"&status="+status+"&carttype="+carttype+"&cart_id="+cartid,

    ✉

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

  292. Info Line 2230, Column 76: entity was defined here 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,
  293. Warning Line 2305, Column 88: reference not terminated by REFC delimiter 
    …uct_id="+product_id+"&status="+status+"&carttype="+carttype+"&cart_id="+cartid,

    ✉

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

  294. Error Line 2305, Column 88: reference to entity "cart_id" for which no system identifier could be generated 
    …uct_id="+product_id+"&status="+status+"&carttype="+carttype+"&cart_id="+cartid,

    ✉

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

  295. Info Line 2230, Column 57: entity was defined here 
    …uct_id="+product_id+"&status="+status+"&cart_id="+cartid+"&carttype="+carttype,
  296. Warning Line 2309, Column 28: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  297. Warning Line 2309, Column 29: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("[&&]");

    ✉

    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.
  298. Warning Line 2345, Column 52: character "&" is the first character of a delimiter but occurred as data 
    	 if(nocart!="" && carttype=="1")

    ✉

    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.
  299. Warning Line 2345, Column 53: character "&" is the first character of a delimiter but occurred as data 
    	 if(nocart!="" && carttype=="1")

    ✉

    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.
  300. Warning Line 2354, Column 83: character "&" is the first character of a delimiter but occurred as data 
    …        if(nocart!="" && carttype=="2")					                  …

    ✉

    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.
  301. Warning Line 2354, Column 84: character "&" is the first character of a delimiter but occurred as data 
    …       if(nocart!="" && carttype=="2")					                   …

    ✉

    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.
  302. Warning Line 2382, Column 24: cannot generate system identifier for general entity "pro_id" 
    	  data: "id="+id+"&pro_id="+pro_id,

    ✉

    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.

  303. Error Line 2382, Column 24: general entity "pro_id" not defined and no default entity 
    	   data: "id="+id+"&pro_id="+pro_id,

    ✉

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

  304. Warning Line 2382, Column 30: reference not terminated by REFC delimiter 
    	  data: "id="+id+"&pro_id="+pro_id,

    ✉

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

  305. Error Line 2382, Column 30: reference to entity "pro_id" for which no system identifier could be generated 
        data: "id="+id+"&pro_id="+pro_id,

    ✉

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

  306. Info Line 2382, Column 23: entity was defined here 
    		    data: "id="+id+"&pro_id="+pro_id,
  307. Warning Line 2387, Column 59: character "&" is the first character of a delimiter but occurred as data 
    	  var str_array = data.split('[&&]');

    ✉

    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.
  308. Warning Line 2387, Column 60: character "&" is the first character of a delimiter but occurred as data 
    	 var str_array = data.split('[&&]');

    ✉

    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.
  309. Error Line 2403, Column 60: character ";" not allowed in attribute specification list 
    	  for(var i=0;i<limit;i++)

    ✉

  310. Error Line 2403, Column 60: element "limit" undefined 
    	   for(var i=0;i<limit;i++)

    ✉

    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).
  311. Warning Line 2423, Column 30: reference not terminated by REFC delimiter 
    	    data: "id="+id+"&pro_id="+pro_id,

    ✉

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

  312. Error Line 2423, Column 30: reference to entity "pro_id" for which no system identifier could be generated 
    	   data: "id="+id+"&pro_id="+pro_id,

    ✉

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

  313. Info Line 2382, Column 23: entity was defined here 
    	 data: "id="+id+"&pro_id="+pro_id,
  314. Warning Line 2428, Column 59: character "&" is the first character of a delimiter but occurred as data 
    	  var str_array = data.split('[&&]');

    ✉

    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.
  315. Warning Line 2428, Column 60: character "&" is the first character of a delimiter but occurred as data 
    	  var str_array = data.split('[&&]');

    ✉

    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.
  316. Error Line 2450, Column 60: character ";" not allowed in attribute specification list 
    	  for(var i=0;i<limit;i++)

    ✉

  317. Error Line 2450, Column 60: element "limit" undefined 
    	    for(var i=0;i<limit;i++)

    ✉

    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).
  318. Error Line 2455, Column 58: character ";" not allowed in attribute specification list 
    	    for(var i=0;i<num;i++)

    ✉

  319. Error Line 2455, Column 58: element "num" undefined 
    	    for(var i=0;i<num;i++)

    ✉

    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).
  320. Warning Line 2492, Column 31: cannot generate system identifier for general entity "size" 
    	    data: "pro_id="+pro_id+"&size="+size,

    ✉

    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.

  321. Error Line 2492, Column 31: general entity "size" not defined and no default entity 
    	    data: "pro_id="+pro_id+"&size="+size,

    ✉

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

  322. Warning Line 2492, Column 35: reference not terminated by REFC delimiter 
    	    data: "pro_id="+pro_id+"&size="+size,

    ✉

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

  323. Error Line 2492, Column 35: reference to entity "size" for which no system identifier could be generated 
    	    data: "pro_id="+pro_id+"&size="+size,

    ✉

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

  324. Info Line 2492, Column 30: entity was defined here 
    	    data: "pro_id="+pro_id+"&size="+size,
  325. Warning Line 2497, Column 31: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("&&");

    ✉

    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.
  326. Warning Line 2497, Column 32: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("&&");

    ✉

    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.
  327. Error Line 2529, Column 9: end tag for "num" 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 ">".

  328. Info Line 2455, Column 54: start tag was here 
    	                                       for(var i=0;i<num;i++)
  329. Error Line 2529, Column 9: end tag for "limit" 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 ">".


  330. Info Line 2450, Column 54: start tag was here 
    	  for(var i=0;i<limit;i++)
  331. Error Line 2529, Column 9: end tag for "limit" 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 ">".

  332. Info Line 2403, Column 54: start tag was here 
    	    for(var i=0;i<limit;i++)
  333. Error Line 2530, Column 30: 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>.

  334. Warning Line 2550, Column 25: character "&" is the first character of a delimiter but occurred as data 
    	  x=d.split("[&&]");

    ✉

    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.
  335. Warning Line 2550, Column 26: character "&" is the first character of a delimiter but occurred as data 
    	 x=d.split("[&&]");

    ✉

    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.
  336. Warning Line 2576, Column 52: reference not terminated by REFC delimiter 
    	var parameters="country_id="+country_id+"&userid="+userid;

    ✉

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

  337. Error Line 2576, Column 52: reference to entity "userid" for which no system identifier could be generated 
    	var parameters="country_id="+country_id+"&userid="+userid;

    ✉

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

  338. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  339. Warning Line 2617, Column 19: character "&" is the first character of a delimiter but occurred as data 
    	 x=d.split("[&&]");

    ✉

    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.
  340. Warning Line 2617, Column 20: character "&" is the first character of a delimiter but occurred as data 
    	 x=d.split("[&&]");

    ✉

    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.
  341. Warning Line 2629, Column 36: character "&" is the first character of a delimiter but occurred as data 
    	    if (errorids!=null && errorids!="")

    ✉

    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.
  342. Warning Line 2629, Column 37: character "&" is the first character of a delimiter but occurred as data 
    	    if (errorids!=null && errorids!="")

    ✉

    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.
  343. Warning Line 2635, Column 32: character "<" is the first character of a delimiter but occurred as data 
    	 for(var i = 0; i < (errorids.length-1); i++)

    ✉

    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.
  344. Warning Line 2649, Column 31: character "<" is the first character of a delimiter but occurred as data 
        for(var i = 0; i < (str_array.length-1); i++)

    ✉

    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.
  345. Warning Line 2664, Column 36: character "&" is the first character of a delimiter but occurred as data 
    	   if (errorids!=null && errorids!="")

    ✉

    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.
  346. Warning Line 2664, Column 37: character "&" is the first character of a delimiter but occurred as data 
    	  if (errorids!=null && errorids!="")

    ✉

    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.
  347. Warning Line 2670, Column 32: character "<" is the first character of a delimiter but occurred as data 
    	  for(var i = 0; i < errorids.length-1; i++)

    ✉

    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.
  348. Warning Line 2693, Column 30: character "<" is the first character of a delimiter but occurred as data 
    	   for(var i = 0; i < sarray.length; i++)

    ✉

    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.
  349. Error Line 2773, Column 30: 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>.

  350. Warning Line 2795, Column 20: character "&" is the first character of a delimiter but occurred as data 
    	   else if(tax==0 && taxerr==1)

    ✉

    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.
  351. Warning Line 2795, Column 21: character "&" is the first character of a delimiter but occurred as data 
    	   else if(tax==0 && taxerr==1)

    ✉

    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.
  352. Warning Line 2803, Column 24: character "&" is the first character of a delimiter but occurred as data 
    	   if (errorids!=null && errorids!="")

    ✉

    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.
  353. Warning Line 2803, Column 25: character "&" is the first character of a delimiter but occurred as data 
    	   if (errorids!=null && errorids!="")

    ✉

    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.
  354. Error Line 2816, Column 30: 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>.

  355. Error Line 2833, Column 39: character ";" not allowed in attribute specification list 
     	  for (i=0;i<ARRcookies.length;i++)

    ✉

  356. Error Line 2833, Column 39: element "ARRcookies.length" undefined 
     	  for (i=0;i<ARRcookies.length;i++)

    ✉

    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).
  357. Error Line 2844, Column 9: end tag for "ARRcookies.length" 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 ">".

  358. Info Line 2833, Column 21: start tag was here 
     	   for (i=0;i<ARRcookies.length;i++)
  359. Error Line 2846, Column 30: 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>.

  360. Error Line 2865, Column 66: required attribute "alt" not specified 
    	 var test="<img src="/+cost+" style='width:90px;height:100px;'>";

    ✉

    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>.


  361. Error Line 2865, Column 66: document type does not allow element "img" here 
    	 var test="<img src="/+cost+" style='width:90px;height:100px;'>";

    ✉

    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).

  362. Error Line 2865, Column 67: end tag for "img" omitted, but OMITTAG NO was specified 
    	 var test="<img src="/+cost+" style='width:90px;height:100px;'>";

    ✉

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

  363. Info Line 2865, Column 16: start tag was here 
    	 var test="<img src="/+cost+" style='width:90px;height:100px;'>";
  364. Error Line 2882, Column 30: 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>.

  365. Warning Line 2927, Column 38: reference not terminated by REFC delimiter 
    	    data: "pro_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+w…

    ✉

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

  366. Error Line 2927, Column 38: reference to entity "cartid" for which no system identifier could be generated 
    	   data: "pro_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+w…

    ✉

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

  367. Info Line 105, Column 52: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  368. Warning Line 2927, Column 50: cannot generate system identifier for general entity "wrapid" 
    …: "pro_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&…

    ✉

    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.

  369. Error Line 2927, Column 50: general entity "wrapid" not defined and no default entity 
    …: "pro_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&…

    ✉

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

  370. Warning Line 2927, Column 56: reference not terminated by REFC delimiter 
    …_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid…

    ✉

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

  371. Error Line 2927, Column 56: reference to entity "wrapid" for which no system identifier could be generated 
    …_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid…

    ✉

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

  372. Info Line 2927, Column 49: entity was defined here 
    …a: "pro_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"…
  373. Warning Line 2927, Column 68: cannot generate system identifier for general entity "wrap_msg" 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,

    ✉

    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.

  374. Error Line 2927, Column 68: general entity "wrap_msg" not defined and no default entity 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,

    ✉

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

  375. Warning Line 2927, Column 76: reference not terminated by REFC delimiter 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,

    ✉

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

  376. Error Line 2927, Column 76: reference to entity "wrap_msg" for which no system identifier could be generated 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,

    ✉

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

  377. Info Line 2927, Column 67: entity was defined here 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,
  378. Warning Line 2927, Column 96: reference not terminated by REFC delimiter 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,

    ✉

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

  379. Error Line 2927, Column 96: reference to entity "userid" for which no system identifier could be generated 
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,

    ✉

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

  380. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  381. Warning Line 2929, Column 45: character "&" is the first character of a delimiter but occurred as data 
    	var data_array = data.split('[&&]');

    ✉

    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.
  382. Warning Line 2929, Column 46: character "&" is the first character of a delimiter but occurred as data 
    		var data_array = data.split('[&&]');

    ✉

    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.
  383. Error Line 2952, Column 30: 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>.

  384. Warning Line 2958, Column 36: reference not terminated by REFC delimiter 
    	    data: "pro_id="+proid+"&cartid="+cartid,

    ✉

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


  385. Error Line 2958, Column 36: reference to entity "cartid" for which no system identifier could be generated 
    	    data: "pro_id="+proid+"&cartid="+cartid,

    ✉

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

  386. Info Line 105, Column 52: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  387. Warning Line 2960, Column 40: character "&" is the first character of a delimiter but occurred as data 
    		var data_array = data.split('[&&]');

    ✉

    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.
  388. Warning Line 2960, Column 41: character "&" is the first character of a delimiter but occurred as data 
    	var data_array = data.split('[&&]');

    ✉

    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.
  389. Warning Line 2988, Column 18: character "&" is the first character of a delimiter but occurred as data 
    	 x=d.split("[&&]");

    ✉

    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.
  390. Warning Line 2988, Column 19: character "&" is the first character of a delimiter but occurred as data 
    	 x=d.split("[&&]");

    ✉

    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.
  391. Warning Line 3092, Column 37: reference not terminated by REFC delimiter 
    	   data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  392. Error Line 3092, Column 37: reference to entity "userid" for which no system identifier could be generated 
    	  data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  393. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  394. Warning Line 3092, Column 49: cannot generate system identifier for general entity "coupon_code" 
    …: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+v…

    ✉

    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.

  395. Error Line 3092, Column 49: general entity "coupon_code" not defined and no default entity 
    …: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+v…

    ✉

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

  396. Warning Line 3092, Column 60: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  397. Error Line 3092, Column 60: reference to entity "coupon_code" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  398. Info Line 3092, Column 48: entity was defined here 
    …a: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+…
  399. Warning Line 3092, Column 85: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  400. Error Line 3092, Column 85: reference to entity "vendorid" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  401. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  402. Warning Line 3103, Column 28: character "&" is the first character of a delimiter but occurred as data 
    	  cartids=id.split("&&");

    ✉

    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.
  403. Warning Line 3103, Column 29: character "&" is the first character of a delimiter but occurred as data 
    	 cartids=id.split("&&");

    ✉

    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.
  404. Error Line 3105, Column 22: character ")" not allowed in attribute specification list 
    	 while(i<count) {

    ✉

  405. Error Line 3105, Column 22: element "count" undefined 
    	 while(i<count) {

    ✉

    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).
  406. Warning Line 3139, Column 37: reference not terminated by REFC delimiter 
    	  data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  407. Error Line 3139, Column 37: reference to entity "userid" for which no system identifier could be generated 
    	  data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  408. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  409. Warning Line 3139, Column 60: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  410. Error Line 3139, Column 60: reference to entity "coupon_code" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  411. Info Line 3092, Column 48: entity was defined here 
    …a: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+…
  412. Warning Line 3139, Column 85: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  413. Error Line 3139, Column 85: reference to entity "vendorid" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  414. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  415. Warning Line 3149, Column 42: character "&" is the first character of a delimiter but occurred as data 
    	  cartids=id.split("&&");

    ✉

    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.
  416. Warning Line 3149, Column 43: character "&" is the first character of a delimiter but occurred as data 
    	    cartids=id.split("&&");

    ✉

    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.
  417. Error Line 3151, Column 36: character ")" not allowed in attribute specification list 
    	    while(i<count) {

    ✉

  418. Error Line 3151, Column 36: element "count" undefined 
    	  while(i<count) {

    ✉

    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).
  419. Warning Line 3184, Column 37: reference not terminated by REFC delimiter 
    	   data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  420. Error Line 3184, Column 37: reference to entity "userid" for which no system identifier could be generated 
    	  data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  421. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  422. Warning Line 3184, Column 60: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  423. Error Line 3184, Column 60: reference to entity "coupon_code" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  424. Info Line 3092, Column 48: entity was defined here 
    …a: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+…
  425. Warning Line 3184, Column 85: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  426. Error Line 3184, Column 85: reference to entity "vendorid" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  427. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  428. Warning Line 3194, Column 42: character "&" is the first character of a delimiter but occurred as data 
    	 cartids=id.split("&&");

    ✉

    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.
  429. Warning Line 3194, Column 43: character "&" is the first character of a delimiter but occurred as data 
    	  cartids=id.split("&&");

    ✉

    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.
  430. Error Line 3196, Column 36: character ")" not allowed in attribute specification list 
    	    while(i<count) {

    ✉

  431. Error Line 3196, Column 36: element "count" undefined 
                while(i<count) {

    ✉

    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).
  432. Warning Line 3228, Column 37: reference not terminated by REFC delimiter 
    		    data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  433. Error Line 3228, Column 37: reference to entity "userid" for which no system identifier could be generated 
    		    data: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&ven…

    ✉

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

  434. Info Line 105, Column 70: entity was defined here 
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  435. Warning Line 3228, Column 60: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  436. Error Line 3228, Column 60: reference to entity "coupon_code" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  437. Info Line 3092, Column 48: entity was defined here 
    …a: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+…
  438. Warning Line 3228, Column 85: reference not terminated by REFC delimiter 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  439. Error Line 3228, Column 85: reference to entity "vendorid" for which no system identifier could be generated 
    …id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+vendorid,

    ✉

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

  440. Info Line 707, Column 112: entity was defined here 
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  441. Warning Line 3232, Column 20: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("&&");

    ✉

    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.
  442. Warning Line 3232, Column 21: character "&" is the first character of a delimiter but occurred as data 
    	 x=data.split("&&");

    ✉

    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.
  443. Error Line 3236, Column 26: character ";" not allowed in attribute specification list 
    	   while(i=0;i<count;i++)

    ✉

  444. Error Line 3236, Column 26: element "count" undefined 
    	  while(i=0;i<count;i++)

    ✉

    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).
  445. Error Line 3284, Column 10: end tag for "count" 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 ">".

  446. Info Line 3236, Column 20: start tag was here 
    	 while(i=0;i<count;i++)
  447. Error Line 3284, Column 10: end tag for "count" 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 ">".

  448. Info Line 3196, Column 30: start tag was here 
    	  while(i<count) {
  449. Error Line 3284, Column 10: end tag for "count" 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 ">".

  450. Info Line 3151, Column 30: start tag was here 
    	    while(i<count) {
  451. Error Line 3284, Column 10: end tag for "count" 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 ">".

  452. Info Line 3105, Column 16: start tag was here 
    	    while(i<count) {
  453. Error Line 3298, Column 8: required attribute "type" not specified 
    <script>(function(d, s, id) {

    ✉

    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>.

  454. Warning Line 3302, Column 57: cannot generate system identifier for general entity "version" 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

    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.

  455. Error Line 3302, Column 57: general entity "version" not defined and no default entity 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

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

  456. Warning Line 3302, Column 64: reference not terminated by REFC delimiter 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

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

  457. Error Line 3302, Column 64: reference to entity "version" for which no system identifier could be generated 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

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

  458. Info Line 3302, Column 56: entity was defined here 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";
  459. Warning Line 3302, Column 70: cannot generate system identifier for general entity "appId" 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

    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.


  460. Error Line 3302, Column 70: general entity "appId" not defined and no default entity 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

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

  461. Warning Line 3302, Column 75: reference not terminated by REFC delimiter 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

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

  462. Error Line 3302, Column 75: reference to entity "appId" for which no system identifier could be generated 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";

    ✉

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

  463. Info Line 3302, Column 69: entity was defined here 
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";
  464. Error Line 3305, Column 8: required attribute "type" not specified 
    <script>

    ✉

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

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

  465. Error Line 3327, Column 43: end tag for "input" omitted, but OMITTAG NO was specified 
     <input type="hidden" id="carts" value="">

    ✉

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

  466. Info Line 3327, Column 2: start tag was here 
     <input type="hidden" id="carts" value="">
  467. Error Line 3328, Column 45: end tag for "input" omitted, but OMITTAG NO was specified 
     <input type="hidden" id="protect" value="">

    ✉

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

  468. Info Line 3328, Column 2: start tag was here 
     <input type="hidden" id="protect" value="">
  469. Error Line 3390, Column 145: required attribute "rows" not specified 
    …;}" onfocus="if (this.value=='Details') {this.value = '';}"/>Details</textarea>

    ✉

    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>.

  470. Error Line 3390, Column 145: required attribute "cols" not specified 
    …;}" onfocus="if (this.value=='Details') {this.value = '';}"/>Details</textarea>

    ✉

    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>.

  471. Error Line 3390, Column 163: end tag for element "textarea" which is not open 
    …;}" onfocus="if (this.value=='Details') {this.value = '';}"/>Details</textarea>

    ✉

    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.

  472. Error Line 3407, Column 146: required attribute "rows" not specified 
    …" onfocus="if (this.value=='Feedback') {this.value = '';}"/>Feedback</textarea>

    ✉

    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>.

  473. Error Line 3407, Column 146: required attribute "cols" not specified 
    …" onfocus="if (this.value=='Feedback') {this.value = '';}"/>Feedback</textarea>

    ✉

    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>.

  474. Error Line 3407, Column 165: end tag for element "textarea" which is not open 
    …" onfocus="if (this.value=='Feedback') {this.value = '';}"/>Feedback</textarea>

    ✉

    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.

  475. Error Line 3445, Column 31: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right" 
    	<img align="absmiddle" border="0"   src="/userdata/languages/1/Thumb_en…

    ✉

    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.

  476. Error Line 3445, Column 107: required attribute "alt" not specified 
    …/1/Thumb_english.jpg"  title="English">&nbsp;English</a><a  onclick="change_la…

    ✉

    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>.

  477. Error Line 3445, Column 108: end tag for "img" omitted, but OMITTAG NO was specified 
    …1/Thumb_english.jpg"  title="English">&nbsp;English</a><a  onclick="change_lan…

    ✉

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

  478. Info Line 3445, Column 10: start tag was here 
    	<img align="absmiddle" border="0"   src="/userdata/languages/1/Thumb_en…
  479. Error Line 3446, Column 31: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right" 
    	<img align="absmiddle" border="0"  src="/userdata/languages/5/Thumb_spa…

    ✉

    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.

  480. Error Line 3446, Column 106: required attribute "alt" not specified 
    …/5/Thumb_spanish.jpg"  title="Spanish">&nbsp;Spanish</a><a  onclick="change_la…

    ✉

    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>.

  481. Error Line 3446, Column 107: end tag for "img" omitted, but OMITTAG NO was specified 
    …5/Thumb_spanish.jpg"  title="Spanish">&nbsp;Spanish</a><a  onclick="change_lan…

    ✉

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

  482. Info Line 3446, Column 10: start tag was here 
    	<img align="absmiddle" border="0"  src="/userdata/languages/5/Thumb_spa…
  483. Error Line 3447, Column 31: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right" 
    	<img align="absmiddle" border="0"  src="/userdata/languages/6/Thumb_fre…

    ✉

    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.

  484. Error Line 3447, Column 104: required attribute "alt" not specified 
    …rdata/languages/6/Thumb_french.jpg"  title="French">&nbsp;French</a>					</div>

    ✉

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

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

  485. Error Line 3447, Column 105: end tag for "img" omitted, but OMITTAG NO was specified 
    …rdata/languages/6/Thumb_french.jpg"  title="French">&nbsp;French</a>					</div>

    ✉

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


  486. Info Line 3447, Column 10: start tag was here 
    	<img align="absmiddle" border="0"  src="/userdata/languages/6/Thumb_fre…
  487. Error Line 3456, Column 194: required attribute "alt" not specified 
    …g" title="To find  stores near to you"></img></span><span class="qckc_numer">S…

    ✉

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

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

  488. Error Line 3479, Column 63: there is no attribute "placeholder" 
    …"text" id="searchwordbox" placeholder="Search Products" value="" class="textBo…

    ✉

    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.

  489. Error Line 3479, Column 154: there is no attribute "autocomplete" 
    …alue="" class="textBoxnew txt searchdiv" name="searchword" autocomplete="off"/>

    ✉

    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.

  490. Error Line 3480, Column 94: end tag for "input" omitted, but OMITTAG NO was specified 
    …put type="button" name="submit"  value="Search"  class="searchboxdiv 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 ">".

  491. Info Line 3480, Column 13: start tag was here 
                <input type="button" name="submit"  value="Search"  class="searchbo…
  492. Error Line 3481, Column 60: end tag for "input" omitted, but OMITTAG NO was specified 
                 <input type="hidden" name="venid"  value="0" >

    ✉

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

  493. Info Line 3481, Column 14: start tag was here 
                 <input type="hidden" name="venid"  value="0" >
  494. Error Line 3504, Column 16: there is no attribute "href" 
      	  <div href="#" class="alcategoriesbtn">

    ✉

    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.

  495. Warning Line 3513, Column 182: character "&" is the first character of a delimiter but occurred as data 
    …ories/details/1/Baby-Care--Toys" class="first_caspan">Baby Care & Toys</a></li>

    ✉

    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.
  496. Error Line 3562, Column 61: required attribute "alt" not specified 
           		<img src="/images/loading.gif" style="display:none"/>

    ✉

    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>.

  497. Error Line 3568, Column 69: document type does not allow element "link" here 
    <link rel="stylesheet" href="/css/owl.carousel.css" type="text/css" />

    ✉

    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).

  498. Error Line 3569, Column 66: document type does not allow element "link" here 
    <link rel="stylesheet" href="/css/owl.theme.css" type="text/css" />

    ✉

    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).

  499. Error Line 3570, Column 68: document type does not allow element "link" here 
    <link rel="stylesheet" href="/css/prettyPhoto.css" type="text/css" />

    ✉

    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).

  500. Error Line 3595, Column 5: invalid comment declaration: found character "<" outside comment but inside comment declaration 
    <!--<script type="text/javascript" src="/jquery-1.2.6.pack.js"></script>-->

    ✉

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  501. Info Line 3594, Column 1: comment declaration started here 
    <!--<link rel="stylesheet" href="/9lessons.css" type="text/css" />
  502. Error Line 3595, Column 71: end tag for element "script" which is not open 
    <!--<script type="text/javascript" src="/jquery-1.2.6.pack.js"></script>-->

    ✉

    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.

  503. Error Line 3596, Column 8: required attribute "type" not specified 
     <style>

    ✉

    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>.

  504. Error Line 3596, Column 8: document type does not allow element "style" here 
     <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).

  505. Error Line 4544, Column 7: end tag for "script" 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 ">".

  506. Info Line 3708, Column 1: start tag was here 
    <script type='text/javascript'>//<![CDATA[
  507. Error Line 4544, Column 7: end tag for "div" 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 ">".

  508. Info Line 3558, Column 1: start tag was here 
    <div class="wrapper">
  509. Error Line 4544, Column 7: end tag for "body" 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 ">".

  510. Info Line 3292, Column 1: start tag was here 
    <body>
  511. Error Line 4544, Column 7: end tag for "html" 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 ">".

  512. Info Line 2, Column 1: start tag was here 
    <html xmlns="http://www.w3.org/1999/xhtml">
  513. Error Line 4544, Column 7: missing marked section end 
    </div>

    ✉

  514. Info Line 3708, Column 34: marked section started here 
    <script type='text/javascript'>//<![CDATA[
Details
Hits: 12863
ad networking scriptadsense cloneadserver scriptadvertiser publisher networking scriptadwords cloneAndroid Appandroid app developersandroid app developmentAndroid Applicationandroid application development companyappdevapps designer and developerbugsbulk