Note that this is also included in the Hierarchical Select module.

In fact, just yesterday, I committed *more* hierarchical term formatters: #308823-12: More hierarchical formatters for Taxonomy fields.

Back in the D6 days, it didn't make sense to put this in a separate module. But now in D7, it does. Would you be interested to include all of the hierarchical term formatters from HS as well? I'd then remove them from HS and point my users to this module instead :)

(Less code duplication, more focused modules, less bloat in HS, which already is a far too large module!)

Comments

zoo33’s picture

zoo33 commented

Sounds reasonable. I wasn't aware that Hierarchical Select did formatters as well. Only I kind of liked the idea of a really tiny module that would need little to no maintenance. :) How about a co-maintainership in that case?

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Exactly :)

Well, I can tell you that the hierarchical formatters in HS were a case of "commit and forget" — there's nothing that can go wrong, so co-maintainership is fine by me :)

BenK’s picture

BenK commented

Interesting. This makes a lot of sense. Please keep us updated in the Hierarchical Select issue queue when the formatters change over.

--Ben

zoo33’s picture

zoo33 commented

I guess the first step is to make a quick overview of what's different between the two modules' formatters, and what should be added/changed. How similar are they?

Another question: how should we deal with upgrading/migrating sites from Hierarchical Select to Hierarchical Term Formatter? Just documentation, or some automatic migration?

mrpeanut’s picture

mrpeanut commented

I realize this issue is from April, but I'm looking to use one of these two modules, and am wondering if they will still be merged. I'm using Hierarchical Select right now, but am wondering if I should use Hierarchical Term Formatter instead. Any updates or thoughts on this?

awolfey’s picture

awolfey commented
Issue summary: View changes

I'm a new maintainer of the module catching up on the issue queue. If this is still needed please reopen the issue. It sounds like a good idea, but it's been a couple of years. Thanks.

awolfey’s picture

awolfey commented
Status: Active » Closed (won't fix)