views - contextual filter - how to get term name, not term id

Not sure if I understood your issue, but Drupal allow you to use the replacement pattern {{ name }} directly in the Title field of your view:

see:

Yep
My view DO have a contextual filter, but it is not expanded.
And yes, I understood your point. What I am saying is that you don't need to use this override title behaviur inside contextual filters. If you just use the tag directly you can have the result that you want to achieve.
If you pass a different term id as a contextual filter parameter, the {{ name }} will change according the taxonomy id.

Ok! Good luck :)

This is not critical per https://www.drupal.org/core/issue-priority

Also, you show a screenshot where your replacement in the title override is different than the actual available replacements, so this is kind of confusing.

Also, this should work, take a look at the drupal 8 default taxonomy view, that is using a replacement pattern and prints out the term name fine (even if the machine name of the replacement is confusing, I agree, but it description explicitely says it will print the title). I tested with depth as well and works fine.

view config

output

fyi, I'm having the same issue as @websiteworkspace. Here the contextual filter is on a reference field. For example list the contacts of a company.

A contact has a field company_reference and the contextual filter is on that one.

And while I'm typing this I think of a workaround:

* Add the relation to the target entity.
* Use the ID contextual filter.
* Override title and use the correct replacement pattern. Now the title is shown.

I have the same issue and I figured out, that it reproduces only when you use node's taxonomy term reference field for contextual filter. (In my case field_category).
I replaced it with "Has taxonomy term id" contextual filter and now it shows term's title instead ID.
But I suppose it still a bug, because in D7 it worked even with reference fields.

Hello,

I think feature could be great. Let's me explain another case.
Content type A has Taxonomy Vocabulary 1
Content type B has Taxonomy Vocabulary 2

Some terms could be into Vocabulary 1 and 2 (but ID are different).
If i want to display with view some related content, for example displaying onto content A page related content from content B, i can't use taxonomy ID. I must use taxonomy name.
It was possible with Drupal 7, but not anymore with Drupal 8.

But maybe i mess something ?

Best regards,

+1 ..same problem for me. I want to override views title with contextual filter's label.

See https://www.drupal.org/project/views_taxonomy_term_name_into_id for a related problem that might actually give many of you what you need. That gives you tokens for both the ID and the label, and generally results in more efficient queries. Good luck.

Hi,

I've encountered the same issue. I tried many things and some patches but nothing was working. (and I wanted another field than the term name, so it is even more complicated)

I thought about a simple trick that works great waiting the solution directly inside views. I have just written a Twig Extension to get the data that I want. I pass the term id in the twig function and then I load my term and extract the data I need.
The override title input in the view configuration allows you to use twig, so this workaround should work. I hope it will help some people.

I post the example if someone want it. I've written it really quickly, you should use a dependency injection to load you Term and add some checks :)

use Drupal\taxonomy\Entity\Term;

/**
 * Class DefaultService.
 *
 * @package Drupal\demo_module
 */
class TwigExtension extends \Twig_Extension {

  /**
   * {@inheritdoc}
   * This function must return the name of the extension. It must be unique.
   */
  public function getName() {
    return 'tvshows_config';
  }

  /**
   * In this function we can declare the extension function.
   */
  public function getFunctions() {
    return array(
        new \Twig_SimpleFunction('taxonomyFieldFromId', array($this, 'taxonomyFieldFromId'), array('is_safe' => array('html'))),
    );
  }
  /*
   * This function is used to return alt of an image
   * Set image title as alt.
   */
  public function taxonomyFieldFromId($id, $field_name) {
    $field = '';
    $term = Term::load($id);

    if (!empty($term)) {
      $field = $term->{$field_name}->value;
    }

    return $field;
  }

}

There is a way to use term related information in content/node views, it is through Relationships. It was already mentioned previously in this issue but I guess it wasn't clear enough.

Entity reference fields store only the ID of the entity they are referencing. It wouldn't make sense to copy **everything** about the term into the node that is tagged with the term.

Term information is held in its own database table, separate from the place where content/node data is. Views is a tool that builds queries **after** you've chosen the base table to pull info from. When you're building Content Views the content table is used as the base, when you're listing users then the users table is being used as the base, etc.

There is a way to pull related data from other tables into your Views. It is done through Relationships.

If you have Content Views you only have the term ID number available as a Contextual filter, out-of-box that is. But if you add the **Relationship** for the taxonomy reference field you are making all the term data available to this View!

So after you have added the Relationship for the taxonomy term into your Content Views, the **Name** Contextual filter becomes available it's in the Taxonomy term Category. That Category is added and made available on the Contextual filters list after adding the Relationship!

I'm aware that you don't need the Relationship to show the term names in Fields, but that was done through some extra code, Formatter "magic".

In D7 more "magic" was done especially for Taxonomy module in Views so you can do stuff without adding Relationships, but we can view those as extras because you can still build Views to behave the same, it's just a slightly different procedure (add Relationship). I don't know why some parts weren't ported to D8, it probably wasn't straightforward.

And adding special features for Taxonomy module only doesn't help a lot of other similar cases where we're referencing other entities. For example when referencing article Content type nodes from Basic page nodes. To build Views that list related nodes contextually we have to use Relationships, even in D7.

I'd love to have the extra Taxonomy support in Views if it optimizes the query performance or helps in some other way (usability), but otherwise I don't see it as a bug and I'm ok with having to add the Relationship for extra info.

BTW there is a bug related to relying on Taxonomy term Names to filter - if you have a term with the same name in different Vocabularies - vocabulary validation isn't working properly: TermName views argument_validator is not working as expected

