Enforce deepest + required without prepopulated defaults [#316267]

This is such an amazing set of modules I feel I must be missing something somewhere. I'm using it for a content taxonomy field for a required vocabulary. I have "force deepest" set but the subsequent drop downs then have a default term already set. Is there anyway to make it "" or "--" and still have it be both required and deepest required? I read most of the issues touching this but either the issue wasn't quite the same or it was against an earlier version.

Any info would be greatly appreciated--

Thanks.

Comments

Comment #1

wim leers

Ghent 🇧🇪🇪🇺

commented 2 October 2008 at 15:34

Assigned:	Unassigned	» wim leers
Status:	Active	» Fixed

This won't happen, because then it's no longer "enforcing the deepest" term: it'll allow you to select *nothing* at the deepest level!
You could of course argue that an error should be displayed when that happens, but that makes your suggested approach inferior to the currently implemented one: the beauty of the current approach is that it *enforces* through the lack of alternatives that you select an item in the deepest level.

Comment #2

WorldFallz commented 2 October 2008 at 16:37

This won't happen, because then it's no longer "enforcing the deepest" term: it'll allow you to select *nothing* at the deepest level!

You could of course argue that an error should be displayed when that happens...

The thing is this is how it's works with plain taxonomy fields-- it creates a "-Please Choose-" option and knows that it doesn't count as a selection forcing the user to actively pick one of the other choices in the drop down (and creating an error message if it doesn't).

...the beauty of the current approach is that it *enforces* through the lack of alternatives that you select an item in the deepest level.

Up until recently I would have agreed. Unfortunately I just discovered that's it's not so beautiful when users simply hit "submit" without being forced to make an intelligent selection. Because of carelessness I'm going to have to now manually go through 1500+ nodes, determine the correct value for a field, and update it. One could argue that it's a training issue but as a refactored usability engineer I've learned the hard way over the years (and this is just the latest of many times i've come across this) that if a system allows the human to make an incorrect choice more easily than a correct one they will, lol.

Also, since i have a mixture of regular taxonomy and HS fields, I'm not comfortable with there being 2 different behaviors for essentially the same (from the user's perspective) function.

I'll look into the taxonomy code and the HS code and see if i can figure out how big a deal it would be to mirror this behavior-- if you're open to it of course. If not, or if i can't figure it out, I'll probably have to revert back to regular taxonomy or content_taxonomy + active_select.

And thanks for the quick reply!

Comment #3

Anonymous (not verified) commented 16 October 2008 at 16:43

Status:

Fixed

» Closed (fixed)

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

Comment #4

WorldFallz commented 16 October 2008 at 23:54

Status:

Closed (fixed)

» Active

i didn't realize the issue was "fixed"-- just wondering if you would accept a patch on this before I put any effort into it. It really bothers me that hs works differently then cck and taxonomy fields in this respect.

Comment #5

wim leers

Ghent 🇧🇪🇪🇺

commented 2 November 2008 at 22:27

Title:	force deepest without prepopulated defaults?	» Enforce deepest without prepopulated defaults?
Version:	5.x-3.0-rc3	» 5.x-3.0-rc6
Component:	Code - Content Taxonomy	» Code
Category:	support	» task

I'm almost certain now that I agree with you, although I haven't really had the time to think about this better.

In any case, you wouldn't have to put an effort into it, unless you could do it quickly. Which I doubt, because the code is ridiculously complex. It'll take me much less time to do this, so I wouldn't expect anybody to take this on.