Posted by Mark Theunissen on May 1, 2009 at 2:33pm
| Project: | Context |
| Version: | 6.x-2.0-beta1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | yhahn |
| Status: | closed (won't fix) |
Issue Summary
Based on the work done on the taxonomy integration, here's Faceted Search integration! I'm still waiting for David to hopefully review what I've done (creator of Faceted Search module), but in the meantime this is the alpha version.
There's a known bug whereby submitting the context form causes the hook to be invoked twice. Then the next time you do a faceted search, you get an error about the temporary tables already existing. It then clears up. I'm not sure how to avoid this.
Also it only supports taxonomy and content type facets. Still waiting for David's opinion on how to write a generic id collector.
Thanks.
| Attachment | Size |
|---|---|
| context_facets.zip | 2.17 KB |
Comments
#1
New code
#2
Hi Mark,
I'm a little confused about the behavior you are looking for here. It seems like you want to trigger a context reaction based on a component of an active search. So that if you do a search an choose a particular taxonomy term as a facet the context will get triggered. Is that correct? How do you see this being used?
Thanks!
#3
Yes, that's correct! So imagine we have five taxonomy terms:
-USA
-Canada
-Switzerland
-Thailand
-New Zealand
On our sites, our primary navigation will link to the faceted search for the term. In other words, we use Faceted Search as the main component of the site - if you are viewing a list of content, it is almost always a faceted search with the option to filter using the guided search block.
So if those five terms each had context associated with the faceted search, we could display a New Zealand flag as the background anytime a user is looking at a Faceted Search list of content with the term "New Zealand", etc.
#4
Ah, ok. So I'm using faceted search slightly differently where there are several different environment and want to use the context module to control visibility of the supporting blocks (guided search, keyword search, etc..).
Two questions:
How do you feel about extending this for both usages?
Do you think it's better for this to live in the context or faceted search project?
#5
It's unlikely that I'll be extending it as the work was sponsored by my previous employer, and they have since left the project dormant. So possibly, but unlikely.
Surely your faceted search environments all have distinct URLS like /enviro1/results /enviro2/results ... can't you use that URL to set the blocks visibility?
#6
I agree with both points here --
If you need a context set for the entire faceted search environment, the path condition should suffice.
If you need more granular control, I think it's best that any context integration of this level live in the faceted search module.
Given that this won't be making its way into context_contrib (which I would like to slowly phase out in favor of integration by the contrib modules themselves), I'm closing this one.
#7
sub