Latest News: (loading..)
iankil

[Contribution] Mindsparx Admin v5 for 2.3

66 posts in this topic

Hey, Great addon. but some errors in the addon, 113 to be precise and that on the admin main page. Is there a version in the future that will be more "stable"? "PS: I don't have any other addons installed."

 

done validation through http://validator.w3.org/check#

 

Validation Output: 113 Errors 
Line 7, Column 50: NET-enabling start-tag requires SHORTTAG YES 
<base href="http://shop.cyberscene.co.za/admin/" />

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 9, Column 117: document type does not allow element "LINK" here 
… href="http://shop.cyberscene.co.za/ext/jquery/ui/redmond/jquery-ui-1.8.6.css">

✉ 

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 21, Column 70: document type does not allow element "LINK" here 
<link rel="stylesheet" type="text/css" href="includes/stylesheet.css">

✉ 

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 22, Column 56: required attribute "TYPE" not specified 
<script language="javascript" src="includes/general.js"></script>

✉ 

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>. 
Line 43, Column 7: end tag for element "HEAD" which is not open 
</head>

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 44, Column 6: document type does not allow element "BODY" here 
<body>

✉ 

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 48, Column 92: NET-enabling start-tag requires SHORTTAG YES 
…lesheet" type="text/css" href="mindsparx_admin/template/sparx/stylesheet.css"/>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 48, Column 92: document type does not allow element "LINK" here 
…lesheet" type="text/css" href="mindsparx_admin/template/sparx/stylesheet.css"/>

✉ 

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 50, Column 74: there is no attribute "HEIGHT" 
…enter"  border="0" width="1000" height="800px" cellspacing="0" cellpadding="0">

✉ 

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
Line 56, Column 131: NET-enabling start-tag requires SHORTTAG YES 
…g src="mindsparx_admin/template/sparx/images/store_logo.png" border="0"  /></a>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 56, Column 131: required attribute "ALT" not specified 
…g src="mindsparx_admin/template/sparx/images/store_logo.png" border="0"  /></a>

✉ 

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>. 
Line 63, Column 71: there is no attribute "BACKGROUND" 
…gn="right" valign="bottom" background="mindsparx_admin/template/sparx/images/p…

✉ 

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
Line 63, Column 276: NET-enabling start-tag requires SHORTTAG YES 
…mplate/sparx/images/panel_01.gif" width="97" height="45" border="0" /></a></td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 63, Column 276: required attribute "ALT" not specified 
…mplate/sparx/images/panel_01.gif" width="97" height="45" border="0" /></a></td>

✉ 

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>. 
Line 64, Column 268: NET-enabling start-tag requires SHORTTAG YES 
…mplate/sparx/images/panel_02.gif" width="67" height="45" border="0" /></a></td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 64, Column 268: required attribute "ALT" not specified 
…mplate/sparx/images/panel_02.gif" width="67" height="45" border="0" /></a></td>

✉ 

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>. 
Line 65, Column 270: NET-enabling start-tag requires SHORTTAG YES 
…mplate/sparx/images/panel_03.gif" width="79" height="45" border="0" /></a></td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 65, Column 270: required attribute "ALT" not specified 
…mplate/sparx/images/panel_03.gif" width="79" height="45" border="0" /></a></td>

✉ 

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>. 
Line 66, Column 263: NET-enabling start-tag requires SHORTTAG YES 
…mplate/sparx/images/panel_04.gif" width="81" height="45" border="0" /></a></td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 66, Column 263: required attribute "ALT" not specified 
…mplate/sparx/images/panel_04.gif" width="81" height="45" border="0" /></a></td>

✉ 

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>. 
Line 67, Column 265: NET-enabling start-tag requires SHORTTAG YES 
…mplate/sparx/images/panel_05.gif" width="79" height="45" border="0" /></a></td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 67, Column 265: required attribute "ALT" not specified 
…mplate/sparx/images/panel_05.gif" width="79" height="45" border="0" /></a></td>

