Article Index
Page 11 of 21
It's not a joking. 514 bugs with Inoutscripts Shopping Cart - 11
Article Index
Page 11 of 21
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.
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.
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.
Line 1786, Column 35: entity was defined here
data: "searchword="+searchbox+"&search_cat="+search_cat,…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).
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).
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 "<"
- 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 1902, Column 30: character "+" not allowed in attribute specification list
if (atpos<1 || dotpos<atpos+2 || dotpos+2>=f_email.length) 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).
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 "<"
- 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 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 "<"
- 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 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 "&" (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 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.
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.
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.
Line 1963, Column 35: entity was defined here
data: "f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_……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 "&" (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 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.
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.
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.
Line 1963, Column 55: entity was defined here
…"f_name="+f_name+"&f_email="+f_email+"&f_mobile="+f_mobile+"&f_feadback="+f_fe……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 "&" (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 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.
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.
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,
