I've found a display glitch when a content type has two autocomplete taxonomy fields, each of which is set to display a different Vocabulary under "Specify terms to show". It's easiest to describe with an example:

Let's say, for the "restaurant" content type, that taxonomy field 1 is set to display terms from the "Cuisine" vocabulary, and taxonomy field 2 is set to display terms from the "Atmosphere" vocabulary. If a restaurant node has both fields set to "Irish", content_taxonomy_field_formatter gets an $item array that contains both the "Irish" term from "Cuisine" and the "Irish" term from "Atmosphere" for either of these fields. Since content_taxonomy_field_formatter isn't filtering the $item array by $field['vid'], both of the "Irish" terms are displayed for each field.

I've attached a patch that does this filtering and fixes the problem for me.

CommentFileSizeAuthor
#2 content_taxonomy.210824.patch905 bytessutharsan
content_taxonomy-specify-terms-to-show-limit-by-vocab.patch475 bytesBiteme

Comments

csc4’s picture

csc4 commented
Status: Active » Reviewed & tested by the community

Great patch thanks - this fixes the problem for me.-

sutharsan’s picture

sutharsan commented
StatusFileSize
new content_taxonomy.210824.patch905 bytes

I have the same situation; two autocomplete content_taxonomy fields. Each assigned to a different vocabulary. Both vocabularies with a depth of 1.
The patch solved the problem.

Attached patch has a little touch of paint added for code style and is placed slightly different in the code to prevent errors if $item is not an array.

thepanz’s picture

thepanz commented

+1 for this patch, works fine!
I created a patch #259302: Add more formatters that includes this one, adding more formatters (list, and linked list), you know, theming terms separated by BR isn't too easy :)

Regards

k8n’s picture

k8n commented

Also here, another version; should have posted my patch here: http://drupal.org/node/261421

socialnicheguru’s picture

socialnicheguru commented

subscribing

Chris Johnson’s picture

Chris Johnson commented

We are also successfully using the patch at http://drupal.org/files/issues/content_taxonomy.210824.patch. I recommend it being applied to the module by the maintainer, since the behavior without it is clearly wrong.

pcorbett’s picture

pcorbett commented
Status: Reviewed & tested by the community » Patch (to be ported)

Patch works for me, too! This is a pretty necessary patch, let's get it committed...

magnus’s picture

magnus commented
Status: Patch (to be ported) » Closed (won't fix)

Cleanup of old issues. According to maintainer: "active development is only done for the 6.x branch! 5.x is not supported any more".
Reopen issue if problem still exist in 6.x branch.