Space Admin not able to edit the page

[Leena Bakshi]

Hello,

I am a space admin on a space called ABC( restriction applies) Now in this space I have a page called XYZ and that further has a sub page called 123. When I try to edit this 123 page I get message "Not Permitted- you are not permited to perform this operation."  and I found following in the conlfuence log:

2017-07-10 12:37:32,953 WARN [http-bio-443-exec-1177] [com.opensymphony.xwork.DefaultActionInvocation] executeResult No result defined for action com.atlassian.confluence.security.actions.NotPermittedAction and result cancel
-- url: /confluence/pages/doeditpage.action | userName: L.La | referer: https://confluence.cfs.com/confluence/pages/editpage.action?pageId=87687892

In the Space tool> Permission, I have green checks in all the fields ( All, Pages, Blog, comments,  attachments, restrictions, mail and space) 

In Restricted Pages Permissions, I do have the Edit and View permission on XYZ page. 

Can someone please tell me if I am missing some permission or is it a bug?

We have confluence on local server.

Thanks 

[Jobin Kuruvilla [Adaptavist]]

Did you check if there are any page restrictions on 123 page or not?

[Leena Bakshi]

How would I be able to tell because it shows the path as Follow:

Pages/ABC/XYZ ( with a lock symbol)

123

content of the page 123

However when I am here on this page 123 and  I click on the lock

I see the following

Viewing restricted to : User1 and User2

Editing restricted to : User1,User2 and my userid

and at the bottom it says: This page has restricted parent pages. It can only be seen by users who can see those pranet pages.

Does it make any difference if I am not added to Viewing Restricted to: group?

[Leena Bakshi]

Any further suggestions?

[Jobin Kuruvilla [Adaptavist]]

So, just to clarify, you are able to see Page 123 but not able to edit it even though the restriction on that page includes your id? Also, are you able to edit XYZ page?

[Leena Bakshi]

Unfortunately User didnt get back to us so I am gonna pursue this issue again when user returns again. Thank you for all your help!