Hierarchical ordering of terms in field Taxonomy: All Terms

This has at least two style problems:

1) { should never be on a line by itself.
2) $ary is not a good variable name. Nor is $filt -- Drupal coding style chooses readable names for variables most of the time. $ary is also bad because it has very little meaning. It should probably be something like $terms.

Beyond that: This patch is pretty crude because, really, it is just one of many ways that someone might want to re-order the terms, and it only works if you have your terms set up a particular way. So it satisfies your use case and pretty much only your use case.

What would be better would be to create some kind of hook that would allow an external entity to control the ordering. Possibly some kind of ordering plugin though the complexity rises. This is mostly a presentation issue, so doing it as a theme function might be acceptable, though it wouldn't actually change the output, just re-order (and possibly add or remove) terms that are then rendered later in the pipeline.

Additional using recursive methos to make ordering is afaik not the fastest way: http://www.php.net/manual/de/function.uasort.php should be the better way

No updates to patch in more than 3 months.

Thanks for the patch. I was looking for this exact feature in views. Would be great to see it committed to Views proper.

Thanks so much for this patch! Looks like the maintainers don't like it, but at a high level, this patch makes a lot of sense. Taxonomy is all about hierarchical categorization and it would be great if the Taxonomy: All Terms field respected hierarchy by default.

I found hook_views_pre_render too difficult to use as a novice Drupal/PHP programmer. It was given as a potential solution in a similar issue.

This may appear as an edge-case to some, but hierarchy is very common in taxonomies. I bet you a lot of people just gave up looking for a solution to this :). This issue is something that's been bugging me for years and I've given-up looking for solutions a few times :). Thanks Shawn_S!

I've made the code changes as suggested by merlinofchaos and fixed a warning - "Invalid argument supplied for foreach()" which occurred if no terms are attached to a node.

Please don't suggest that a 'Won't fix due to uncorrected problems' as a "the maintainers don't like it". One of the primary maintainers asked for changes - that suggests that the maintainers, did, in fact, think it was worthwhile. We can't leave issues just sitting around forever though, and not much work is happening in 6.x at this point.

Since stevehart808 made the changes, I'll happily set it back to 'needs review' - thanks steve!

Sorry corrected the last patch so its against the latest dev version.