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
WP Extended Search does not work with REST by default since version 2.0.2 This is to achieve maximum compatibility with WordPress and other plugin/themes. To enable the support, pass wpessid in REST request with ID (for specific search setting) or without ID (for global search setting). e.g. /wp-json/wp/v2/posts?search=technology&wpessid or /wp-json/wp/v2/posts?search=technology&wpessid=10 Ref: https://wordpress.org/support/topic/search-queries-with-metakey-name-issue-version-2-0-2/#post-14376988 PS:- I am … Read more
This is because PUT requests don’t have body parameters, that’s not how PUT works. PUT doesn’t quite do what you thought it did, and can only be used to upload a file from a client. Your endpoint is incompatible with PUT as a request type because you’re providing parameters as key value pairs, and that … Read more
One approach is to cast the objects as arrays. I recently had to do this in a project where I retrieved a list of articles and needed to display the featured image. There may be alternate ways to handle this issue, but I’ve found it to be reliable. Here is some relevant code from the … Read more
You are right, APIs should not expose internal data and structures, but if you depend on APIs not written by you, it will rarely be a good use of your time to develop a different API just feel better about this. And even if you develop your own API it is going to be hard … Read more
Add to your __construct function: add_action( ‘rest_api_init’,[$this, ‘register_routes’] ); And the rest api will take it from there. No need to process routes in your activation functions, and no need to flush the rules. The $wp_rest_server is constructed after the plugins are loaded. Hence it is null when you instantiate your class in the plugin.
Herewith find the below answer for my own question for the custom taxonomies based listing the categories add_action( ‘init’, ‘rest_custom_category_request’, 25); function rest_property_type_category_request(){ global $wp_taxonomies; $wp_taxonomies[‘custom_category’]->show_in_rest = true; $wp_taxonomies[‘custom_category’]->rest_base=”custom_category”; $wp_taxonomies[‘custom_category’]->rest_controller_class=”WP_REST_Terms_Controller”; } Answer for the filter with custom meta key & values add_filter(‘rest_query_vars’, ‘custom_rest_query_vars’); function custom_rest_query_vars($query_vars) { //print_r($query_vars);exit; $query_vars = array_merge( $query_vars, array(‘meta_key’, ‘meta_value’, ‘meta_compare’) ); … Read more
You need to use the slug argument: /wp-json/wp/v2/pages?slug=happy-days
After a whole day of digging and debugging through the super duper WordPress core functions, I realized the primary issue was that the session token used to create versus to verify the nonces were not equivalent. I tried different things, ending up calling the wp_set_auth_cookie method specifying the ‘logged_in’ cookie target. Then, I fell on … Read more
First of all we need to find the posts related to our taxonomy term. Then we will delete them one by one by running a foreach loop. Try below code. I hope that will work for you- add_action(‘pre_delete_term’, ‘the_dramatist_delete_posts_on_taxonomy_delete’, 1, 1 ); function the_dramatist_delete_posts_on_taxonomy_delete( $term ) { $args = array( ‘post_type’ => ‘post’, // post_type … Read more