There are no brand fields in WooCommerce core by default. This answer comes from a post 2 years ago, given by an engineer from Automattic. I double-checked the validity of this answer again today. Yes correct use vendor_id or another field which is valid. Let me share mine which was worked for me. i place … Read more
So getEntityRecords( ‘taxonomy’, ‘genre’ ) will make a request to the “list terms” endpoint at /wp/v2/genre (or /wp/v2/<rest_base> if your taxonomy uses a custom rest_base) in the REST API, and because the “list terms” endpoint for custom taxonomies by default use the same parameters used by /wp/v2/categories (the “list terms” endpoint for the built-in category … Read more
TL;DR – ACF now has support for the WP REST API Hey all, Iain the Product Manager for Advanced Custom Fields here 👋 As part of the ACF 5.11 release we added native support for ACF fields in the WordPress REST API. Read more about that here.
You don’t need to include query parameters in the endpoint. Just the path: register_rest_route( ‘myplugin/v1’, ‘/posts’, array( ‘methods’ => ‘GET’, ‘callback’ => ‘my_rest_function’, ‘permission_callback’ => ‘__return_true’, ‘args’ => array( ‘number’ => array( ‘validate_callback’ => function( $param, $request, $key ) { return is_numeric( $param ); } ), ‘offset’ => array( ‘validate_callback’ => function( $param, $request, $key … Read more
REST or anything RESTful is a generally adhered to standard of getting things done via API. It also has the capability of documenting itself. Now I had expected to write an answer here about how it’s not a great idea to allow endpoints to update or modify any of your codebase but I see it … Read more
If you look at the documentation, first_name is not in the list of accepted values for the fields parameter, and if you enabled debugging, you’d see adding first_name to that parameter would actually cause a database error — Unknown column ‘wp_users.first_name’ in ‘field list’. And the same goes to the “firstname” and any other non-standard … Read more
For posts (Posts, Pages and custom post types), the very first parameter for register_meta() is always post and to set a custom post type, use the object_subtype argument in the third parameter like so: $meta_args = array( ‘object_subtype’ => ‘splash_location’, // the post type ‘type’ => ‘string’, ‘description’ => ‘A meta key associated with a … Read more
If you use the _fields argument, then it needs to include id. Otherwise, getEntityRecords() will always return a null, even if the REST API request succeeded. So to fix the issue in question, you just need to add id to your args, i.e. _fields: ‘id,name,slug’. You should also know that per_page is limited to 100, … Read more
The routes in question have two or three default endpoints: /wp/v2/users — it has two endpoints, one GET and one POST, i.e. “List Users” (GET /wp/v2/users), and “Create a User” (POST /wp/v2/users). /wp/v2/users/<id> — it has three endpoints, one GET, one POST and one DELETE, i.e. “Retrieve a User” (GET /wp/v2/users/<id>), “Update a User” (POST … Read more
First you should save the data somewhere in your wordpress. I personally like to use custom tables. Then use a schedule (cron job) to check if there is new data. Then try to submit the data. If you sumitted the data successfully delete it or mark your local data as successfully submitted. Else retry it … Read more