Jakub Klapka

This plugin adds new status for posts (or pages/custom post types) called “Secured with link”. If you select this status, that specific post wouldn’t be accessible on its standard URL anymore, but you have to access it on URL with random token in it. This URL is displayed on post edit screen in administration.
<h4>Configuration</h4>
For now, there is no administration screen yet. To configure plugin, you can inject your changes to plugin configuration array from your theme or plugin. Just put this code into functions.php file in your theme:
<pre><code>add_filter( 'lumi.secure_post_with_link.config', function( $config ){
 $config[ 'allowed_post_types' ] = [ 'post', 'page' ];
 $config[ 'url_identifier' ] = 'sec';
 // ... Other $config variables
 return $config;
} );
</code></pre>
Preferably, don’t include lines with attributes, which you don’t want to change.
These are attributes (with defaults), which you can change this way:
<ul>
<li>
allowed_post_types ([ ‘post’ ]) List of post types, which should be affected by this plugin. Use array notation like: <code>[ 'post', 'page', 'custom_type' ]</code>.
</li>
<li>
secured_meta_name (‘_secured_with_link_token’) Name of meta, which stores post token. You can change that in case of conflicts with themes or other plugins.
</li>
<li>
url_identifier (‘s’) Part of URL before token, which identifies secured posts.
</li>
<li>
token_length (4) Length of random token. With default generator, length is in bytes!
</li>
<li>
use_openssl (true) If plugin should use cryptographically secure random generator, or less-secure PHP functions. (See below)
</li>
<li>
assets_url (Defaults to [plugin URL]/assets) URL for static assets (like Javascripts), in case, you want to use your assets for some reason.
</li>
<li>
translations_dir (Defaults to [Plugin path]/lang) You can change path, where plugin looks for translation files. If you want to translate plugin, you should not use this setting, but create standard translation in wp-content/languages folder.
</li>
</ul>
In case, you have changed any settings after plugin installation, deactivate and reactivate plugin, so all changes are correctly applied.
<h4>Compatibility</h4>
<ul>
<li>For now, you need to use WP URL Rewriting for plugin to work correctly</li>
<li>Plugin should work with PHP 5.4, but at least PHP 5.6 is highly recommended. I’m sorry, but I won’t support older, insecure and slow versions of PHP.</li>
<li>By default, plugin uses OpenSSL library to generate cryptographically secure random tokens. If your hosting provider don’t have OpenSSL set up, you can use configuration variable: <code>$config[ 'use_openssl' ] = false</code> to use less-secure method of token generating. This should still be secure enough for most use cases.</li>
</ul>
<h4>Planned features</h4>
<ul>
<li>Administration page</li>
<li>Regenerate token</li>
<li>Role management – users with privileges should be able to access post without token</li>
</ul>
<h4>Developers</h4>
Plugin is also hosted on <a href="https://github.com/jakub-klapka/wp-secure-post-with-link" rel="nofollow ugc">Github</a>.

Secure post with link

Adds new post status "Secured with Link". Posts with this status will be accessible only with randomly generated token in URL.

NipponMonkey

This plugin makes your BuddyPress community private. You can control which areas of your site are accessible to logged out users in two ways, “restrict site access, but allow some public pages” or “allow site access, but restrict some private pages”. This plugin also can block widgets from logged out users and block all RSS feeds.
In the default mode (restrict access, but allow some public pages), logged out users only have access to your homepage, or access to a list of pages/areas that you’d like to make public. Logged in members have full site access.
If you visit the community when you’re logged out and you’re visiting a private page, then you’re redirected to a landing page of your choice (defaults to the homepage).
You can set uris that are accessibly to non-logged in users using a special config php file – no database calls are needed.
In the alternative mode (allow site access, but restrict some private pages), logged out members have full site access, but you are able to make some pages/areas of your site private – so only logged in members are able to view them. This is the opposite to the default mode.
In the default mode, the plugin blocks all of your widgets from being visible to logged out users. This stops possible private information from being seen when non-logged in users visit your site. 
You can change the config file so that some of your widgets are still displayed. In the alternative mode, all widgets are shown but you’re able to block widgets that should only be displayed to members.
Also, all RSS feeds are blocked by default too.
You might also like to change these setting in your WordPress and BuddyPress settings.
<ul>
<li>BP Setting: Hide admin bar for logged out users? = YES</li>
<li>WP Setting: Membership – Anyone can register? = NO</li>
<li>WP Privacy Settings: Site Visibility = I would like to block search engines, but allow normal visitors</li>
</ul>
See the FAQs or the example config file in the download for more information on configuring this plugin.
You can see an example of this plugin working in the default mode here: http://www.englishpubpool.co.uk/bppc_test/about/
<ul>
<li>Please note, this plugin requires PHP 5.</li>
</ul>
If you’d like to ensure that users don’t stay logged into your site after a set period of inactivity (for security reasons), then you could use this plugin:
<ul>
<li>Inactivity Auto Sign Out plugin: https://wordpress.org/extend/plugins/inactivity-auto-sign-out-plugin/</li>
</ul>

BuddyPress Private Community

This plugin makes your BuddyPress community private. Only logged in members can view the social areas in full. You can configure the default settings.

Secure post with link vs BuddyPress Private Community