This isn’t valid: add_action(‘rest_api_init’, $b2_items_rest_route->b2_register_route); By all rights this should generate either a warning or a fatal error add_action takes a PHP callable as a second parameter, e.g.: ‘function_name’ function( $im_a_closure_yay) {} array( ‘class_name’, ‘static_method’ ) array( $object, ‘method’ )
Woocommerce rest API is an extension of WordPress rest API, so you should first check global parameters and specifically “_fields” in the REST API Handbook of WordPress.org. I will give you an example of the data that you want, price and quantity, but also the id and the name of the products for the response … Read more
WordPress does not count views or traffic, it’s not a part of WordPress’ feature set. Plugins and code snippets can add this but it’s highly specific to the service you’re using. Usually for apps you will need to integrate tracking into the app itself. But how you would do that is specific to the service … Read more
The error in question — “Invalid parameter(s): tags” and “tags[0] is not of type integer.“, means that you need to supply a list of tag IDs and not names or slugs. So for examples, ‘tags’ => 123 and ‘tags’ => [ 123 ] are both valid. (Comma-separated list is also accepted, e.g. ‘tags’ => ‘123,4,5’.) … Read more
I’m getting a Promise with the post object inside when I do a console.log( mypost ) Yes, because apiFetch() indeed returns a Promise object, and apiFetch() doesn’t assign the response received from the server to the mypost constant, and the return value of your then() callback is also not going to be assigned to the … Read more
As I said in the comments, since it’s a custom endpoint, you could just cancel the post creation via the main callback, i.e. something like so: ‘callback’ => function () { if ( some condition ) { // create the post } else { // return existing post or something else } } And here’s … Read more
The REST API does not support basic authentication out of the box, you need a plugin. The documentation points to this one, accompanied by this warning: Note that this plugin requires sending your username and password with every request, and should only be used for development and testing i.e. not in a production environment.
I was having the same issue with Woocommerce Oauth 1.0 authentication and this solution worked for me. I’m running it on localhost, so far so good. Edit: Let me elaborate this answer a bit more. I just started learning React last night and the best way to learn is by doing. I’ll explain as a … Read more
WordPress (version 5.0) doesn’t use namespaces for it’s classes, so try to use the global one: \WP_REST_Server to avoid assuming it’s in your custom namespace. One of the reason for this is that WordPress supports PHP 5.2.4+ that doesn’t support namespaces. The minimum is PHP 5.3.3+, if I remember correctly, to support it. Later this … Read more
I’m answering myself for the benefit of others. I was passing an array of post type slugs to apiFetch instead of passing an array with their rest_base parameter. So, the correct function should be: const postTypes = useSelect( ( select ) => { const { getPostTypes } = select( ‘core’ ); const excludedPostTypes = [ … Read more