The module does not work in view filter disclosed, why?

CommentFileSizeAuthor
#4 views-issue.png39.14 KBrinashah
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DarkteK’s picture

It does work, sadly, you need to active depends on how many options your filter have, in Admin->Config->Chosen

bunthorne’s picture

Category: Bug report » Support request
Priority: Critical » Normal

If you're saying you can't get it to work using a Views Exposed Filter, I have several Exposed Filters working just fine with the Chosen widget. Remember that the fields that you are exposing should use the Select widget in the Content Type.

Changing this to Support Request and Normal priority. Perhaps if you provide details about your View setup and the Content Type, it would be easier to help with the problem.

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)
rinashah’s picture

FileSize
39.14 KB

Same issue with me too.
Pls help.

mattsmith3’s picture

I'm having a similar issue, applying to an existing site. I've enabled chosen on the content type field, but it's not applying to the view exposed filter with the same field.

bunthorne’s picture

If you have a select list on a Content Type, there is a setting under "Additional behaviors" with a checkbox "Render Views filters as select list". If you leave this box unchecked, any View exposed filter will treat this field like a text field to be searched. If you want Views to get the actual Select list to use in the Exposed filter, you have to check the box.

You will see the difference at the Exposed Filter setup. If you have "Render Views filters as select list" checked, your Exposed filter will allow you to specify pick list values with "is one of" and "is not one of" logic. But it you do not have it checked, your Exposed filter will only have the greater than/less than logic.

mattsmith3’s picture

Thanks bunthorne- but is this only for taxonomy? I'm using a "List (text)" field with widget type "Select list". I have no "Additional behaviors"...

bunthorne’s picture

Now that you mention and I investigate, the behavior I described seems to be a function of the Entity Reference field and not the List (text) field (or even Term reference). Entity Reference wants you to decide whether your field (that may come from a huge list) should pass its list to Views as a select list, or whether to let Views treat it as a searchable text field. You will only see the "Additional behaviors..." item in the Entity Reference field Edit tab.

If anyone has problems trying to set up an Exposed Filter in Views and can't figure out why there is no select list when one was expected it could be that it is an Entity Reference field and needs to have this "Render Views filters as select list" checkbox selected on the Content Type.

Sorry that this doesn't answer your problem. It might answer someone else's, though!

bserem’s picture

For me it doesn't work when jQuery is greater than 1.7 (jquery_update 1.8+)