• Role Scoper is a comprehensive drop-in replacement for capability enforcement and administration in WordPress. Assign reading, editing or administration roles to users or groups on a page-specific, category-specific or other content-specific basis.

    Existing WordPress roles are honored by default, but with Role Scoper can be:

    • supplemented with content-specific role assignment
    • disregarded if a section (category) or object (page/post) is marked exclusive

    Scoped role requirements and assignments are reflected in every aspect of the WordPress interface, from front end content and navigation to administrative post and comment totals. Content administrators control who can view/edit/administer specified content, and what content anonymous users see.

    Section and object roles can be set to propagate to child sections/objects. User groups can be created and assigned roles. Choose whether unqualified front-end content is hidden or replaced with a customizable teaser. The object role assignment UI indicates where users have a role implicitly applied through another blog, section or object role assignment. Other plugin and core developers will be interested in the underlying users_who_can function, made possible by a new roles storage schema.

    The abstract data model and API support additional data sources, object types, capabilities and taxonomies (using term_taxonomy or other custom schema). If your plugin uses the WordPress current_user_can function and supports filtering of its listing query, you can use Role Scoper’s API to define your data source, object types, sections and scopeable roles. These will supplement any other assigned roles; there is no need to merge all capabilities into one all-inclusive role.

    Role Scoper is currently a public beta release.

Viewing 13 replies - 16 through 28 (of 28 total)
  • The full description of version 0.9.13, linked above, was there for a little while, but now it is gone.

    I wish to allow registered users to contribute some articles on my blog. The problem is if a contributor user logs in, he presently sees the title of all the drafts, future posts from all the users.

    I will want the contributing user to know the count of only his drafts or future posts and not of any other user. I will not want him to even see the title of such posts.

    Can this be achieved by this plugin?

    I want some people to only have ONE page of their own where they can update their content. And the headline should be MEMBERS.

    For instance – one member is called Kirsten Iversen (Title then Kirsten Iversen and when people click on this link their page will open with the info). She and the admin should have the rights to make changes and update.

    And then another member called Werner Andersen and this as a tittle and like Kirsten iversen and so.

    Would it be easy to do this? And if yes please tell me how?

    Do I as an admin make the pages ready when a new member subscribe to the blog and then give the person rights for only this page?

    Thread Starter Kevin Behrens

    (@kevinb)

    @jayant,

    Yes, Role Scoper’s Admin filtering is designed to work just as you describe. Posts which the user cannot edit will not appear in the Edit Posts / Edit Pages list. The published / future / draft counts also pertain only to what the user can edit (although since WP does not actually provide hooks to do that, the filtering code is messy and will need testing with each WP release to ensure that functionality is not broken).

    Thread Starter Kevin Behrens

    (@kevinb)

    @tinem,

    1. Create a Page named Kirsten Iverson
    2. While editing the page, scroll down to the “Contributors” tab (under “Advanced Options”)
    3. In “Contributors” tab, select the “exclusive” checkbox
    4. In “Editors” tab, select the “exclusive” checkbox
    5. In “Editors” tab, select Kirsten
    6. Save the Page

    Now only Kirsten and Administrators can edit the page.

    Note that Role Scoper will not create these pages automatically for you. I’m not sure what you mean by “the headline should be MEMBERS”. If you want, it’s fine to make a Members page with “Kirsten Iverson” etc. as a subpage. That won’t affect these instructions.

    thanks kevinB, looks good will have to try it out.

    Would Role Scoper solve this problem?

    We have a firm blog that requires “peer” review from management and from legal prior to publication. Could Role Scoper be used to define a new role for “reviewer” which would allow them to preview a post prior to publication without giving them the ability to edit or to publish the post?

    Thread Starter Kevin Behrens

    (@kevinb)

    Actually, you could do it without Role Scoper if you don’t already use private posts for some other purpose. The post could be published with “keep private” checked.

    Install Role Manager to perform the one-time operation of defining a new Role “Private Reviewer”, with the capabilities “read” and “read_private_posts”.

    Then assign your user(s) the “Private Reviewer” role.

    After the review is completed, and editor / administrator would need to remove the “keep private” setting.

    If you need to control visibility per-post or per-category, Role Scoper could be used (and would make the Role Manager operation unnecessary).

    Thread Starter Kevin Behrens

    (@kevinb)

    If anyone has had trouble getting Role Scoper to force the listing of private pages to users who have a sufficient role assignment, try this manual code patch.

    That function was working with the hidden content teaser enabled, but not otherwise. Will include this in the next plugin revision.

    great plugin – thanks. however, its so useful, that i am attempting to us it on an WordPress MU 2.6 installation also. seems generally to work ok so far as i’ve tested, however the following warning message is produced:


    Warning: Illegal offset type in …../htdocs/wp-content/plugins/role-scoper/admin/filters-admin_rs.php on line 1259

    when i select admin, links, edit link.

    any idea what might be causing this (it looks a bit worrying)?

    thanks in advance

    Hi Kevin,

    I have downloaded Role Scoper and followed all of your instructions. However, when I log in as anything but the administrator and click ‘manage’ and then ‘posts’ it says no posts found.

    Any idea what I’m doing wrong?

    Thanks.

    i do not know if this is related.
    i am using Role Scoper, but now anonymous user cannot view my private page. how do i enable it so that anyone also can view those private pages?
    thanks in advance

    Hi all, I’m having some trouble with role-scoper 1.0.1 and 1.0.0 (however, 0.9.27 works fine).

    As soon as I activate the plugin, I get a white page with this error:

    WordPress database error BLOB/TEXT column ‘group_name’ can’t have a default value for query ALTER TABLE wpcdgitest_groups_rs MODIFY COLUMN group_name text NOT NULL default ” made by activate_plugin, do_action, call_user_func_array, scoper_activate, scoper_db_setup, scoper_update_schema
    WordPress database error BLOB/TEXT column ‘group_description’ can’t have a default value for query ALTER TABLE wpcdgitest_groups_rs MODIFY COLUMN group_description text NOT NULL default ” made by activate_plugin, do_action, call_user_func_array, scoper_activate, scoper_db_setup, scoper_update_schema

    Sorry for the lack of formatting, but that is how it kicks out in firefox.

    Here are my server settings:

    * Operating System : WINNT
    * Server : Microsoft-IIS/6.0
    * Memory usage : 14.26 MByte
    * MYSQL Version : 5.0.27-community-nt
    * SQL Mode : STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
    * PHP Version : 5.1.6
    * PHP Safe Mode : Off
    * PHP Allow URL fopen : On
    * PHP Memory Limit : 128M
    * PHP Max Upload Size : 10M
    * PHP Max Post Size : 8M
    * PHP Max Script Execute Time : 3600s
    * PHP Exif support : Yes ( V1.4 )
    * PHP IPTC support : Yes
    * PHP XML support : Yes

    I’m using WordPress 2.7.1

    What changed from role-scoper 0.9.27 to 1.0.0 that would make it throw like this?

    Thanks!

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘New Plugin: Role Scoper’ is closed to new replies.