Hiya,

I really like this module and being able to set what powers the content that will get shown; however, I do not see a way to actually set where that associated content can appear (even with Display Suite; it shows up after all the other DS fields). Any help with this would be greatly appreciated.

Comments

codycraven’s picture

codycraven commented
Category: support » feature

BTMash, you're the second person to request that functionality. I previously had decided to not add it as there is a module Views Field View that is under active development that achieves the functionality.

Please note I haven't attempted to use Views Field View, so if it doesn't work please let me know and I'll work up some sort of solution.

btmash’s picture

btmash commented

What I ended up doing was using EVA to create the view that I wanted and displaying that (though that had its hurdles over something views field would have probably been a lot easier on. And I then use Taxonomy Display to disable/hide the view handler.

Even though I solved my issue, it still does seem like Taxonomy display handling that aspect would be better as it would avoid taking some of these steps for other users.

codycraven’s picture

codycraven commented

BTMash, you've convinced me. I'll begin working on a solution to allow placement as a field -- may take some time to get to though.

btmash’s picture

btmash commented

Awesome! I'll be able to take a look at the module sometime early next week and hopefully I can be of some help as well :)

btmash’s picture

btmash commented

While I didn't end up getting a chance to look at this code, I'm trying to change up how the taxonomy stuff works at #1067120: Missing hook_taxonomy_term_view() or hook_entity_view() when viewing a term. Letting you know that in the odd event that it goes further than it is currently at, it would affect this module.

Anonymous’s picture

Anonymous (not verified) commented

I just wanted to chime in and mention that you can expose a views block as a field using Display Suite. However, I agree it would be really nice to simply have the results handler exposed as a field directly from the Taxonomy Display module.

Great module. Combined with the Taxonomy Menu module, terms are now first class citizens!

checker’s picture

checker commented

+1
I hope it is possible to add this feature. I really like it!

checker’s picture

checker commented

Alternatively you can use viewreference (http://drupal.org/project/viewreference) but you need furthermore this module to hide taxonomy core display.

codycraven’s picture

codycraven commented

Well I started to write up a big post about the different implementation methods we could choose from with strengths and weaknesses of each so that we could make a community decision on whether this should affect all taxonomy build modes or just the taxonomy term pages.

After getting a fraction of the way through writing the strengths and weaknesses the decision was 100% clear. For maintainability of the module going forward we should leave build modes of taxonomy terms (outside of the term page display) up to other modules that are well suited for handling those displays, such as Display Suite.

This means we will either have an Associated Content field that is either always available, or only available after selecting a checkbox in the Taxonomy Display form, and this will only affect the taxonomy term page build mode.

So as soon as I get time to work on this, I'm currently strapped with projects at my work, I will be able to begin work with a clear direction.

If anyone would like to contribute a patch for speeding this process along I will be ecstatic to review it.

codycraven’s picture

codycraven commented
Assigned: Unassigned » codycraven
btmash’s picture

btmash commented

@codycraven, One simple way to do this would be by having an extra field (implemented using hook_field_extra_fields which would check on which option the user chose. Then have that get displayed (if it is meant to be displayed via hook_entity_view_alter the patch mentioned after pulls through). If its not, and you get to see how that happens, then it won't get any results for that display. I had been trying this out for #1067120: Missing hook_taxonomy_term_view() or hook_entity_view() when viewing a term in one of the patches and think part of it would likely fit in here in a better way.

codycraven’s picture

codycraven commented

Indeed I was thinking along the same lines, thanks BTMash.