Writing a custom endpoint is not hard at all. Your code goes to your theme’s functions.php file, or a plugin. After you register a REST route, you can access it via this URL: www.example.com/wp-json/myplugin/v1/foo Also I assume you are missing \ in your callback function’s parameters, as it should be \WP_REST_Request $request.
The true reason of not using nonces for non logged in users, is that it adds a pointless burden on their usage as they need to refresh the page when the nonce expire, and the only way they will know that they need to do it is when something do not work. There is probably … Read more
No it shouldn’t. The first parameter is called namespace. It’s like the scope for your functions such as this: function my_function(){ $data = 0; } You can only use $data inside that function. Same goes with the REST endpoints. The path /test/ will be available only under its specific namespace. You should choose a unique … Read more
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
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
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
Add orderby=include to your GET request. See the docs here: https://developer.wordpress.org/rest-api/reference/posts/#arguments