I cannot make this module work

This module works with two different filters: the values in filter A control whether filter B is visible. I can't tell whether your case applies to that.

Closing as fixed.
If the README wasn't clear enough about how to set it up, please reopen with the bits that were hard to follow.

It is only working when I added the Published and Title field. It is not working with drop down filters.

Hi

I am doing it the same fashion. but its not working. can u plz explain its wrking in an elaborative way.
It will be of great help.
Thanks in advance.

Have you read the README file?

1. Add a filter of type 'Global: Dependent filter' to your view. It should be positioned after the controlling filter and before the dependent filter(s).
2. In the first settings form, choose the controller filter. Only filters prior to this one in the filter order are available.
3. In the second settings form, choose the values on the controller filter that allow the dependent filters, and choose which filters are dependent.

I'm having some trouble as well.

I've positioned my global filter between the controlling and dependent filters, but both of the filters are always exposed/visible -- the second filter is never hidden (I have selected it as a dependent filter). It has been set to 'exposed', but I don't think that should be an issue, because if I uncheck that box, then it isn't available in the global filter's screens.

I'm just wondering, might this have to do with some of my filter settings (such as that I allow multiple selections, etc)?

I haven't figured it out yet, but am wondering whether there are any restrictions in this module's usage that I should be aware of.

Thanks so much!

Hi ditcheva,
I have the same issue. Did you alredy solve it?

I set up a new sandbox just to play around with this module and found out that it does not hide dependent exposed filters if the controlling filter is a field. For example, say you have a content type called "Vegetable" and it has fields called, "plant type" and "flower color." You make these two fields exposed filters in the view, but you only want the "flower color" filter to show if someone selects certain value(s) in the "plant type" filter. For whatever reason, both filters will still show.

So far, I have figured out that the dependent filters will work beautifully if you make the controlling filter anything but a field from a content type. I noted that this also applies to taxonomy term reference fields; if they are set as controlling filters, the dependent filters will not be hidden, but you can use Content: Has taxonomy term as a controlling filter instead.

The module does work, and it's a really slick one at that, but there's something weird going on with the way it interacts with fields.

Could someone with this problem give me either a zipped-up Feature that shows the problem, using core Drupal entities please?

I'm pretty sure when I wrote this module I was working with fields!

Closing again; see #1664812: Fields set as controlling filters do not hide dependent filters .