Taxonomy Access Control doesn't like to play nice with advanced forum, at least not during the setup phase.
I've jiggered with this endlessly, and can sometimes even make it work, but I swear it's by random chance. I realize I'm not the most educated user out there, but a workflow on getting users access to forums based on their role, even a simple sketch, would be most appreciated.
Even if it's something like "don't assign taxonomy access to forums" or whatever I need to do to make it work reliably. As my site grows and I have more roles and more forums, it's becoming impossible to manage in my ad hoc way.
Thanks for any help!
Comments
Comment #1
MaramonJ commentedWhen a user goes to the content creation page to create a new forum topic, the forum dropdown is there, but the list is not populated, so the only choice is "Please choose." Of course it doesn't let them post.
The role has permission under the TAC to create and to view and to list (but not to update or delete).
The role has permission to access forum vocab under Admin->Permissions.
The role has permission to view and post in the forum under Admin->Forum->Edit Forum.
What permission am I missing?
Like I say, I've had it working before, and then I change something and everything stops working, and I'm never sure what or why. Then it takes hours and hours to fix. What am I missing?
Comment #2
michelleAF shouldn't have any effect on this. It has no access control of its own and just uses what forum/node/comment gives it. Sending this over to TAC.
Michelle
Comment #3
xjm@OP: Please update to the most recent release of TAC (6.x-1.2), and take a look at the recently improved module documentation. There were a lot of bugs in the earlier 6.x releases of TAC that have since been fixed.
If you continue to experience the problem described:
I haven't used the Advanced Forum module before, but I'm assuming it is similar to the regular Forum module in that each forum is a taxonomy term in a forums vocabulary.
Comment #4
xjmComment #5
michellexjm: AF just builds on core forum. Most of its work is done in the preprocess layer. There shouldn't be anything to interfere with node access.
Michelle
Comment #6
xjmIn that case I suspect the OP's issue was caused by the node access update bugs fixed in 6.x-1.1, so hopefully an upgrade and node access rebuild will resolve the issue. If it doesn't, I'll help with permissions configuration.
Comment #7
xjmNo response for months. Closing. OP: Please reopen if the issue persists or you need further assistance.