This happens when the page in question uses auth::require_login instead of
permission::require_permission
Not sure of a way around that. The idea of auth::require_login is to require users to have an up to date login session for certain action (at least that's my understanding of it).
Can't see requiring it for checking read permission though.
