- Issue created by @mlncn
When you enable Taxonomy Views Integrator module, and choose "Enable taxonomy views integrator to override presentation" and select the View and Views Display to use, you pretty naturally expect it will begin doing that for a normal taxonomy term page. It does not, until you also select:
Child terms will use these settings.
Checking this field will allow you to define a view used by the current term and display on all of its children, unless they have their own settings configured.
Still do not fully understand what that means, but if it has to be checked maybe it should be checked be default or very prominently documented.
This issue is a direct follow-up to 🌱 Simplify TVI Closed: outdated and lisastreeter → 's comment there:
I'm new to TVI, so my perspective is likely fairly limited. I'm using it for just one vocabulary. On the Edit vocabulary page, I enabled TVI, selected the view, and a page-type display. I was initially confused by the "Child terms will use these settings" checkbox and discovered that without it, nothing worked. My taxonomy is flat, without any nesting, so I mistakenly thought that meant I didn't have any "child terms." Once I figured out that I needed to check the box anyway, I was left wondering why the checkbox existed at all. Wouldn't it always be required? I guess I don't really understand the use-case for not checking the box. Perhaps it's for the case in which only the pages of of the terms should be overridden and the rest should just display as normal?
Seven years later, and i am having exactly the same experience! "This is simply… not working? No one else is reporting this, so there is somehow something wrong with my setup or everybody else also thinks they are losing their mind." I really should do a test on a clean install and see if this is reproducible, and then file an issue… i never did put in that work, but on the second usage on another project i at least identified which checkbox did the trick (i had mistakenly thought it was setting the global configuration that was needed).
Active
2.0
Code