Closed (fixed)
Project:
Taxonomy Access Control
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Feb 2005 at 09:15 UTC
Updated:
23 Feb 2005 at 21:15 UTC
Jump to comment: Most recent file
Now that I'm using the new taxonomy_access module (CVS), I'm discovering some odd behavior in selecting permission catagories. If I "save category permissions" on an empty set of permissions (no checks in boxes and no adds or removes selected), a pattern of permissions (one that I did not select) gets automatically generated for any given role. Its the same terms that generate the same permissions for the rolse each time.
Also, the defaults don't seem to carry over to other vocabularies and roles... hmmm, am I missing something here? Thanks in advanced for your help!
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | term_data.pdf | 34.07 KB | bomarmonk |
| #9 | node_access table.pdf | 10.93 KB | bomarmonk |
| #8 | term_access defaults table.pdf | 17.34 KB | bomarmonk |
| #7 | term_access table.pdf | 176.21 KB | bomarmonk |
Comments
Comment #1
pyromanfo commentedThe default sets the permissions for that role for the categories in that vocabulary. So it's working as intented
Also if you have any of the dropdowns set to add or remove it's adding or removing that permission for the categories in that vocabulary for that role.
Comment #2
pyromanfo commentedActually, how I described defalult is somewhat inaccurate. Default sets the permissions for that role for new categories in that vocabulary. It doesn't change any existing categories, only the dropdowns do that.
Comment #3
bomarmonk commentedOkay, but any idea why taxonomy access is generating unwanted permissions (checks in boxes). It's odd. Here's the example:
I have a role called "administration." I can "remove" all the checks in the boxes just fine. I can also add permissions by checking boxes, but with limitations. If I give the "administration" role permissions to "view," "update," "delete," and "create" for the category, "administration," taxonomy_access automatically generates the same permission for another term in the same vocabularly. It also fills-in the checkboxes for another, seemingly random term. The only way I can be rid of these auto-filled checkboxes is to not select the desired permissions. Argg! It's simply not doing what it's supposed to. I'm not sure if this is because of the module or because of some corruption in my database? Would erasing my roles and recreating them get rid of the problem? Or is this a bug in the CVS release of this module? Thanks again for looking into this.
Your explanation of the default box makes sense...
Comment #4
pyromanfo commentedCould you give me the contents of term_data, term_access and term_access_defaults?
I'll take a look at it, sounds like a bug.
Comment #5
bomarmonk commentedPyro, can you give me an e-mail so I can send you .pdf files of my tables? I've printed the pdf's from phpMyAdmin so you can see what's going on with the database-- including node_access, term_access, and term_access_default.
I have cleaned out my node_access table, deleted the term_access tables, uninstalled the taxonomy_access module and started over. I still get the same result (even after simplifying my roles to one role per user-- I had multiple roles assigned to each user)-- still permissions are getting added when I don't select them. I reinstalled the old taxonomy_access (4.50-- non CVS) and everything seems to work fine, but without the added features...
I hope I can help you do some bug hunting!
Comment #6
pyromanfo commentedCan you just attach them here? Unless your term_data holds sensitive infomation (in the descriptions maybe?) there isn't anything but category names and a bunch of numbers in those tables.
Comment #7
bomarmonk commentedYou are exactly right... here is the term_access table in .pdf format...
Comment #8
bomarmonk commentedThe term_access_default table....
Comment #9
bomarmonk commentedThe node_access table... that should do it, if I understand the tables involved in this module. Thank you for looking into this! I hope you solve the mystery.
Comment #10
pyromanfo commentedThanks for the help, could I get term_data as well?
Comment #11
bomarmonk commentedAh, yes, after looking through this table, I suspect the problems are somewhere in here: if some the numbers seem slightly misaligned, I changed some of the names to keep them generic, but I changed nothing else in the report of this table. I hope it helps
Comment #12
bomarmonk commentedAny luck? Is there still a way to access the version of Taxonomy Access with check-boxes at the top of each vocabularly? They worked in much the same way as the drop downs and there was the "create" field for catagory permissions. I think this version worked with my setup. I would go back to the 4.50 version, but it only has "update," "delete," "create," and "view." Just checking... thanks for your help. Once I can get it working right, this module will do wonders for the site I am building!
Comment #13
pyromanfo commentedI'm gonna look at it tonight.
Are you not seeing any create permissions now? I haven't changed how that works since I added them in the first place.
Comment #14
bomarmonk commentedI tried reverting back to 4.50 (the most recent version that download from the module page). I deleted and reinstalled the tax_access table, etc. The module does give me a "duplicate" error when I first enable it, but it seems to work fine after that... but "view," "update," and "delete" are the only options for my category permissions. There are also only checkboxes for individual terms in this version, not for the larger vocabularies.
Hope that helps explain my situation.
Comment #15
pyromanfo commentedOh okay yeah that's just really old, I'll try to fix your problem tonight.
Comment #16
pyromanfo commentedI think I finally fixed it, try the latest CVS.
Comment #17
bomarmonk commentedBingo...almost everything is behaving the way I would expect it to behave now. Good work! The only thing that behaves a bit differently is the default box. It seems that these boxes are filled in automatically for every vocabulary, no matter what I do. Perhaps this is by design, and I still don't fully understand the "default's" function yet.
Comment #18
pyromanfo commentedDo you mean it's setting all the permissions on for each default, regardless of what you check/uncheck?
It's not doing that on mine, though I don't think I've disabled and enabled it, when I do that, it should set 'view' and 'create' for any defaults you didn't already set.
The latest CVS has better docs, if you're still unclear.
Comment #19
(not verified) commentedi think the problem is $vids array with duplicate values. for a vocabulary, hidden form-item with 'name=vids[] value=x' is written twice, one top of vocabulary and the other top of defaults.
the solution is either using array_unique for $vids or not outputting the second hidden form-item with 'vids[]'.
both works for me.
Comment #20
pyromanfo commentedDidn't notice that, fixed in CVS. Thanks.
Comment #21
(not verified) commented