Braad

Got a WordPress install that serves only as the data layer and/or admin UI of your web application?
This plugin will effectively turn off all default front end output, redirect all front end urls to the main site url, and optionally display a message of your choice. The message can be a simple plain text message or you can use the included filters to completely control the HTML output.
All activity in the wp-admin and all requests for assets like images, scripts, files, etc. will be unaffected by this plugin. Only requests that go through the <code>template_redirect</code> action will be affected.
<h4>Message Output</h4>
Rather than contaminate the data structures you might be using for your application (like posts and pages) this plugin includes a settings page with a simple textarea box where you can save any basic message you want to show. The message content is stored in the options table, and the textarea supports all the same HTML that you can use in post content.
You can use the <code>only_rest_api_page_content</code> filter to include any custom HTML output you want inside the <code><body></code> tags, or you can use the <code>only_rest_api_page_html</code> filter to completely replace all HTML output of the message page, including the <code><html></code> and <code><head></code> tags.
There is also an <code>only_rest_api_page_css</code> filter that allows you to override the 5 lines of CSS this plugin includes to center the message on the page.
If you want a hook added or have a feature request let me know. Pull requests are welcome <a href="https://github.com/BraadMartin/only-rest-api" title="Only REST API on Github" rel="nofollow ugc">on Github</a>.
<h4>Filter Examples</h4>
Use custom HTML inside the <code><body></code> tags:
<pre><code>add_filter( 'only_rest_api_page_content', 'xxx_page_content' );
function xxx_page_content( $content ) {

 $content = '<div class="custom-output">Sorry, I Only Speak REST. Please try again at a proper endpoint.</div>';

 return $content;
}
</code></pre>
Add custom CSS to the default output:
<pre><code>add_filter( 'only_rest_api_page_css', 'xxx_page_css' );
function xxx_page_css( $css ) {

 $css .= '.page-content { color: red; font-size: 72px; }';

 return $css;
}
</code></pre>
Replace the entire HTML output for the page:
<pre><code>add_filter( 'only_rest_api_page_html', 'xxx_page_html' );
function xxx_page_html( $html ) {

 ob_start();

 ?>
 <!doctype html>
 <html lang="">
 <head>
 <meta charset="utf-8">
 <meta http-equiv="x-ua-compatible" content="ie=edge">
 <title>Call me back over the REST API yo!</title>
 <meta name="description" content="">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <link rel="stylesheet" type="text/css" href="your-awesome-stylesheet.css">
 <script type="text/javascript">
 // Do neat stuff...
 </script>
 </head>
 <body>
 <div class="page-content">
 Ain't nobody got time for non-REST API requests. Please try again at a proper endpoint. :)
 </div>
 </body>
 </html>
 <?php

 $html = ob_get_clean();

 return $html;
}
</code></pre>

Only REST API

Redirects all front end, non-REST API requests to a single page.

Brandon

Now with shortcodes and post/custom-post-type support, as well as a comprehensive admin interface for setting plugin defaults
WordPress Access Control is a plugin designed to integrate into membership sites where certain pages, posts and custom post types should only be available to members of the site. The plugin offers fine tuned features for this purpose, including the ability to set site wide defaults and override these on a per-page basis.
You can easily set a page to be accessible only by members of your site, or even a specific role. You can also set pages to be accessible only to non-members of your site, useful for registration pages.
By default, you can add Members only pages to your menus, and users who cannot access them (non-members) won’t be able to see them. This applys to the children of a menu item as well, making it easy to build a separate menu for your members.
Additionally, you have the ability to customize search pages, completely hiding posts/pages from search results if a user can’t access them, showing search results without an excerpt, or showing search results normally.
New Features in 4.0
Enhanced theme compatiblity! We now have a much smaller impact on sites due to a new way of implementing our nav walker code. This should significantly improve compatability with third party themes.
New Features in 3.1
<ul>
<li>You can add member only versions of each menu on your site (Only when using WordPress menus)</li>
<li>You can make certain widgets only visible to members or non-members.</li>
</ul>
Translators: The POT file is included with the plugin and all text output uses gettext functions. Alternatively, you may download the POT file from http://brandonwamboldt.ca/files/wordpress-access-control.pot.
Documentation: The plugin includes comprehensive documentation file accessible via the plugin directory

WordPress Access Control

Yeah..thats good plugin. solve my issue with menu access



Better plugin...for me

Restrict pages, posts, custom post types, menus and widgets to members, nonmembers or specific roles and still add to navigation

Only REST API vs WordPress Access Control