✉ 

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>. 
Line 68, Column 271: value of attribute "ALIGN" cannot be "ABSBOTTOM"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT" 
…/panel_06.gif" width="95" height="45" align="absbottom" border="0" /></a> </td>

✉ 

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. 
Line 68, Column 284: NET-enabling start-tag requires SHORTTAG YES 
…/panel_06.gif" width="95" height="45" align="absbottom" border="0" /></a> </td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 68, Column 284: required attribute "ALT" not specified 
…/panel_06.gif" width="95" height="45" align="absbottom" border="0" /></a> </td>

✉ 

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>. 
Line 93, Column 90: "IF" is not a reserved name 
…href="#"><span>Configuration</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 93, Column 109: "ENDIF" is not a reserved name 
…iguration</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 94, Column 2582: "IF" is not a reserved name 
…nui0" href="#"><span>Catalog</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 94, Column 2601: "ENDIF" is not a reserved name 
…n>Catalog</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 95, Column 1061: "IF" is not a reserved name 
…nui0" href="#"><span>Modules</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 95, Column 1080: "ENDIF" is not a reserved name 
…n>Modules</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 96, Column 1248: "IF" is not a reserved name 
…i0" href="#"><span>Customers</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 96, Column 1267: "ENDIF" is not a reserved name 
…Customers</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 97, Column 396: "IF" is not a reserved name 
…="#"><span>Locations / Taxes</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 97, Column 415: "ENDIF" is not a reserved name 
…s / Taxes</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 98, Column 762: "IF" is not a reserved name 
… href="#"><span>Localization</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 98, Column 781: "ENDIF" is not a reserved name 
…alization</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 99, Column 525: "IF" is not a reserved name 
…nui0" href="#"><span>Reports</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 99, Column 544: "ENDIF" is not a reserved name 
…n>Reports</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 100, Column 857: "IF" is not a reserved name 
…Menui0" href="#"><span>Tools</span><![if gt IE 6]></a><![endif]><!--[if lte IE…

✉ 
Line 100, Column 876: "ENDIF" is not a reserved name 
…pan>Tools</span><![if gt IE 6]></a><![endif]><!--[if lte IE 6]><table><tr><td>…

✉ 
Line 121, Column 152: cannot generate system identifier for general entity "status" 
…min/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a cl…

✉ 

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 121, Column 152: general entity "status" not defined and no default entity 
…min/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a cl…

✉ 

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 121, Column 158: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a class="t…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 285: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=2">Processing</a>: 0, <a class="text2" …

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 406: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=3">Shipped</a>: 0, <a class="text2" hre…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 524: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=4">PayPal [Transactions]</a>: 0, <b>Tod…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 737: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=1">Awaiting Payment</a>: R0.00, <a clas…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 868: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=2">Processing</a>: R0.00, <a class="tex…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 993: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=3">Shipped</a>: R0.00, <a class="text2"…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 121, Column 1115: reference to entity "status" for which no system identifier could be generated 
…ders.php?selected_box=customers&status=4">PayPal [Transactions]</a>: R0.00,<b>…

✉ 

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 121, Column 151: entity was defined here 
…dmin/orders.php?selected_box=customers&status=1">Awaiting Payment</a>: 0, <a c…
Line 138, Column 221: cannot generate system identifier for general entity "read" 
…gories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_v…

✉ 

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 138, Column 221: general entity "read" not defined and no default entity 
…gories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_v…

✉ 

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 138, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=29&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 138, Column 231: cannot generate system identifier for general entity "pID" 
…?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?…

✉ 

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 138, Column 231: general entity "pID" not defined and no default entity 
…?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?…

✉ 

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 138, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 138, Column 238: cannot generate system identifier for general entity "origin" 
…=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1'…

✉ 

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 138, Column 238: general entity "origin" not defined and no default entity 
…=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1'…

