Felipe Elia

Hi! That code should work, but it should be added to a plugin, not to your theme’s functions.php file, for example.

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

Hi! Version 2.6.2 was released back in 2018 and the plugin changed a lot during these 6 years (especially from v2 to v3.) What was done by the ep_format_args( $query_args )?method is now majorly handled by the Indexables::factory()->get( 'post' )->format_args( $query_args, $query ) method.

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

Hi there!

ElasticPress does not rely on any cron jobs: posts are sync’d to Elasticsearch in the moment you save them. You can check for errors in the Status Report page, but I’d recommend you to double-check your cache setup. Things could be set in a way that although the post was saved, the cache for your archive pages were not flushed, for example.

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

• This reply was modified 3 months, 1 week ago by Felipe Elia.

The sync via dashboard works using several AJAX calls. In some setups, if things are heavily cached, WP will send the same response to ElasticPress over and over again, instead of processing what needs to be done. If you had it working using WP-CLI you should be all set now, but if you need to sync again in the future using the dashboard, I recommend you to start investigating all cache layers the website may have.

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

It is probably not related to the XYZ PHP plugin, but to some code that you have running there. If you have access to your terminal, try to run wp elasticpress sync --setup --yes --show-errors and check if any errors logged help you identify which script is preventing your sync to run.

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

As we don’t provide support here, all follow-up questions and comments will happen on this issue in our GitHub repository.

For reference, there is a new support article covering that topic: https://www.elasticpress.io/documentation/article/how-to-programmatically-index-posts-using-elasticpress/

Hi there!

You can call \ElasticPress\Indexables::factory()->get( 'post' )->index( $post_id, true ); to index an individual post (or product.)

If you want to index them in batches, you can add them to the queue (using \ElasticPress\Indexables::factory()->get( 'post' )->sync_manager->add_to_queue( $post_id )) and then index the queue using ElasticPress\Indexables::factory()->get( 'post' )->sync_manager->index_sync_queue();.

Ultimately, you can use \ElasticPress\IndexHelper::factory()->full_index( $args ); to run the process as the plugin itself runs it. See how we do it in the WP-CLI command for reference.

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

• This reply was modified 5 months, 4 weeks ago by Felipe Elia.

I’m not sure I follow the question, but indexing unpublished materials is the whole point of the Protected Content feature. If your queries are requesting those posts, you’ll need to tweak your WP_Query parameters to hide them back.

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

I recommend you to understand how your posts are being indexed in Elasticsearch and which fields are really being used in your searches. For that you can use our Debugging Add-On.

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

We don’t provide support here, can you please open an issue in our?GitHub repository? When you do that, please make sure you share how you are calling that ep_get_related_posts function (is the post_id really being passed?) You may also need to tweak the fields being used to find related posts. Thanks!

Hello there!

We do not provide any support for self hosted infrastructure, meaning that the person who set up the Elasticsearch server should know what the URL to that server should be. To test if it is working, you can use our debugging plugin.

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

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!