I have a hierarchical_select tree with 3 or more levels attached to a content type. The field is a compulsory field, and of type "content taxonomy fields". Selection from level 1, then produces level 2 options.

But node can still be saved without necessarily picking term form level 2 and so on. Even though "Force the user to choose a term from a deepest level" is selected in configuration.

Also tried 6.x-3.x-dev, and had same issue.

Comments

zeezhao’s picture

zeezhao commented

Hi. Please has anyone got a fix for this? Thanks

zeezhao’s picture

zeezhao commented
Status: Active » Closed (fixed)

Resolved. Needed to set in both places:
- admin/content/taxonomy
- admin/settings/hierarchical_select/configs

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Component: Code » Code - Content Taxonomy
Assigned: Unassigned » wim leers
Priority: Normal » Minor
Status: Closed (fixed) » Active

Hm, it should only be necessary to set that in a single place, so this *is* a bug. But what did you set in both places? That it's required or "Force the user to choose a term from a deepest level"?

zeezhao’s picture

zeezhao commented

Hi. At first, was only setting ""Force the user to choose a term from a deepest level" via admin/content/taxonomy

Then when it was not taking effect, also then checked it at admin/settings/hierarchical_select/configs and found that it was not set. So then also set "Force the user to choose a term from a deepest level" via here too.

I guess the confusion was because there are two separate places with the same information. Thanks

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Category: bug » support
Status: Active » Fixed

Ah, right admin/content/taxonomy is for normal taxonomy. Content Taxonomy doesn't use these settings. Taxonomy UI vs. Content Taxonomy UI confusion is to blame. Won't be an issue in D7.

Gotcha, thanks for the reply! :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.