Jump to content

phoenix90

Members
  • Content count

    17
  • Joined

  • Last visited

Profile Information

  • Real Name
    Shaun
  • Gender
    Male
  1. phoenix90

    [CONTRIBUTION] PDF Customer Invoice

    THUMBS UP! Thanks so much for your help, worked perfectly:)
  2. phoenix90

    Easy populate + Different Supplier prices

    I thought about the same method, but the problem will be, what if I have 40 suppliers?
  3. Hey guys, i hope someone can help me with this problem, I need to get the easy populate to export 1 more table, diff from products and products_description, the table I want to export and be able to import again is suppliers_products_groups , how will I go about doing this?? the fields are suppliers_group_id, suppliers_price, suppliers_ve, suppliers_min_order, suppliers_model, suppliers_url, suppliers_comment, products_price .. Thanks in advance :)
  4. phoenix90

    [CONTRIBUTION] PDF Customer Invoice

    Hey guysm great contrib.. But I have a strange problem when the invoice is pulled. It shows for example Sub-Total: R4,900.00 Speed Services Couriers (Overnight Delivery to <b>Post office Counter</b> R70.00 Total: <strong> R4970.00</strong> Instead of: Sub-Total: R4,900.00 Speed Services Couriers (Overnight Delivery to Post office Counter R70.00 Total: R4970.00 I have changed the following: $pdf->Text(130,113, tep_html_entity_decode(ENTRY_PAYMENT_METHOD) . ' ' . tep_html_entity_decode($temp)); TO $pdf->Text(130,113, tep_html_entity_decode(ENTRY_PAYMENT_METHOD) . ' ' . tep_html_entity_decode(strip_tags($temp))); But no luck.. please help
  5. Nevermind, i fixed the problem, if anyone has a simmilar problem, here's the fix. find <td width="100%" valign="top"><table border="0" width="100%" cellspacing="0" cellpadding="2"> <tr> <td width="100%"><table border="0" width="100%" cellspacing="0" cellpadding="0"> <tr> <td class="pageHeading"><?php echo HEADING_TITLE; ?></td> <td class="specialPrice" align="right">NOTICE: <a href="<?php echo tep_href_link( DIR_WS_LANGUAGES.$language.'/'.FILENAME_DISCOUNT_COUPONS_MANUAL ).'">'.HEADING_TITLE_VIEW_MANUAL; ?></a></td> replace with <table> <td width="100%" valign="top"><table border="0" width="100%" cellspacing="0" cellpadding="2"> <tr> <td width="100%"><table border="0" width="100%" cellspacing="0" cellpadding="0"> <tr> <td class="pageHeading"><?php echo HEADING_TITLE; ?></td> <td class="specialPrice" align="right">NOTICE: <a href="<?php echo tep_href_link( DIR_WS_LANGUAGES.$language.'/'.FILENAME_DISCOUNT_COUPONS_MANUAL ).'">'.HEADING_TITLE_VIEW_MANUAL; ?></a></td>
  6. 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.
  7. Mabe he didn't update the tables php file?
  8. 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.
  9. phoenix90

    alot of errors..

    . please close.
  10. I have a vry strage problem, everything installed fine and working, but the problem that annoys me is that the coupons.php page and other from this contribution is showing outside the borders, this is 2.6 on osc 2.3.1 running sparx's admin.. below is a scrrenshot
×