Algolia Search needs application Key [solved]

[wafer-li]

To be simple:

Let's see here:

hexo-theme-next/source/js/src/algolia-search.js

Lines 6 to 8 in e12bb0b

	var isAlgoliaSettingsValid = algoliaSettings.applicationID &&
	algoliaSettings.apiKey &&
	algoliaSettings.indexName;

It needs an application key and etc.

So, where does it come from? Here:

hexo-theme-next/layout/_partials/head/head.swig

Lines 124 to 130 in 1cb4d08

	algolia: {
	applicationID: '{{ theme.algolia.applicationID }}',
	apiKey: '{{ theme.algolia.apiKey }}',
	indexName: '{{ theme.algolia.indexName }}',
	hits: {{ theme.algolia_search.hits | json_encode }},
	labels: {{ theme.algolia_search.labels | json_encode }}
	}

It should be an application key field in the config.

hexo-theme-next/_config.yml

Lines 641 to 648 in 7e71b4b

	algolia_search:
	enable: false
	hits:
	per_page: 10
	labels:
	input_placeholder: Search for Posts
	hits_empty: "We didn't find any results for the search: ${query}"
	hits_stats: "${hits} results found in ${time} ms"

Without it, it will complain about the Algolia Setting is invalid.

In fact, in the NexT 5.1.x, there is a doc describe the application keys:

[wafer-li]

After a carefully check, this does not duplicate with #67

This bug I show is related to the lack of doc or lack of the algolia config.

[sli1989]

i am going to take a PR in theme-next-algolia-instant-search to add the configurations, and wondering how to index the content with the latest hexo-Algolia.

---

maybe it's a different way to index using instantsearch.js.

---

it's too hard for me using instantsearch.js for full test search instead of hexo-algolia. 😂