-
Notifications
You must be signed in to change notification settings - Fork 12
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
REST POST with “custom_meta” does not change the field values. #13
Comments
Do non-protected custom meta fields get updated? Is is just the protected fields that don't update or are none of the custom fields working on the V3 API? |
No! No custom_field gets updated, I am afraid! (tried with "pageview", wc "on_sale", shipping_required, ) While title and I guess core Post(<-db) fields do get updated. Endpoint: I am especially after the fields: unprotecting is done rude in: |
Thank you. That detail helps me narrow down what I am looking for. |
Hi again, got a step closer! Your plugin-works fine including updateing "_" protected fields, if I deactivate all other plugins. I'll now figure out which plugin breaks the request, step by step! |
Use the new v2 REST API (WC 3.x) instead of this plugin. It now does everything this plugin does out of the box. The README gives some examples of how you would manage the metadata fields. |
`Hi Jason,
Thank you for your wc-api-custom-meta plugin on https://github.com/judgej/wc-api-custom-meta.
I have been trying to use it with woocommerce REST api v3 , but also want to update protected meta fields (the ones starting with “_”) after unprotecting them.
But it seems that REST POST with “custom_meta” does not work changing the fields.
I have also tried the approach http://torquemag.io/2015/07/working-with-post-meta-data-using-the-wordpress-rest-api/
But my skills set doesn’t seem to be sufficient to adapt to woocommerce api v3.
Would you know what I could still be doing wrong ?
Thanks for any help ! And have a great day!
IL
Ps: my JSON on the POST looks somewhat like this:
The text was updated successfully, but these errors were encountered: