JianShuo

I created my first plugin when I created my CEO Blog. The problem is obvious: I am going to have a CEO blog where I can share my thoughts with the team frequently. I tried to write a different blog, and I found it is just impossible to maintain two. So I decided to put it on to my own personal blog.
Although most of the articles are public in nature, I do have something that I hope to disclose to the general public later. I don’t want to have complicated OAuth based verification. A simple IP based restriction is good enough. There is no simple solution so I wrote one myself.

IP Only

Restrict access only to specific IP address. Other visitors will see a message. The article is hidden from feed as well.

lienann

This plugin allow to set access level value for users and materials and limit 
access to materials of a specific type (posts, pages, custom post types) when 
user access level lower then material access level.
Also this plugin creates a new capabilities:
<ol>
<li>dal_admin – capability to change plugin settings</li>
<li>dal_edit – capability to change user access level</li>
</ol>
Attention to developers! 
Filters used in this plugin does not work when using get_posts() with 
the parameter ‘suppress_filters’ => true.
Install script don’t assign any values of user access levels and post access levels. 
By default post access level = 100 and user access level = 0 (except Administrator = 100 ). 
By default access to posts is limited in front-end. There is an option 
“Should we apply restrictions in admin console?” in plugin settings to limit access in 
administrator interface too. 
Users can assign records access level equal or lower their own access level.
Languages: English, Русский
I apologize for possible mistakes in plugin translation. 
I will be glad to accept the help with the correct translation of a plugin into 
English and to correction of my mistakes.

Data access levels

Restrict access to posts by user access level.

IP Only vs Data access levels