I was looking through the settings and I was wondering why the "Level Labels" are disabled for all but the root level when the deepest level is forced? Wouldn't having the option to have ALL of the labels show up be a better idea?

Basically, it could be setup so that the user could choose to either have no labels, just the root label (like it does now), or labels on ALL levels (like you can do now, but only when you don't force the deepest level.)

I just figured that I would mention this since it seems like it could be quite useful in many situations....

Comments

GroovyFX-Matts’s picture

Subscribed, looking for the same solution. Would be great for us as we are doing Country, State, County, City, Neighborhood. Would love to have the labels in the dropdowns but we require the user to pick the deepest level for registration.

We have done a workaround in our CSS to add labels above the dropdowns but would love to see this option in the next release. This would be usefully for our use as well as genres, products, etc.

We will provide a patch if we fix it! Love this module BTW. Eliminates us having to use the address module!

joachim’s picture

Version: 6.x-3.7 » 7.x-3.x-dev

Upping the version.

I don't really understand this limitation, as I don't see the 'enforce deepest' option has got to do with the labels.

marcoBauli’s picture

Title: Force Deepest Level WITH Labels... » Force Deepest Level WITH Labels

Having the Level Labels displayed for every level EVEN if "Force the user to choose a term from a deepest level" is selected would solve some usability issues. +1

Pablo Gosse’s picture

Issue summary: View changes

+1 for this as well from me. This would be very useful. I plan to look at the module and see if I can implement a patch to allow such functionality, but for now I have implemented a workaround that might be useful to others in this thread who are saving the term lineage and want to force a user to select from the deepest level, and still have the ability to display labels for each level.

Workaround:

1. Enable the Allow the user to choose a term from any level option which allows one to populate the Level Labels.

2. Populate the Level Labels as desired and save the options form.

3. Write a simple module that implements hook_form_validate (or you could also add code to an existing module that implements hook_form_validate) and in the validation function verify that the hierarchical select field has the correct number of options (or an option from the correct level) selected, calling form_set_error if it does not.

Cheers,
Pablo

morbiD’s picture

Just another +1 here.

I was amazed when I realised this wasn't already possible and I really can't think of a good argument against it.