what's the appropriate hook to theme taxonomy/term/n pages?

I think the default layout of this is to just list all the node teasers. In this case, you can edit your node-tpl.php file to customize what you want a teaser to look like, And of course you can override specific types by creating a node-blog.tpl.php, node-story.tpl.php, etc.

...But if you want to add a special header or footer over this page listing, then I guess the above won't help. You would have to find a way to customize this in your page template file.

Change $tid by you current term id and it should help.
http://drupal.org/node/104316

I ended up making some progress on this, after a few hours of teeth grinding :P

Unfortunately, I still didn't figure out how to theme taxonomy listings (besides the whole page.tpl.php override mentioned above) in the usual Drupal theming way (e.g. like overriding node.tpl.php or node-contenttype.tpl.php).

However I did get the "taxonomy_term" default View working, and was able to then theme its output the way I wanted to. So in case it helps anyone, I'll go ahead and outline the steps and provide an export of my View, as well as a copy of my views-list-taxonomy_term.tpl.php file and CSS. I'm reconstructing the steps after the fact, so if there are any glitches, please let me know. If it proves helpful (and people can provide any additional tweaks or fixes), I'll be happy to make a version in the Drupal Handbook.

I'm sure this is old news for some people... though for us newbies and un-programmers it might be useful :)

Getting started

Of course, firstly you will need to install and enable the Views module (as well as Views Theme Wizard & Views UI). I'm using Views 5.x-1.6 on Drupal 5.2.

You can't have a taxonomy listing without a taxonomy, so make sure you have a vocabulary and some terms set up already in admin/content/taxonomy so you can see the results of your new taxonomy theme. Also make sure you have some nodes tagged with these terms so you have something to list.

Also, I recommend you open up a few tabs in Firefox, each pointing to the same taxonomy listing page. One of them you'll be reloading along the way to keep an eye on your progress... and the other you'll be leaving "un-reloaded" while you work so that you can go back and refer to how it used to look before you blew it to pieces... er I mean, themed it :P

Lastly, if you've somehow survived the CSS revolution thus far without the Firebug extension... now's the time to get it (check GetFirebug.com for extra details - and the secret magic button you need most of all is the Inspect button). If you can theme without it... I want your autograph ;)

Setting up the "taxonomy_term" view

Alrighty then. The first step is to go to admin/build/views/import to Import the view which I'll include below (just paste it in, Submit, scroll to the bottom, and hit Save). This will save you "a lot" of steps in adding and tweaking all of the fields to include in the List view (once it's imported, you can go in and adjust things to your needs). In case you don't want to use my exported view, from the admin/build/views page, click the Add link next to "taxonomy_term" in the Default views area. This will create a new "override" view and take you to the edit page for the view to begin customizing. If you go this route you still might want to import a copy of my view for reference on which fields to use - and don't forget you have to use the List view.

Import this custom "taxonomy_term" view at admin/build/views/import
The configuration of this view is meant to approximate the standard fields output in the Garland theme, along with a tweak or two (such as a different date format that I think is more "human friendly").

  $view = new stdClass();
  $view->name = 'taxonomy_term';
  $view->description = 'The taxonomy view with a depth of 0.';
  $view->access = array (
);
  $view->view_args_php = '';
  $view->page = TRUE;
  $view->page_title = 'Taxonomy';
  $view->page_header = '';
  $view->page_header_format = '1';
  $view->page_footer = '';
  $view->page_footer_format = '1';
  $view->page_empty = '';
  $view->page_empty_format = '1';
  $view->page_type = 'list';
  $view->url = 'taxonomy/term';
  $view->use_pager = TRUE;
  $view->nodes_per_page = '10';
  $view->sort = array (
    array (
      'tablename' => 'node',
      'field' => 'sticky',
      'sortorder' => 'DESC',
      'options' => '',
    ),
    array (
      'tablename' => 'node',
      'field' => 'created',
      'sortorder' => 'DESC',
      'options' => 'normal',
    ),
  );
  $view->argument = array (
    array (
      'type' => 'taxid',
      'argdefault' => '1',
      'title' => '%1',
      'options' => '0',
      'wildcard' => '',
      'wildcard_substitution' => '',
    ),
    array (
      'type' => 'node_feed',
      'argdefault' => '2',
      'title' => '',
      'options' => '',
      'wildcard' => '',
      'wildcard_substitution' => '',
    ),
  );
  $view->field = array (
    array (
      'tablename' => 'node',
      'field' => 'title',
      'label' => '',
      'handler' => 'views_handler_field_nodelink',
      'options' => 'link',
    ),
    array (
      'tablename' => 'users',
      'field' => 'name',
      'label' => '',
    ),
    array (
      'tablename' => 'node',
      'field' => 'created',
      'label' => '',
      'handler' => 'views_handler_field_date_custom',
      'options' => 'F jS, Y',
    ),
    array (
      'tablename' => 'node',
      'field' => 'body',
      'label' => '',
      'handler' => 'views_handler_field_teaser',
    ),
    array (
      'tablename' => 'comments',
      'field' => 'add',
      'label' => '',
      'options' => 'Add new comment',
    ),
    array (
      'tablename' => 'term_node',
      'field' => 'name',
      'label' => '',
      'options' => 'link',
    ),
  );
  $view->filter = array (
    array (
      'tablename' => 'node',
      'field' => 'status',
      'operator' => '=',
      'options' => '',
      'value' => '1',
    ),
  );
  $view->exposed_filter = array (
  );
  $view->requires = array(node, users, comments, term_node);
  $views[$view->name] = $view;

