Felipe Elia

The ElasticPress Custom Results post type is not intended to be displayed to end users, it is just the way the plugin controls how search results should be changed given a certain search term.

As?we don’t provide support here, please open an issue in our?GitHub repository if you need further clarification. If that is the case, please make sure you describe your use case on why you think that post type should be displayed to all users. Thanks!

Hi! Actually, that is not related to ElasticPress, but something your browser adds automatically. You can work around that by following something like this article.

Hi! Most probably those plugins will not use Elasticsearch aggregations, making things a bit slower. Depending on the size of your website, the difference would be negligible though, you’d need to test.

As?we don’t provide support here, feel free to ask any follow-up questions in our?GitHub repository. Thanks!

Hi! To make all instances use the same index name, you’ll need to use the ‘ep_index_name’ filter (see here.)

As?we don’t provide support here, feel free to ask any follow-up questions in our?GitHub repository. Thanks!

Hi! I’ve just replied to a very similar question in our GitHub repo here.

As we do not provide support here, please ask any follow up questions in that topic. Thanks!

Hi! As stated in the linked article, you should use “site__in”, instead of “sites”.

As?we don’t provide support here, if you have any follow-up questions, please open an issue in our?GitHub repository. Thanks!

Hi! Yes, ElasticPress indexes files in the Media Library through its “Documents” feature — it will require your Elasticsearch server to have the documents ingest plugin though.

As we don’t provide support here, feel free to ask any follow-up questions in our?GitHub repository. Thanks!

Hi! We don’t provide support here, but it seems we already have an issue with that bug here. Do you mind adding a comment there saying what is the exact value you are setting as synonyms? Thanks.

Hi! Currently, Elasticsearch 7.10 is our latest fully tested version, but all tests so far indicate it is safe to use Elasticsearch with any 7.x release or even 8. You can dismiss that warning, but if you have any problems with that version let us know.

As we don’t provide support here, if that happens please open an issue in our?GitHub repository. Thanks!

We don’t provide support here, can you please open an issue in our?GitHub repository? Thanks!

As?we don’t provide support here,?this was answered in https://github.com/10up/ElasticPress/issues/3796.

Hi!?If you have access to WP-CLI, it would probably be an easier solution (wp elasticpress sync --include=<post_ID> would be the command.)

As?we don’t provide support here, if you have any follow-up questions, please open an issue in our?GitHub repository. Thanks

It seems your database is not handling the number of posts being processed per batch. You can try to run the command with a lower number:

wp elasticpress sync --show-errors --per-page=100

Give that a try, it’ll probably solve the problem.

As?we don’t provide support here, if you have any follow-up questions, please open an issue in our?GitHub repository. Thanks

Hi! Although it is not in our roadmap for the next few months, this is definitely something we have under our radar for next year. Thanks for asking!

As?we don’t provide support here, if you have any follow-up questions, please open an issue in our?GitHub repository. Thanks

Hi! That error indicates the request timed out after 5 seconds, so you’ll need to check with your Elasticsearch hosting provider for any downtime or general availability.

As?we don’t provide support here, if you have any follow-up questions, please open an issue in our?GitHub repository sharing your full status report. Thanks!