1.5.20 fixed an authenticated XSS Vulnerability in the Acceas Areas List Table. Everybody should upgrade the plugin ASAP.<\/p>"},"ratings":{"1":"2","2":0,"3":0,"4":"1","5":"14"},"assets_icons":[],"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":1005076,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.7","1.2.8","1.2.9","1.3.0","1.3.1","1.3.2","1.3.3","1.4.0","1.4.1","1.4.2","1.4.3","1.4.4","1.4.5","1.4.6","1.4.7","1.5.0","1.5.1","1.5.10","1.5.11","1.5.12","1.5.13","1.5.14","1.5.15","1.5.16","1.5.17","1.5.18","1.5.19","1.5.2","1.5.20","1.5.21","1.5.22","1.5.3","1.5.4","1.5.5","1.5.6","1.5.7","1.5.8","1.5.9"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":2231737,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":2231737,"resolution":"2","location":"assets","locale":""},"screenshot-3.png":{"filename":"screenshot-3.png","revision":2231737,"resolution":"3","location":"assets","locale":""},"screenshot-4.png":{"filename":"screenshot-4.png","revision":2231737,"resolution":"4","location":"assets","locale":""}},"screenshots":{"1":"Area Access Manager","2":"User Editing","3":"Post Access Control","4":"Post Access Behaviour"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[1911,4436,3710,600,2153],"plugin_category":[46,54],"plugin_contributors":[78906],"plugin_business_model":[],"class_list":["post-24325","plugin","type-plugin","status-publish","hentry","plugin_tags-access","plugin_tags-capability","plugin_tags-role","plugin_tags-security","plugin_tags-user","plugin_category-editor-and-writing","plugin_category-security-and-spam-protection","plugin_contributors-podpirate","plugin_committers-podpirate"],"banners":{"banner":"https:\/\/ps.w.org\/wp-access-areas\/assets\/banner-772x250.png?rev=1005076","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/wp-access-areas_616579.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/wp-access-areas\/assets\/screenshot-1.png?rev=2231737","caption":"Area Access Manager"},{"src":"https:\/\/ps.w.org\/wp-access-areas\/assets\/screenshot-2.png?rev=2231737","caption":"User Editing"},{"src":"https:\/\/ps.w.org\/wp-access-areas\/assets\/screenshot-3.png?rev=2231737","caption":"Post Access Control"},{"src":"https:\/\/ps.w.org\/wp-access-areas\/assets\/screenshot-4.png?rev=2231737","caption":"Post Access Behaviour"}],"raw_content":"\n
WP Access Areas lets you fine-tune who may read, edit or comment on your Blog posts.\nYou can either restrict access to logged-in uses only, certain WordPress-Roles or even custom Access Areas.<\/p>\n\n
Please head over to the source code on Github<\/a>.<\/p>\n\n\n Upload the 'wp-access-areas.zip' to the Activate the plugin through the 'Plugins' menu in WordPress<\/p><\/li>\n<\/ol>\n\n\n Because the plugin can only protect posts, which are database entries. A media also contains a\nfile stored on your servers file system. A file is normally just returned by the server, the\nWordPress core is not involved. In order to protect a file, let's say an image, the Image URL\nwould have to be point to a special Script, that decides whether the file is protected or not,\nand if so, which user or group of users would be granted access.<\/p>\n\n A lot of processing would be going on, and each and every little thumbnail would add another\none or two seconds to your page load time. The result: Tears, rage and support requests.<\/p><\/dd>\n For each Post it stores a capabilty the user needs to have in order to view, edit or comment on a post.\nBy defining an Access Area you create nothing more than a custom capability.<\/p><\/dd>\n I did this mainly for performance reason. For detecting the reading-permission on specific content,\nthe plugin mainly affects the WHERE clause used to retrieve posts. In most cases, using post_meta\nwould mean to add lots of JOIN clauses to the database query, slowing down your site's performance.<\/p><\/dd>\n It makes changes to your database, but it won't make a mess out of it. Upon install it does two things:\n1. It creates a table named \u00b4{$wp_prefix}_disclosure_userlabels\u00b4. The access areas you define are here.\n2. It adds three columns to Your Posts tables: post_view_cap and post_comment_cap.<\/p>\n\n Upon uninstall these changes will be removed completely, as well as it will remove any custom generated\ncapability from your user's profiles.<\/p><\/dd>\n Developer documentation can be found in the project wiki<\/a>.<\/p><\/dd>\n Please do so in the GitHub Repository<\/a>.<\/p><\/dd>\n Pull request are welcome in the GitHub Repository<\/a>.<\/p><\/dd>\n\n<\/dl>\n\n\n Fixing that one: http:\/\/wordpress.org\/support\/topic\/plugin-causing-crash-post-woocommerce-update-today?replies=5<\/p>\n\n\n
\/wp-content\/plugins\/<\/code> directory and unzip it.<\/p><\/li>\n\n
Why can't I protect media?<\/h3><\/dt>\n
What does it exactly do?<\/h3><\/dt>\n
Why didn't you use post_meta to store permissions? WordPress already provides an API for this!<\/h3><\/dt>\n
Does it mess up my database?<\/h3><\/dt>\n
I'd like to do some more magic \/ science with it. And yes: I can code!<\/h3><\/dt>\n
I found a bug. Where should I post it?<\/h3><\/dt>\n
I found a bug and fixed it. How can I contribute?<\/h3><\/dt>\n
1.5.22<\/h4>\n\n
\n
1.5.21<\/h4>\n\n
\n
1.5.20<\/h4>\n\n
\n
1.5.19<\/h4>\n\n
\n
1.5.18<\/h4>\n\n
\n
1.5.17<\/h4>\n\n
\n
1.5.15<\/h4>\n\n
\n
1.5.14<\/h4>\n\n
\n
1.5.13<\/h4>\n\n
\n
1.5.12<\/h4>\n\n
\n
1.5.11<\/h4>\n\n
\n
1.5.10<\/h4>\n\n
\n
1.5.9<\/h4>\n\n
\n
1.5.8<\/h4>\n\n
\n
1.5.7<\/h4>\n\n
\n
1.5.6<\/h4>\n\n
\n
1.5.5<\/h4>\n\n
\n
1.5.4<\/h4>\n\n
\n
1.5.3<\/h4>\n\n
\n
1.5.2<\/h4>\n\n
\n
wpaa_can_protect_{$post_type}<\/code>, wpaa_can_edit_{$post_type}_view_cap<\/code>, wpaa_can_edit_{$post_type}_edit_cap<\/code>, wpaa_can_edit_{$post_type}_comment_cap<\/code><\/li>\n<\/ul>\n\n1.5.1<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.7<\/h4>\n\n
\n
1.4.6<\/h4>\n\n
\n
1.4.5<\/h4>\n\n
\n
1.4.4<\/h4>\n\n
\n
1.4.3<\/h4>\n\n
\n
1.4.2<\/h4>\n\n
\n
1.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.3<\/h4>\n\n
\n
get_editable_roles<\/code> not found)<\/li>\n<\/ul>\n\n1.3.2<\/h4>\n\n
\n
1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
wpaa_update_access_area_data<\/code><\/li>\nwpaa_grant_access<\/code>, wpaa_grant_{$wpaa_capability}<\/code>, wpaa_revoke_access<\/code>, wpaa_revoke_{$wpaa_capability}<\/code>, wpaa_create_access_area<\/code>, wpaa_update_access_area<\/code><\/li>\nwpaa_get_access_area( $identifier )<\/code><\/li>\n<\/ul>\n\n1.2.9<\/h4>\n\n
1.2.8<\/h4>\n\n
\n
1.2.7<\/h4>\n\n
\n
wpaa_is_post_public( $post )<\/code><\/li>\n<\/ul>\n\n1.2.6<\/h4>\n\n
\n
1.2.5<\/h4>\n\n
\n
1.2.4<\/h4>\n\n
\n
1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.11<\/h4>\n\n
\n
1.1.10<\/h4>\n\n
\n
1.1.9<\/h4>\n\n
\n
1.1.9<\/h4>\n\n
\n
1.1.8<\/h4>\n\n
\n
1.1.7<\/h4>\n\n
\n
1.1.6<\/h4>\n\n
\n
1.1.5<\/h4>\n\n