Created on 5 July 2016, over 8 years ago
Updated 27 July 2023, over 1 year ago

After some internal discussion last Friday, one of the last bits of code that has not been refactored since Drupal 6 basically is the code that selects the TVI configuration to use for a given term.

Historically, TVI has allowed the flexibility to be able to do the following:

  • Override vocab presentation with a View
  • Override term presentation with a View

There is complexity however in allowing children terms (nested hierarchy) to have their own view, because it means a lot of evaluation to determine which View should be shown.

At the same time, the issue πŸ› Views permissions not respected by TVI Needs work made me think about what parameters TVI should have around it as far as configuration, and under what circumstances it works well under.

I feel like the following changes should be proposed:

  • Make TVI work at the vocab level, without term level override
  • Make TVI support only page level display, so Views access can be respected

Is anyone really using TVI on deeply nested taxonomy that needs the ability to do multi level overrides? I tried to think of use cases where a taxonomy would be so loosely structured that the presentation of X terms within it would be different than other terms within the same taxonomy tree.

🌱 Plan
Status

Closed: outdated

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States kevinquillen

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦Canada mikeohara Moncton, NB

    Closing as outdated, and the 8.x-1.x branch will be considered minimally maintained and soon to be deprecated.

    If there is value for the 2.x branch, please re-open and provide feedback for improvement.

Production build 0.71.5 2024