Jump to content

Recommended Posts

Posted

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

 

Posted

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?

Posted

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.

 

Posted

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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...