Felipe Elia

Hi! As that is an Elasticsearch plugin that might not be available in most of Elasticsearch configurations, no, it is not in our roadmap right now.

In terms of how you can integrate that with ElasticPress, you can use our filters to do that, especially ep_default_analyzer_filters.

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

Hi! It is probably happening because the indexable content report is timing out. You can disable that specific report by adding this snippet to your codebase:

add_filter(
	'ep_status_report_reports',
	function( $reports ) {
		unset( $reports['indexable'] );
		return $reports;
	}
);

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

Hi!?We don’t provide support here, please open an issue in our?GitHub repository?sharing your ElasticPress Status Report. Thanks!

Hi! Actually, when a product is changed, ElasticPress will automatically sync only that product instead of re-indexing everything. If you need to update only a group of products (or posts) the easiest way is to use the WP-CLI command (wp elasticpress sync –include=<post_ids>).

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

Hi there! Closing this out as it was answered in this GitHub issue already: https://github.com/10up/ElasticPress/issues/3723

As?we don’t provide support here,?any follow up conversation is happening in the GitHub issue already opened: https://github.com/10up/ElasticPress/issues/3707

Hi. That generally happens because your webserver has a problem communicating to your Elasticsearch server. Unfortunately, as that is specific to your hosting, we can’t help you with that.

You can always install our debugging plugin (as described in this article), and check which messages Elasticsearch is sending back to you. The plugin also gives you the time taken for each query, which will help you to measure if it is really your ES server that is taking too long or if it is something else.

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

Hi!

So, as the message suggests, you’ll need to add in your code a snippet listing to ElasticPress which metafields exactly you need to index. This article here has 2 snippets that can help you with that: https://elasticpress.zendesk.com/hc/en-us/articles/360052019111

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

Hi! Unfortunately, we can’t help you as?we don’t provide support here nor can help with infrastructure problems. The main thing you will need to do is to make sure the webserver hosting the site can contact the Elasticsearch server directly (generally curl calls via terminal can help to debug that.)

Hi! We don’t provide support here, please open an issue in our?GitHub repository sharing your ElasticPress Status Report. Thanks!

Hi @kostanv, do you mind opening an issue in GitHub with all the details? I could not reproduce that problem. Thanks in advance!

Hi! As stated in the?FAQ section, I do not provide support here. Can you please open an issue in the?GitHub repository, please? Thanks!

The plugin does not work with attachments yet. To keep track of the progress of that please see https://github.com/felipeelia/cf7-repeatable-fields/issues/12 (Pull Requests are welcomed!)

I’ve moved the new problem to GitHub: https://github.com/felipeelia/cf7-repeatable-fields/issues/61

As there is no other actionable item in this thread, I’m marking it as resolved.

Hi! As stated in the?FAQ section, I do not provide support here. Can you please open an issue in the GitHub repository, please? Thanks!