Closed (outdated)
Project:
Drupal core
Version:
11.x-dev
Component:
views.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Jun 2022 at 19:57 UTC
Updated:
6 Mar 2025 at 15:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
cilefen commentedSome housekeeping:
Comment #3
arunkumarkUnable to reproduce the issue with the Views Combined filter.
Attached is the screen capture for the same.
Need more information.
Comment #4
cilefen commentedComment #5
lendudeIf it's giving a 502 I would expect the PHP error log to maybe show something, is that giving any hints maybe?
Comment #7
kristen polThanks 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!
Comment #8
thomasmurphy commentedPossibly 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.
Comment #9
vlyalko commentedHello, 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.
Comment #10
daniel-san commented@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.
Comment #12
lendudeWould 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
Comment #13
anybodyMight be one of the many related issues:
Comment #14
smustgrave commentedSince 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