I think it really all depends on what the issue with limiting this information is. Do you not want this particular data to be exposed? Do you not want to iterate through so much data? Are you intending on passing this data through a $.getJSON() request? Are you passing this data to a PHP function … Read more
To anyone who might still be hitting this problem, here’s a checklist: Make sure you are authenticated AND your user has the list_users capability. Example: When adding a custom role, I make sure to add the list_users capability. The user should also be logged in (what authenticated means) when making the request. By default, only … Read more
I will give you a small answer to your update, doing this with the WP API. The API have the possibilities to use the WP_Query like also in core, but about the get parameters in the url. A URL to pull content from Post Status would look like this: http://example.com/wp-json/posts To pull content with WP_Query … Read more
It did appear that the json wasn’t being cached by wp-super-cache, but we decided to take a different approach. By using the transient api, we were able to do a faux-cache on all json, and drastically reduce the taxing of the database. Then on the ajax side of things, we are caching the html that … Read more
Just add the next parmater into the function register_post_type, it can be before ‘menu_position’parameter. ‘show_in_rest’ => true if you’re using a plugin to register your posttype you can use the next code: add_action( ‘init’, ‘add_anuncios_to_json_api’, 30 ); function add_anuncios_to_json_api(){ global $wp_post_types; $wp_post_types[‘anuncio’]->show_in_rest = true; } after that, you’ll be able to list your posts from … Read more
There is a navigation menu plugin extension for the REST API v2: https://wordpress.org/plugins/wp-api-menus/
You can get it without plugins by adding _embedas param to your query /?rest_route=/wp/v2/posts&_embed /wp-json/wp/v2/posts?_embed