- 🇫🇷France pacproduct
(just as a side note, we're facing the same issue with module term_reference_tree → - here is their equivalent issue: Use widget for taxonomy term parent field → )
The "Parent terms" list of the RELATIONS section of a Taxonomy term form is very difficult to use with large taxonomies. By default it only shows 4 items in a drop-down list, with no search feature:
This can be improved by installing the Chosen module → , which automatically gives search functionality and a longer drop-down list:
1. Add many terms at different levels of a very large taxonomy or edit the relations of existing terms (without Chosen installed).
2. Weep.
To leverage the power of jsTree, allow the Entity Reference Tree Widget to be used as the widget for the RELATIONS section of the Taxonomy term form, as if it is a regular field:
When the "Taxonomy term tree" button is clicked, the Entity Reference Tree modal dialog pops open so parent term(s) can be selected. Proposed dialog title is "Select Parent Term(s)":
Ideally, "RELATIONS" would appear like a field on a taxonomy term's "Manage Form display" page so that its widget, settings and order can be configured like they can for fields. If that is not possible, perhaps Entity Reference Tree Widget could have a simple configuration page with a checkbox for "Use for taxonomy RELATIONS (Parent terms) selection", to override the standard widget (& Chosen, if installed).
1. Determine if it is possible. Refer to how Chosen achieves it.
2. Code it as a feature within this module if possible.
3. If not possible within the Entity Reference Tree Widget module, develop a separate module for it.
4. If still not possible for core reasons, investigate a change to core to make it possible.
Related Discussions:
Parent term relations select list as Hierarchical select list →
How to show more terms in the “Parent terms” select list when adding taxonomy term?
Active
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
(just as a side note, we're facing the same issue with module term_reference_tree → - here is their equivalent issue: Use widget for taxonomy term parent field → )