Hi, David. Thanks for using WP Search with Algolia. At the WordPress plugin repo, we have a Support page where you can submit your request for support and interact with the developer directly. Thank you. https://wordpress.org/support/plugin/wp-search-with-algolia/

Hi, Michail. Thanks for using WP Search with Algolia. At the WordPress plugin repo, we have a Support page where you can submit your request for support and interact with the developer directly. Thank you.

i am trying to use your plugin with algolia search in wp and i want to add search filters like for a spesific category, i looked that the algolia api has an option for this to happen with php for example:

// Search the “category” facet for values matching “phone”
// in records having “Apple” in their “brand” facet.
$index->searchForFacetValues(“category”, “phone”, [
‘filters’ => ‘brand:Apple’
]);

i am wondering if its posible to make the filtered search from your plugin directly
if its possible please let me know how its done

thanks a lot for your time
Michail

Hi Jay,

Can you provide what code you’re using thus far? It’ll help us make sure we’re providing accurate amended snippets to help here. For example if you’re adding this via a callback on say the `algolia_post_shared_attributes` hook from Darren’s example above.

Going to assume a moment, but if you have something like this:

“`
$geodata = get_field( ‘geodata_field’, $post->ID );

if ( ! empty( $geodata ) ) {
$attributes[ ‘_geoloc’ ] = $geodata;
}
“`
And `$geodata` is that JSON data directly, then I think you’d want to do this:

“`
$attributes[‘_geoloc’][] = $geodata;
“`

This turns the `$attributes[‘_geoloc’]` index into a nested array itself.

If your latitude and longitude are stored in their own then perhaps something like this:

“`
$geolat = get_field( ‘geodata_lat’, $post->ID );
$geolng = get_field( ‘geodata_lng’, $post->ID );
$geodata = [ ‘lat’ => $geolat, ‘lng’ => $geolng ];
$attributes[‘_geoloc’][] = json_encode( $geodata );
“`
This would construct an array with the key/value pairs, and then encode and store in the same way on the returned `$attributes`

I am having One issue though and wondering if you have any thoughts –

https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/

I’m trying to pass geolocation fields from ACF like:
“_geoloc”: {
“lat”: 40.639751,
“lng”: -73.778925
}

I’m not sure how to build a nested array like this based on your instructions above.. Any thoughts?

Just making sure I’m understanding, you’re wanting to change where the search takes place in a given query, because the SKU is long?

Based on the link provided, thank you for that, I think we’d want to get you adding in the sku to shared attributes spot, and them parsed out similar to what the docs page shows where you’re breaking it up into smaller chunks. Then once those are indexed, add that new index to the searchable parts in your Algolia dashboard.

Here it is!
https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/how-to/how-can-i-make-queries-within-the-middle-of-a-word/
Actually, i just wanna search for SKU. But my problem is sku is too long ( more than 6 characters )… that why i wanna change it!
Thanks bro!

Hey Minh,

Can you link us to the article you are referring to? I’m not sure about this one offhand and how to possibly help with it. It’s potentially an Algolia Dashboard configuration change needing made, outside of the WP Search with Algolia portion of the overall process and integration.

Hi Daz,

Something like the code in the following GitHub gist should help.

https://gist.github.com/tw2113/64c1598758f0540265dce8cbd7aa590a

This checks the current product/post getting indexed, and retrieves if it’s marked as a hidden catalog item for WooCommerce. If it is considered hidden, we return false to make it not get indexed. Otherwise it should get indexed.