Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.As well as having issues with the UI of Views, it seems to be making some quite strange queries when using filter groups. I've made a video showing these issues, but the basics is that the WHERE part of the query is wrong.
I have two groups, group A, and group B, separated by an OR operator.
For a filter I have in group B, it's placing the WHERE in the wrong position.
WHERE ((node__field_occasion_types.field_occasion_types_target_id = '69')) AND
node__field_occasion_types is a field I only have in group B, so the above is obviously not going to work!
Here's the video:
http://i.imgur.com/jvxsY0H.gif
Comments
Comment #2
MustangGB CreditAttribution: MustangGB commentedComment #3
LendudeChanging the priority to match the described problem.
The video is pretty clear in indicating there is something strange going on, but some solid steps to reproduce would be nice. I don't think all filter groups are broken in this way, so there must be some other factors here.
Comment #4
catchComment #7
jeroen.b CreditAttribution: jeroen.b at .VDMi/ commentedI have this too. It only happens on new filter groups.
When you create a new filter group, it seems to be impossible to add a filter to it. And since it won't save the filter group when it's empty it won't be there after saving the modal either. I had to try 5 times before it actually had saved the filter group with 1 filter in it, after that I was able to add more filters fine.
Comment #8
LendudeLooking at the video again, this is a duplicate of #2825446: Moving a filter to the end of a Filter group in filter rearrange doesn't work but does allow dropping in invalid regions, there is a patch on that issue.