inactive-user

Um die Ausgabe als JSON zu aktivieren, muss an eine beliebige WordPress-URL nur der GET Parameter “json” angehängt werden:
?json
/category/news/?json Posts innerhalb einer Kategorie auslesen. 
/hello-world/?json Einen einzelnen Post auslesen.
Es können optional zwei GET Parameter übergeben werden:
?json&count=3 Durch den Parameter “count” kann die Anzahl der Posts in der Rückgabe limitiert werden.
?json&category=news Möglicherweise ist ein Filtern nach Katagorie auch per GET Parameter gefragt.
Das JSON liefert allgemeine Informationen über den Blog:
<ul>
<li>blog_title </li>
<li>blog_desc </li>
<li>blog_url </li>
<li>blog_rss </li>
</ul>
…und Inhalte des Posts:
<ul>
<li>id </li>
<li>slug (Teil des Permalink ohne die Domain) </li>
<li>url (Permalink) </li>
<li>title </li>
<li>excerpt </li>
<li>author </li>
<li>date (wie in WordPress konfiguriert) </li>
<li>categories (Array aller Kategorien)</li>
</ul>
Das ist sehr nützlich, wenn beispielsweise auf einer anderen Webseite eine Vorschau auf einen oder mehrere Artikel des Blogs angezeigt werden soll.
=Beispiel JSON=
{ 
 “blog_title”: “”, 
 “blog_desc”: “”, 
 “blog_url”: “”, 
 “blog_rss”: “”, 
 “posts”: [{ 
 “id”: 1, 
 “slug”: “”, 
 “url”: “”, 
 “title”: “”, 
 “excerpt”: “”, 
 “author”: “”, 
 “date”: “”, 
 “categories”: [] 
 }] 
}

Simply JSON

Dieses Plugin gibt anstelle einer WordPress Seite ein JSON zurück. Sowohl Blog-Infos, als auch Posts werden ausgegeben.

Dave McHale

Tang Rufus

The most comprehensive plugin for controlling access to the WordPress REST API!
Works as a “set it and forget it” install. Just upload and activate, and the entire REST API will be inaccessible to your general site visitors.
But if you do need to grant access to some endpoints, you can do that too. Go to the Settings page and you can quickly whitelist individual endpoints (or entire branches of endpoints) in the REST API.
You can even do this on a per-user-role basis, so your unauthenticated users have one set of rules while WooCommerce customers have another while Subscribers and Editors and Admins all have their own. NOTE: Out of the box, all defined user roles will still be granted full access to the REST API until you choose to manage those settings.
For most versions of WordPress, this plugin will return an authentication error if a user is not allowed to access an endpoint. For legacy support, WordPress 4.4, 4.5, and 4.6 use the provided <code>rest_enabled</code> filter to disable the entire REST API.

Disable REST API

The plugin uses a is_user_logged_in() check to grant access to disabled REST API endpoints. I run a membership site for one year and just realized it now, that any logged in visitor STILL HAVE ACCESS to any disabled REST API endpoints.

This should be very explicit, and there should be a setting in the plugin settings page to set the minimum role for the user to have access to the disabled endpoints.

ANY logged-in visitor can view the disabled endpoints


Blocking the REST API entirely breaks plugins that require this functionality, so being able to selectively enable routes is perfect.



I recommend this plugin to everyone who uses Independent Analytics to secure their site while still enabling analytics to be recorded.


Excellent solution


The plugin does what it says on the tin, without being pretentious. Absolutely fantastic!


Fantastic

Disable the use of the REST API on your website to site users. Now with User Role support!

Simply JSON vs Disable REST API