-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using query parameters with requests #112
Comments
Hello @julien-MD, Thanks for creating the issue and explaining your problem. We will be happy if we can include them. Can you share some examples that you are trying to do? |
Hi, Here is some more data about the request. I have a Controller which build the data array needed:
Here, the thing is my Then I have a Job which process the sending of the order to Woocommerce, it is called in the Controller like so: Here is the job:
You can see that I need to wait for the Woocommerce response in order to go on with the code. The issue is at this point, because the Woocommerce API default behavior is to send me back the whole order data. If the server is almost idling and the order not to big, it has time to build its response. Otherway, it timeouts (but the order is created on the Woocommerce side). In order to get around the issue I had to edit the Woocommerce API, forcing it to send me back only the data I need:
This method allows a I did not find a proper way to send this Let me know if you need more info. |
Hi,
I had an issue where orders created were too big for the Woocommerce server to be able to build a response, the query ending in a server timeout.
I asked Woocommerce if it was possible to request the REST API to not send back the whole order data, as I send it in the first place and do not need it. They replied that I could use the query parameters in order to achieve that (see here).
It appears that this library does not allow this possibility (or I didn't find out how it is possible to do it), so I had to edit files for myself.
Is it possible to add this feature in a future release?
Thanks
The text was updated successfully, but these errors were encountered: