!name isn't working

this is true! I have the same issue!

I have tested this with 6.x-1.1 and the code from the DRUPAL-6--1 branch from the cvs repository and I can't recreate your bug.
I have tried it on a specific term of a vocabulary and vocabulary wide and it works for both.

Can you give any further information so I can try to reproduce the error? For example:
What you are putting in the path field and what paths are actually being produced?
are you running any other modules that might be interfering with paths or links?

Hi

I debugged about 2 hours to find out the source of the problem:

!name is not working in views 2.0 rc5. To reproduce this issue, create a list with all words of a vocabulary and configure taxonomy redirect for this vocabulary. Add a view with an unordered list somewhere in your test environement.

Cause:
Because the l() method is called from the views module, the $term variable has not all properties.

$term->name for example is missing.

After hours of testing I added the $term->name property in the views_handler_field_taxonomy.inc in the views module. After this correction taxonomy redirect worked.

File:
modules/views/modules/taxonomy/views_handler_field_taxonomy.inc

Around line 44 function render_link()

  /**
   * Render whatever the data is as a link to the taxonomy.
   *
   * Data should be made XSS safe prior to calling this function.
   */
  function render_link($data, $values) {
    if (!empty($this->options['link_to_taxonomy']) && !empty($values->{$this->aliases['tid']})) {
      $term = new stdClass();
      $term->tid = $values->{$this->aliases['tid']};
      $term->vid = $values->{$this->aliases['vid']};
      
      //Add this line, and taxonomy redirect will work again
      $term->name = $values->term_data_name;

      return l($data, taxonomy_term_path($term), array('html' => TRUE));
    }
    else {
      return $data;
    }
  }

Maybe someone can confirm or test this issue.

Thanks for the extra info.

I have fixed this in the taxonomy redirect module in 6.x-1.2 so you don't have to modify any other files.

So you can now un-modify views_handler_field_taxonomy.inc in the views module and it will still work.