Posted by NaX on April 5, 2011 at 3:25pm
2 followers
Jump to:
| Project: | Taxonomy Access Control Lite |
| Version: | 6.x-1.4-rc3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
I needed to change a few things in tac_lite, attached is my custom module that changes a few things and adds a few things.
There is a settings page @ admin/user/access/tac_lite/mod
These are the options you will see:
-Show on user create form
-Show on user edit form
-Remove user account category tab
-Show user categories on profile page
I don’t know if the way I did it was the best way and most correct. I also don’t fully understand how tac_lite works, but this seems to do what I need it to do.
Hope somebody else find this useful.
| Attachment | Size |
|---|---|
| tac_lite_mod.tgz | 1.7 KB |
Comments
#1
FYI: As I posted the issue I found that the install hook is changing the weight of tac_lite when it should be tac_lite_mod.
#2
I tested your module and I found it to be really convenient! Everything is loaded in a single page.
I have an idea that I'm not capable of doing though. My site has over 90000 terms with two access schemes. That just means the individual access control (site/user/N) page will have to load more than 180000 terms upon display and again after access updates. I had to alter server settings to allow a longer timeout to set the permissions and reset it back to normal (30-60 seconds) afterwards.
My idea is, can the select list be changed to an auto-complete text field, just like the one we use when tagging terms in the node create page (node/add/page or any other content type). It'd be great too if it allows for comma-separated tagging of multiple terms.
#3
@amal850720
Currently my custom module does not really provide its own UI, it uses the tac_lite UI form elements, but if needed I don't see why you can provide alternative UI form elements, but this would require also providing additional submit handlers and validation. I personally will not be doing any additional development on this custom module as it currently meets all my current requirements.
Maybe your should do a feature request for an optional tac_lite UI module that extends the default/basic UI similar to what my custom module does.