Access Areas for WordPress
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. Features Define custom Access Areas and assign them to your blog-users Restrict reading, editing and commen
About this tool.
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.
Features
- 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.
Development
Please head over to the source code on Github .
Getting started.
- 01Upload the ‘wp-access-areas.zip’ to the /wp-content/plugins/ directory and unzip it.
- 02Activate the plugin through the ‘Plugins’ menu in WordPress
Frequently asked questions.
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?