Unable to assign taxonomy terms to Minutes
| Project: | Minutes |
| Version: | 6.x-1.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
I'm using Views to aggregate items according to taxonomy terms, and discovered that I'm not able to assign controlled taxonomy terms to the Minutes content type. All of the permissions seem to be in order, and I tried to set them through the UI, but the assigned term did not save appropriately - it appeared to be set but didn't stay that way. I set it in the database instead (term_node table), and the Minutes node showed up correctly in the appropriate view. However, once I went in to edit the Minutes node, the taxonomy term was removed once more, so the change is not "sticking".
Also, the Minutes node inherits any tags from the associated event - is this as designed? It seems like it might occasionally be undesirable.
I will be able to work around this issue by adjusting the View once I've finished migrating about 15 years of minutes and attendance into the Minutes node type, but it may be more problematic for others. If anyone can provide an idea of what to look for in the code, I can try to dig around and find the cause of the issue, but I'm really not sure what to look for.
#1
Hi! This is by design; the minutes inherit the taxonomy settings of their parent event, and there is code that updates the terms whenever the parent changes.
What is your use case where you need to have terms on the minutes that are not on the parent?
#2
Oops, sorry, didn't realize that was by design! It was just unexpected. I think I can find other ways to build views that have the content I want, but I didn't expect that I would be able to enable taxonomy on a node type if it was actually completely ineffective. If it weren't permitted, I would have understood the inheritance right away. Perhaps there's a way to make it clear that just because the taxonomy selection field shows up doesn't mean that it does anything, or better yet, disable that entirely?
I need a view that just shows minutes, not the associated events. I'm currently aggregating minutes as page nodes just using taxonomy, but could do a combination of taxonomy and node type. Using taxonomy alone is a little more straightforward to understand and would have worked with my existing views, but it's only a little more complicated to fix the view. Once I finish moving content, that is - trying to keep the view integrated while moving the node content would be too much of a headache for now.
Thanks for the explanation!