I’m not a WP API expert. It sounds like you want to store more information than the API supports, so you will need to add an endpoint – https://developer.wordpress.org/rest-api/extending-the-rest-api/adding-custom-endpoints/ If you are doing payment processing, I assume you are using a service or plugin + service for that, so you may want your custom endpoints … Read more
I think you are looking for WP_REST_Response.
You should have a nonce provided by your WP instance, and of course, being authenticated previously (through cookies, set by the wp-login normal process, a JWT, or even Basic authentication). This is because some requests are not approved if they come without the nonce, in order to prevent abuse. So, you could pass to your … Read more
Use the _Embed at the end of your JSON call. It should look something like this: https://example.com/wp-json/wp/v2/posts?_embed. That will give you both the json objects and include a the featured image url that you’re looking for. 😉
The problem was with parsing wp:featuremedia:. I handle this with @SerializedName. Instead of creating class wp that contains featuremedia,named all to wp:featuredmedia public class EmbeddedDto implements Serializable{ @SerializedName(“wp:featuredmedia”) @Expose private List<MediaDto> featuremedia; } Now Json parses in right way.
I used your exact set of .htaccess directives to achive json gzip’ing. Took my files from 23k to 4k. So I would assume its one of the two following things: Your.htaccess is not allowed to use these directives so it ignores them. Thus you either need to do one of the following: a) edit the … Read more
For some reason, you have to double the arrays, maybe this doesn’t affect you as you are referencing the firt element. I use this in PHP: function saveMetaItem($id_order,$id_item,$id_product,$meta_key,$meta_value){ $woo = new wooclient(); $data = array( ‘line_items’ => array(array( ‘id’ => $id_item, ‘product_id’ => $id_product, ‘meta_data’ => array(array( ‘key’ => $meta_key, ‘value’ => $meta_value )) )) … Read more
The problem is with the bbe_sortables&replace in the permalink: <My URL>/wp-json/bridge/v1/test-data/process/bbe_sortables&replace&_wpnonce=<thenonce> which results in an invalid route, where the supposedly query string is seen as part of the route: /bridge/v1/test-data/process/bbe_sortables&replace&_wpnonce=<thenonce> (the valid route for that URL is /bridge/v1/test-data/process/bbe_sortables) and eventually the REST API throws the rest_no_route error. To fix the problem, use add_query_arg() when generating … Read more
I found out how to grab each result and add a link. For the ananda_video_audio post type: add_filter( ‘rest_prepare_ananda_video_audio’, function( $results ) { // These two lines are unique to our code of course $video = new Ananda_Video_Audio( $results->data[‘id’] ); $authors = $video->get_author_IDs(); foreach( $authors as $author_id ) { $results->add_link( ‘author’, rest_url( ‘/wp/v2/users/’ . $author_id … Read more
The filter is dynamic, i.e. generated from rest_{$post_type}_query. So for the post post type it’s rest_post_query and for the cpt post type it’s rest_cpt_query Note that REST pagination is available: https://example.com/wp-json/wp/v2/posts?per_page=100&page=1 https://example.com/wp-json/wp/v2/posts?per_page=100&page=2 … The maximum of per_page is to reduce the risk of fatal errors if available resources are exceeded when too many items are … Read more