Ratul Hasan

Custom Role Creator plugin allows you to add or change user roles and capabilities easily. You can add new role or edit existing role. You can add capabilities to a role or change a roles’ capability. 
Just turn on check boxes of capabilities you wish to add to the selected role and click “Save Capabilities” button to save your changes. Add new role and customize its’ capabilities according to your needs. You can add role from scratch or as a copy of other existing role. 
An unnecessary role can be deleted. If there is no use for this role, you can delete that role. That’s it. 
Currently supports: 
– Create new role. 
– Edit role. 
– Create new role as a copy existing role capabilities. 
– Assign capabilities to a role. 
– Delete unnecessary role. 
– Assign capabilities to individual users’. 
– Reset Custom Role Creator Made Roles To Default. 
– Restore roles and capabilities to default as WordPress Core.
The plugin is an open source project. If anyone has new ideas – pull requests are welcome! 
The development repo is <a href="https://github.com/RatulHasan/custom-role-creator" rel="nofollow ugc">GitHub Repo</a>.
<h3>Privacy Policy</h3>
Custom Role Creator (CRC) uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements.
Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users.
Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case.
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.

Custom Role Creator (CRC)

Custom Role Creator plugin allows you to add or change user roles and capabilities easily.

benwills

The mmbrs plugin allows you to restrict content access using shortcodes.
Content may be restricted based on role, capability, user meta, and logged-in status.
<h3>What makes mmbrs different:</h3>
<ul>
<li>Restriction based on role, capability, user meta, and logged-in status is 
all in one place.</li>
<li>You are able to restrict content based on if a user is=’not’. For 
example, Show this content if a user is not an administrator.</li>
<li>You can pass multiple variables to the roles and capabilities shortcodes. 
For example, Show this content to users who are subscribers, 
contributors, or editors.</li>
<li>By default, any content within these four shortcodes is not displayed in 
feeds. You may also set the showinfeed=’yes’ attribute to show the 
content in feeds.</li>
<li>It is as lean as I could get it, with logic ordering to cut down on 
processing. Which isn’t saying much, but if you’ve got suggestions, I’m 
open to hearing them.</li>
</ul>
<h3>The four mmbrs shortcodes are:</h3>
<ul>
<li>[mmbrs_logged_in]</li>
<li>[mmbrs_roles]</li>
<li>[mmbrs_capabilities]</li>
<li>[mmbrs_user_meta]</li>
</ul>
<h3>[mmbrs_logged_in]</h3>
<blockquote>
[mmbrs_logged_in]Content.[/mmbrs_logged_in]
</blockquote>
<ul>
<li>Attribute: none
<ul>
<li>Shows content to logged in users.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_logged_in is=’not’]Content.[/mmbrs_logged_in]
</blockquote>
<ul>
<li>Attribute: is
<ul>
<li>Optional.</li>
<li>is only accepts not.</li>
<li>Shows content to logged out users.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_logged_in showinfeed=’yes’]Content.[/mmbrs_logged_in]
</blockquote>
<ul>
<li>Attribute: showinfeed
<ul>
<li>Optional.</li>
<li>showinfeed only accepts yes.</li>
<li>Shows content in the feed and ignores all other attributes when displaying in the feed. (If it is not being displayed in a feed, all of the attributes take effect.)</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<h3>[mmbrs_roles]</h3>
<blockquote>
[mmbrs_roles]Content.[/mmbrs_roles]
</blockquote>
<ul>
<li>Attribute: none
<ul>
<li>Returns nothing.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_roles equals=’subscriber’]Content.[/mmbrs_roles]
</blockquote>
<ul>
<li>Attribute: equals
<ul>
<li>Required.</li>
<li>Accepts multiple. e.g. equals=’subscriber,contributor’</li>
<li>Shows content to users with the ‘subscriber’ role.</li>
<li>Case sensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_roles is=’not’ equals=’subscriber’]Content.[/mmbrs_roles]
</blockquote>
<ul>
<li>Attribute: is
<ul>
<li>Optional.</li>
<li>Shows content to users who do not have the ‘subscriber’ role.</li>
<li>is only accepts not.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_roles showinfeed=’yes’]Content.[/mmbrs_roles]
</blockquote>
<ul>
<li>Attribute: showinfeed
<ul>
<li>Optional.</li>
<li>Shows content in the feed and ignores all other attributes when displaying in the feed. (If it is not being displayed in a feed, all of the attributes take effect.)</li>
<li>showinfeed only accepts yes.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<h3>[mmbrs_capabilities]</h3>
<blockquote>
[mmbrs_capabilities]Content.[/mmbrs_capabilities]
</blockquote>
<ul>
<li>Attribute: none
<ul>
<li>Returns nothing.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_capabilities can=’delete_others_posts’]Content.[/mmbrs_capabilities]
</blockquote>
<ul>
<li>Attribute: can
<ul>
<li>Required.</li>
<li>Shows content to users with the ‘delete_others_posts’ capability.</li>
<li>Accepts multiple. e.g. can=’delete_others_posts,edit_others_posts’</li>
<li>Case sensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_capabilities is=’not’ can=’delete_others_posts’]Content.[/mmbrs_capabilities]
</blockquote>
<ul>
<li>Attribute: is
<ul>
<li>Optional.</li>
<li>Shows content to users who do not have the ‘delete_others_posts’ capability.</li>
<li>is only accepts not.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_capabilities showinfeed=’yes’]Content.[/mmbrs_capabilities]
</blockquote>
<ul>
<li>Attribute: showinfeed
<ul>
<li>Optional.</li>
<li>Shows content in the feed and ignores all other attributes when displaying in the feed. (If it is not being displayed in a feed, all of the attributes take effect.)</li>
<li>showinfeed only accepts yes.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<h3>[mmbrs_user_meta]</h3>
<blockquote>
[mmbrs_user_meta]Content.[/mmbrs_user_meta]
</blockquote>
<ul>
<li>Attribute: none
<ul>
<li>Returns nothing.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_user_meta key=’first_name’][/mmbrs_user_meta]
</blockquote>
<ul>
<li>Attribute: key (with no content)
<ul>
<li>Required. (key attribute is required. Content is not required.)</li>
<li>Shows a logged-in user’s first_name meta value.</li>
<li>Does NOT accept multiple values when content is null/empty.</li>
<li>Case sensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_user_meta key=’first_name’]Content.[/mmbrs_user_meta]
</blockquote>
<ul>
<li>Attribute: key (with content)
<ul>
<li>Required. (key attribute is required. Content is not required.)</li>
<li>Shows content to logged-in user with the first_name meta value.</li>
<li>Accepts multiple as OR. e.g. key=’first_name,last_name’</li>
<li>Case sensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_user_meta is=’not’ key=’first_name’]Content.[/mmbrs_user_meta]
</blockquote>
<ul>
<li>Attribute: is
<ul>
<li>Optional.</li>
<li>Shows content to users who do not have the first_name meta value.</li>
<li>is only accepts not.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_user_meta is=’not’ key=’first_name’ equals=’Ben’]Content.[/mmbrs_user_meta]
</blockquote>
<ul>
<li>Attribute: equals
<ul>
<li>Required.</li>
<li>Shows content to users who do not have the first_name user meta of ‘Ben’.</li>
<li>Case sensitive.</li>
</ul>
</li>
</ul>
<blockquote>
[mmbrs_user_meta showinfeed=’yes’]Content.[/mmbrs_user_meta]
</blockquote>
<ul>
<li>Attribute: showinfeed
<ul>
<li>Optional.</li>
<li>Shows content in the feed and ignores all other attributes when displaying in the feed. (If it is not being displayed in a feed, all of the attributes take effect.)</li>
<li>showinfeed only accepts ‘yes’.</li>
<li>Case insensitive.</li>
</ul>
</li>
</ul>
<h4>Other Notes:</h4>
For every shortcode, except [mmbrs_logged_in], if a user is not logged in, the shortcode will return nothing. The exception is when using is=’not’ in [mmbrs_logged_in], as in [mmbrs_logged_in is=’not’]Content.[/mmbrs_logged_in]
By default, everything is hidden from feeds unless showinfeed=’yes’ is defined.
<h4>Motivation for this plugin:</h4>
I wrote this plugin to fill some holes, reduce some unnecessary functions, and fix some minor bugs I found in other plugins. I now use this, and only this, to control all shortcode-based content access on my membership-style websites.
The Members plugin checks roles by checking capabilities. You are not supposed to do that. The proper way of checking roles is included here. Notes on this:
<ul>
<li><a href="https://codex.wordpress.org/Function_Reference/current_user_can#Notes" rel="nofollow ugc">WordPress current_user_can() Notes</a></li>
</ul>
Aside from that, I love and use the Members plugin and suggest you check it out for other role- and capability-based content access management.
I removed a bunch of stuff from the User Meta Shortcodes plugin that I didn’t want. If you want the additional functionality, I recommend that plugin.
In the end, I wanted very clear control of in-post content via shortcodes. I wasn’t finding anything that was totally stripped down. So I wrote this.
<h4>Inspiration and Credits:</h4>
<ul>
<li><a href="https://wordpress.org/plugins/members/" rel="ugc">Members Plugin</a></li>
<li><a href="https://wordpress.org/plugins/user-meta-shortcodes/" rel="ugc">User Meta Shortcodes Plugin</a></li>
<li><a href="http://docs.appthemes.com/tutorials/wordpress-check-user-role-function/" rel="nofollow ugc">AppThemes User Role Function</a></li>
</ul>

mmbrs

Restrict content access using shortcodes; based on roles, capabilities, user meta, and logged in status.

Custom Role Creator (CRC) vs mmbrs