Dizze plugin is net hifke mei de lêste 3 grutte releases fan WordPress . It kin net langer wurde ûnderhâlden of stipe en kin kompatibiliteitsproblemen hawwe as it wurdt brûkt mei resinte ferzjes fan WordPress.

WordPress Access Areas


WP Access Areas lets you fine-tune who may read, edit or comment on your Blog posts.
You can either restrict access to logged-in uses only, certain WordPress-Roles or even custom Access Areas.


  • Define custom Access Areas and assign them to your blog-users
  • Restrict reading, editing and commenting permission to logged-in users, certain WordPress-Roles or Access Areas
  • define global access areas on a network
  • Supports bulk editing
  • German, Italian, Polish and Swedish localization (Huge Thankyou @ all translators!)

Known Issues

  • WordPress calendar Widget still shows dates where restricted posts have been created.
    When clicked on such a date a 404 will occur. There is an open WordPress Core ticket on that issue.
  • Taxonomy menus (e.g. Tags / Categories) also count restricted posts when the total number of posts in a taxonomy is ascertained.
    See this post for details.


Please head over to the source code on Github.


  • Area Access Manager
  • User Editing
  • Post Access Control
  • Post Access Behaviour


  1. Upload the ‘wp-access-areas.zip’ to the /wp-content/plugins/ directory and unzip it.

  2. Activate the plugin through the ‘Plugins’ menu in WordPress


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?

Please do so in the GitHub Repository.

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

Pull request are welcome in the GitHub Repository.


17 jannewaris, 2018
I like this mechanism to restrict contents. But I cannot uninstall this plugin (1.5.4) by manager UI. Just a blank page is shown when clicking the uninstall link.
18 oktober, 2017
Like everyone here, I have tested so many plugins to protect content (posts, pages, etc) based on user groups. This plugin does the job beautifully. You can set the default group for content. You can assign users to groups. You can assign content to groups. The only feature it needs, in my view, is hierarchical access. This is probably too much to ask – because it will put all paid plugins out of business 🙂 I’m a bit hesitant to implement this for clients because I fear it has been abandoned – last updated a year ago.
16 juny, 2017
I spent 2 full days looking for a plugin that redirects non-logged in user to specific url if the guest clicks on a specific page. I have downloaded over 30 plugins and none specifically caters my need until I find this plugin. I can’t emphasise enough how happy I am now 🙂
Lês alle 17 resinsjes

Meiwurkers & amp; Untwikkelders

“WordPress Access Areas” is iepen boarne software. De folgjende minsken hawwe bydroegen oan dizze plugin.


“WordPress Access Areas” is oerset yn 1 locale. Tank oan de oersetters foar harren bydragen.

Oersette “WordPress Access Areas” yn jo taal.

Ynteressearre yn ûntwikkeling?

Blêdzje troch de koade , besjoch de SVN-repository , of abonnearje op it ûntwikkelingslogboek troch RSS .



  • Fix: Nonce Verification fails when using WP password reset


  • Fix: PHP Warning when using plugin together with imsanity


  • Fix: Access settings broken in post quick edit


  • Fix: could not save website settings in network admin when running on multisite
  • Fix: role capabilities not saved


  • Fix: could not add caps on user-edit


  • Fix: WP deprecation warning
  • Fix: Chrome DOM warning


  • Fix: nonce error when adding User in network admin if plugin is not network active


  • Fix: __doint_it_wrong message wpdb->prepare


  • Fix: wpdb table prefix messed up in multisite


  • Fix: Pages saved via ajax not working. (Elementor)


  • Security hardening


  • Fix anaother PHP Warning


  • Fix Multisite Database Error when WPAA is not active for network.


  • Fix PHP Warning


  • Fix WSOD when saving post


  • Fix a Bug where a logged in user wasn’t redirected to the fallback page. Thanks to Andrey Shevtsov
  • Merry Christmas (Gregorian Calendar)


  • Fix Multisite: Network Access Areas were visible when plugin was single activated
  • Introduce filters: wpaa_can_protect_{$post_type}, wpaa_can_edit_{$post_type}_view_cap, wpaa_can_edit_{$post_type}_edit_cap, wpaa_can_edit_{$post_type}_comment_cap


  • Localization: move de_DE and de_DE_formal to translate.wordpress.org


  • Fix: A network admin without blog role could not edit post access by WP Roles
  • Plugin settings: Use WP Post statuses in favor of hard coded status list (allows use of custom post statuses now)
  • Introduce filter: ‘wpaa_allowed_post_stati’
  • Localization: Rework strings
  • Localization: Introduce de_DE_formal
  • Localization: consistent use of plugin textdomain


  • Fix: PHP deprecated warning during install + network upgrade
  • Fix: Incorrect Post Classes


  • Fix: Crash during install


  • Fix: WP _doing_it_wrong message


  • Fix: Multisite install procedere
  • Fix: Add self repair functionality (Ass missing posts table columns)


  • Fix: Post Custom behavior not dispalying in metabox when fallback page is default fb page
  • Fix: invalid login redirect URI in subdirectory installs


  • Fix: no restrictions for empty post objects (fixes buddypress profile page issue)
  • Fix: wrong redirection behavior for logged in users


  • Fix: set suppress_filters to false on get_posts
  • Fix: Saving Access Area Name


  • Feature: Explicitly enable / disable custom behaviour on posts.
  • UI: Combine columns in Posts list table
  • Fix: Contained roles were not assumed correctly
  • Fix: QuickEdit did not show Access after save
  • Compatibility: Drop support for WP < 3.8
  • Code refactoring, switched classname prefixes


  • Fix: Database error on comment feeds. Hiding or redirecting from comment feeds should work now.
  • Fix: Crash during update (function get_editable_roles not found)


  • Security Fix: Exclude restricted posts from comment feeds


  • Fix: Possible vulnerability where unauthorized users could change post access settings
  • L10n: change plugin textdomain from ‘wpundisclosed’ to ‘wp-access-areas’ (= Plugin slug). Rename lang/ > languages/.


  • WordPress 4.0 compatibility
  • Feature: Show Access Columns on Media and Custom Post type list views
  • Feature: Select default access for new posts.
  • Feature: Role Caps. Set which roles can edit post access properties
  • Improvement: Cache DB results
  • Plugin API: Added filter: wpaa_update_access_area_data
  • Plugin API: Added actions: wpaa_grant_access, wpaa_grant_{$wpaa_capability}, wpaa_revoke_access, wpaa_revoke_{$wpaa_capability}, wpaa_create_access_area, wpaa_update_access_area
  • Plugin API: Added function: wpaa_get_access_area( $identifier )


