After the most recent update to Role Scoper (I believe 1.3.1) all of my users besides the admins (just me) have lost the ability to see any posts whatsoever either on the backend or even on the site itself when they're logged in. I've looked at my set up of permissions in the options area and they are set correctly. My "Authors" are able to do everything that the WP authors are, except publish posts and delete published posts.

One of my users was set to "Editor" and I hadn't made any changes to that role whatsoever (even when as far as syncing the RS role with the WP role) and couldn't see any posts either place either. 

When I deactivate Role Scoper, everything works fine, but the minute I reactivate it goes back to the same problem. Please help!!

This may not be quite what it appears. I was just about to ask you to try forcing a WP role re-sync as follows:

• Go to Roles > Options > RS Role Defs tab
• Check "Re-sync with WordPress roles on next Update"
• Click the Update button

But switching versions also triggers the re-sync, and I suspect that's what just corrected your site.

Role Scoper stores a record in its own table to track each user's WordPress role. I discovered that those were being re-inserted redundantly on each user registration or RS version change / re-activation. So the new code (both 1.2.9+ and 1.3+) runs a maintenance script on version update to delete and regenerate those records. Thought I could get away with that and it tested out okay for me, but it sounds like I will need to make it a manual operation.

Can you move back to 1.3 (at least temporarily) and let me know if your users have normal access with it now?

I haven't been able to recreate this error. If anyone else is seeing it, please let me know.

alnitak said:

I'm seeing a similar problem. When I upgraded to the latest version from 1.2.9 my scoped users cannot publish posts. I reverted to back to 1.2.9 and still they can't publish. HELP!

CHeers,

Pete

This looks like a totally different issue from billyadams'. It actually stems from a bug in the previous version which your configuration was relying on. You had default Post Restrictions set for Post Contributor and Post Editor. That means nobody can edit or publish newly created posts unless they are explicitly assigned as an Editor for that particular post. However, default Post Restrictions were not applied to new posts in your previous version.

Have you set any Restrictions on Pages or page-related taxonomies?

Well, interesting. When I try to check on restrictions to either Posts or Pages I get a note saying "Cheatin' uh?"

Under RS Role Defs -> Page Editor I've got:

  Create Child…
# Delete…
# Delete Others…
# Delete Private…
# Delete Published…
# Edit…
# Edit Others…
# Edit Private…
# Edit Published…
# Moderate Comments
# Publish…
# Read
# Read Private…
# Unfiltered Html
# Upload Files

Under WP Role Defs -> Editor, I've got:

Delete Others Posts
Delete Posts
Delete Private Posts
Delete Published Posts
Edit Others Posts
Edit Posts
Edit Private Posts
Edit Published Posts
Manage Links
Moderate Comments
Publish Posts
Read
Read Private Posts
Unfiltered Html
Upload Files

As for the "Cheatin, uh" on attempting to edit Page Restrictions, does your logged user have the edit_users capability?

For the WP Editor caps, it looks like Role Scoper's "sync WP Roles" action is malfunctioning for the Editor role. It's supposed to just sync post caps to your selections and leave other caps alone, but I can confirm that the current RS version (at least with WP 3.0.2 multisite) is clearing them on the sync request. I'll get that corrected shortly. Sorry about that, but at this point you'll have to use a basic role editor such as Capability Manager to reinstate the capabilities:

read_private_pages, edit_pages, edit_others_pages, edit_published_pages, edit_private_pages, delete_pages, delete_others_pages, delete_published_pages, delete_private_pages, publish_pages.

The Sync WP Editor bug is fixed in Role Scoper 1.3.13. To recover from it, re-save with "Sync WP Editor" checked for your "Page Editor" role definition.

If you prefer to apply the fix manually, edit plugins/role-scoper/submittee_rs.php as follows:

add:

after: