Show terms for taxonomy reference fields allowing multiple taxonomies

Created on 12 September 2020, about 4 years ago
Updated 17 February 2024, 10 months ago

Problem/Motivation

When using the inline entity form widget with a taxonomy term reference field that allows multiple taxonomies, only the taxonomy categories are shown.

Steps to reproduce

  1. Add a taxonomy term reference field to an entity (in my case I'm adding it to a paragraph).
  2. Select multiple taxonomies able to be referenced.
  3. Choose the 'Inline entity form (Complex)' option - I don't see the simple option for this field.
  4. Create a node with that entity (paragraph) and you will see the broad taxonomy categories, but none of the actual terms.
πŸ’¬ Support request
Status

Needs work

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States w01f

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.

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    I'm closing old IEF support issues. Please feel free to re-open the issue if you still require assistance.

  • Status changed to Needs work 10 months ago
  • πŸ‡ΊπŸ‡ΈUnited States w01f

    Well, I don't think a note simply stating you're closing it because it's "old" is a proper method to close tickets.

    Might I recommend something a bit more helpful, such as "We do not currently intend to support this feature." or "We do not currently have time to develop this additional feature, but are open to contributions if someone would like to take this up. Closing for now." Or... possibly even a "After reviewing the request, I realize this is already possible, and am including instructions for how to implement below, with a reference in the readme."

    But generally the maintainer of module leaving a note that doesn't even convey they took the time to read a submitted ticket is rather discouraging. If you find yourself strapped for time or lacking technical expertise to respond properly, I would suggest opening the module up and advertising for a co-maintainer.

    Note: Copy/pasting my response from the other ticket that was inadequately closed... as that was the method used for the closing comment.

Production build 0.71.5 2024