On fresh install of Drupal 5.1 and 5.2
I created a role "auteur linux"
than a user "eddylinux" with the roles "auteur linux"
I added a vocabulary with the term "linux", "windows", "other"
than I grant "create" permision only for term "linux" for the role "auteur linux"
but when I login with my user "eddylinux" I'm able to create a page in "linux", "windows" or "other" categories
I'm also able to view and list node
I've missed something ?
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | Notes on Setting up a Secure Client Area Drupal.doc | 23.5 KB | glassbyd |
Comments
Comment #1
nwe_44 commentedhave you checked to see what permissions are given to "authenticated user", roles will inherit permissions from there.
Comment #2
doudweb commentedpermissions given to "authenticated user" : access comments, post comments, post comments without approval, access content.
even if I dissallow all permissions for "authenticated user", my user "eddylinux" stilll can create content in all categories.
Comment #3
nwe_44 commentedI meant have a look at "authenticated user" permissions in Taxonomy Access permissions, not the core permissions dialog.
Comment #4
doudweb commentedok I changed permision for "authenticated user" in "Taxonomy Access: Permissions"
nothing append, I'm also able to create with my user "eddylinux" in all term of my category ... I tried :
role "auteur linux" > categ1 > term linux > view = deny ; update = deny ; delete = deny | create = unchecked, list = unchecked
with
role "authenticated user" > categ1 > term linux > view = deny ; update = deny ; delete = deny | create = unchecked, list = unchecked
:(
Comment #5
iradi8 commentedI was having a similar issue. No matter what I set in Taxonomy_access permissions, authenticated users could edit anything they wanted. After much jiggering the problem was corrected when I went into the main Drupal Access Control (Administer>>User Management>>Access Control) and DISABLED "edit page content" and "edit story content" under Node Module.
Once I did this Taxonomy_access started working and users were only able to add and edit content for taxonomy they had rights to!
Comment #6
cdesautels commentedI have this exact same problem. Taxonomy Access Control is simply not working. All roles continue to have full access to pages they shouldn't. The only changes in behavior I get is that when I go to the edit page of a page I shouldn't even have access to, the "unallowed terms" don't show up in the taxonomy pulldown menu. But I can edit, save and publish the pages as if the module weren't even installed.
I'm using a fresh install of Drupal 5.3 and I've followed the instructions in the help section to the letter several times. I've also followed the procedure detailed on this page precisely, http://drupal.org/node/153686..
The module is just not doing anything.
Comment #7
jjohnsonBLC commentedI found a solution by tampering with the authenticated user role, which seems to be applied to every logged in user.
I wish I had been paying a bit more attention to what I did when I fixed this for myself, but I I think my solution involved something like unchecking everything that the authenticated user can do, submitting, rechecking "view content", and then submitting one more time.
I had a role that was not allowed to view any content at all, but I found he was able to view everything. The only thing I had checked for authenticated user was that they could view content. Once I did the steps I just listed above, the role was no longer able to access anything. I hope this helps.
Comment #8
glassbyd commentedThe other thing to remember is after working on the permissions for the role in Access Control is also to change the Taxonomy access permissions for that role as well (as mentioned above)
Comment #9
glassbyd commentedAs an extra I have added my notes written for`the site owner. If they help fine - if they don't sorry but it works for me { and if you spot an error then please feel free to help me after all I'll probably need it}
Comment #10
thomasmurphy commentedsubscribing
Comment #11
thomasmurphy commentedahh, TAC applies everything set for authenticated users to all other roles because they are logged in as someone! I was going crazy denying "create" rights for some categories for one user group, and all the time is was being overridden by the authenticated users groups. ahhhhhhhrrrghhh........and relax =)
Comment #12
xjmIn a nutshell, the authenticated role's permissions will affect specific roles, and core edit/update permissions for the content type(s) must be disabled in order for TAC to affect it.
See:
#358178: Elaborate relation to core node permissions
#165848: TAC permissions overriden by core?
This should be improved in the module's documentation.