Select which vocab to display images from in a view ...

I don't suppose you allow profile images that the author can upload and use the "Author Information" block from the profile module?

If NacyDru's solution didn't solve (are the Authors actual users on the system? if so, enable profile, turn on user images in your theme settings.) The relationships you are describing do not seem to jive with that, though (there is only one author of a drupal node) so read on, if not...

I think there are a couple of data-modeling issues here.

Taxonomy-image defines a 1->many relationship (put all the images that apply to a thing in there) between taxonomy images and nodes. What you are describing is a many->many relationship, where multiple images are assigned to a single node, sometimes in the same category (Authors) but you only want to see only one (arbitrarily, the "first")

I think your data model for Authors and it's relationship to images and nodes is more complicated then what taxonomy image is designed for (Nancydru: I think you can better speak on this.) and there are alot of tools for doing this sort of thing with nodes, which might be better suited to serving as the the entities involved (Podcast/Issue with Authors - blog only has one author, who is actually a user of the system, so in that case use the above profile image)

Here is one way to solve:
Use something that makes more sense for your data model: CCK imagefields + node associations. Make a content-type that describes Authors, attach imagefield to them. Use some form of node-reference to pull Author information into Podcast display/editing.

Here are some ways to do that:

• Use a CCK nodereference field. Play with content-type display settings until you get it right, or use theming to make something more specific. You can also use custom PHP code in a block, or even use a view-block to display stuff, too. If you need to do something fancy with the node edit form, use simple form_alter in a module.
• Use http://drupal.org/project/relativity with views
• Use http://drupal.org/project/nodefamily with views
• Use http://drupal.org/project/nodehierarchy with views

this compares 2 or 3 of them.

When choosing from several modules that you don't know, look at development activity, who developed it (do they write good code?) and do google searches for comparisons. This can sometimes be frustrating, and slow, so something you know may be a lot faster.

The last one has a drupal 6 version, and seems slightly more active, recently, so I'd probably look at that first, if the first option didn't work (I like to use as few modules as I can easily, and efficiently: Views and CCK is already installed...) Also, my brain hurts when I have non-standard, complicated relationships between nodes, and I have to juggle the weird specialized ways that a bunch of modules do some special little task. Sometimes it's the way to go, if things are simple, and it does just what you need (taxonomy_image will be that for alot of situations), but sometimes it's just better to break out your swiss-army knife and widdle something special (CCK+Views+theming fields/nodes/views can do just about anything, really)

In ronan's description of their module here, they say:

I have found though that if you find yourself trying to force a hierarchical structure onto your data in order to use this module, you might be better off using a more manual solution with node reference and views.

This may apply to your data model.

When I am working on data-modeling, in any language, or on any platform here's what really helps me, it may help you:

1. draw little boxes representing things with arrows going 1 or 2 ways to show relationships. Write in any fields that the joins happen on, if that's important (not really here, everything is joined on nid, maybe field names...)
2. Color code them if it's too much data (red for 1-many, blue for 1-1, green for many-1, etc)
3. Find the absolute simplest way, that is manageable, to describe that relationship without "working against the tools", write pseudo-code if it needs some logic to manage it, or in this case: if it needs complicated theming/display options, stub out type-based theme pages with comments, or at least make little drawings of what the form/display fields should look like
4. Make a throw-away version of drupal (or whatever the application base/framework/setup is) that you can just test ideas on. Try making a simple version that tests your ideas (don't invest alot of time)
5. Look for all the places that it seems clunky, or over-engineered. If you find too many, try another idea. If you're doing it right, it should be simple and manage itself
6. If you don't find too many bad spots, go back and fill it in, and polish it up. Copy it over to your dev site

This may be more then you need for a simple relationship, but when I start to feel like I have too many models floating in my head, that's what I do.

TI does not, and probably never will, allow more than one image for a single term. You may, however, select multiple terms, each of which may have an image.

Actually, to be more precise, a given node may only have one author at a time. Each revision (if you use that feature) may have a different author and they could all be retrieved with a bit of creativity (as I do in IndexPage).

I have a similar need on one web site and solved it by creating blocked user accounts for the non-member authors. Kind of hokey, but it works for me since I have very few of them.

Well, I can maybe give you some theme code that can be modified to do this.

I'm not sure that filtering on an image makes sense. You can, however, filter on terms already. Doing that should limit which images are displayed.

A patch would be wonderful. I have learned more about Views2 recently, but am far from what merlinofchaos (Earl) would even classify as a "beginner." I might be able to fix this now for you, but am afraid I might break everyone else's site. I am sort of drawn back to konsumer's suggestion of using Image Attach in your case.

Here's a theme snippet you can use which seems to work ok for me:

<?php
$termarray = taxonomy_node_get_terms_by_vocabulary($nid,6);
  foreach($termarray as $ta) {
    $imgtid = $ta->tid;
  }
print taxonomy_image_display($imgtid);
?>

The integer "6" above is $vid - the vocabulary ID. Change to suit your installation.

taxonomy_node_get_terms_by_vocab is documented here:

http://api.drupal.org/api/function/taxonomy_node_get_terms_by_vocabulary/5

Your mileage may vary. HTH.

This version of Taxonomy Image is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.