Closed (won't fix)
Project:
Search Lucene Tagcloud
Version:
6.x-1.0-beta1
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Dec 2009 at 02:18 UTC
Updated:
29 Sep 2011 at 17:35 UTC
Comments
Comment #1
cpliakas commentedHi onesimpleman.
Thanks for the post. In terms of displaying the facets anywhere on the website as opposed to just the search pages, I think it would be possible to do so similar to the "block" realm's implementation. Displaying the actual search terms is more of a request for the core Search Lucene API module, and I think it is a usability bug that this is not available. Great request! The reason why it is a Search Lucene API request is because the way facets are constructed, this is something that architectualy should be added in core so other facet realms can make use of it as well.
I am going to update the title to reflect the empty searches tag, and I am going to post the bug report on Search Lucene API. I will update this thread with the issue page.
Thanks,
Chris
Comment #2
onesimpleman commentedHi Chris,
Thank you for editing the post and your answer.
There is no module available on Lucene search, core search, apache solr or sphider to actually show the most popular search terms in a block. May be if we could implement it , it would be a first. I would think a lot of people would be interested in something like this ( seo and usability)
I have noticed the searches are stored in the Access logs and have been looking for a way to pull it to a block. Views access logs dont have an option to do it .
Again thank you so much for this really useful module.
Onesimpleman
Comment #3
cpliakas commentedA facet to display the original search terms was added to the RC2 version of Search Lucene API and is made available to Search Lucene Tagcloud. #653600: There is no way to get back to the original search other then re-clicking the search button
Comment #4
cpliakas commentedMoved target to beta3 so the fix for the critical bug #695472: Fatal error after upgrading Search Lucene API to version 2.0 could be released.
Comment #5
j0nathan commentedsubscribing...
Comment #6
ukrdrupal commentedsubscribing...
Comment #7
cpliakas commentedDue to end of life announcement.