Add facets_taxonomy_path_processor module to readme file

There's currently no documentation on drupal.org on how to do this, but the facet has ::setActiveItems. That should be passed an array of items that need to be active.

We use hook_search_api_query_alter to alter the actual items to be active before the query runs, so if your hook runs before that one everything should work.

@matjaz_zavski did you find a solution? It would be great to provide some documentation for this (even if it was just in the issue queue).

Given the goal "set facet item as active programmatically" and the status "works as designed", I'd say the current (suggested) workaround to "set [...] path to ?f[0]=[taxonomy_name]:[tid]" doesn't cut it.

Example : you want to force a default value that's dynamic (e.g. set the current year to active only if none is selected on a date filter facet).
→ Can't change links pointing to that page, as they would become outdated every year.

Here are my current failed attempts :

Implementing hook_preprocess_block() and getting the facet object like $facet = Facet::load($variables['derivative_plugin_id']);
→ nothing comes out of $facet->getActiveItems() when an item is indeed selected, and $facet->setActiveItems() has NO effect whatsoever (and I cleared caches to make sure in every test).

Implementing hook_search_api_query_alter() : setting the values from there does work using $query->addCondition() for the results, however the corresponding item in the rendered facet block does not appear as "active".

@borisson_ When you say "We use hook_search_api_query_alter() to alter the actual items to be active before the query runs", how do you actually access the Facet items from there ?

I made a small sandbox project that should satisfy this use case: Facets taxonomy path processor

This adds a processor that activates the taxonomy facet if the term is in the path. You need to activate this in your facet configuration. If it doesn't work for you it should at least be a good starting point.

@borisson If this is something you would like to add to the module I can provide a patch.

No, I think keeping this is a seperate module is better, I would like to keep the functionality here as small as possible, we've already created enough code to maintain :)

If you'd like, I can mention this in the README.txt, we have a list of EXTENSION MODULES in there, to link to those modules.

You could open a patch with a change to just the readme.

Sure thing! I made a release and the patch attached adds the project to the readme.

Looks great. Thanks!

Committed and pushed. Thanks!