Forum Discussion
Andrew Silcock
Jun 14, 2017Steel Contributor
Warning - Modern Pages on Existing (None Microsoft Teams) SharePoint sites - Lots of things broken
Hi all, I've been creating New Site Pages on standard SharePoint sites in order to utilise the Modern pages on our Sites. Everyday at the moment I am discovering more and more issues with usi...
pnthrzrule
Oct 03, 2017Iron Contributor
I agree totally with Number 5 in your list - the New button fakes read only users out by letting them get to the Name Your Page screen.
To make matters worse...the error that read only users get is ridiculous. It says the error is "unexpected" well...what was unexpected was the fact that a read only user even saw the add new page button in the first place.
This all resulted in me having to rebuild 2 new pages with the old wikis
Andrew Silcock
Oct 06, 2017Steel Contributor
Hi Michael,
I logged a support ticket and the latest I heard is "Product team has now finding the root cause of this issue from code level and re-directing it to the correct team who owns the feature. Hopefully the fix won’t be too long. ".
- pnthrzruleOct 11, 2017Iron Contributor
Here is something I noticed in testing.
- Create new classic site collection
- Grant "everyone except external users" access to the "members" group (Contribute permission level)
- Create new modern site page
- All users have ability to add a new page (+new button) as expected
- Edit top level permissions for "members" group to "Read"
- Now all users have only read access to the page
- +New button does NOT show on site page (expected behavior)
- Access permissions for "Site Pages" and break inheritance
- Edit unique permissions for site pages by changing the members group to "Read"
- Result is that users now see the +New button and get an unexpected error when they use the button and try to save the page.