As stated in an issue about views field filter for selects:
http://drupal.org/node/1494884

If you add a taxonomy filter, there's an "is all of" operator that's especially useful when exposing the filter and allowing multiple selections. The user can narrow down the result set by filtering one additional term at a time.

This operator doesn't seem to exist for select lists, though, where it would offer the same benefit.

I was just looking for the same thing using entityreference select. Is there any reason we aren't using the "views_handler_filter_many_to_one" instead of "views_handler_filter_in_operator"?

CommentFileSizeAuthor
#1 entityreference-many-to-one-filter-1679688-1.patch1.34 KBalexverb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alexverb’s picture

alexverb CreditAttribution: alexverb commented
FileSize
entityreference-many-to-one-filter-1679688-1.patch1.34 KB

If there's no reason at all here's a patch :)

alexverb’s picture

alexverb CreditAttribution: alexverb commented
Status: Active » Needs review

Change status...

jlockhart’s picture

jlockhart
Primary language English
Location PNW Washington
CreditAttribution: jlockhart commented
Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

This patch still applies cleanly and does exactly what its suppose to. My use case are taxonomy terms referenced via entity reference. I need to allow multiple terms using checkboxes. Using the comment #31 from here https://www.drupal.org/node/1392702 , better exposed filters and this patch gives me exactly what I need. Thanks.

PhilY’s picture

PhilY
he/him
Primary language French
Location 🇪🇺🇫🇷 Paris, France
CreditAttribution: PhilY commented

This patch works with Entity reference release 7.x-1.1.
Thanks to alexverb.

PhilY’s picture

PhilY
he/him
Primary language French
Location 🇪🇺🇫🇷 Paris, France
CreditAttribution: PhilY commented
Version: 7.x-1.0-rc3 » 7.x-1.2
Status: Reviewed & tested by the community » Patch (to be ported)

Patch #1 is still needed with 1.2 release. It still works ;-)

MustangGB’s picture

MustangGB CreditAttribution: MustangGB commented
Status: Patch (to be ported) » Needs work

If it's a re-roll that's needed then typically NW is used.

odegard’s picture

odegard CreditAttribution: odegard commented
Version: 7.x-1.2 » 7.x-1.4
Status: Needs work » Reviewed & tested by the community

It doesn't need work. I think what PhilY meant was that the patch is not included in any release yet.

I've used this patch successfully for ~2 years throughout several versions of entityreference including 7.x-1.4.

I'm setting this to reviewed & tested.

minorOffense’s picture

minorOffense CreditAttribution: minorOffense at Coldfront Labs Inc. commented
Status: Reviewed & tested by the community » Postponed (maintainer needs more info)

I'm a bit weary changing the default behavior of the reference filters in views. And considering you can modify the handler as needed using https://api.drupal.org/api/views/views.api.php/function/hook_views_plugi... I'd rather leave it be.

Unless you can make the case that the change will not introduce any behavior changes and only exposes new options.