Article Index
Page 10 of 21
It's not a joking. 514 bugs with Inoutscripts Shopping Cart - 10
Article Index
Page 10 of 21
Line 1306, Column 16: start tag was here
for(var j=0;j<n+1;j++)
Line 1418, Column 9: end tag for "checkboxcount-1" 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 ">".
Line 1123, Column 24: start tag was here
for(i=0;i<checkboxcount-1;i++)</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 ">".
Line 1104, Column 24: start tag was here
for(i=0;i<radiocount-1;i++)</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 ">".
Line 910, Column 24: start tag was here
for(i=0;i<checkboxcount-1;i++)</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 ">".
Line 891, Column 24: start tag was here
for(i=0;i<radiocount-1;i++)
Line 1508, Column 32: character "&" is the first character of a delimiter but occurred as data
var aa=data.split("&&");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 1508, Column 33: character "&" is the first character of a delimiter but occurred as data
var aa=data.split("&&");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 1517, Column 106: document type does not allow element "div" here
…erHTML='<div class="noresult" style="height:200px;"><b>No Products</b></div>'; 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 1539, Column 25: character ";" not allowed in attribute specification list
for(i=0;i<brand_len-1;i++) for(i=0;i<brand_len-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 1561, Column 25: character ";" not allowed in attribute specification list
for(i=0;i<brand_len-1;i++) for(i=0;i<brand_len-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 1605, Column 29: character ";" not allowed in attribute specification list
for (i=0;i<ARRcookies.length;i++)for (i=0;i<ARRcookies.length;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 1628, Column 11: end tag for "ARRcookies.length" 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 ">".
Line 1605, Column 11: start tag was here
for (i=0;i<ARRcookies.length;i++) </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 ">".
Line 1561, Column 13: start tag was here
for(i=0;i<brand_len-1;i++) </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 ">".
Line 1539, Column 13: start tag was here
for(i=0;i<brand_len-1;i++) data: "searchword="+searchbox+"&search_cat="+search_cat,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.
