I try to use Select list (with groups) in views filter.
My List is Taxonomy Hierarchical, Categories with subcategories, In views filter I dont need the category field be selected to default category,
because default value can be selected only from subcategories,
user make choice the category he interested in, and additional select fields also should not have default value from subcategories.
Also Taxonomy container Removes Label -none-
in my case it is replaced with field label and it look great when you have 4-7 fields and labels inside select lists.
But when I apply Taxonomy Container it removes it, and each field become unlabeled.
1) Preserve label -none- in Select list (with groups)
2) No deafault value, because I should chose it from subcategory, user should choose his variant
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | required_none_option.png | 1.87 KB | kirie |
Comments
Comment #1
chi commentedThere is not any integration with Views in Taxonomy container. The module just adds an extra widget to term reference fields.
Can you provide more information?
Comment #2
Jarviss commentedChi you can forget about views. The field is the same and problem is the same in creating node form and in views filter form (the same field widget).
Category Term reference field:
Category 1
-subcategory 1 category 1
-subcategory 2 category 1
Category 2
-subcategory 1 category 2
-subcategory 2 category 2
As Admin when I choose Taxonomy container to my Category field (Select list (with groups))
in form settings by DEFAULT VALUE -subcategory 1 category 1 is choosen and I can't change it with no default.
When user try to add node: he will see -subcategory 1 category 1
in my case when -subcategory 1 category 1 additional fields are added to the form.
when -subcategory 2 category 2 different fields are added to the form.
So I need
1) no Default Value for Taxonomy container Field.
2) it should leave as usual -None- as first user choice, in my case -None- is replaced by field label "CHOOSE CATEGORY"
Comment #3
chi commentedJust one question. Is your Category field marked as required?
Comment #4
Jarviss commentedHi Chi! yes Category is required in content type and in views filter it is not required.
Comment #5
chi commentedWhy do you expect that -None- will be available if you marked your Category field as required?
Comment #6
chi commentedJust uncheck "Required" checkbox and -None- became available.
Comment #7
kirie commentedIt is probably bad usability to automatically select the first item in the option list - even if the field is required. Core, by default, has the "- Select a value -" option, even for required fields (see image below/ attached).
Comment #8
chi commentedHi kirie! Perhaps you're right. I made a separate issue for that. #1471298: Do not select the first item in the option list - even if the field is required.
Comment #10
end user commentedJust had this issue creep up on me while testing this and unchecking Required field is not really an option for a community driven site as people will forget to choose a required term field. What I like about this module is that it works with JS turned off and no need to worry about it having graceful degrading issues with JS turned off.
Comment #11
chi commentedThe issue is already fixed. Have you tried the latest dev version of the module? Also I am wondering about JS issue. The module doesn't use any JS snippets and works well with JS turned off.
Comment #12
end user commentedOk got the latest version of the module and the problem is fixed. Thanks!