Custom "views-based" theming for your taxonomy term pages

First I should note: I made this while using the standard, unmodified Garland theme... it may not come out quite right at first in other themes (different CSS classes, HTML tag order, etc), but with a little tweaking and adjusting CSS class names and the order things appear in the HTML, it should be possible to get it whipped into shape in your own theme.

Your next stop will be the Views Theme Wizard at admin/build/views/wizard

Here you select the name of the View that you want to theme (in this case taxonomy_term: The taxonomy term with a depth of 0), and select Simple List for Theme Type. Press the Select Theme Type button to proceed.

First text area: template.php
Now in your text editor, open your theme's template.php file (or make one if one isn't present - if you're making a new template.php make sure you add the <?php tag at the top before anything else). Select all the code in the first text area and copy/paste it at the bottom of template.php. I won't waste space pasting mine here since your copy will be exactly the same.

Second text area: views-list-taxonomy_term.tpl.php
Click in the second text area, select all, and copy/paste this into a new blank file in your text editor. Save this file in your theme's directory as views-list-taxonomy_term.tpl.php.

Third text area: CSS
We're going to ignore the CSS text area. For some views you make, sure the CSS here might be useful (well, maybe - the CSS/code here doesn't tend to be on the "lean and mean" side)... but in this case we've already got the CSS in our theme that styled the taxonomy listing "the old way". We want to add those same classes to our HTML as a starting point, and then just modify the CSS to make our amazing redesign of taxonomy listings.

Just for encouragement, head over to one of the tabs you opened earlier of your taxonomy listing and reload it. It looks a bit weird right now (don't worry, we'll get to that)... but holy smokes it works!

Customizing the HTML and CSS to make things look... right

You've probably noticed that the code in views-list-taxonomy_term.tpl.php looks a bit scary. However once we brush away some unnecessary stuff it will look a whole lot more welcoming (HTML "can" look welcoming... can't it? haha).

If you want to take the easy road, young grasshopper, then just erase everything you pasted into the file and replace it with my example code below. For the more adventurous (and of course anyone with a theme besides Garland)... start by removing ALL of the div tags that surround PHP variables that say "$something_label". Also, you can keep it for reference if you want, but you can delete the whole area between the <?php and ?> tags so nothing remains but plain old HTML (also remove the drupal_add_css part, since we won't be needing it).

views-list-taxonomy_term.tpl.php that emulates Garland's taxonomy listings

<div class="taxonomy-list-item">

<h2><?php print $title?></h2>

<span class="submitted">
  <?php print $created?> &#8212; <?php print $name?>
</span>


<div class="content">
  <?php print $body?>
</div>

<div class="clear-block clear">
  <div class="meta">
    <div class="terms"><?php print $term_node_name?></div>
  </div>

  <div class="links"><?php print $add?></div>
 </div>

</div> <!-- /taxonomy-list-item -->

Addition to style.css
I also added the following CSS to my style.css file, as it helps get elements back in their proper positions, and also gets rid of the unordered list bullet points that appear by default next to every field in the view (this overrides a default CSS class in system.css and/or style.css of Garland - it only applies "within" a view, so it doesn't affect other areas of the page, such as the menu where you actually "want" the lists to behave this way). You can also go all out and restyle these any way you want.

/**
 * Styling for Taxonomy Term Listings
 * Recycles some classes from the default style so we can override/customize separately
 */
.taxonomy-list-item {
  border-bottom: 1px solid #E9EFF3;
  padding: 1.5em 6px;
}

.taxonomy-list-item .content {
  margin: 0.6em 0;
}

/* Showing this class since you might want to set it to float: none; */
.terms {
  float: right;
}

/* Removes all list item styles within the View */
.view .item-list ul li {
  list-style-image: none;
  list-style-position: outside;
  list-style-type: none;
  background: none;
  margin: 0;
  padding: 0;
}

Now theme away!

Your taxonomy listings now look just about the same as they did before - but now they're completely editable! Go forth Drupal theming ninja... design great and wonderful things :)

A few quirks - maybe others can improve these bits

• I couldn't figure out how to get the additional class of "inline" into the list of taxonomy terms that seems to give extra spacing around each term... e.g. <ul class="links inline">
• My HTML and CSS hasn't been tested yet in a eh... particular browser... ah hem... if anyone would like to confirm it works feel free.

-- Dave
absolutecross.com

Some solutions in this thread are based on using Views.

If you want to do it with taxonomy, try the solution mentioned here
http://drupal.org/node/135130

Hi, i am looking this too.

But for my case... in taxonomy/term/n...
I only want to display some fields from the node.
Thanks

I'm trying to get this to work as well. What I don't understand is why taxonomy terms/vocabs are treated as pages and not similar to how node templates work. What you'd ideally what is to implement a template for a certain vocabulary or even a term or a specific term id in a vocabulary. Something like:

taxonomy-vocab-term-tid.tpl.php
taxonomy-vocab-term.tpl.php
taxonomy-vocab.tpl.php
taxonomy.tpl.php

But that's unfortunately not how it currently works (which I think is weird). Almost as if it's been forgotten. I was expecting that there would be template_preprocess_taxonomy hook where I can create the template suggestions based on the path just as I can do for nodes and pages.

The way it currently works is not very flexible becuase it only allows me to create a template for 'taxonomy', as if all taxonomy is the same. I have plenty of vocabularies that are totally different from each other and I'd like to display them in their own distinct way.

Not sure how I'm going to some this in a non-hacky way or without lots of duplication... Any suggestions are welcome.

- Luke