Did you check the "Restrict" checkbox?

The restriction and role assignment are two separate settings. By setting the restriction, you are effectively "taking the role assignment away" from a class of users who have it implicitly by default. That may seem redundant for the Page Reader role, but really isn't. To restrict a user from reading a page, you must restrict each role they own implicitly. So even after you restrict the Page Reader role, all Contributors will still be able to read it unless you also restrict the Page Contributor role, etc, etc.

When dealing with the editing roles, the separation of role restriction and role assignment becomes even more important. You may want to give certain low-level users the Page Editor role for a particular page without forcing the manual assignment of that role to every WP Editor who can edit it by default!

ok

so this is my setup

All pages set to restricted as default

- Visitors to the website can still see pages

All pages set to restricted as default and pages marked private

- Visitors to the website can see all pages except for private

So I kind of have it working now by;

Creating a new page

Set to private

Creating a new user

Setting user as specific page editor

He can now read and write to only this page

However when in the user login, he can see the tabs for roles and restrictions?

Aslo unles the page is marked private both the files associated with this page and page itself are visible to the public even though I have labelled them restricted in the admin section.

ccmjr said:

ok

All pages set to restricted as default

- Visitors to the website can still see pages

I'm having trouble confirming this on my test installation. What versions of WP and Role Scoper are you running? Have you modified the Role Scoper Options at all?

ccmjr said:

ok

All pages set to restricted as default

- Visitors to the website can still see pages

This is fixed in the updated development snapshot (rc9.9222.b).

The error occurred for any Page Roles which were Default-Restricted and did not have any page-specific Unrestrictions set. Likewise for Posts. It is not a new bug, but has existed since the inception of the Default Restrictions feature.

Thank you for reporting this bug.

The bug you found will be present in all versions prior to rc9.9122.b That would include any development snapshot you downloaded prior to 10 minutes ago, and any stable version.

I confirmed that the fix correct file attachment filtering along with the corresponding Page access.

For the Default Restrictions fix you need the development snapshot.

If you are uneasy using a development version and can live with the bugs fixed since rc9.9216,
download the current stable version and modify query-interceptor_rs.php as follows:

change:

elseif ( ! empty($objscope_objects['unrestrictions'][$role_handle]) )
  $objscope_clause = " AND {$src->cols->id} IN ('" . implode("', '", array_keys($objscope_objects['unrestrictions'][$role_handle])) . "')";

to:

elseif ( isset($objscope_objects['unrestrictions'][$role_handle]) ) {
  if ( ! empty($objscope_objects['unrestrictions'][$role_handle]) )
    $objscope_clause = " AND {$src->cols->id} IN ('" . implode("', '", array_keys($objscope_objects['unrestrictions'][$role_handle])) . "')";
  else
    $objscope_clause = " AND 1=2";
}