Plugin Directory

Test out the new Plugin Directory and let us know what you think.

WordPress Access Areas

Fine tuning access to your posts.

Why can't I protect media?

Because the plugin can only protect posts, which are database entries. A media also contains a file stored on your servers file system. A file is normally just returned by the server, the WordPress core is not involved. In order to protect a file, let's say an image, the Image URL would have to be point to a special Script, that decides whether the file is protected or not, and if so, which user or group of users would be granted access.

A lot of processing would be going on, and each and every little thumbnail would add another one or two seconds to your page load time. The result: Tears, rage and support requests.

What does it exactly do?

For each Post it stores a capabilty the user needs to have in order to view, edit or comment on a post. By defining an Access Area you create nothing more than a custom capability.

Why didn't you use post_meta to store permissions? WordPress already provides an API for this!

I did this mainly for performance reason. For detecting the reading-permission on specific content, the plugin mainly affects the WHERE clause used to retrieve posts. In most cases, using post_meta would mean to add lots of JOIN clauses to the database query, slowing down your site's performance.

Does it mess up my database?

It makes changes to your database, but it won't make a mess out of it. Upon install it does two things: 1. It creates a table named ´{$wp_prefix}_disclosure_userlabels´. The access areas you define are here. 2. It adds three columns to Your Posts tables: post_view_cap and post_comment_cap.

Upon uninstall these changes will be removed completely, as well as it will remove any custom generated capability from your user's profiles.

I'd like to do some more magic / science with it. And yes: I can code!

Developer documentation can be found in the project wiki.

I found a bug. Where should I post it?

I personally prefer GitHub but you can post it in the forum as well. The plugin code is here: GitHub

I want to use the latest files. How can I do this?

Use the GitHub Repo rather than the WordPress Plugin. Do as follows:

  1. If you haven't already done: Install git

  2. in the console cd into Your 'wp-content/plugins´ directory

  3. type git clone git@github.com:mcguffin/wp-access-areas.git

  4. If you want to update to the latest files (be careful, might be untested on Your WP-Version) type git pull´.

Please note that the GitHub repository is more likely to contain unstable and untested code. Urgent fixes concerning stability or security (like crashes, vulnerabilities and alike) are more likely to be fixed in the official WP plugin repository first.

I found a bug and fixed it. How can I contribute?

Either post it on GitHub or—if you are working on a cloned repository—send me a pull request.

How can I contribute a localization?

My goal is to host all translations on translate.wordpress.org. For German this is already accomplished. For almost every other localization the project is still in need of translation editors.

If you want to contribute a translation please let me know by posting a comment to this thread stating the name of this plugin, the locale you would like to maintain and some brief information about you - e.g. if you are a native speaker. I will back up your request with all the authority that a simple plugin developer can have.

Requires: 3.8 or higher
Compatible up to: 4.5.7
Last Updated: 11 months ago
Active Installs: 1,000+


5 out of 5 stars


0 of 1 support threads in the last two months have been marked resolved.

Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.

100,1,1 100,1,1