Access to edit a page not authored

Hi slavallee,

WordPress has a good capability for that which is called “Edit Others Pages”. So if user or user’s role does not have this capability checked, it means user is not able to edit any page except the one he/she is an owner of.

To make an exception for one user you might consider to create a new role like “Extended Contributor” and inherit all capabilities from the Contributor role. Then check Edit Others Pages capability for this role.

AAM Plus Package extension has an option to setup the default access to all pages so you can restrict all pages from editing and allow only few.

Appreciate your interest in AAM.
Vasyl

Hi Vasyl- I enabled ‘edit others pages’ for this one user, but now that user has access to ALL the pages. I went to the ‘Posts & Pages’ tab for the user and found the page I want him to have access to. I checked ‘list’ and ‘edit’ under the ‘BAckend’ header, but he still has access to ALL pages.

What an I missing here?

Thanks.

Nevermind….I was able to set this user as the author of both pages….thanks.

I’m having this same problem. When I restrict access to all pages and then allow access to a specific page, that page never shows up for the user to edit. When I allow access to all pages and try to restrict any individual pages, they are still available to edit.

It seems that the ability to act on individual pages is broken since the latest updates.

Hi Bishop81,

I’m assuming you have AAM Plus Package. What options (List, Edit etc) do you use on Posts & Pages tab to restrict access to your pages?

Thank you,
Vasyl

For the Root > Pages, I have it set:
Backend
List > checked
Add > checked
Edit > checked
Delete > checked

For the Individual Page that should be available:
Backend
List > unchecked
Edit > unchecked

I’ve even tried unchecking things under the main Page settings, and then restricting individual pages, but that doesn’t work for me either.

I’m using version 3.0.7 of the plugin, and have the AAM Plus Package installed.

Hi Bishop81,

You settings for Root > Pages are for the Role or individual User?
Go to AAM and select a user that you have problems with. Then check the access settings for the specific page that is still editable or listed.

Regards,
Vasyl

The settings are for the role. I’ll check the user now, but I was assuming that changing a user’s role would at least reset any user defined settings (of which we never set anyway).

The user has the same settings as the role. Individual page settings are being inherited when they aren’t supposed to.

Hi Bishop81,

Inheritance in AAM is probably one of the most complicated parts of the functionality. At some point it turned to be so complex that we had to give up on multi-role support. That is why it is very important to understand how it work (in our future AAM releases we’ll make sure that this part is explained in an easy way).

Below the example how AAM retrieves the access options for a single page for current user. The inheritance chain stops when the first non-empty set of access options found.

1. Get access options for specific page;
2. Inherit access options from the page parent category;
3. Inherit access options from the User’s default page settings (Root > Pages);
4. Inherit default access settings from the user’s parent role;
5. Inherit page access settings from the user’s parent role;
6. Inherit parent category access options from the user’s parent role.

Regards,
Vasyl

Ok, I’ll read those steps carefully a few times to try and understand how it goes. The real problem is that inheritance was working perfectly at one time. I didn’t change the role permissions or anything, I only performed plugin updates. Now it doesn’t work.

I’ve even tried creating a new role and testing it, but that didn’t work. The page-specific permissions just wouldn’t override the “Role > Page” default permissions. Whether I had default locked down and the page open, or had default open and the page locked down. Nothing I did on the page level was actually being applied.

I know this is marked as resolved, and my issue was slightly different, but I thought I’d let you know that the latest Posts and Pages update fixed my issue.

Thanks!