Kevin Behrens

thomstark

Show or hide any portion of post content based on usernames, user roles, capabilities, custom groups, or logged-in status. Construct shortcodes manually or using a point and click UI.
<h4>Mini Update Log</h4>
<ul>
<li>v1.8.2 compat with WordPress 3.9</li>
<li>
v1.8.1 fixed conflict with the Tabify Edit Screen plugin
</li>
<li>
v1.8 added new shortcode handlers for nesting eyesonly shortcodes. also added body classes for logged-in user roles and logged-in usernames.
</li>
<li>
v1.7.1 fixed bug with TinyMCE button where TinyMCE panel is used outside post/page editor.
</li>
<li>
v1.7 added multisite support for username multiselect; fixed bug with role/level dropdown in non-Mozilla browsers.
</li>
<li>
Lots of new features in v1.6, including smooth integration with Role Scoper and Press Permit, thanks to their author Kevin Behrens, who has also now joined the Eyes Only team. Two makes a team, right?
</li>
<li>
As of v1.5, has compatibility with BuddyPress and BBPress forums in conjunction with the bbPress2 shortcode whitelist plugin by Anton Channing.
</li>
<li>
As of v1.4, includes TinyMCE Shortcode Button with Shortcode Generator Modal, with options to restrict access to the Shortcode Button, and to determine its position on the TinyMCE panel.
</li>
<li>
As of v1.3, includes Options page, with options to restrict access to the Meta Box, and to prevent content being hidden from Administrators.
</li>
<li>
As of v1.2, includes Shortcode Generator Meta Box
</li>
<li>
<a href="https://wordpress.org/plugins/eyes-only-user-access-shortcode/changelog/" title="Right-Click to Open in New Window">See full changelog</a>
</li>
</ul>
<h4>The Shortcode</h4>
[eyesonly] [/eyesonly]
or
[eyesonlier] [/eyesonlier]
or
[eyesonliest] [/eyesonliest]
<ul>
<li>
Required attributes: either logged=”in|out” or level=”anyrole, any_capability” or username=”anyusername” or all three
</li>
<li>
Newly integrated attributes: rs_group=”any_Role_Scoper_group(s)” or pp_group=”any_Permit_Press_group(s)”
</li>
<li>
Optional attribute: hide=”yes”
</li>
</ul>
All shortcodes must include at least one of the three required attributes. In some cases, it makes sense to use all of them together.
<ul>
<li>
The ‘logged’ attribute takes one of two values: ‘in’ or ‘out’
</li>
<li>
The ‘level’ attribute takes any user role (including custom roles) or any capability (including custom capabilities). It can take multiple roles and/or capabilities, separated either by spaces or commas.
</li>
<li>
The ‘username’ attribute takes any userlogin (username), or multiple, separated either by spaces or commas.
</li>
<li>
The ‘rs_group’ and ‘pp_group’ attributes can take comma or space-separated lists just like the ‘level’ and ‘username’ attributes. If you have the latest versions of either Role Scoper or Press Permit activated, you’ll get an extra menu in your shortcode generators to filter your content by those custom user groups. This attribute can also be used in combination with any of the others to fine tune your filtering.
</li>
<li>
The ‘hide’ attribute: By default, the shortcode will show the content only to the users specified by the ‘username’, ‘level’ or ‘logged’ attributes. Adding the ‘hide’ attribute will reverse that, and hide the content from the specified users. To hide content from the specified users, use hide=yes or hide=true.
</li>
</ul>
Any other shortcode can be used inside this shortcode.
<h4>Examples</h4>
<ul>
<li>
[eyesonly level=”administrator, customrole, moderate_comments”] Any kind of content. [/eyesonly] This will show the content only to users with the ‘administrator’ role, the ‘customrole’ role, and the ‘moderate_comments’ capability.
</li>
<li>
[eyesonly hide=”yes” logged=”out” level=”subscriber customrole”] Any kind of content. [/eyesonly] This will hide the content from all logged out users, and from anyone with the roles ‘subscriber’ or ‘customrole’.
</li>
<li>
[eyesonly username=”joebob, billyjean” level=”administrator”] Your content. [/eyesonly] This will show the content to all administrators and to the specific users ‘joebob’ and ‘billyjean,’ whether they’re administrators or not.
</li>
<li>
[eyesonly logged=”in”] Content for logged-in users. [/eyesonly][eyesonly logged=”out”] Content for logged-out users. [/eyesonly] This will show different content in the same location on the page depending on a user’s logged-in or out status.
</li>
<li>
[eyesonly level=”administrator”] Content. [/eyesonly] This will show the content only to administrators.
</li>
<li>
[eyesonly hide=”yes” level=”administrator custom_capability”] Content. [/eyesonly] This will hide the content only from administrators and from any role that has the ‘custom_capability’.
</li>
</ul>
<h4>Eyes Only Nesting</h4>
<ul>
<li>Eyes Only allows for nested user access shortcodes up to three levels deep. Example:</li>
</ul>
[eyesonly level=”administrator, editor, author”] Restricted content. [eyesonlier level=”administrator, editor”] Restricteder content. [eyesonliest level=”administrator”] Restrictedest content. [/eyesonliest] More restricteder content. [/eyesonlier] More restricted content. [/eyesonly]
<ul>
<li>It doesn’t matter which order you use them in, just so long as you keep your nested levels straight. </li>
</ul>
<h4>Requirements</h4>
<ul>
<li>
PHP 5.2+
</li>
<li>
WordPress 3.3+
</li>
</ul>

