Jump to content

augustas

Members
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • First Name
    Aug
  • Last Name
    Kli

augustas's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I decided to use the following API URL request: /api/orders?display=full&filter[date_add]=>[YYYY-MM-DD]&date=1 replace YYYY-MM-DD with a valid date. This returns detailed information about all the orders created from YYYY-MM-DD. In the details of each order I can see the "order_state", which helps to decide what to do with the order next in the API application.
  2. Ecom.Agora - I was not using "order_state" till now, but after starting to analyse this filter, the problem is that it does not return all the orders with state=4 at the moment. It returns all history recordings when orders had state=4 in the past, but now they might have changed the status. Anyone got a solution for Prestashop 1.6.0.11 an later - how to filter orders only with specific STATE at the moment?
  3. Hello, I will create a Product Feature called "Shipping Time" and will display it on the Product page. Product will also have several Combinations where Size can be selected from the drop-down box. Question: how could I make the drop-down selection to change the value of "Shipping time" shown on the Product Page. For example: if size L is selected - the "Shipping Time" text should say "5 days" if size XXL is selected - the "Shipping Time" should show "10 days" Any advice how to achieve that? Is that possible? Thank you
  4. Thank you! That's useful. Indeed filter /order_histories/?filter[id_order_state]=4 works.
  5. Hello Luchtdichtshop, How did you "reinstall" the webservice? Was it on the "Sendcloud", or did you Disabled-then-Enabled webservice inside your Prestashop's "Advanced Parameters"? Are you using "current_state" filters? Do they work after "reinstallation" of webservice? Thank you.
  6. There are 2 things I can share, which might help you to solve the problems. At least, they helped me: There is a bug in the Order Class which brakes the WebService, and it is documented here: PSCSX-4403 and PSCSX-4423 The fix is described here. Orders cannot be filtered using "current_state" filter anymore. (The system returns error that this filter is dynamic (?) and cannot be used) So, if you were using it in the calls to API, then you have to redo/reprogramm your codes. You can pull out all the orders and do status check of each of them one-by-one. I hope this helps.
  7. I am also running into similar API problems after the upgrade to 1.6.0.11 Any advice, or information would be highly appreciated. Thank you
×
×
  • Create New...