Modifying Search Query in Wordpress Plugin with Typesense API
TLDR Noorhalim needs help modifying search query in WordPress plugin. Digamber explains that instant search js is used, but queries can't be intercepted before reaching Typesense servers.
1
1
Feb 21, 2023 (7 months ago)
Noorhalim
07:43 AM1
Kishore Nallan
11:14 AMDigamber
11:16 AMhttps://www.algolia.com/doc/guides/building-search-ui/what-is-instantsearch/js/
As of this moment there isn’t a way to intercept the queries before it hits typesense servers
1
Noorhalim
02:56 PMFeb 22, 2023 (7 months ago)
Noorhalim
08:12 AMNoorhalim
08:12 AMDigamber
08:18 AMDigamber
08:18 AMNoorhalim
08:35 AMNoorhalim
08:35 AMNoorhalim
08:35 AMNoorhalim
08:36 AMNoorhalim
08:47 AMDigamber
08:49 AMwe keep a list of current instancs in window.swtInstance
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Implementing State Export Feature Using Typesense InstantSearch.js on Node.js Backend
Kyle needed help passing search state to backend for implementing an "Export" feature, while using Typesense InstantSearch. Jason provided multiple solutions including advice on using Typesense InstantSearch adapter. The issue was resolved after some iteration.
Typesense Sorting Query and Bug Report
michtio is new to Typesense and is querying sorting implementation. Jason shares resources and suggests use of specific adapters. However, michtio shares a bug found when applying a filter on Typesense. Jason asks for a GitHub issue to be opened for the bug.
Troubleshooting Typesense-Instantsearch Adapter Version Compatibility
Steve noticed JavaScript errors when using a specific typesense-instantsearch adapter with Instantsearch.js. Jason provided support but a solution is yet to be identified.
Issues with Search UI for Vector Search
WL is building a search UI for vector search and having issues with syntax, while Jason provides context on the issue.
Issue with Updated Javascript Dependencies in Typesense
em1nos faced an error after updating javascript dependencies. Jason suggested using `2.4.1-1` and to move 'query_by' to 'collectionSpecificSearchParameters' which solved the issue and was identified as a bug.