Problem/Motivation

The "Combine Fields Filter" for Drupal Views is causing two issues on our site:

Deleting the combine fields filter does not remediate this issue.

Steps to reproduce

  1. Create a view page and populate it with fields as you normally would
  2. Create a list of filters including the Combine Fields Filter
  3. Execute a search on the completed view page using the view filters just created
  4. Click the [reset] button

Someone who properly reproduces this issue will see that the "?combine=" parameter in their view's url does not get cleared out of the url, nor does the text box that they entered their keywords into clear out.

Comments

JakeAPoe created an issue. See original summary.

cilefen’s picture

Version: 9.3.x-dev » 9.4.x-dev
Priority: Critical » Normal
Issue tags: -views, -combine, -fields, -filter, -reset, -button, -clear

Some housekeeping:

  • There are issue priority standards so I updated that field.
  • Drupal 9.3.x is no longer having ordinary bug fix releases, so I'm changing this to 9.4.x.
  • There are issue tag guidelines so I've cleaned them up.
arunkumark’s picture

StatusFileSize
new657.5 KB
new214.01 KB

Unable to reproduce the issue with the Views Combined filter.

Attached is the screen capture for the same.

Views Combined filter

Need more information.

cilefen’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs steps to reproduce
lendude’s picture

If it's giving a 502 I would expect the PHP error log to maybe show something, is that giving any hints maybe?

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

kristen pol’s picture

Issue tags: +Bug Smash Initiative

Thanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.

As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" more than 6 months ago with a request for steps to reproduce and there has been no activity since that time.

Since we need more information to move forward with this issue, I am tagging for Bug Smash Initiative and keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

thomasmurphy’s picture

Possibly related, I had a problem very similar to this, where the view exposed reset button wasn't clearing the URL out. The entire view block was also not rendered after a reset. I uninstalled the bigpipe module and the problem was resolved.

vlyalko’s picture

Hello, I am using https://www.drupal.org/project/views_filters_populate, which is an alternative filter field to the combined filter field, and experiencing same problem. Reset button does not clear the result when this populate (combined) field is used for the filtering.

daniel-san’s picture

@thomasmurphy Thank you so much for your comment. I tried what you shared and it fixed my issue as well!! Thanks so much for sharing.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

lendude’s picture

Would still be good to get some steps to reproduce this on a clean install of Drupal core to make sure this is a core issue. The steps in the IS by themselves are certainly not enough to trigger this on a clean install

smustgrave’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Since it's been a few years of asking for steps I'm going to close this one out. If this particular one is still an issue please reopen providing the steps to reproduce.

Thanks all