⚠ NOTICE: This plugin is no longer in active development.
I no longer use this plugin in any way and don't plan to work on it further. You can of course continue to use it, just be aware that I will not offer any support or fix any bugs. You're also welcome to fork it and base your own plugin on it.

# page-whitelists Requires at least: 3.6 Tested up to: 4.6.1 Stable version: 4.0.2 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html Limit user access only to selected ("whitelisted") pages, by creating Whitelists and assigning them to users or roles. Using this plugin, you can let user edit only a single page (or a handful of them), while the rest of the content is out of sight. Useful when for dynamic, shortcode-heavy sites with content that still needs to be edited by inexperienced users (i.e. an 'About us' section), or a company website whith multiple administrators each maintaining their own section. Page Whitelists is an administration tool that can be used to allow selected users to edit only certain pages, leaving the rest inaccessible. This is done by creating "whitelists", and assigning them to users and/or roles. Each whitelist can also limit creation of new pages.Every page, user and role can belong to multiple whitelists. The user sees only the pages they are allowed to edit - reducing confusion and clutter on the Page listing. This plugin was written as a light-weight replacement for the whitelisting functionality of Role Scoper. #### Combining whitelists: * Whitelists are additive - every user has access to all pages in all whitelists they're assigned to. * 'Strict' whitelists have priority - once a user is assigned to a whitelist that disables creation of new pages, they are not allowed to do so (even if other whitelists are 'non-strict'). #### I set up Page Whitelists, but my users still can't access Pages. What's happening? This is most likely caused by a missing capability 'edit-pages'. Page Whitelists is substractive, so the user must have access to all pages first. This can happen if you previously used another access manager, especially Role Scoper, and it didn't reset the capabilities properly when uninstalling. You can fix that easily with any plugin that can edit user roles (for example [User Role Editor](https://wordpress.org/plugins/user-role-editor/)). ## Installation 1. Install and activate like any other plugin. 1. Create a whitelist in Users->Maintain Whitelists. 1. Add users/roles and pages to it. You can also add page to a whitelist when editing it in Page Editor, or a user through User Editor. Additional (default) plugin settings can be edited in Settings->Page Whitelists. ## Changelog ### 4.0.1 Version upgrade error - this is the working version. ### 4.0.0 New - pages in Whitelist editor are now arranged in a tree, so parent-child branches can be selected simultaneously. New - names and links to assigned pages in the Whitelist table. New - new plugin options controlling default behavior of whitelists and scope of filtering. Whitelist management was moved under Users, the Page Whitelists page under Settings now contains default plugin settings. Numerous bug fixes. ### 3.0.3 Bug fix - fixed compatibility issues with NextGen Gallery - creating albums when user is assigned to a strict whitelist. Enhancement - less log messages when WP_Debug is on. ### 3.0.2 Bug fix (bug is only in the version from Wordpress Plugin Repository) - missing file `wp-content/plugins/page-whitelists/templates/profile_field.php` causes Fatal Error on Edit User page. ### 3.0.1 Bug fix - setting strict whitelist also blocked creation of new posts (creator-introduced bug, I am very sorry) ### 3.0 Bug fix - fixed an issue with plugins that allow creation of pages Plugin compatibility fix - Tree Page View. New - column with assigned whitelists in User Table New - field on User Profile editor New - select all/none pages when creating/editing whitelist. ### 2.0 Bug fix - plugin now doesn't fail on screen-less admin pages (various AJAX helpers etc.) New - plugin now filters all backend queries that request pages (including those made by AJAX). #### 1.2 Bug fix - automatic addition of newly created pages to non-strict whitelists now works. #### 1.2 Version fixes a bug in the non-strict whitelist functionality. Update recomended. #### 1.0 First published version. ## FAQ ### What happens when user is assigned more than one whitelist? Whitelists are additive - every user has access to all pages in all whitelists they're assigned to. 'Strict' whitelists have priority - once a user is assigned to a whitelist that disables creation of new pages, they are not allowed to do so (even if other whitelists are 'non-strict'). ###I set up Page Whitelists, but my users still can't access Pages. What's happening?### This is most likely caused by a missing capability 'edit-pages'. Page Whitelists is substractive, so the user must have access to all pages first. This can happen if you previously used another access manager, especially Role Scoper, and it didn't reset the capabilities properly when uninstalling. You can fix that easily with any plugin that can edit user roles (for example [User Role Editor](https://wordpress.org/plugins/user-role-editor/)).