Jump to content
Latest News: (loading..)

lucsangel

Members
  • Content count

    47
  • Joined

  • Last visited

  • Days Won

    1

lucsangel last won the day on September 24

lucsangel had the most liked content!

1 Follower

Profile Information

  • Real Name
    bobbee

Recent Profile Visitors

2,220 profile views
  1. lucsangel

    AJAX Attribute Manager support

    Rziner I do not have the error anymore. The image of the error was in one of my previous posts. For now all is well after setting that call to false.
  2. lucsangel

    AJAX Attribute Manager support

    Oh yes, in the zipped files the change to false is not shown as I zipped it before thinking of the QTPro stock deletion. Sorry for all the trouble. Bobbee
  3. lucsangel

    AJAX Attribute Manager support

    You made me think of something.... in attributeManagerConfig.class.php I had AM_DELETE_ZERO_STOCK in the QTPro section set to true (as I had AM_USE_QT_PRO obviously set to true as I use it), now set it to false : $this->add('AM_DELETE_ZERO_STOCK', false); // if true, deletes options combinations with zero quantity from stock and now the error is gone (with of course the changes you suggested line by line above). Just in case her are my zipped files Thank you Rainer attributeManager.zip
  4. lucsangel

    AJAX Attribute Manager support

    Hello Rainer, It is switched off, never switched it on so why would the part of code in the function mentioned above throw the error? Bobbee
  5. lucsangel

    AJAX Attribute Manager support

    Found that commenting out the code lines 415-430 for Product Attribute Code it goes away and all functions. I do not use Product Attribute Code so I do not know if commenting it out is correct or not but the error does go away. Wonder if I should comment it out elsewhere ? Also picked up 3 missing semi-colons : line 402 : <?php echo AM_AJAX_IMAGE?> line 436: <?php echo AM_AJAX_WEIGHT_PREFIX?> line 439: <?php echo AM_AJAX_WEIGHT?> Don't know if they affect anything... Thank you again for your help ! Bobbee
  6. lucsangel

    Additional Orders Info

    Thank you Jack. It is a great addon.
  7. lucsangel

    AJAX Attribute Manager support

    Thank you Rainer.
  8. lucsangel

    AJAX Attribute Manager support

    This time I have Warning/homepages/11/d570016152/htdocs/osc234/cav2mt/attributeManager/attributeManager.php417 Still with Quantity Tracking Professional (QT Pro) underneath the color option as in the screenshot, so somehow it must have a problem with the QTPro
  9. lucsangel

    AJAX Attribute Manager support

    Now it says : Parse error: syntax error, unexpected '$rec' (T_VARIABLE) in /xxx/attributeManager/attributeManager.php on line 536 line 536 with the quotes <?php echo $rec['products_stock_id']; ?>
  10. lucsangel

    AJAX Attribute Manager support

    Hello Rainer, Just uploaded the new version and have a little error that seems to come with QTPro and Attribute Manager but I can not figure out what it is referring to (screenshot included : Warning /xxxxx/xxxx/attributeManager/attributeManager.php 526 line 526 : $val_array=explode(",",$rec[products_stock_attributes]); On FROZEN CE BS3, PHP 7.2 QTPro was functioning fine and is set to true in attribute manager. There is stock for the product attributes. What do you think? Bobbee
  11. lucsangel

    Additional Orders Info

    addons are throwing these types of errors. (sorry my hand slipped and posted without finishing). It happens on PHP 7.2, not in the earlier versions
  12. lucsangel

    Additional Orders Info

    Hello Jack I am using the latest version you uploades v.1.5 https://apps.oscommerce.com/8oFiX&additional-orders-info with FROZEN BS3 and see no control in configuration Additionnal Info for this in particular. So many of the
  13. lucsangel

    Additional Orders Info

    Hi Jack, I see that there has been no activity in a while but just to update for those who are still using this useful add-on... passing to php 7.2 on the admin side, when you click "invoice" for an order the undefined constant error comes up for SHOW_INVOICE_SHIPPING. To fix it I just put it in single quotes 'SHOW_INVOICE_SHIPPING', so in admin/includes/functions/general.php : CHANGE *************************************************** //// /*** BOF: Additional Orders Info ***/ // Return orders shipping method function tep_get_orders_shipping_method($order_id) { $check_order_query= tep_db_query("select title from " . TABLE_ORDERS_TOTAL . " where orders_id='" . $order_id . "' and class='ot_shipping'"); $check_order= tep_db_fetch_array($check_order_query); if (SHOW_INVOICE_SHIPPING=='2' and ($check_order['title']=='United Parcel Service' or $check_order['title']=='United States Postal Service')) { // return short version on UPS and USPS *************************************** TO ************************************** //// /*** BOF: Additional Orders Info ***/ // Return orders shipping method function tep_get_orders_shipping_method($order_id) { $check_order_query= tep_db_query("select title from " . TABLE_ORDERS_TOTAL . " where orders_id='" . $order_id . "' and class='ot_shipping'"); $check_order= tep_db_fetch_array($check_order_query); if ('SHOW_INVOICE_SHIPPING'=='2' and ($check_order['title']=='United Parcel Service' or $check_order['title']=='United States Postal Service')) { // return short version on UPS and USPS ******************************************************* Works for me but you are the programmer so you can check to see if it is the right fix. Bobbee
  14. lucsangel

    PayPal App for osCommerce Online Merchant

    Hi! To correct it you simply need quotes around the offending constant in the original line where (int)OSCOM_APP_PAYPAL_TRANSACTIONS_ORDER_STATUS_ID is, like this line 37: $ppstatus_query = tep_db_query("select comments from " . TABLE_ORDERS_STATUS_HISTORY . " where orders_id = '" . (int)$oID . "' and orders_status_id = '" . (int)'OSCOM_APP_PAYPAL_TRANSACTIONS_ORDER_STATUS_ID' . "' and comments like 'Transaction ID:%' order by date_added desc limit 1"); Note the 'OSCOM_APP_PAYPAL_TRANSACTIONS_ORDER_STATUS_ID' quotes. That way the module will still work and you won't have to think about anymore - it is functional should you one day want Paypal but forgot what you did to make the warning disappear. Hope this helps. Bobbee
  15. lucsangel

    QTPro BS

    Thank you Rainer, that did do the trick ! Have a good day. Bobbee
×