Allow entity reference views arguments to display the entity label in titles and summaries

I too have experienced this same problem.

After selecting "override title" in the contextual filter, only the following twig replacement values are available:

{{ arguments.field_taxo_term_prod_category_target_id }}
{{ raw_arguments.field_taxo_term_prod_category_target_id }}

The foregoing values output the term ID in the view title, not the term name.

So, for example, when working with D8 commerce products with a taxonomy field for product category, the result is something like:

Products in Category - 21

where 21 is the term ID of a Product category, when it should display the term name. The 99.999999% use case is that the output should be:

Products in Category - Category0001

-

View ought to provided replacement values like:

{{ arguments.field_taxo_term_prod_category_target_name }}
{{ raw_arguments.field_taxo_term_prod_category_target_name }}

not the ID values it currently provides.

This is a serious bug for which no workaround I have tried works.
It is just bizarre that a basic bug (feature omission) like this has existed for two years since the Drupal 8.0.0 release.

{{ arguments.field_taxo_term_prod_category_target_id }}
{{ raw_arguments.field_taxo_term_prod_category_target_id }}

The functional features of the View operate correctly, except this one, which makes the View rather useless to work since, the dynamic title of the View is essential to its presentation.

In D8 the Views module was moved into core.

Yes, of course we know that views is in Drupal 8.x core.
Someone would have be brain dead not to know that.

This is all the more reason why this bug should have been fixed years ago.

It is absolutely astonishing that this bug, (this omission of an essential feature), has existed for all the years that Drupal 8.x has been in development and production.

This frequently used/needed type of Views contextual filter is basically impossible without:

{{ arguments.field_(some_taxonomy_field)_target_name }}
{{ raw_arguments.field_(some_taxonomy_field)_target_name }}

available as replacement values for use with the Views contextual filter "override title" feature.

@Sinan Erdem

Been around open source for many years, knowing a lot about Drupal, and the machinery of getting bugs fixed.

Meanwhile, THANK YOU !!!!!!

Your workaround works!

Remembering now that replacement patterns from the available fields can be used in a View title!

1. Add the needed field to the field list and set it to hidden if needed.

Then, for the title of the View that traverses the product categories via /taxonomy/term/%

The view title:

Products in {{ field_taxo_term_prod_category }}

Works like a charm, showing the name of the current taxonomy term in the title dynamically.

The workaround from #6 works like a charm!
@websiteworkspace: thanks for the further explanation!

The workaround from #6 worked well for me as well.

But if Breadcrumbs block is used, it doesn't get the twig parsed and shows like 'Home > {{ name }}'

Another (very hacky) workaround is to create a custom twig extension that gets TID and returns term name (Here is a sample)

With that, you can put this in Override Title field:
{{ term_name(arguments.field_tags_target_id) }}

#12 helped me. Thanks.

Same as #12, we can use Twig Tweak: {{ drupal_field('name', 'taxonomy_term', arguments.field_tags_target_id) }}

Solution from #6 is not reliable with multiple entity reference field, it gets first entity from the field value of the last entity on the page, this can be different term from page the user is on now.

Also, Twig Tweak takes care about language of the page is loading and term field value translation for this language. So if you are using Twig Tweak already, this is the easiest and fastest solution.

The following module helps with this.

https://www.drupal.org/project/product_taxonomy_filter

When using the above module the [ override title ] feature on the view's contextual filter may be working correctly now with the token:

{{ arguments.term_product_tid_depth }}

I've created a sandbox for doing this in a language-aware way: https://www.drupal.org/sandbox/andileco/3021338

Im using drupal 8.5 with bootstrap barrio 4 theme. The defauld taxonomy view does not show the Title name of the taxonomy either. In "override title" in the contextual filter, by default show this value {{ arguments.tid }}.
So I opened the twig theme/bootstrap_barrio/template/content/taxonomy-term.html.twig

<

div{{ attributes.setAttribute('id', 'taxonomy-term-' ~ term.id).addClass(classes) }}>
  {{ title_prefix }}
  {% if not page %}
    <h2><a href="{{ url }}">{{ name }}</a></h2>
  {% endif %}
  {{ title_suffix }}

// I added this div class with {{name}}

 <strong> <div class="taxonomy-title-header">{{ name }}</div></strong>

// end

  <div class="content">
    {{ content }}
  </div>
</div>

And magicly the title shows in the top of the view page. I hope that helps.

Here's a first attempt at implementing this. To preserve BC, since people may rely on the workarounds listed above, labels are only displayed if the related option is enabled:

Re-rolled the patch against 8.8.x branch.

Rerolled

Hopefully, the updated patch will solve the failed test issue. added an interdiff as well.

Thanks!

I tested and it works great!

I think it would make sense to also asd this for argument "Has taxonomy term ID" where I guess in many cases it also would make sense to display term name rather than the ID in title.

@matsbla:

I think it would make sense to also asd this for argument "Has taxonomy term ID"

I think I'd be fine either way. It's unlikely I'll have the time to work on that myself though.

Minor performance improvement.

