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
{{ message }}
This repository was archived by the owner on May 9, 2019. It is now read-only.
I installed the system on a preproduction server.
I expected it to fetch data from production, but not to write to the index
What happened instead?
Production index is rewritten by data from preproduction instance
Technical info
WordPress version: 4.9.8
Algolia Search plugin version: 2.11.22.11.2
I would like more control on indexing vs search + production vs preproduction.
Algolia provides a search-only API key, but WordPress plugin does not work if both key (search-only + admin) are set. This is the first issue, because I would like preproductions servers to only rely upon the former.
Even so, in the event I would like to test the indexing to, I'd like to be able to disable. Currently there is no hook that I know, to disable indexing on an installation (for example to restrict for a given value of WP_ENV/developer/docker vm/hostname/machine/...). Whether from cli or admin UI, there is always a re_index function calling re_index method. A filter to disable this behavior (CLI | UI) would be welcome.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What did you expect to happen?
I installed the system on a preproduction server.
I expected it to fetch data from production, but not to write to the index
What happened instead?
Production index is rewritten by data from preproduction instance
Technical info
I would like more control on indexing vs search + production vs preproduction.
Algolia provides a search-only API key, but WordPress plugin does not work if both key (search-only + admin) are set. This is the first issue, because I would like preproductions servers to only rely upon the former.
Even so, in the event I would like to test the indexing to, I'd like to be able to disable. Currently there is no hook that I know, to disable indexing on an installation (for example to restrict for a given value of WP_ENV/developer/docker vm/hostname/machine/...). Whether from cli or admin UI, there is always a
re_index
function callingre_index
method. A filter to disable this behavior (CLI | UI) would be welcome.The text was updated successfully, but these errors were encountered: