It's not a joking. 514 bug with Inoutscripts Shooping Cart - 19

It's not a joking. 514 bug with Inoutscripts Shooping Cart - 19
  • Warning Line 3228, Column 37reference 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.

  • Error Line 3228, Column 37reference 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.

  • Info Line 105, Column 70entity was defined here
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  • Warning Line 3228, Column 60reference 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.

  • Error Line 3228, Column 60reference 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.

  • Info Line 3092, Column 48entity was defined here
    …a: "pro_id="+proid+"&userid="+userid+"&coupon_code="+coupon_code+"&vendorid="+…
  • Warning Line 3228, Column 85reference 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.

  • Error Line 3228, Column 85reference 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.

  • Info Line 707, Column 112entity was defined here
    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
  • Warning Line 3232, Column 20character "&" 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.
  • Warning Line 3232, Column 21character "&" 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.
  • Error Line 3236, Column 26character ";" not allowed in attribute specification list
    	   while(i=0;i<count;i++)

  • Error Line 3236, Column 26element "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).
  • Error Line 3284, Column 10end 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 ">".

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

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

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

  • Info Line 3105, Column 16start tag was here
    	    while(i<count) {
  • Error Line 3298, Column 8required 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>.

  • Warning Line 3302, Column 57cannot 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.

  • Error Line 3302, Column 57general 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.

  • Warning Line 3302, Column 64reference 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.

  • Error Line 3302, Column 64reference 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.

  • Info Line 3302, Column 56entity was defined here
    …connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1636949589883252";
  • Warning Line 3302, Column 70cannot 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.