In Views 2, there was a taxonomy term field for node views, that could be limited to one (or more) vocabulary. In Views 3, I can not find this field type anymore, at least not in all views. In some cases it shows up after setting up a relationship to taxonomy, in other cases it doesn't. Maybe this has something to do with the version of Views where the field was created?
Also, the relationship to taxonomy allows to limit the relationship (?) to a certain vocabulary, but this "limitation" is ignored in the term fields. This would be nice if there was a vocabulary limiter in the term field since one would only require one relationship and get access to multiple vacabularies, separated into different term fields. However this seems to bevae pretty inconsistent.
Another observation is that migrated views (that were built with Views 2) seem to not require relationships to access terms of a certain vocabulary; however, this type of term field can neither bei created in Views 3, nor is there a way to "clone" these fields.
'nuff said, I have played for hours with these taxonomy fields in Views 3 and can not make much sense of it. So I'd really appreciate some explanation how this is supposed to work (e.g. put a number of term fields from several different vocabularies into a tabular view).
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | available-taxonomy-fields-a.jpeg | 93.28 KB | asb |
| #1 | available-taxonomy-fields-b.jpeg | 100.29 KB | asb |
| #1 | term-field-limited-to-on-vocabulary.jpeg | 62.92 KB | asb |
| #1 | term-field-without-limitation-by-vocabulary.jpeg | 154.66 KB | asb |
Comments
Comment #1
asb commentedTrying to illustrate:
Number and type of available taxonomy fields (sometimes) stays the same, no matter if relationship of taxonomy exists:
Sometimes this field shows up in Views 3. It's what I want, it allows to limit a term by vocabulary. It's unclear what makes this field available. It's not the taxonomy relationship (or is it?)
Migrated view from Views 2: term field can be limited by cocabulary:
This term field has no option to limit field to a vocabulary:
Comment #2
kars-t commentedDear fellow Drupal enthusiasts,
This issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project, everyone is helping on a voluntary basis. That this was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex, or the problem was not described comprehensibly.
But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and it is a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.
Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.
Help can also be found for it on IRC and in the user groups.
In order to close this issue, I have set this issue to "Closed (won't fix)".
If there is new information, please re-open the issue by changing the status to active.
--
This issue was edited with the help of Issue Helper