There is also the issue of standard views filters. If you have an entity with a reference to some sort of taxonomy and you expose the filter to visitors, it will still want to reference tags via ID and not name. This issue is more difficult to workout because if you configure a relationship, it will not give you the same options to allow them to select from a dropdown/autocomplete and instead gives a textbox.

In the case of a 'tags' property, you don't want to make the visitor guess as to what tags may exist for a given entity (say, we tag our blog posts of Node entity with descriptive terms like 'educational' or 'personal'). If you want to give your users a dropdown list to choose from, this will cause the tags to insert IDs as url parameters and not the name property.

I'm still looking for a solution to this since we have an e-commerce site with products tagged with taxonomy terms as descriptors. Commerce's custom taxonomy module is quite buggy and results in a lot of weird errors when working with views (issues with parent terms when nesting tags, etc.)

Will probably need to write a custom views filter plugin or something along those lines to get this to work, e.g. when I filter products by something like 'clothes' I want the url parameter to be 'tags=clothes' instead of 'tags=43'.

There is a module that does the exact opposite: https://www.drupal.org/project/views_taxonomy_term_name_into_id
Maybe code there will help you.

In any case, what you ask would be nice for drupal core.

UPDATE: if you check into admin/structure/views/view/taxonomy_term you will see how Drupal core does it.

As maintainer of https://www.drupal.org/project/views_taxonomy_term_name_into_id I should clarify. What it does is add an argument validator plugin for taxonomy term arguments to convert human readable names into term IDs.

So if you have a view like /news/%category

You can use the term ID argument (better queries) but the URLs to access it can be stuff like:

/news/international
/news/environment
...

See the docs on the project page for more.

But this is only for contextual filters (aka "arguments"), not regular exposed filters.

Cheers,
-Derek

See #2640994: Label token replacement for views entity reference arguments not working.

There is a solution but not a terribly pretty one. Include this in your .module file:

function yourmodule_views_pre_render(ViewExecutable $view) {
  if ($view->id() == 'name_of_your_view' && $view->current_display == 'machine_name_of_your_view_page') {
    $tid = $view->args[0];
    $view->setTitle(Term::load($tid)->label());
  }
}

Or any variation of this, depending on where your contextual filter is in the args, or what you want to put into the title. And if you have more than one view, you have to cover all of them. And if you change the name or add another view, you have to keep the code in sync. And if you're one of those who only mouse around in Drupal but won't write your own code, well, you're hosed. :-)

Thank you, now I'll just have to figure out how to add i18n support.

Edit

Posted my code here: https://drupal.stackexchange.com/a/298186/7177

To put this into perspective, the proper way to do this would be to write a route enhancer and, in its `enhance()` function, set your title with:

$defaults['_title'] = ...whatever

The problem is a still outstanding bug: https://www.drupal.org/project/drupal/issues/2981183 causing the system not to pick up the modified title. Hence the need for this view altering hack. If it worked, Views could probably incorporate it easily by default.

I faced same issue, #9 provided by maxdev is solved my issue.

I was facing the same issue and since I want to show a custom entity on the taxonomy page not "node" solution in #9 didn't work for me so instead I added a relationship using my term reference field and then used Taxonomy term: Term ID in contextual filter.

i like solution #16 and I created relationship with field_catalog: Taxonomy term
then I created a contextual filter (field_catalog: Taxonomy term) Taxonomy term: Name

and I see after the replaced name has this

replacement tokens

{{ arguments.field_catalog_target_id }} == Product: Catalog (field_catalog) title
{{ raw_arguments.field_catalog_target_id }} == Product: Catalog (field_catalog) input
{{ arguments.name }} == Taxonomy term: Name title
{{ raw_arguments.name }} == Taxonomy term: Name input

I chose {{ arguments.field_catalog_target_id }} to Override title of the view
but it aint working

I also tried
{{ arguments.name }} and not working....still figuring out....Drupal 7 got that working nicely....
so this is still unresolved?

I also added new field and it shows up the category name very well, but only in field not in the view name
(field_catalog: Taxonomy term) Taxonomy term: Name

Basically my product terms are called Catalog (earrings, rings, pendants) ......

I created 3 contextual filters
Product: Catalog
(field_catalog: Taxonomy term) Taxonomy term: Name
(field_catalog: Taxonomy term) Taxonomy term: Term ID

and tried replacement patterns, nothing works

I have 6 replacements patterns now and none of them works
{{ arguments.field_catalog_target_id }} == Product: Catalog (field_catalog) title
{{ raw_arguments.field_catalog_target_id }} == Product: Catalog (field_catalog) input
{{ arguments.name }} == Taxonomy term: Name title
{{ raw_arguments.name }} == Taxonomy term: Name input
{{ arguments.tid }} == Taxonomy term: Term ID title
{{ raw_arguments.tid }} == Taxonomy term: Term ID input

i confirm this is a bug, because it should show up

https://pasteboard.co/zEQzZZYJ91v2.png

rossidrup: This works:

https://www.drupal.org/forum/support/post-installation/2013-03-15/how-to...

Keep your relationship, erase all of your contextual filters, add one to field-catalog: Taxonomy Term: Term ID
And replace title with {{ arguments.tid }}
That's all!

Solution https://www.drupal.org/project/drupal/issues/2912332#comment-12898360 works foe me without any patch. Drupal 9.4.5

I was using two custom entities and attempting to change the title - the "proper" solution doesn't work because the custom entities (as generated by Drupal console) don't have a title, they have a name.

I had to use the solution in #22, adapted for the correct entity names.

#9 worked for me in combination with https://www.drupal.org/project/views_taxonomy_term_name_into_id