Closed (fixed)
Project:
Pretty Facets Paths for Search API
Version:
7.x-1.9
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
8 Jul 2011 at 21:21 UTC
Updated:
20 Mar 2012 at 14:50 UTC
Hi there!
I don't know if you have already noticed, but I plan to move the Search API's facet system to the Facet API: #1182614: Integrate with Facet API.
The search_api_facets module will then be phased out in the course of the next Beta releases. Therefore, you'll have to adapt this module's functionality to use the Facet API. Chris Pliakas, the maintainer of the Facet API, has remarked in the linked issue about this probably being relatively easily possible (#52). Maybe contact Chris regarding the details.
Well, just wanted to give you a heads-up! Sorry for the trouble, but it's definitely the right thing to do in the long term for the Search API.
Comments
Comment #1
Refineo commented+1 Subscribing
Comment #2
miiimoooComment #3
jakonore commentedsubscribe
Comment #4
miiimoooIs this in the current dev version or how could I see what changes?
Comment #5
drunken monkeyYes, it's now in the current dev version. In the contrib/ folder, in the future only the search_api_facetapi module will remain and the search_api_facets module completely removed.
Comment #6
jnpwebdeveloper commentedAny chance this can be ported? I tried having a go at it but it's quite confusing to me. I just started using the facet API for a new project and would like to get the facet paths working for SEO. Now the only other option available I think is manually writing some rewrites but like it to work out of the box. Is there anything I can help out to get this moving along? Thanks
Comment #7
miiimooo@drunken monkey : I used to parse the taxonomy out of hook_url_outbound_alter / $options['query']['filter'] . It looks a bit like it's now in $options['query']['f'] . Could you think of a better place to get it from or should I stick to this?
Comment #8
drunken monkeyThe place this is put is actually both pluggable and customizable on a per-index base, so we can't say for sure. Assuming
$options['query']['f']will be right nearly all the time, though, I guess.Not really sure about the whole thing, though, I'm not that familiar myself with the Facet API. :-/
Comment #9
miiimoooNo worries. Chris has actually given me some pointers over at #1226592: Make URL creation & resolving pluggable
Comment #10
dasjocoming from #1354654: Is this working with facet api ? i have a little recap:
miiimooo was working on this
http://drupal.org/node/1226592#comment-5126886
now, chris forwarded the discussion to a separate issue:
#1226592: Make URL creation & resolving pluggable was deferred in http://drupal.org/node/1226592#comment-5378558
so it might be discussed in #1375104: Add a method that URL Processors can implement to alter the path of facet links or here.
i would be interested in using nice looking facet paths with search api. if i can help testing something please let me know.
regards josef
Comment #11
marcoka commentedMore related stuff:
#1375104: Add a method that URL Processors can implement to alter the path of facet links
just putting some ideas here. can we eventually get it out of $_GET['f']?
http://screensnapr.com/v/YOzvWd.jpg
Comment #12
srsbl commented+1
Comment #13
dasjowork is being made over at http://drupal.org/node/1375104#comment-5539010
Comment #14
dasjoplease check out the new Facet API Pretty Paths module.
i think we can port a lot of functionality from Pretty Facets Paths for Search API, for example in #1431692: Provide more configuration options.
Comment #15
miiimoooThanks to dasjo