Hope this is listed under the right component. After searching around here, couldn't find similar issues - apologies if this has cropped up elsewhere.

As you can see (image attached), I have a "Tickets" View (Views 6.x-2.12) with a few exposed filters (I've hidden 2 other standard, non-HS exposed filters for the screenshot).

Each ticket shown is a game-type node. Each game node has a Node Reference to its associated seating-type node. For example:

[node:seats-a]
- Available Seats: 5
- Cost: $100 each
- Taxonomy [vid:1]: [tid:80:Cleveland Cavaliers]

[node:game-1]
- Date: 2/6/2011
- Taxonomy [vid:1]: [tid:90:Portland Trail Blazers]
- Seats: [node-reference:seats-a]

[view:tickets]
- Core Filter: [node-type:game]
- Core Relationship: [node-reference:seats]
- Taxonomy Filter 1: [game]->[terms:HS Widget] (No Relationship)
- Taxonomy Filter 2: [seats]->[terms:HS Widget] (Seats Relationship)

  • Both games and seats share the same taxonomy.
  • The view is node:game based, but uses the node-reference:seats relationship to match up home and away information.
  • The "Home" HS widget is set to use the "Seats" relationship.
  • Finally, I've configured each of the HS exposed filters to hide terms w/o nodes.

The "Opponent" HS widget works fabulously. It hides terms (teams) that no game nodes exist for, and only shows terms from any tagged game nodes. The counts also accurately reflect the game-type nodes with each term.

However, the "Home" HS widget fails to recognize the relationship assigned to its views filter. Instead, it shows the same taxonomy results as the game node HS select, as if there was no relationship and both filters were using the same information.

As you can see, there should be at least (3) nodes listed for "Cleveland Cavaliers." In fact, the view goes on for several pages for Cleveland Cavaliers (as the Home team). The (1) in the screenshot here is actually reflecting the number of game nodes (or "Opponents") with the term, Cleveland Cavaliers.

In comparison, there is in fact only (1) game node that has "Portland Trail Blazers" as the Opponent team, and the second HS filter—"Opponent" (not using a relationship)—displays this count accurately.

It is a different story when I actually Apply the filter for the exposed "Home" HS filter. Views at least respects the [seats] relationship, and will only return tickets where the home team explicitly matches the selected HS widget term. Regardless, the HS selection is limited to only the false list of terms HS is pulling incorrectly from the "Opponent" terms (game-type terms).

I very much need to get the "Home" HS select properly respecting my [seats] Views Relationship. Meaning, the "Home" HS should only show and count terms from [seats] nodes, and the "Opponent" HS should only show/count terms from [game] nodes (working fine).

How can I configure for this? Or patch for it? Thanks.

CommentFileSizeAuthor
Screenshot of erroneous HS filters99.37 KBamaisano
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Wim Leers’s picture

Version: 6.x-3.6 » 6.x-3.x-dev
Category: bug » feature
Status: Active » Postponed
Issue tags: -taxonomy, -relationship, -HS, -views filter +HS4, +Advanced Use Cases

Indeed, Views Relationships are not supported. This is a very complex case. I'm not sure Views' exposed filters are flexible enough to support this: after all, I need to get sufficient information.

Tagging for HS4. Will be included in the HS4 roadmap: http://drupal.org/node/1052670.

amaisano’s picture

Thanks for adding to the road map. Essentially you are saying that HS Select as a Views filter does not respect Views relationships, which I would agree is a big issue regardless of my particular use case. If you need any more info from me that may help going forward in HS4 please let me know - I've been using it extensively on several websites :)

In the meantime, is there anyone who could suggest a "dirty" way of making a particular HS Views exposed filter query referenced nodes rather than the main nodes? I'd hate to have to downgrade both selectors to a standard drop down. I am willing to get very, very dirty.

Feel free to adjust this thread's status/category - this may be treading on simple support request now. Thanks.

klonos’s picture

Version: 6.x-3.x-dev » 7.x-3.x-dev

This will happen in the 7.x branch.

amaisano’s picture

I still need help with this for the 6.x version. I will open a new support request.

Wim Leers’s picture

Please don't open a new support request. This will be implemented in the D7 version of HS4 first. If feasible, it will then be backported.

amaisano’s picture

Ok - I will hold off. However, is it out of the question then to ask what the turnaround for this is expected to be? (Looks like it won't be until September 2011). I will need to move forward with this as soon as possible, and may post for support elsewhere. Since upgrading to D7 will not be feasible for my project, my only options are to wait for a 7.x backport or for a 6.x hack.