Posted by naught101 on September 10, 2009 at 12:55pm
Jump to:
| Project: | Taxonomy Access Control |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
If a user is denied access to a term (let's say "members only"), then that user can still access the term's taxonomy view page (ie. /taxonomy/term/XX), which is generally ok, because it's empty.
I was wondering if there was a way to deny access to that page too? It looks a bit dodgy having an empty page there for anonymous visitors...
If there isn't already a way to do this, consider it a feature request.
Comments
#1
It does seem like it would make sense for term pages to follow the module's access rules.
A workaround might be to use Views to override the taxonomy/term/ pages and then use views to determine the behavior when the page is empty. If there's just one specific page you'd like to hide, another possibility would be to use the path access module to deny access to that page to anonymous users.
#2
#3
#166265: Create and List permissions not working is a duplicate of this issue in the 5.x branch; once it is fixed in 6.x-1.x-dev the fix should be backported to 5.x-2.x-dev.
Until this is fixed, users may wish to try the Path Access module to restrict term pages as a workaround.
#4
Marked #181461: Denied users to be redirected to Register /login page as duplicate.
#5
If your users are seeing empty term pages and you don't want them to, you should uncheck "List" for the term for both that role and the authenticated user role. (Or, in the case of anonymous users, just the anonymous role).
Ideally, you would get a 403 "Access Denied" error; however, the current behavior when permissions are configured properly is a "Page not found" error. See: #311649: "Page Not Found" error for all non-accessible term pages.
Marking as duplicate of that issue.
#6
Fair call. Cheers.