Problem/Motivation
The Views setting option for the "Any" value appears to have no effect on the output except for the top row in the grouped exposed filters configuration form.

I also don't find any use in the code of that configuration (old_any) except:
- On the Views settings form (
/admin/structure/views/settings) - On the grouped exposed filters configuration form.
- In YAML configuration files.
Here are screenshots of the grouped filters configuration form and the preview of the exposed form, showing where the setting does and doesn't have an effect.


Steps to reproduce
Proposed resolution
If my understanding of the setting and its lack of effect is correct, remove it.
Remaining tasks
Change record review
Check for uses in contrib
Decide if this should be removed or made configurable, #2156059: Allow the “Any” label to be customised in individual Views Grouped filters
User interface changes
Grouped Filter
Before

After

Settings page
Before
After
Introduced terminology
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | after-grouped-crop.png | 22.77 KB | jesus_md |
| #4 | before-grouped-crop.png | 21.97 KB | jesus_md |
| #3 | 3569063-3.patch | 5.94 KB | chaitanyadessai |
| Screenshot 2026-01-22 at 11.37.11 AM.png | 58.11 KB | kentr | |
| Screenshot 2026-01-22 at 11.38.05 AM.png | 27.93 KB | kentr |
Issue fork drupal-3569063
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
kentr commentedMaybe it's really a bug, since the setting doesn't do what it sounds like it's meant to.
Comment #3
chaitanyadessai commentedPlease review patch.
Comment #4
jesus_md commentedTested the patch in #3 and the code checks out. I agree with the analysis in the summary: nothing else reads
ui.exposed_filter_any_label, and the exposed form always renders- Any -because it's hardcoded in the filter handlers. So the setting only ever changed the top row of the grouped filters table in the admin UI.Before the patch the setting was stored as
old_any, the select showed on/admin/structure/views/settings, and the grouped table for the content view's "Published status" filter showed<Any>. After applying it and runningdrush updb, the post-update removed the key, the select is gone, the settings form still saves without errors, and the grouped table shows- Any -. The new update test,SettingsTestandExposedFormUITestpass, and phpcs is clean.Setting to Needs work for a few non-code things:
main, with one hunk offset by 71 lines.<Any>to- Any -, which now matches what visitors see.#[IgnoreDeprecations]on the new update test doesn't look necessary.Tested on:
Comment #5
jesus_md commentedComment #6
kentr commentedComment #8
chaitanyadessai commentedMR raised please review.
Comment #9
amitgoyal commentedAdded a change record for the removed views.settings:ui.exposed_filter_any_label config key: https://www.drupal.org/node/3626113
Reviewed MR !17254:
- Pipeline is green (only allow_failure PHP 8.6-ubuntu next-major jobs failed, unrelated to this change)
- No open review threads
- PHPCS clean on all changed files
- ViewsRemoveExposedFilterAnyLabelUpdateTest, SettingsTest, and ExposedFormUITest all pass locally
- Verified locally: the "Any" select is gone from /admin/structure/views/settings, and the grouped exposed filters table now shows the "- Any -" label instead of the old bracketed label
Moving to RTBC.
Comment #10
quietone commented@chaitanyadessai, when you make an MR it helps everyone if you remove the 'Needs merge request' tag.
@jesus_md, thanks for the screenshots. They should be added to the issue summary. This helps other contributors. reviewers and committers.
According to the Usability core gate, issues changing the UI are to be tagged 'Usability'.
Issues changing the UI should also have before and after screenshots, available from the issue summary.
Did some research and
old_anywas introduced in Views3 for Drupal 7, back in 2009.Comment #11
quietone commentedI searched for uses in contrib and there does appear to be some in PHP code in some projects. Those should be checked to determine if the module is compatible with Drupal 12. If so, then this setting should be deprecated instead of simply removed.
The change record has not been reviewed, so I am tagging for that and setting to needs work.
Comment #12
quietone commentedAnd I found an Feature Request for allowing the 'Any' label to be customized.
Tagging for Views maintainer review to decide if this should be done or #2156059: Allow the “Any” label to be customised in individual Views Grouped filters