Eyes Only: User Access Shortcode

The plugin does the job. The authors should update compatibility :-)



Works

Show or hide any portion of post content based on usernames, user roles, capabilities, custom groups, or logged-in status.

Andrei

atanasprchev

Elena

Control what menu items your site’s visitors see, with visibility rules. Here are a few examples:
<ul>
<li>Display a menu item only if <code>User is logged in</code></li>
<li>Hide menus if <code>Device is mobile</code></li>
<li>Display menus only for <code>Admins and Editors</code></li>
<li>Hide Login or Register links for <code>Logged in Users</code></li>
<li>Display menus for <code>Users from US or UK</code></li>
<li>Display menus only for <code>Customers with active membership</code></li>
<li>Display menus for visitors browsing with <code>Language English or Spanish</code></li>
</ul>
After the plugin is enabled, each menu item will have a new option “Change menu item visibility” which will enable the selection of visibility rules.
Check the examples in screenshots or try it here → <a href="https://demos.layered.store" rel="nofollow ugc">demos.layered.store</a>
<h3>Features</h3>
<ul>
<li>Basic set of visibility rules
<ul>
<li>User state <code>User is logged in</code></li>
<li>User roles <code>Admin</code> <code>Editor</code> <code>Author</code> etc</li>
<li>Page type <code>Front page</code> <code>Single page</code> <code>Single post</code></li>
<li>Is Archive page (year, category, search results, etc)</li>
<li>Visitor device <code>Is Mobile</code></li>
</ul>
</li>
<li>Advanced visibility rules – requires <a href="https://layered.store/plugins/more-visibility-rules" rel="nofollow ugc">More Visibility Rules Add-on</a>
<ul>
<li>Visitor location – detect visitor’s Country</li>
<li>Visitor language – detect visitor’s selected Language</li>
<li>WooCommerce Subscriptions – Display menus for users with active subscription</li>
<li>WooCommerce Memberships – Display menus for customers with active membership plans</li>
<li>Groups – Detect if users are in specific groups</li>
<li>WishList Member – Detect the users’ membership level</li>
<li>Restrict Content Pro – Detect the users’ subscription level</li>
</ul>
</li>
<li>Multiple rules – mix multiple rules for a menu item visibility
<ul>
<li>show if <code>User is logged in</code> AND <code>Device is mobile</code></li>
<li>show if <code>User is Admin</code> AND <code>Is front page</code></li>
</ul>
</li>
<li>Support for <a href="https://wordpress.org/plugins/if-menu/#how%20can%20i%20add%20a%20custom%20visibility%20rule%20for%20menu%20items%3F" rel="ugc">adding your custom rules</a></li>
</ul>

If Menu – Visibility control for Menus

Display tailored menu items to each visitor with visibility rules

Eyes Only: User Access Shortcode vs If Menu – Visibility control for Menus