✉ 

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 138, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 140, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=29&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 140, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 140, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1">HTC T…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 143, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=30&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 143, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=30&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 143, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=30&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 145, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=30&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 145, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=30&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 145, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=30&origin=stats_products_viewed.php?page=1">Class…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 148, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=31&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 148, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=31&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 148, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=31&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 150, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=31&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 150, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=31&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 150, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=31&origin=stats_products_viewed.php?page=1">Power…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 153, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=33&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 153, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=33&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 153, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=33&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 155, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=33&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 155, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=33&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 155, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=33&origin=stats_products_viewed.php?page=1">Warri…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 158, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=34&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 158, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=34&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 158, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=34&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 160, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=34&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 160, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=34&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 160, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=34&origin=stats_products_viewed.php?page=1">XP Po…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 163, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=35&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 163, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=35&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 163, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=35&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 165, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=35&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 165, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=35&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 165, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=35&origin=stats_products_viewed.php?page=1">Power…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 168, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=32&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 168, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=32&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 168, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=32&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 170, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=32&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 170, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=32&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 170, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=32&origin=stats_products_viewed.php?page=1">Perfo…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 173, Column 225: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=36&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 173, Column 234: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=36&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 173, Column 244: reference to entity "origin" for which no system identifier could be generated 
…new_product_preview&read=only&pID=36&origin=stats_products_viewed.php?page=1'">

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 175, Column 199: reference to entity "read" for which no system identifier could be generated 
…es.php?action=new_product_preview&read=only&pID=36&origin=stats_products_viewe…

✉ 

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 138, Column 220: entity was defined here 
…egories.php?action=new_product_preview&read=only&pID=29&origin=stats_products_…
Line 175, Column 208: reference to entity "pID" for which no system identifier could be generated 
…tion=new_product_preview&read=only&pID=36&origin=stats_products_viewed.php?pag…

✉ 

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 138, Column 230: entity was defined here 
…p?action=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php…
Line 175, Column 218: reference to entity "origin" for which no system identifier could be generated 
…roduct_preview&read=only&pID=36&origin=stats_products_viewed.php?page=1">Voyag…