(forgot the interdiff)

The patch in #29 worked well for me! Using Drupal 8.7.3, and a view block with a contextual filter for taxonomy terms to override the block title with the term label versus term id.

#29 working so nicely!!!
Thank you

A short review. Patch looks good.

1. +++ b/core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
   @@ -0,0 +1,199 @@
   +<?php
   ...
   +class EntityReferenceArgument extends NumericArgument implements ContainerFactoryPluginInterface {
   

   Just to be sure. Entity references can only be of the type numeric?

2. +++ b/core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
   @@ -0,0 +1,199 @@
   +    /** @noinspection PhpParamsInspection */
   

   This line can be removed.

3. +++ b/core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
   @@ -0,0 +1,199 @@
   +   * @throws \Exception
   

   Why? And can this be solved without throwing an exception.

4. +++ b/core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
   @@ -0,0 +1,199 @@
   +
   ...
   +    $id = $data->{$this->name_alias};
   

   What happens when $data->{$this->name_alias} is not set?

5. +++ b/core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
   @@ -0,0 +1,199 @@
   +   * @throws \Exception
   

   Why? And can this be solved without throwing an exception.

6. +++ b/core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
   @@ -0,0 +1,199 @@
   +   * @throws \Exception
   

   Why? And can this be solved without throwing an exception.

7. +++ b/core/modules/views/views.views.inc
   @@ -833,6 +833,11 @@ function core_field_views_data(FieldStorageConfigInterface $field_storage) {
   +    // Add a dedicated entity reference argument handler.
   +    $field_columns = $field_storage->getColumns();
   +    $column_real_name = $table_mapping->getFieldColumnName($field_storage, key($field_columns));
   +    $data[$table_name][$column_real_name]['argument']['id'] = 'entity_reference';
   

   I am not completely sure about this code. Can somebody give me some explanation.

1. Just to be sure. Entity references can only be of the type numeric?

\Drupal\views\EntityViewsData::processViewsDataForEntityReferenceassumes this is the case for all content entity types. So I guess it's safe to assume the same.

7. [...] I am not completely sure about this code.

Me too, because this doesn't apply the logic from 1. and changes the argument for config entities, too. I don't think config entities are supported by the patch (yet).

8. I'm wondering how well this works for taxonomy reference fields. taxonomy_field_views_data_alter already adds a custom filter (but forgets the argument handler, that the module also provides). I also find the implementation of that argument handler (Drupal\taxonomy\Plugin\views\argument::IndexTid) quite elegant, can't we go about it the same way (without the bloat)?

To preserve BC, since people may rely on the workarounds listed above, labels are only displayed if the related option is enabled

9. I find this setting rather annoying, since it's redundant with the chosen argument (vs. raw argument). How about we instead use a (post?) update hook that replaces all ocurrences of arguments.field_foo_target_id with raw_arguments.field_foo_target_id? That way, existing views will still work as expected (they're getting the entity id), while the argument title behaves as it should have from the beginning?

Thanks. #25 worked great for me on Drupal 8.7.7

Config schema is missing for *use_label* field, so got error when validating config with Configuration inspector

Updated patch from #29

#37 failed on 8.8

atching file core/modules/views/config/schema/views.argument.schema.yml
patching file core/modules/views/src/EntityViewsData.php
Hunk #1 FAILED at 617.
1 out of 1 hunk FAILED -- saving rejects to file core/modules/views/src/EntityViewsData.php.rej
patching file core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
patching file core/modules/views/tests/src/Unit/EntityViewsDataTest.php
Hunk #1 succeeded at 1159 (offset 25 lines).
patching file core/modules/views/views.views.inc
Hunk #1 succeeded at 891 (offset 58 lines).

#29 failed also on 8.8.2

patching file core/modules/views/src/EntityViewsData.php
Hunk #1 FAILED at 610.
1 out of 1 hunk FAILED -- saving rejects to file core/modules/views/src/EntityViewsData.php.rej
patching file core/modules/views/src/Plugin/views/argument/EntityReferenceArgument.php
patching file core/modules/views/tests/src/Unit/EntityViewsDataTest.php
Hunk #1 succeeded at 1159 (offset 54 lines).
patching file core/modules/views/views.views.inc
Hunk #1 succeeded at 891 (offset 58 lines).

Most of this appears to duplicate the work in #2640994: Fix label token replacement for views entity reference arguments, but is less comprehensive. So let's get that in first, and then we can see what's left to do here.

Solution #16 works foe me without any patch. Drupal 9.4.5

Closing in favour of #2640994: Fix label token replacement for views entity reference arguments which has green (and working) patches for 9.3.x and 9.4.x.

FYI: Both #2640994: Fix label token replacement for views entity reference arguments and #3442227: Use labels in Views argument summaries for entity references are committed and will be available in 10.3.0 and up. 🎉 At last, these bugs are fixed! We copied over credit for the effort here to #3442227, too.

Enjoy,
-Derek

p.s. Doesn't really matter, but I'm restoring this to a bug. 😅

I still have the issue with D10.3.0