You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that when using search sever side eg. $results = Injector::inst()->get(AlgoliaQuerier::class)->fetchResults(...)
I am getting an error with the fact that this method seems to use the adminApiKey rather than the expected searchApiKey
I am unsure if this is my misunderstanding of the setup or a bug.
My workaround was just to create a new "master" key on Algolia with all permissions enabled for both indexing and searching.
The text was updated successfully, but these errors were encountered:
@josephlewisnz you're correct - it looks like fetchResult calls AlgoliaService::getClient() which uses the Admin API key by default. An enhancement would be to have AlgoliaService::getSearchClient() which uses the right key.
Hey I've set up the module as normal including:
I've noticed that when using search sever side eg.
$results = Injector::inst()->get(AlgoliaQuerier::class)->fetchResults(...)
I am getting an error with the fact that this method seems to use the
adminApiKey
rather than the expectedsearchApiKey
I am unsure if this is my misunderstanding of the setup or a bug.
My workaround was just to create a new "master" key on Algolia with all permissions enabled for both indexing and searching.
The text was updated successfully, but these errors were encountered: