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

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

Article Index

  • Info Line 1963, Column 77entity was defined here
    …e="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_feadback,
  • Warning Line 2036, Column 12character "<" 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.
  • Error Line 2036, Column 30character "+" not allowed in attribute specification list
    	if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)

  • Error Line 2036, Column 30element "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).
  • Warning Line 2065, Column 26character "<" 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.
  • Warning Line 2067, Column 37character "<" 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.
  • Warning Line 2104, Column 43reference 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.

  • Error Line 2104, Column 43reference 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.

  • Info Line 1963, Column 35entity was defined here
    	data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_…
  • Warning Line 2104, Column 64reference 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.

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

  • Info Line 1963, Column 55entity was defined here
    …"f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_fe…
  • Warning Line 2104, Column 88reference 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.

  • Error Line 2104, Column 88reference 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.

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

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

  • Info Line 1902, Column 24start tag was here
    if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length)
  • Error Line 2142, Column 30required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 2167, Column 30required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 2176, Column 30required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 2192, Column 30required 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>.

  • Warning Line 2202, Column 22character "&" 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.
  • Warning Line 2202, Column 23character "&" 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.
  • Warning Line 2207, Column 24character "<" 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.
  • Warning Line 2230, Column 40cannot 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.

  • Error Line 2230, Column 40general 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.

  • Warning Line 2230, Column 46reference 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.

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