Site managers should not be able to create hierarchical vocabularies unless the site is built to show the parent terms
Given that I am logged in as a site manager,
when I rearrange terms in a taxonomy
I want to not nest terms if the site doesn't support it so that my expectations are not frustrated.
Drupal 8 removed the option to declare a vocabulary hierarchical or non-hierarchical. It's non-hierarchical until a site manager or other person with access to administer taxonomy intentionally or accidentally nests one term under another.
This should be an explicit decision made by site-builders.
(For Grassroots Economic Organizing we are using Client-side Hierarchical Select – agaric/sites/geo#15 (closed) – and configured it to only allow selection of the deepest term. The display doesn't show parent terms, and we haven't dealt with that yet— agaric/sites/geo#86
Alternatively, or in addition, we make sure to handle hierarchical vocabularies. This module also supports allowing only one level of inheritance, which may be a good compromise.
- Decide if we want it.
- Enable and configure in taxonomy-providing Drutopia feature modules.
- Spin off handling hierarchical vocabularies when displayed on content (and perhaps in facets) into separate issue(s).