I am developing a website for our Master of Divinity program where I need to restrict most of the site to logged in members.  That part I have been able to design.  These members are assigned the following roles:  Program Administrators , Students, Mentors. 

We assign a mentor/student relationship and would like the mentors and students to be able to collaborate on posts the student would make.   Using Role Manager I have created these new roles.  I have then been able to use Role Scoper to set several WordPress categories to only be viewable at specific role levels.  This has all worked well.  What I am struggling with is how to give specific users (these would be Mentors) the ability to view the private posts of specific other users (these would be students). 

So the scenario would be this:  Student A creates several posts (some private, some public).  Mentor A has been assigned to Student A and therefore needs to be able to view and comment on all of Student A’s posts, both public and private but not able to view the private posts of Student B who has not been assigned to him.

If this website flies I might have several dozen students and a handful of mentors registered at any given time.  Each mentor will have one or more specific students assigned to him/her.  Is this possible with Role Scoper?  If it is, would you point me in the right direction?  I would also be glad to provide you with a login.  The temporary site location is dev.nbseminary.com.

Thanks!

LorenW said:

So the scenario would be this:  Student A creates several posts (some private, some public).  Mentor A has been assigned to Student A and therefore needs to be able to view and comment on all of Student A’s posts, both public and private but not able to view the private posts of Student B who has not been assigned to him.

Here's the most convenient way that comes to mind, assuming you don't need categories for normal categorization purposes (could use tags for that):

* Define a category "Student A"

* Set the user "Student A" and "Mentor A" as WordPress Subscribers

* Assign "Student A" a Category Role of "Post Editor" for the "Student A" category

* Assign "Mentor A" a Category Role of "Private Post Reader" for the "Student A" category

When posting, Student A will have only one available category, and should default to that category (you should test that.)

Kevin said:

---

Here's the most convenient way that comes to mind, assuming you don't need categories for normal categorization purposes (could use tags for that):

* Define a category “Student A”

* Set the user “Student A” and “Mentor A” as WordPress Subscribers

* Assign “Student A” a Category Role of “Post Editor” for the “Student A” category

* Assign “Mentor A” a Category Role of “Private Post Reader” for the “Student A” category

When posting, Student A will have only one available category, and should default to that category (you should test that.)

You should also set "Post Reader" and "Private Post Reader" as Restricted Roles for the "Student A" category.

If the student category approach is not workable, the less convenient solution would be to require "Student A" to assign "Mentor A" as a Reader for each post.

For now, you can prevent the error by editing query-interceptor_rs.php as follows:

add:

                    if ( ! isset($roles[$op_type][$object_type]) )
                        continue;

right before:

                    foreach ( $roles[$op_type][$object_type] as $status => $check_role ) {
                        // If a restriction is set for this object and role,
                        // OR if the role is default-restricted with no unrestriction for this object…

Okay, that nuisance message occurs when you create a group without initially defining any members. I've fixed it for the next Role Scoper revision.

Your group should be created, even with the error message.