Closed (won't fix)
Project:
Views Filter Pack
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2009 at 00:10 UTC
Updated:
2 Dec 2009 at 19:33 UTC
Hi,
I am looking at a solution to be able to build views with a filter with terms of a depth of say 3.
Will this module only support exposed filters? Please also support "normal" filters.
Thanks for considering!
Greetings,
Martijn
Comments
Comment #1
peter-boeren commentedMartijn,
could you explain what you mean with 'normal filters'. An Exposed filter is nothing more than a filter applied to the view, but with the exposed operator enabled. For depth in combination with view you can use the filter "Taxonomy: Term ID (with depth)". The description is as following:
The depth will match nodes tagged with terms in the hierarchy. For example, if you have the term "fruit" and a child term "apple", with a depth of 1 (or higher) then filtering for the term "fruit" will get nodes that are tagged with "apple" as well as "fruit". If negative, the reverse is true; searching for "apple" will also pick up nodes tagged with "fruit" if depth is -1 (or lower).
kind regards Peter
Comment #2
summit commentedHi Peter,
I would like to filter to ONLY the terms with say a depth of 2 having a filter setting in views where I can 1) only set possible vocabulary or all, and a setting for the depth of terms. Then the filter would work that ONLY (in your example) the "apple" nodes will be shown if I set the filter setting to 2.
[Then fruit has a depth of 1 and apple has a depth of 2].
So not AND the apple, and the fruit nodes shown, but only the apple nodes. The current views filter I can filter, but only on specific terms. I would like to filter on a depth, so I do not need to check new terms in the filter on the right level when I add terms on the needed depth level.
Is this explanation clarifying please?
Thanks for considering this!
Greetings, Martijn
Comment #3
peter-boeren commentedMartijn,
Thanks for your quick reply. It's clear now and indeed can't be done with views at this point. The name of the module is views filter pack so I don't see any trouble adding some extra filters on request. I have to warn you though, that the priority will be to make the exposed filters work for the other fields.
gr, Peter
Comment #4
summit commentedHi Peter,
You also thanks for the quick reply, and thanks you add this depth only filter to your scope. Priority is not in my hands :) but thanks for taking this in!
greetings, Martijn
Comment #5
peter-boeren commentedDue to complexity of the module, I will focus on exposed filters only.
Comment #6
summit commentedHi, of course you have to focus now, please keep after the exposed filters the normal filters in scope..
Thanks for considering.
greetings, Martijn