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.
The "Allow Multiple Selections" option creates an INNER JOIN that leaves out the "entity_type" field.
When there is a similar tid with the entity type of "node" it returns the entity_id as a users.uid.
This results in a user that is does not have this term set to be included in the resulting view.
Attached is a JPG of the Filter Criteria, the data, table structure, the term/field filter criterion and the resulting SQL.
Comment | File | Size | Author |
---|---|---|---|
SQLissues.jpg | 780.08 KB | stevecory |
Comments
Comment #1
azinck CreditAttribution: azinck commentedI think this is a dupe of [#2214601] though I can't reproduce the difference you're seeing between "allow multiple" and single selections. I see the bug in either case.
Comment #2
azinck CreditAttribution: azinck commentedOk, it appears the extra criteria get correctly added to the join only if the filter operator is set to "is one of". I'm still not seeing any difference when using "allow multiple" vs. not using "allow multiple".