- Issue created by @falcon03
- 🇮🇹Italy falcon03
@cilefen I'm not sure I agree on considering this a feature request than a bug. Reading the help text "Start typing the title of a piece of content to select it. You can also enter an internal path "that is shown below the field it seems that its intended behavior would be to autocomplete paths for all "pieces of content" (and in deed taxonomy terms are content entities).
Anyway this is at least a major usability issue, considering the fact that we do not have any simple way in core to add taxonomy terms to menus (like the options available for nodes).
On a side note, the reason why after 10 or so years of work on entity field API and internal core architectures we still have to worry about implementations for each content entity is still a mistery for me, but that's another story :)
- 🇺🇸United States cilefen
Major bugs have no workaround → . You described the workaround above.
Now that I’m thinking about this more, aren’t taxonomy term pages a view? Views are not content entities.
- 🇮🇹Italy falcon03
@cilefen fair enough; we should discuss wether that workaround is acceptable for being in 2024 (and of course I'd say no), but I do not want to bikeshed on this: we'd better have this discussion in a policy issue.
Anyways I did not find anything on the fac that taxonomy term pages are now views; do you have the CR on hand? A quick Google search didn't help
- 🇺🇸United States cilefen
https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/taxon... but in fact it is optional. These are content entities otherwise.