Entity_lookup taxonomy_term restricted by VID

Created on 23 August 2021, over 3 years ago
Updated 25 February 2025, about 1 month ago

Problem/Motivation

Currently there's no way of restricting the entity look up search for a taxonomy to a single vocabulary.
This is important for situation where the same word is found in multiple vocabularies but only on is needed.
Additionally the UI lets you restrict entity reference taxonomy fields by those desired but this takes that back as the bundle_key seems to not work for it without erring out due to the determineLookupProperties function.

Proposed resolution

Provide a YML key from which one can restrict the taxonomy to one value or many values.

✨ Feature request
Status

Needs review

Version

6.0

Component

Plugins

Created by

πŸ‡ΊπŸ‡ΈUnited States bernardm28 Tennessee

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.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Thanks for pursuing this @bernardm28, if entity_lookup really does search across all vocabularies, that would be a pretty big bug ...

    Maybe you can add a short "How to replicate" section? Like:

    1. Create two vocabularies, "Vocab1" and "Vocab2"
    2. Add the same term "business" in both vocabularies
    3. Create a simple migration, filter to a single vocabulary with [...]
    4. See that the term is getting detected from both vocabularies

    I think the problem of no progress in the issue is that your specific vocabularies don't mean a lot to the other users here ... and setting it up correctly can take quite some time, whereas you know exactly how to replicate it.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Adding a possibly related issue.

  • πŸ‡ΊπŸ‡ΈUnited States bernardm28 Tennessee

    Uff it's been so long, it might have been specific to that scenario or user error.
    I will take a look next week and close iit if i can't replicate it.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Thanks, and yes it might have been fixed ... but it would be awesome to verify if the problem is still there. Thanks!

  • πŸ‡ΊπŸ‡ΈUnited States bernardm28 Tennessee

    Pretty sure this likely was fixed along something else.

Production build 0.71.5 2024