Fixing that one: https://wordpress.org/support/topic/plugin-causing-crash-post-woocommerce-update-today?replies=5


  • Fix: Post Edit save 404 behaviour
  • Fix: Hide inacessible posts in Recent Comments widget
  • Fix: Hide inacessible posts in Latest posts widget
  • Fix: Hide inacessible posts in Archive widget
  • Fix: Don’t show comments to inaccessible posts in WP-Admin. (Prohibits editing as well.)
  • L10n: Polish localisation


  • Feature: Explicitly select Front page as Fallback page.
  • Feature: Edit view cap now available for backend-only posts as well.
  • Fix: 404 behaviour not saving when default behaviour is other than 404
  • API: added function wpaa_is_post_public( $post )


  • Feature: Option to select post status after deleting access area
  • Fix: Wrong viewing permissions after delete access area
  • Fix: remove options upon uninstall
  • Swedish localization


  • Feature: Bulk edit users: Grant and revoke access.
  • Fix: Was able to create access areas with empty names.
  • Fix: Ignores WP’s Comments closed status


  • Fix: User list table column


  • Check WP 3.9 compatibility
  • Fix: With no AAs present add Access Area didn’t show up on profile edit page


  • Fix: Used wrong option name on edit post
  • Fix: Embarrassing wrong var name on edit post
  • L10n: Added one more italian string


  • Feature: Option to redirect to wp-login or to fallback page.
  • Feature: action hook an filter on access attempt for a restricted post. (see GitHub Repo for details)
  • Feature: post classes
  • CSS: use dashicons
  • Italian localization


  • Feature: Bulk edit Posts
  • Feature: Ajax-Add AAs on User edit screen
  • Debug: Fix invalid HMTL on user list table
  • Debug: Remove edit post link from frontend
  • Debug: Invisible posts are now also excluded from editing
  • Debug: Remove “Who can read”-Select from non-public post types


  • Debug: Fix Comment issue. Selecting “WordPress default” now does what it is supposed to: handling over the comment responsibility to WordPress.


  • Debug: Fix missing file issue


  • Feature/Debug: Network admins now have access to all areas on all blogs. Blog admins have access to all areas on their own blog(s).
  • Code: put general use processes into function


  • Feature/Debug: Network admins now have access to all areas on all blogs. Blog admins have access to all areas on their own blog(s).
  • Code: put general use processes into function


  • Fixed: Fixed issue, where access areas where not shown on user editing in single-site installs.


  • Fixed: Fixed issue, where posts table was not modified after creating new blog. Use WP’s upgrade network function to fix all posts tables.


  • Feature: WP-Capability column in Access Areas table view
  • Fixed: Commenting was still possible after switching off comments and setting comment capabilities to ‘use WP defaults’.



  • Fix: issue where WP-comment settings were not applied while saving post
  • Improve DE Localization


  • Fix: post tables did not update on wpmu_new_blog
  • Fix: deletion issue
  • Localize Plugin description


  • Added versioncheck


  • Improve loading behaviour


  • Added editing restrictions.
  • Several fixes.


  • Initial Release