Article Index
Page 5 of 21
It's not a joking. 514 bugs with Inoutscripts Shopping Cart - 5
Article Index
Page 5 of 21
Line 707, Column 112: entity was defined here
…ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;
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 "&" (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 æ 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.
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.
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.
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.
Line 770, Column 36: entity was defined here
data: "product_id="+pro_id+"&page="+pagestat, 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 "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 891, Column 37: character ";" not allowed in attribute specification list
for(i=0;i<radiocount-1;i++) 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).
Line 910, Column 40: character ";" not allowed in attribute specification list
for(i=0;i<checkboxcount-1;i++) 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).
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 "&" (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 æ 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.
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.
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.
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.
Line 931, Column 39: entity was defined here
data: "product_id="+prd_id+"&select="+selectfields_value1+"&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 "&" (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 æ 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.
Line 931, Column 71: general entity "selectid" not defined and no default entity
…d_id+"&select="+selectfields_value1+"&selectid="+selectfield_ids+"&radioid="+r…
