Add ability to add taxonomy/term fields to node views in header/footer

That would be a great feature, also for D6

In theory a 100% ctools content type integration could solve this.

Yes, I'd like this too. Or a workaround would be nice.

I have a taxonomy vocabulary of 'client'. I have a term of, say, 'Client One' plus I've created a text field inside each term for the URL called field-client-url and populated with 'www.client-one-url.co.uk' for example.

In the Views Filters UI I cannot display this new field. I can output the term but not this added field.

I'm not sure if this is a Views issue or Taxonomy or Token.

keeping a hopeful eye on this one....

I've boxed myself into a bit of a corner with a current project, and this feature would be something of a life-saver. I've tried a few workarounds for what I'm intending to achieve, but keep hitting brick walls (I can get all the content I want to the page just using the standard term page, but just can't nail the formatting of the content which I've already achieved using views)

The view is getting the title (term name) from the term ID argument although it is a listing of nodes as the view type is node. A general solution would be able to take the description (and other field values) as well as the title from the argument term ID.

Maybe values "retrieved" from the argument could even be provided for header and footer output as a kind of token.

PS
When taxonomy integration is ready for Panels in D7 it could also be done by overriding /taxonomy/term/[termID]

+1

subscribing

OK the term does seem to show the fields, but only when the field 'description' has been filled in. I think this is a taxonomy issue?
OK it was a cacheing issue ignore me but still +1

yesyes

subscribing

Subbing

I think what we really need is a display type that is an area handler. So you make a view display that you can then add as an area handler to other views. That'll solve the problem.

Another solution would be to allow token substitution from the first row in the area handler. Also the title handler. That one's easier to do and easier to implement. But it won't help if you don't actually have fields.

Embed a view in the header of another view is already possible. There is a area plugin view: area

You can also "Inherit contextual filters" and with this you can do exactly what you want.

The tokens would still be a nice one for the Global: Custom Text one, though, and pretty easy now that the tokens are stored so that the style can use them properly.

Ok, checked in a fix for both 6.x-3.x and 7.x-3.x that allows token use in the global text area as well as the title.