Out of the box there is no mechanism for a user to login via the REST API to begin a session without pre-configured access. WordPress Core provides 2 authentication methods for the REST API: cookies + nonces application passwords Likewise there is no mechanism for registering for an account via the REST API, user creation … Read more
You should use cookie based authentication instead of basic auth. Delete the basic auth/application password authentication code. Follow the cookie authentication example that creates a post via the REST API from the REST API handbook: https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/#cookie-authentication Create a valid nonce for use in your AJAX requests in PHP wp_create_nonce( ‘wp_rest’ ) as the docs tell … Read more
Looking at the code for the users endpoint, I don’t think this is possible. I also dug up this ticket on the issue which links to this ticket that confirms that this is a deliberate limitation. The explanation is that WordPress does not give the option to delete users without either deleting their content or … Read more
I want to add a POST request functionality, that allows me to introduce new data rows to the wpso_messages table through the rest api. Any advise how to accomplish that? Yes, and note that I wrote this based on the official REST API handbook and the core endpoints. So from the “Routes and Endpoints → … Read more
This is because you are sending unauthenticated anonymous requests, but still specifying an author. If what you were trying to do worked then it would be possible to impersonate any person on your site in a comment by specifying their author ID when creating the request. With this in mind, the error message is quite … Read more
You can internally route REST API requests using rest_do_request and a WP_REST_Request object. $request = new WP_REST_Request( ‘GET’, ‘/fb_connect’ ); $request->set_param( ‘x’, true ); // You can also use it this way: $request[‘y’] = true; $request[‘z’] = true; $response = rest_do_request( $request );
You can use the WP_REST_Server::get_namespaces() method. For instance. $exists = in_array( ‘ns/v1’, rest_get_server()->get_namespaces() );
I had to do this yesterday, here’s how I did it. Like you have already done register_meta to appear in the api. register_meta(‘user’, ‘meta_key’, array( “type” => “string”, “show_in_rest” => true, “single” => true, )); Then you will need to make a POST or PUT request to the users endpoint with the meta values in … Read more
Looks to me like WordPress doesn’t enable UTF-8 mode when it runs the regex. https://github.com/WordPress/WordPress/blob/5.2.1/wp-includes/rest-api/class-wp-rest-server.php#L837 In PHP, matching multibyte characters requires the u flag. (The code above just adds the case-insensitive flag). So although some strings will still match (like “Département”), they’re not matching as whole Unicode characters. For example the following pattern matches when … Read more
The Posts endpoint accepts a slug parameter when querying for posts, so if you can get the slug from the URL, then you can make request to /wp-json/wp/v2/posts?slug=<slug>. So if the URL is http://example.com/hello-world/ and you know the slug is hello-world, then for example in JavaScript, you can do something like: fetch( ‘http://example.com/wp-json/wp/v2/posts?slug=hello-world’ ) .then( … Read more