Access Denied after page modified

%3CLINGO-SUB%20id%3D%22lingo-sub-1505929%22%20slang%3D%22en-US%22%3EAccess%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1505929%22%20slang%3D%22en-US%22%3E%3CP%3EUsers%20are%20getting%20an%20Access%20Denied%20message%20on%20a%20page%20they%20previously%20had%20access%20to%20(and%20they%20are%20still%20showing%20as%20having%20Read%20permissions)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20page%20was%20edited%204%20days%20ago%20but%20the%20changes%20weren%E2%80%99t%20published.%20I%E2%80%99m%20wondering%20if%20the%20problem%20might%20be%20something%20to%20do%20with%20that%20(though%20of%20course%20normally%20this%20wouldn%E2%80%99t%20matter%20-%20people%20should%20still%20be%20able%20to%20see%20the%20current%20version).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1505929%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1507811%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507811%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112079%22%20target%3D%22_blank%22%3E%40David%20BROOKS%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20minor%20and%20major%20version%20activated%20on%20the%20library%20page%3F%20Were%20they%20in%20the%20%22visitor%22%20part%3F%3C%2FP%3E%3CP%3EIf%20you%20have%20minor%20version%20activated%2C%20in%20the%20library%20setting%2C%20under%20the%20section%20%22version%20history%22%2C%20which%20option%20is%20ticked%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Vertebre85_0-1594184745456.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F204034i1A9B41A60B191865%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Vertebre85_0-1594184745456.png%22%20alt%3D%22Vertebre85_0-1594184745456.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EIf%20it's%20not%20%22any%20user%20who%20can%20read%20items%22%2C%20they%20may%20not%20see%20it.%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1507877%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507877%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F492370%22%20target%3D%22_blank%22%3E%40Vertebre85%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20page%20library%20has%20%22%3CSPAN%3EOnly%20users%20who%20can%20edit%20items%22%20selected.%20However%20this%20applies%20to%20all%20our%20page%20libraries%20and%20the%20issue%20is%20only%20being%20reported%20for%20one%20specific%20page.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%26nbsp%3B%22any%20user%20who%20can%20read%20items%22%20is%20selected%20I%20assume%20this%20means%20users%20would%20see%20unpublished%20drafts%2C%20which%20we%20don't%20want.%20They%20should%20just%20be%20seeing%20the%20previous%20published%20version.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E(As%20a%20workaround%20I%20am%20going%20to%20try%20publishing%20the%20page%20to%20see%20if%20this%20sorts%20out%20the%20problem)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1507937%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507937%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112079%22%20target%3D%22_blank%22%3E%40David%20BROOKS%3C%2FA%3E%26nbsp%3BI%20forgot%20to%20ask%3C%2FP%3E%3CP%3EWith%20the%20current%20setting%2C%20the%20page%20version%2C%20was%20it%20lower%20than%201.0%3F%20if%20there%20is%20at%20least%20a%201.0%20they%20should%20see%20the%20previous%20published%20page.%20If%20there%20was%20no%20version%201.0%2C%20the%20page%20is%20%22not%20existing%22%20for%20people%20with%20no%20edit%20right%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1507980%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507980%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F492370%22%20target%3D%22_blank%22%3E%40Vertebre85%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20current%20version%20(which%20people%20should%20be%20seeing)%20is%205.0%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1508044%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1508044%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue..Only%20difference%20is%2C%20my%20sitepages%20has%20workflow%20enabled.%20So%20the%20page%20was%20in%20the%20state%20%22Review%20approvals%22%20when%20people%20tried%20accessing%20gave%20access%20denied%20error.%20After%20publishing%20it%20was%20accessible.%3CBR%20%2F%3E%3CBR%20%2F%3EFrom%20my%20understanding%20people%20should%20be%20able%20to%20see%20the%20last%20published%20version%20at%20least%20not%20access%20denied%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20appreciated.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1508320%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1508320%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92321%22%20target%3D%22_blank%22%3E%40Ankita%20Pillai%3C%2FA%3E%26nbsp%3BI%20dont%20know%20if%20this%20helps%20but%20we've%20solved%20the%20mystery.%20The%20page%20is%20giving%20Access%20Denied%20because%20the%20author%20deliberately%20un-published%20it%20in%20order%20to%20hide%20out%20of%20date%20information%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1508342%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20Denied%20after%20page%20modified%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1508342%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112079%22%20target%3D%22_blank%22%3E%40David%20BROOKS%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20author%20accidentally%20edited%20the%20page%20again%2C%20and%20submitted%20for%20approval%20again%20and%20forgot%20to%20review%20the%20approval.%20But%20for%20a%20page%20which%20was%20already%20once%20published%2C%20should%20we%20(the%20others)%20not%20see%20the%20already%20published%20version%3F%20Why%20are%20they%20getting%20the%20access%20denied%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Users are getting an Access Denied message on a page they previously had access to (and they are still showing as having Read permissions)

 

The page was edited 4 days ago but the changes weren’t published. I’m wondering if the problem might be something to do with that (though of course normally this wouldn’t matter - people should still be able to see the current version).

 

7 Replies
Highlighted

@David BROOKS 

Do you have minor and major version activated on the library page? Were they in the "visitor" part?

If you have minor version activated, in the library setting, under the section "version history", which option is ticked?

Vertebre85_0-1594184745456.png

If it's not "any user who can read items", they may not see it.

Regards

Highlighted

Hi @Vertebre85 

 

That page library has "Only users who can edit items" selected. However this applies to all our page libraries and the issue is only being reported for one specific page.

 

If "any user who can read items" is selected I assume this means users would see unpublished drafts, which we don't want. They should just be seeing the previous published version.

 

(As a workaround I am going to try publishing the page to see if this sorts out the problem)

Highlighted

@David BROOKS I forgot to ask

With the current setting, the page version, was it lower than 1.0? if there is at least a 1.0 they should see the previous published page. If there was no version 1.0, the page is "not existing" for people with no edit right

Highlighted

@Vertebre85 

 

The current version (which people should be seeing) is 5.0

Highlighted

I have the same issue..Only difference is, my sitepages has workflow enabled. So the page was in the state "Review approvals" when people tried accessing gave access denied error. After publishing it was accessible.

From my understanding people should be able to see the last published version at least not access denied error.

 

Any help would be appreciated. 

Highlighted

@Ankita Pillai I dont know if this helps but we've solved the mystery. The page is giving Access Denied because the author deliberately un-published it in order to hide out of date information

Highlighted

@David BROOKS 

The author accidentally edited the page again, and submitted for approval again and forgot to review the approval. But for a page which was already once published, should we (the others) not see the already published version? Why are they getting the access denied?