- Issue created by @francismak
- π¦πΊAustralia ahsanra Sydney, Australia
I am having same issue not sure what is wrong.
Probably the "Select all" is missing from the selection which should fix the error although leave blank messages is there.
- π΅πPhilippines abhaypai
I believe this works as expected and proposed resolution is good solution for the time being according to the reporter although it is true that "Leave blank for all" is misleading according to my understanding if administrator doesnt wanna configure it via expose filter option.
Just sourcing above information based on my initial level of debugging and saw that "All" option or Default value only works with exposed filter as per this and this line number.
I will leave it up to the reviewer or reporter, if this issue can be closed (works as designed).
- π¦πΊAustralia ahsanra Sydney, Australia
Great information specially the code @abhaypai.
I do not understand why the ALL option is disabled for filter options, why is it visible only on exposed filters fronted?
It should be available on backed as well.
- π¦πΊAustralia ahsanra Sydney, Australia
Honestly, i think this requires a fix to keep using taxonomy filters in views for Drupal 10.
I am also not sure why this was not picked up before or may be there is a workaround to pick "Select All" instead of picking all terms for the filters.
- Status changed to Postponed: needs info
about 1 year ago 12:10pm 7 December 2023 - π³π±Netherlands Lendude Amsterdam
While I agree that the text might be a bit misleading, what would be the use case for an non-exposed term filter that doesn't filter on anything? Or am I missing something?
It works fine for an exposed filter, and the text makes sense in that scenario too. Maybe we could be more specific that this only goes for exposed filters (and when not using the empty/not empty operator for which the value setting makes no sense at all to begin with)
So would an updated description be sufficient here?
- π·πΈSerbia darko_antunovic
I am facing the same issue now.
What I want to achieve with my view is that I display the taxonomy terms, want to mark them all as required, but generate them dynamically through a hook (or alter them, that's the better phrase).
This practically means that not always will I have the same taxonomies displayed, and not always will the same taxonomy be the default one.
I am currently facing the same problem, but the problem occurs when the filter is marked as Required, what is the solution for this problem??
- Status changed to Closed: works as designed
8 months ago 3:49pm 29 April 2024 - π¨π¦Canada francismak
Hi @lendude, for my use case, I wanted to create a views to show list of content that are belongs to all terms under a vocabulary. And there is no need to expose this filter.
I am able to accomplish this by selecting all the terms and save(which means include all terms).
However, if I create a new term later on, I have to go back to the views and add the new terms to save it.And after reviewing other's comments, I realized I may mis-understood the usage of 'filter'. Instead of using filter, I should use the "Relationships" to restrict the results from particular vocabulary.
It could be another ticket whether the text "Leave blank for all" is misleading or not. That's an UI issue, but not a defect.
Closing this now, thx everybody.