Closed (fixed)
Project:
Views Hacks
Version:
6.x-1.x-dev
Component:
Views Filters Selective
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Jul 2010 at 14:02 UTC
Updated:
7 Jul 2011 at 21:52 UTC
Hi guys.
I have nodes (Products), that are connected with taxonomy terms from 2 vocabularies
Vocabulary 1 (Product type):
Camera
Phone
Vocabulary 2 (Product vendor):
Canon
Nokia
Samsung
I want to get a list of all cameras when I choose 'Camera' in first filter, but in second filter must left Canon and Samsung.
Then, if I choose, for example Canon in second filter I want to get all Cameras from Canon.
And the same but in another order: firstly I choose Product vendor, than product type.
BUT: when I choose some value in one filter, the second becomes empty.
Please try use your View Hack)) in such case.
Thanks.
Comments
Comment #1
infojunkieThanks for your report. I'll check it soon.
Comment #2
presich commentedHave you checked it?
Comment #3
Quentin commentedHi there,
I'm experiencing the same problem with my current set up:
Drupal 6.17
Views 6.x-2.11
Views Hacks 6.x-1.x-dev
4 different vocabularies: once one is selected others become empty (although they are related to the content in the result list)
Tried with all taxonomy options (flat list and with depth).
Anyone any ideas?
Comment #4
guygg commentedLikewise. As soon as I set one taxonomy filter, the other taxonomy filter list becomes empty. Doesn't matter which of the two vocabularies is filtered first, the other will go empty.
By the way, I'm absolutely LOVING the functionality that this module provides. I've been needing the selective exposed filter list functionality since I started using Drupal a few years ago. The auto-submit function is an nice extra bell & whistle. It's particularly cool when used in conjunction with having AJAX turned on for the view.
Comment #5
Quentin commentedTried the beta-1 version... problem remains.
Comment #6
Quentin commentedIf anyone feels like he is able to fix this on short notice... I'm willing to pay for it: drop me a note!
Comment #7
joelbox-mondial-it commentedHi I have been trying to figure it out as well, perhaps this helps someone on a way to a solution. Here it goes.
It happens in views_filter_selective.module. There is an option: (set in the view): "further limit ..". Which has as effect that the module runs the view again to get to a result set. With option on a set resulting from all filters and off a set from the full original nodes.
Assume a set of 10 nodes (having 68 terms between them). Assume a filter 1, which results in 3 nodes remaining with 1 term (exa 73). The 3 nodes have 11 terms between them.
There are now two issues. With "further limit" set off, the resultset is the 10 original nodes and all terms (68 rows) with it.
The other issue (the problem described) is, that the resultset contains the 3 nodes, BUT only with the term of the first used filter (term 73).
While it should be a set of rows for all terms in the 3 nodes. So 11 rows of the 3 nids, with different terms. Then the correct selective would work.
The solution I see is altering the view which is run above to find the 3 nodes, but with rows for all attached terms. I believe there must be a simple (programmed) setting change to this views rerun filter, to show the nodes and all connected terms, but was unable to find it yet.
Hope it helps to find a solution soon,
Comment #8
joelbox-mondial-it commentedSee my earlier comment, I added this for someone trying to fixed the resultset-view.
The one selected creates a resultset of the nodes with the term, but the set has ONLY this term. It should have as resultset, those nodes with ALL connected terms. I traced the module a bit to find this as the problem:
Exa.
Node Term1 Term2 Term3
10 31 32 33
12 31 43 44
13 61 43 55
filter on term 1=31
results in resultset:
10 31
12 31
and 0 matches for the other filters.
should be resultset:
10 31
10 32
10 33
12 31
12 43
12 44
and with matches for 32, 33, 43, 44 in the other filters.
Comment #9
momper commentedis there already a fix? i think, i have the same problem ...
Comment #10
infojunkieThe latest dev release has a fix for this situation and should allow programmatic extensibility for other similar situations. You will need to re-visit the filter settings and set the "Limiting field" to "Views Selective Exposed Filters" in the case of taxonomy filters. Please try it (12 hours from now) and let me know how it works.
Comment #11
infojunkieComment #12
infojunkieI updated the hook interface to handle arbitrary filters. In the case of taxonomy terms, select the "Generic taxonomy term" limiting field.
Comment #13
roball commentedComment #15
bartezz commentedSorry to open but I need some help on this.
I have two views, each with exposed filters, each have filters based on taxonomy terms of various vocabularies. I have downloaded latest .dev but whatever I do I can't get this to work.
I've added a field taxonomy: all terms and limited the terms bya cretain vocab. Then under filters where I filter against this vocab I set the limiting field to 'All terms'. But nothing happens... I'm just not getting any options when usinig the 'limited values...' option.
What am I missing here?
Cheers 'n thanx!
Comment #16
okletsgo commentedI'm using CCK allowed value fields. Nothing works without using "Optional" which enables the option which I don't want.
Also I know we can choose the default option... but it doesn't always work in every combo.
Subscribed
Comment #17
wjaspers commentedOdd, this stopped working in Views 6.x-3.x-dev when AJAX is enabled.
Even stranger, the Preview on a Views 6.x-3.x-dev exposed filter (w/ AJAX) works just fine.
But, when the display is added to a Panel (6.x-3.x-dev) it stops functioning. Turn AJAX off and inherit the Panel Path, and it works just fine.
I'm using a View Pane instead of a Block view type if that has any effect.
Comment #18
zhuoyan commentedIt doesn't work for "Taxonomy: Depth"
Comment #19
infojunkieThe reports #15-#18 are all different. Closing this issue once and for all and please open individual issues. To report:
* Make sure to use the dev version of the module
* Include Views version number
* Export the view and attach it to the issue (don't paste the export code)
* Reproduce the problem on a view that uses nothing but core Drupal objects
* If using CCK, please export the CCK type and attach it as well