rgeyer

Twitter API Shortcodes (TAS for short) is currently in Alpha, and should not be considered at all stable! With that said 
please provide any feedback so we can make things better!
TAS allows you to put single tweets or entire twitter searches into your posts and pages using shortcodes. The tweets and searches 
are displayed in HTML markup, so the become “part” of your site, which is good for SEO.
The generated markup can be customized by putting a tweet.tpl (smarty template) file into your theme directory. This also means that 
theme authors can support this plugin directly.
Tweet templates assume that each tweet is in some block with the class ‘status’ (preferably a div like so
<
div class=”status”>), and that in that block, there is a block for images with the class ‘images’ (preferably a div like so
<
div class=”images”>)
All single tweets are cached in your local wordpress database, making performance ultra fast and reducing the number of requests 
necessary to the Twitter API.
Twitter searches can also be cached, allowing you to keep a history of that particular search. This is useful if you want to 
tweet about a particular event with a hash tag, then display all of your tweets for that event on a page, or in a post even 
after those tweets fall out of the twitter search index.
<h3>TODO</h3>
This is a list of things which currently are not yet working (hey it’s an alpha version) 
* Avatar updates

Twitter API Shortcodes

A plugin to add single tweets or twitter searches to your posts and pages using shortcodes

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!

Twitter API Shortcodes vs Disable REST API