'Taxonomy-based access' category inside 'My Account' is visible for any user
kndr - February 21, 2009 - 11:57
| Project: | Taxonomy Access Control Lite |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
'access callback' should be defined inside function 'tac_lite_user' for $op = 'categories'. Without it, it causes problems with i18n - tab 'Taxonomy-based access' inside 'My Account' is visible for all users.
| Attachment | Size |
|---|---|
| category_access_callback.patch | 606 bytes |
#1
#2
Thanks, just checked this into DRUPAL-6--1. Could have sworn I had made a change like that once before.
Also, I used "administer users" rather than "administer tac_lite", because I think that's more appropriate. Anyone care to disagree?
#3
Automatically closed -- issue fixed for 2 weeks with no activity.
#4
If a user has the "administer users" permission and not the "administer tac_lite" permission then the 'Taxonomy-based access' category is visible on the edit user page. However, if you click the category you get take to 'Page not found'.
Wouldn't the 'Taxonomy-based access' be more appropriate for this?
Alternatively would it be better to make both permissions mandatory and write a short access callback function to check them both (I believe user_access only accepts one access argument).