✉ 

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 138, Column 237: entity was defined here 
…n=new_product_preview&read=only&pID=29&origin=stats_products_viewed.php?page=1…
Line 235, Column 89: end tag for element "A" which is not open 
…rn '<a href="http://shop.cyberscene.co.za/admin/orders.php">' + label + '</a>';

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 242, Column 45: end tag for "SCRIPT" omitted, but its declaration does not permit this 
 $('<div id="tooltip">' + contents + '</div>').css( {

✉ 
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag. 
Line 211, Column 1: start tag was here 
<script type="text/javascript">
Line 242, Column 45: end tag for "TABLE" omitted, but its declaration does not permit this 
 $('<div id="tooltip">' + contents + '</div>').css( {

✉ 
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag. 
Line 207, Column 13: start tag was here 
       <td><table border="0" width="100%" cellspacing="0" cellpadding="2">
Line 242, Column 45: end tag for "TABLE" omitted, but its declaration does not permit this 
 $('<div id="tooltip">' + contents + '</div>').css( {

✉ 
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag. 
Line 196, Column 5: start tag was here 
   <table border="0" width="100%" cellspacing="0" cellpadding="2">
Line 274, Column 9: end tag for element "SCRIPT" which is not open 
</script>            </td>

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 301, Column 92: end tag for element "A" which is not open 
…'<a href="http://shop.cyberscene.co.za/admin/customers.php">' + label + '</a>';

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 308, Column 45: end tag for element "DIV" which is not open 
 $('<div id="tooltip">' + contents + '</div>').css( {

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
Line 350, Column 624: entity was defined here 
…_ACTION_RECORDER?module=ar_admin_login&aID=35">shaun</a></td>    <td class="da…
Line 350, Column 1742: NET-enabling start-tag requires SHORTTAG YES 
…ges/icons/tick.gif" border="0" alt="" /></td>    <td class="dataTableContent">…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 350, Column 1876: reference to entity "aID" for which no system identifier could be generated 
…ION_RECORDER?module=ar_admin_login&aID=32">shaun</a></td>    <td class="dataTa…

✉ 

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 350, Column 624: entity was defined here 
…_ACTION_RECORDER?module=ar_admin_login&aID=35">shaun</a></td>    <td class="da…
Line 350, Column 2158: NET-enabling start-tag requires SHORTTAG YES 
…ges/icons/tick.gif" border="0" alt="" /></td>    <td class="dataTableContent">…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 350, Column 2292: reference to entity "aID" for which no system identifier could be generated 
…ION_RECORDER?module=ar_admin_login&aID=31">shaun</a></td>    <td class="dataTa…

✉ 

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 350, Column 624: entity was defined here 
…_ACTION_RECORDER?module=ar_admin_login&aID=35">shaun</a></td>    <td class="da…
Line 350, Column 2574: NET-enabling start-tag requires SHORTTAG YES 
…ges/icons/tick.gif" border="0" alt="" /></td>    <td class="dataTableContent">…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 350, Column 2708: reference to entity "aID" for which no system identifier could be generated 
…ION_RECORDER?module=ar_admin_login&aID=30">shaun</a></td>    <td class="dataTa…

✉ 

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 350, Column 624: entity was defined here 
…_ACTION_RECORDER?module=ar_admin_login&aID=35">shaun</a></td>    <td class="da…
Line 356, Column 2245: NET-enabling start-tag requires SHORTTAG YES 
…gn-Up for the osCommerce Newsletter " /></a> <a href="http://www.facebook…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 356, Column 2473: NET-enabling start-tag requires SHORTTAG YES 
…ecome an osCommerce Fan on Facebook " /></a> <a href="http://twitter.com/…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 356, Column 2661: NET-enabling start-tag requires SHORTTAG YES 
…itle=" Follow osCommerce on Twitter " /></a> <a href="http://feeds.feedbu…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 356, Column 2892: NET-enabling start-tag requires SHORTTAG YES 
…ibe to the osCommerce News RSS Feed " /></a></td>  </tr></table>            </…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 358, Column 2342: NET-enabling start-tag requires SHORTTAG YES 
… to the osC an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 368, Column 12: end tag for element "TABLE" which is not open 
   </table>

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 371, Column 6: end tag for element "DIV" which is not open 
</div>

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occ an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 368, Column 12: end tag for element "TABLE" which is not open 
   </table>

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 371, Column 6: end tag for element "DIV" which is not open 
</div>

✉ 

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. 

If this error occurred in a script section of your document, you should probably read this FAQ entry. 
Line 373, Column 5: NET-enabling start-tag requires SHORTTAG YES 
<br />

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 377, Column 120: NET-enabling start-tag requires SHORTTAG YES 
…; 2010 <a href="http://www.oscommerce.com" target="_blank">osCommerce</a><br />

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 382, Column 82: NET-enabling start-tag requires SHORTTAG YES 
…img src="images/pixel_trans.gif" border="0" alt="" width="1" height="5" /></td>

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 385, Column 123: NET-enabling start-tag requires SHORTTAG YES 
…om" target="_blank">osCommerce</a><br />   <!-- If you are using Mindsparx adm…

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. 
Line 392, Column 5: NET-enabling start-tag requires SHORTTAG YES 
<br />

✉ 

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Share this post


Link to post
Share on other sites

If you look at the table mindsparx_admin (to the left in phpmyadmin) what is the name of the table below? I need to know how your tables are named,

 

Mabe he didn't update the tables php file?

Share this post


Link to post
Share on other sites

Hello

I use the famous pure css menu for this addon and many of thouse errors comes from that, i dont care about validating the admin main page since it works great, if you want a cleaner version you can help me to clean it :thumbsup:

/Janne

Share this post


Link to post
Share on other sites

Hello

I use the famous pure css menu for this addon and many of thouse errors comes from that, i dont care about validating the admin main page since it works great, if you want a cleaner version you can help me to clean it :thumbsup:

/Janne

 

Hi Janne,

 

Mindsparx Admin rocks!

 

I agree its totally pointless to validate the code as it should be locked tight so no one including the search engines can see it.

 

Keep up the good work :thumbsup:

 

Mark

Share this post


Link to post
Share on other sites

Hi Janne,

 

Mindsparx Admin rocks!

 

I agree its totally pointless to validate the code as it should be locked tight so no one including the search engines can see it.

 

Keep up the good work :thumbsup:

 

Mark

 

 

Thanks ;) Btw i ran a few famous sites threw the validator just for fun and Amazone.com´s mainpage has 415 Errors, 108 warning(s) , Ebay has 485 Errors, 23 warning(s) And this thread has 45 Errors, 5 warning(s) :rolleyes:

Share this post


Link to post
Share on other sites

Thanks ;) Btw i ran a few famous sites threw the validator just for fun and Amazone.com´s mainpage has 415 Errors, 108 warning(s) , Ebay has 485 Errors, 23 warning(s) And this thread has 45 Errors, 5 warning(s) :rolleyes:

 

ha ha nice one! :-"

Share this post


Link to post
Share on other sites

All those are understandable, due to the fact user create their own listings with html code. this page has code in where it doesn't belong.. Just thought I could help out.. Reason being it is a great cont. but some others don't display well with it? Maby it's my mistake, but installed coupon and easypopulate, but showing out of the screen, very weird. then there is some packages that shows fine and blend well.. Those errors might be the problem if it doesn't show on some browsers. But I like clean script that display well, loads fast, and no room for errors in the future. Will try and help clean it.

Share this post


Link to post
Share on other sites

All those are understandable, due to the fact user create their own listings with html code. this page has code in where it doesn't belong.. Just thought I could help out.. Reason being it is a great cont. but some others don't display well with it? Maby it's my mistake, but installed coupon and easypopulate, but showing out of the screen, very weird. then there is some packages that shows fine and blend well.. Those errors might be the problem if it doesn't show on some browsers. But I like clean script that display well, loads fast, and no room for errors in the future. Will try and help clean it.

 

Hello

To validate the admin was nothing i tought was nessesary but you have a point, if other contributions dont display well then a cleanup dosnt sound to bad, Thanks for helping out, i´ll clean the code for the next release :)

 

/Janne

Share this post


Link to post
Share on other sites

I was about to validate the admin main page but i can only see 29 Errors, 20 warning(s) and with HTML 4.01 Transitional i see 11 errors, How did you get over 100?

 

/Janne

Share this post


Link to post
Share on other sites

Iankil,

 

Great contrib. I use it on my live store (osc RC2.2a) but am upgrading my store to 2.3.1 as soon as I get enough of the contributions I'm currently using working in 2.3.1 (Like Wishlist).

 

I've installed this on my test site, and added

   include(DIR_WS_BOXES . 'articles.php'); //ArticlesManager v1.57_6
   include(DIR_WS_BOXES . 'header_tags_seo.php'); //Header Tags SEO v3.2.5
   include(DIR_WS_BOXES . 'sitemonitor.php'); //Sitemonitor v2.8 

 

into the header.php file just below

    include(DIR_WS_BOXES . 'configuration.php');
   include(DIR_WS_BOXES . 'catalog.php');
   include(DIR_WS_BOXES . 'modules.php');
   include(DIR_WS_BOXES . 'customers.php');
   include(DIR_WS_BOXES . 'taxes.php');
   include(DIR_WS_BOXES . 'localization.php');
   include(DIR_WS_BOXES . 'reports.php');
   include(DIR_WS_BOXES . 'tools.php');

 

Now, on my test site the header drop menu's appear as thus:

mindsparxheaderproblem0.jpg

 

Is there a way to make it when the header menu 'wraps' that the second line appears a bit lower? So that it appears more like this:

mindsparxheaderproblem0.jpg

 

Naloomi

Edited by Naloomi

Share this post


Link to post
Share on other sites

Iankil,

 

Great contrib. I use it on my live store (osc RC2.2a) but am upgrading my store to 2.3.1 as soon as I get enough of the contributions I'm currently using working in 2.3.1 (Like Wishlist).

 

I've installed this on my test site, and added

   include(DIR_WS_BOXES . 'articles.php'); //ArticlesManager v1.57_6
   include(DIR_WS_BOXES . 'header_tags_seo.php'); //Header Tags SEO v3.2.5
   include(DIR_WS_BOXES . 'sitemonitor.php'); //Sitemonitor v2.8 

 

into the header.php file just below

    include(DIR_WS_BOXES . 'configuration.php');
   include(DIR_WS_BOXES . 'catalog.php');
   include(DIR_WS_BOXES . 'modules.php');
   include(DIR_WS_BOXES . 'customers.php');
   include(DIR_WS_BOXES . 'taxes.php');
   include(DIR_WS_BOXES . 'localization.php');
   include(DIR_WS_BOXES . 'reports.php');
   include(DIR_WS_BOXES . 'tools.php');

 

Now, on my test site the header drop menu's appear as thus:

mindsparxheaderproblem0.jpg

 

Is there a way to make it when the header menu 'wraps' that the second line appears a bit lower? So that it appears more like this:

mindsparxheaderproblem0.jpg

 

Naloomi

 

go to admin>tools>mindsparx admin and increase the width of the template.

Share this post


Link to post
Share on other sites

It seems that index.php is missing from the language files. I'm seeing things like WELCOME_BACK instead of Welcome back and so on. Can you provide this for us? Thanks!

Share this post


Link to post
Share on other sites

Janne

 

A couple of things I picked up on last night - well firebug did :rolleyes:

 

 

In catalog/admin/includes/template_top.php

 


find:

<link rel="stylesheet" type="text/css" href="includes/stylesheet.css">

replace with:

<!--<link rel="stylesheet" type="text/css" href="includes/stylesheet.css">-->

 

that is: comment the line out, this is because stylesheet.css no longer exists with this contribution in place, so should not be called

 

 

In catalog/admin/includes/header.php

 


find:

	<td>
		<img src="./mindsparx_admin/misc/qmenu/images/qNav3.gif" width="150" alt=""></td>
</tr>
<tr>
	<td height="3"><img src="images/qNav3.gif" width="150" height="3"></td>
</tr>

replace with:

	<td>
		<img src="./mindsparx_admin/misc/qmenu/images/qNav3.gif" width="150" alt=""></td>
</tr>
<tr>
	<td height="3"><img src="./mindsparx_admin/misc/qmenu/images/qNav3.gif" width="150" height="3"></td>
</tr>

 

qNav3.gif is in ./mindsparx_admin/misc/qmenu/images/ - not images/

 

still working well though ;)

Share this post


Link to post
Share on other sites

Janne

 

A couple of things I picked up on last night - well firebug did :rolleyes:

 

 

In catalog/admin/includes/template_top.php

 


find:

<link rel="stylesheet" type="text/css" href="includes/stylesheet.css">

replace with:

<!--<link rel="stylesheet" type="text/css" href="includes/stylesheet.css">-->

 

that is: comment the line out, this is because stylesheet.css no longer exists with this contribution in place, so should not be called

 

 

In catalog/admin/includes/header.php

 


find:

	<td>
		<img src="./mindsparx_admin/misc/qmenu/images/qNav3.gif" width="150" alt=""></td>
</tr>
<tr>
	<td height="3"><img src="images/qNav3.gif" width="150" height="3"></td>
</tr>

replace with:

	<td>
		<img src="./mindsparx_admin/misc/qmenu/images/qNav3.gif" width="150" alt=""></td>
</tr>
<tr>
	<td height="3"><img src="./mindsparx_admin/misc/qmenu/images/qNav3.gif" width="150" height="3"></td>
</tr>

 

qNav3.gif is in ./mindsparx_admin/misc/qmenu/images/ - not images/

 

still working well though ;)

 

Thanks, we need to remeber this for the next update B)

 

/Janne

Share this post


Link to post
Share on other sites

I too am having trouble getting the admin to work. Starting with a clean install, I copied all the files into the admin section, uploaded them, installed the SQL, and voila! It broke.

 

When I enter the admin I get:

1146 - Table 'hailwood_oscom.TABLE_MINDSPARX' doesn't exist

 

select * from TABLE_MINDSPARX where id=1

 

[TEP STOP]

 

phpadmin reports:

 

Showing rows 0 - 0 (1 total, Query took 0.0010 sec)

SELECT *

FROM `mindsparx_admin`

LIMIT 0 , 30

 

Looks like the table prefix is not right, perhaps.

 

Any clues?

Share this post


Link to post
Share on other sites

I too am having trouble getting the admin to work. Starting with a clean install, I copied all the files into the admin section, uploaded them, installed the SQL, and voila! It broke.

 

When I enter the admin I get:

1146 - Table 'hailwood_oscom.TABLE_MINDSPARX' doesn't exist

 

select * from TABLE_MINDSPARX where id=1

 

[TEP STOP]

 

phpadmin reports:

 

Showing rows 0 - 0 (1 total, Query took 0.0010 sec)

SELECT *

FROM `mindsparx_admin`

LIMIT 0 , 30

 

Looks like the table prefix is not right, perhaps.

 

Any clues?

Share this post


Link to post
Share on other sites

Ok, it's very late and I'm tired. I had assumed that with a fresh install I need only copy all the files across and bingo it's done. Noooo. The files to be edited are not supplied in the contrib, they need to be edited and uploaded. I'll leave this in place in case some other dummy does the same thing.

Share this post


Link to post
Share on other sites

Quick Question...I had sitemonitor up and working prior to the mindsparx admin install.

 

After the install my sitemonitor disappeared...so I checked my column_left and sure enough it was not there

 

Now after adding it back into the column left it still will not show up. What am I doing wrong?

 

I have completely re-installed the add-on and nada

Edited by wildvettes

Share this post


Link to post
Share on other sites

I am unable to get into my admin. I installed this update and everything worked fine until I logged out. All I get now is the log on screen. When I clear my cache and history I get the .htaccess password pop up enter my info and nothing happens.

 

Thanks

Share this post


Link to post
Share on other sites

Never mind on the above post, I turned my computer off, took a nap came back and now it works it's FRICKIN MAgIC! LOLOL..

Edited by BarnstormingRC

Share this post


Link to post
Share on other sites

I am not sure if this is a minsparx admin issue or something else.

 

[Tue Apr 12 18:10:49 2011] [error] [client 96.8.xxx.xxx] File does not exist: /home/rcshop/public_html/adminBRC/mindsparx_admin/template/images, referer: http://barnstormingrc.com/adminBRC/mindsparx_admin/template/sparx/stylesheet.css

[Tue Apr 12 18:10:49 2011] [error] [client 96.8.xxx.xxx] File does not exist: /home/rcshop/public_html/adminBRC/mindsparx_admin/template/images, referer: http://barnstormingrc.com/adminBRC/mindsparx_admin/template/sparx/stylesheet.css

Share this post


Link to post
Share on other sites

Dude this is rocking...minor issue with body column witdhs on the index page, but when I replaced the adm_pic.jpg with one of my own it got all magically corrected and all. Kind of awesome.

 

Easiest install, cudos to you.

 

One other minor issue...on the Index page when the CONFIGURATION menus drop down (Google Chrome) the TOTAL REVENUE graphs obscure part of the drop down menu. Not a real big issue...just thought I should let you know.

Edited by pjmckee

Share this post


Link to post
Share on other sites

Just wanted to send a quick note to thank you for this great & fun contribution. I was able to add it all with no problems at all and even now have a picture of my granddaughter in my admin. My hats off to you !!! :thumbsup:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now