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

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

Article Index

  • Error Line 2865, Column 66document 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).

  • Error Line 2865, Column 67end 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 ">".

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

  • Error Line 2927, Column 38reference 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.

  • Info Line 105, Column 52entity was defined here
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  • Warning Line 2927, Column 50cannot 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.

  • Error Line 2927, Column 50general 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.

  • Warning Line 2927, Column 56reference 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.

  • Error Line 2927, Column 56reference 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.

  • Info Line 2927, Column 49entity was defined here
    …a: "pro_id="+proid+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"…
  • Warning Line 2927, Column 68cannot 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.

  • Error Line 2927, Column 68general 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.

  • Warning Line 2927, Column 76reference 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.

  • Error Line 2927, Column 76reference 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.

  • Info Line 2927, Column 67entity was defined here
    …id+"&cartid="+cartid+"&wrapid="+wrapid+"&wrap_msg="+wrap_msg+"&userid="+userid,
  • Warning Line 2927, Column 96reference 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.

  • Error Line 2927, Column 96reference 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.

  • Info Line 105, Column 70entity was defined here
    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,
  • Warning Line 2929, Column 45character "&" 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.
  • Warning Line 2929, Column 46character "&" 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.
  • Error Line 2952, 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 2958, Column 36reference not terminated by REFC delimiter
    	    data: "pro_id="+proid+"&cartid="+cartid,