Problem/Motivation

Unfortunately the bugfix #2568889: Views exposed text filter set to required shows an empty error and form error on page load has resulted in quite serious UX regression. In order to see results when a view has a required exposed filter (that's not a bool) you need to press the apply button.

For example if you create a view on nodes and expose a filter on node type and make it required - in Drupal 9.4 it will process the exposed filter as expected but Drupal 9.5 will not.

Steps to reproduce

Change the Content view supplied by standard to make the node type filter required and select Article and Page as the allowed values.

Proposed resolution

Rework #2568889: Views exposed text filter set to required shows an empty error and form error on page load to only be about text filters.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

alexpott created an issue. See original summary.

smustgrave’s picture

smustgrave commented

So think I understand the issue.

As pointed out editing the content view and selecting both basic and article will make the filter appear it has selected article.
But the view is showing both basic and article.

So it's misleading. Not sure if the best approach is to keep the -Any- option?

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Active » Closed (outdated)

We reverted #2568889: Views exposed text filter set to required shows an empty error and form error on page load. Will add comments about what needs to be addressed to the re-opened issue.

solideogloria’s picture

solideogloria commented

Changes have been made in #2568889: Views exposed text filter set to required shows an empty error and form error on page load. Please review them and make sure the regression doesn't happen again. Thanks.