Is it possible to configure filters on certain fields in an index directly in the plugin interface?
I have an event index and I would like past events not to appear in my search results.
Thanks
]]>I have a static site being served by CloudFront. I’m currently using Algolia which works flawlessly but the search queries are limited and are exhausted quickly.
My question is will this work on a static site? Also do I need to configure anything on the server?
Thank you. Best Regards.
]]>I added a custom taxonomy. And now I want to add it to instantsearch module – https://cln.sh/f59PNnjl
How to do that?
]]>Algolia says that this is a third party software, which Algolia does not provide the technical support.
When you delete this plugin, it doesn’t delete codes in your blog posts and pages. This would cause lots of problems in future.
]]>I have a Multisite network with about a dozen subsites, and although it’s all one cohesive website (from a design and content perspective), there are instances where only one of the subsites include a particular Custom Post Type.
WP Search with Algolia is activated on every subsite, and the same prefix is used for all indices. This means that as long as the CPT is available on every subsite (Pages, Posts) the plugin returns results as expected, network-wide.
The problem comes where a single subsite has a CPT enabled (say, an Events CPT or a Products CPT). It doesn’t seem possible from within the plugin to allow results from those indices to be returned from the main site’s autocomplete… The UI where you choose which CPTs to use in the autocomplete can only list the CPTs for the current subsite.
I guess my question is whether there’s some programmatic way to dictate a list of indices that could supersede the Autocomplete options for the plugin.
Sorry for writing a book, hopefully that’s clear!
]]>I have noticed a lot of queries on my Algolia dashboard and I would like to limit them. I wanted to know if re-indexing the products would cost API queries, and if so, how to limit it.
Are there other ways to limit API queries? Currently, what I have done is trigger a query from a minimum of 3 letters, but that is not sufficient.
Thkans !
]]>the error is as follow POST https://places-1.algolianet.com/1/places/query?x-algolia-agent=Algolia%20for%20JavaScript%20(3.35.1)%3B%20Browser%20(lite)%3B%20Algolia%20Places%201.19.0&x-algolia-application-id=&x-algolia-api-key= net::ERR_NAME_NOT_RESOLVED
]]>