I have carefully gone over all the current roles/permission plugins I could find and as it turns out, Role Scoper to work is the only plugin that I have found that do the two things I definitely require.

- It hides all media and posts by other authors on the admin panel. None of the other plugins seem to offer that capability. It is important that my users cannot see each others content in the back-end.

The biggest problem I see with using it though is when I enable the plugin it hides all the standard content as I would expect. However,  all of the posts that reside within custom post types my theme designer built-in (projects and news) are then shown but the authors can no longer edit their own! How strange.

When I disable the plugin, the user goes back to being able to see all the standard posts/media but then can only see their own projects/news posts.

I need for both to work at the same time.

A little background on how the themw works:

In order to use the theme's built-in custom post types, you are required to create a page, assign a built-in custom template. In my case, I chose to make a page called MUSIC ARTISTS, I selected the PROJECTS template.  That somehow enables the content posted in the PROJECTS post type to show up at the address http://www.website.com/music-artists.  Each new project represents one artist.  That artist needs to only be able to edit his or her own project.

I think you probably get the idea….

Role Scoper doesn’t seem to fully recognize the theme's custom post types.  It lists them in some places, such as: Additional Object Roles and Post Type Usage, Object Scope but not on the role definitions pages.

Am I missing something here? I sure hope you can help. I didn’t realize, but this is one of the first things I should have figured out when setting this all up because it is really important.

I really appreciate any help you can offer.

Wordpres 3.1.1
Role Scoper 1.3.29
Prestige Theme 1.4

yeah tried to uncheck them, but when I refresh the page, they are checked agin.  I looked at the note and I have no idea how or where the theme designer would put his registration calls.

something else I noticed:

on the restrictions tab post/page/projects/news are all now shown in the list.  However upon furter inspection of each, the post/news/projects offers tick boxes for reader, contributor and editor. But the pages offer tick boxes for reaader, contributor, editor and associate.

I am confused.  Where is author in that list and where did associate come from?

- Sorry for all the posts.  I am just trying to get a hold of all this.

rajaito said:

I also attepted your wp-config fix and some interesting things happened. Under Realm, with all of the tick boxes next to pages/posts/projects/news selected:

- The projects and news config box showed up on the RS role definition page. However, their corresponding links in the user's admin bar dissapeared.  I tried to access the project list directly and got a "Cheatin huh?" message.

- The authors written posts/categories are no longer shown under the posts link.

I also checked to make sure the post/project/news roles had read/edit capabilities on the RS Role Definitions Tab.

You also need to assign the desired roles.

Enabling the post types for RS filtering causes type-specific capabilities to be required for them. Using Roles > General, you can assign the "Project Author" and/or "News Author" role to the group "[WP Author]" or directly to any desired user(s).

rajaito said:

something else I noticed:

on the restrictions tab post/page/projects/news are all now shown in the list.  However upon furter inspection of each, the post/news/projects offers tick boxes for reader, contributor and editor. But the pages offer tick boxes for reaader, contributor, editor and associate.

I am confused.  Where is author in that list and where did associate come from?

- Sorry for all the posts.  I am just trying to get a hold of all this.

With normal role definitions, there is no difference between assigning a "Page Editor" and "Page Author" role for a specific page. The "edit_others" capability is not necessary when you have already indicated that the user should be able to edit the specific page. If you customize the role defs such that separate object-assignment of the Author and Editor roles is meaningful, see Roles > Options > Advanced > Additional Object Roles.

The Associate role enables a user to select the specified page as Page Parent even if they can't edit it. Of course, this only pertains to hierarchical post types.

rajaito said:

I searched for "init" and did not find something refering to registering types, however I found the code below.  Could this be related?

 add_action('init', array(&$this, 'add_filters'), 0);   

---

Possibly, but Role Scoper 1.3.33 should make this a non-issue for you.