The REST API can be used for straight-up retrieval on any blog that has enabled it. Self-hosteds require an active choice to turn the JSON interface on in Jetpack but once it’s up it’s wide open. This is not necessarily appreciated by everyone, and that’s somewhat understandable. I picked a blog ID at random here … Read more
If possible, only the examples shown in internet is: function qod_remove_extra_data($data, $post, $context) { // We only want to modify the ‘view’ context, for reading posts if ($context !== ‘view’ || is_wp_error($data)) { return $data; } // Here, we unset any data we do not want to see on the front end: unset($data[‘author’]); unset($data[‘status’]); // … Read more
The filter param was removed in WP4.7, you should be able to access tags via their ID. For example to get the tag with the ID of 7 you could use: http://YOUSIITE.DEV/wp-json/wp/v2/posts?tags=7 If you would like to add filters back in the WP-API team released their own Filter plugin, I’d recommend that you check that … Read more
Wordfence blocks the User endpoint from the public. In settings there is a checkbox you can unselect to make it visible in the WP Rest API again.
I made a shortcut to my image by adding it directly to the API response. //Add in functions.php, this hook is for my ‘regions’ post type add_action( ‘rest_api_init’, ‘create_api_posts_meta_field’ ); function create_api_posts_meta_field() { register_rest_field( ‘regions’, ‘group’, array( ‘get_callback’ => ‘get_post_meta_for_api’, ‘schema’ => null, ) ); } //Use the post ID to query the image and … Read more
I managed to solve this and access the JSON data using a foreach loop: $json = lusso_posts(); #var_dump( $json ); #die(); foreach( $json as $post ) { $titles = $post->title; $images = $post->featured_image->guid; ?> <div class=”lusso-posts”> <div class=”image-container”><img src=”https://wordpress.stackexchange.com/questions/210472/<?php echo $images; ?>” /> </div> <h4><?php echo $titles; ?></h4> </div> <?php }
Two things to look at: 1) register_meta() 2) custom-fields support on post type. 1) register_meta You can register your custom post meta with show_in_rest => true to make it accessible via the api. Bottom of this page: Modifying Responses, provides the following example: <?php // The object type. For custom post types, this is ‘post’; … Read more
There are two parts to the solution here. You need to use a JSON API custom controller In your custom controller, you’ll need to decide how to pass the meta_query data structure Depending on how robust you need this to be, you could use a variety of approaches. Here is the maximalist approach, that will … Read more
function checkApiAuth( $result ){ $yourEncryptAPIKey = $_GET[‘request’]; if( yourDecryptFn( $yourEncryptAPIKey ) === $realKey ): $result = true; else: $result = false; endif; return $result; } add_filter(‘rest_authentication_errors’, ‘checkApiAuth’);
From the documentation: According to the JetPack JSON API docs: By default, all metadata keys are allowed in the API, as long as they are not protected keys. Any metadata key that starts with _ is by default protected. Protected metadata keys can, however, be accessed and edited by users with the edit_post_meta (used for … Read more