Jump to content

pagefileSecure not working when template inherits access rights


dynweb
 Share

Recommended Posts

When editing a template like this:

image.thumb.jpeg.7f2c94ab742641ef147b2107c53d04e4.jpeg

  • As long as a template does not define its own access rights, the option "Yes always, regardless of page status or access control" has no effect: it "sticks" in the admin interface, but the folder /site/access/files/XXX is not prefixed with a "-" and access control is not enforced. The file is delivered by Apache.
  • If the template defines its own access right, it works as expected (by me). The file is delivered by PHP.

It this expected behavior? Is there some good reason why a template must define its own access rights to enforce access control to files?

Thank you for your insights.

Edit: Tested on latest PW stable, pristine install.

  • Thanks 1
Link to comment
Share on other sites

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
 Share

  • Recently Browsing   0 members

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