Firstly, your problem with the last post type and/or term overwriting all previous is because ‘filter’ is a 2-dimensional array. Therefore ‘taxonomy’ (the key in this case) can only have one value. If that seems odd, read this super helpful page on the plugin’s github that helped me a lot (read this) tldr; term lists … Read more
Try this instead for pagination. It returns all the posts on my site. http://example.com/wp-json/wp/v2/posts/?filter[category_name]=country&filter[posts_per_page]=-1
Use the file that wordpress generate at “export”. It should contain the basic info you are talking about (although not the user’s passwords if you are expecting to get it as well). It is just an xml file which you can parse, you can even look at the code of the wordpress importer for guidance.
I think you should stop using rewrite endpoints to handle JSON responses. Instead you can and you should use the REST API. So, instead of this: function makeplugins_add_json_endpoint() { add_rewrite_endpoint( ‘json’, EP_PERMALINK | EP_PAGES ); } add_action( ‘init’, ‘makeplugins_add_json_endpoint’ ); And then handle the JSON response at your own, you can and you should do … Read more
Unfortunately I don’t know Angular to give you a hand with that, but I’m seeing this question is related to another about consuming an endpoint with a filter by meta_key (by the way, I’ve updated my previous response with a very simple jQuery-only code to show posts retrieved in a list). However, if you don’t … Read more
Let’s assume your plugin is writing to the /usr/share/wordpress/sitemap_index.xml filesystem location, but you want it can be accessed through http://www.website.com/sitemap_index.xml as if the xml file were stored in /var/www/html/sitemap_index.xml. You can use the alias directive then, available in mainstream webservers Apache and NginX: For an alias in NginX, you put this inside the server of … Read more
You should use custom permalink in your wordpress, please update permalink option. Any way you can use this url ?rest_route=/wp/v2/posts
The correct solution is to add the redirect to index.php in your theme – this will ensure only frontend, non-api based requests are handled. Sniffing wp-json in the request is dodgy at best, and will all out break if another plugin overrides the endpoint (which you can do, it’s pluggable). <?php wp_redirect( ‘http://example.com/’, 301 ); … Read more
This answer has what you want https://wordpress.stackexchange.com/a/314152/49962 WP already does this out of the box thanks to the include_children parameter of tax_query which is true by default. So you do not need to tell it the sub-terms, just do something like this: /wp/v2/posts?categories=1 Where categories=1 is the parent category ID
Those technologies are totally independent of each other. The rest API can not be used as it is (in this context I mean the end points) for push notifications as there is a protocol for that and probably all kinds of restrictions browsers place. On the other end, nothing was preventing you from implementing those … Read more