To reproduce: Set up term reference field, select autcomplete_deluxe widget, configure content_taxonomy to deny new taxonomy terms, then add or edit a node with that field. Start typing a term that doesn't exist in the vocabulary.
Experienced behavior: Drop-down box produced by taxonomy_deluxe reads: "The term 'asdf' will be added"
Expected behavior: Drop-down will tell me that the term doesn't exist (and can't be selected).
Attached image shows text in question.
| Comment | File | Size | Author |
|---|---|---|---|
| autocomplete-will-be-added.png | 10.22 KB | ezheidtmann |
Comments
Comment #1
msypes commentedI just hit this problem as well.
I don't have a solution, but here's a work-around that will at least give you similar functionality:
It's working well enough for my purposes, so I thought I'd share
Comment #2
johnvIMO this is annoying, but only to resolve if the autocomplete widget knows about the 'deny new term'feature.
OTOH: why is this feature disable for some widgets? I can't find a reason.
Comment #3
ezheidtmann commentedWhy? Because the vocabulary is large (several hundred terms) but is fixed (a committee created it and regular content editors can't add terms.
If direct support for this condition is not possible (or not recommended), perhaps you can document a way for other modules to override the displayed text. (I'm now using "chosen" for this project, so unfortunately I won't be able to test or provide patches)
Comment #4
anavrin commentedHi there,
I have the same problem :( Anybody could share the fix for this?
i'd be really grateful ...
Comment #5
damienmckennaI wonder if the problem is on Autocomplete Deluxe's side? The "The term 'asdf' will be added" message doesn't exist in Content Taxonomy (fyi I searched for "will be added").