Closed (duplicate)
Project:
Context
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Oct 2009 at 21:03 UTC
Updated:
21 Dec 2011 at 21:44 UTC
It would be great if the context module could add a condition for searches being executed. This patch works for all implementations of the core Search API, including modules like Search Lucene API and the 1.x branch of Apache Solr Search Integration. It doesn't take into account when searches have been executed in views, but at least it is a start.
Thanks for a great module,
Chris
| Comment | File | Size | Author |
|---|---|---|---|
| search-condition.patch | 999 bytes | cpliakas |
Comments
Comment #1
yhahn commentedLooking at this for 3.x now, sorry for the delay.
Comment #2
cpliakas commentedThanks for getting to it. I know there are a lot of other more important things going on with the module. As a side note, it appears that the 2.x branch of Apache Solr is moving away form the core Search API, and I am exploring doing the same for Search Lucene API. Although adding support for third party modules is probably out of Context's scope, it is worth mentioning as the popularity of alternative search solutions increases.
Thanks again,
Chris
Comment #3
steven jones commentedComment #4
cpliakas commentedBumping to the 7.x version. Facet API now provides API functions as a result of the issue #1373096: Implement a function that stores which adapters ran the FacetapiAdapter::addActiveFilters() method which could provide some context around which searches have been executed. The code is generic to Apache Solr, Search API, and the core Search module which is why Facet API would be a good candidate to integrate with. This probably isn't something that should go in the Context module itself, but rather as a separate contrib that integrates the two projects. Just wanted to bump this issue with new information in case someone wants to take this on.
Comment #5
cpliakas commentedClosing in favor of #1379308: Integrate with the Context module, since a lot more possibilities are exposed by a contrib module integrating Facet API and Context as opposed to the very simple use case of the original post.