Peter Knight 911 Posted May 29, 2019 I'm getting an error 403 Forbidden when a superuser tries to view any unpublished page and I'm trying to track it down. If I goto Access > Roles > superuser I don't see any permissions but note the "Note: superuser role always has all permissions, so permissions field is not shown." If I visit Access > Permissions > Page View, I don't see anything that is unticked etc I then thought it might be a permission issue on a template level but there's no template-level permissions set there either. Any ideas on next steps? Thanks Share this post Link to post Share on other sites
Peter Knight 911 Posted May 29, 2019 Update: If I edit the home template, I see the following. I don't know if it applies to my issue because the 403 is shown to the superuser, Share this post Link to post Share on other sites
wbmnfktr 1,202 Posted May 29, 2019 Does a clone/copy of that page end in a 403 as well? Are there any hooks or if/else statement in your template that check for specific user roles? Can you find more details in the logs? Share this post Link to post Share on other sites
Peter Knight 911 Posted May 29, 2019 I solved it. This was really odd so I'm glad I found it. The test page I created and had the 403 error on was called /test/ Renaming it to anything other than /test/ worked I used the Finder to search for other pages with the same name and there was a page in the trash created by a repeater called /test/ Normally you'd get an alert when naming a page that there was a similar named page and PW would suggest test-1 I wonder if that's worth putting into GitHub as a bug. Share this post Link to post Share on other sites
wbmnfktr 1,202 Posted May 29, 2019 That's weird. Especially as most/all pages within Trash will be re-named. Share this post Link to post Share on other sites
Peter Knight 911 Posted May 29, 2019 Yes thats what I thought too. The conflicting thrash page is called 1399.1078.22_test in the Settings > Name so it doesn't even conflict Share this post Link to post Share on other sites
wbmnfktr 1,202 Posted May 29, 2019 Ok... is test nowadays somehow... protected within page names? I know about issues in field names (back in version 2.whatever.x) but not in page names. Share this post Link to post Share on other sites