markh76 Posted January 26, 2017 Share Posted January 26, 2017 Hi All, trying to find a solution to a shipment tracking number getting sent from shipworks to prestashop. Seems that in table order_carrier gets updated incorrectly and is updating based on id_order_carrier instead of Id_order. For example through shipworks, we shipped order # 476 however in the order carrier table, the record id_order_carrier =476 got updated and added the tracking info and set the status of shipped(with tracking #) to order #: 472 (id_order field). Shipworks3.php sent in 476 and tracking number but the key field is not being selected correctly I think.. Anyone have any ideas? Shipwork3.php is attached as well as a screen shot of table data. Tracking #: 785417592640 should have gone to the top row with id_order 476 but instead went to the row with id_order_carrier=476 and updated wrong order. This happens consistently if the id_order_carrier and id_order field are different Thanks, Mark shipworks3.php Link to comment Share on other sites More sharing options...
JeredBolton Posted January 27, 2017 Share Posted January 27, 2017 The fact that the shipping/tracking number is being updated suggests that the Shipworks software is doing an update wrt to id_order_carrier rather than id_order. Have you contacted the supplier of the code and raised the issue with them? Link to comment Share on other sites More sharing options...
markh76 Posted February 6, 2017 Author Share Posted February 6, 2017 The fact that the shipping/tracking number is being updated suggests that the Shipworks software is doing an update wrt to id_order_carrier rather than id_order. Have you contacted the supplier of the code and raised the issue with them? Shipworks appears to be calling part of the api and I think internally, in PS code, it is using the wrong field for the update. Shipworks3.php is attached above but I'm not a php guy and clueless. I did speak with interapptive (Shipworks) and they feel it is a prestashop bug. Mark Link to comment Share on other sites More sharing options...
JeredBolton Posted February 7, 2017 Share Posted February 7, 2017 In this case it's not a PrestaShop bug. I've sent you a PM. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now