vhauri

Hi,

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi,

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi,

Elasticsearch tends to introduce breaking changes so any time you use a version newer than the latest tested version there could be unexpected behavior.

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi,

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi,

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi,

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi,

All support for ElasticPress is provided via our Github issues page: https://github.com/10up/ElasticPress/issues/

Please share your issue report there and be sure to include all requested information from the template.

Hi, the plugin is free and open source but requires a working Elasticsearch instance of the ElasticPress.io service.

@dciphered EP now supports up to version 7.5 of ES starting with version 3.3.

Hi @menathor,

We provide all support for the plugin via Github at https://github.com/10up/ElasticPress.

ElasticPress uses an Indexable class which can be extended to connect any custom table in WordPress to use Elasticsearch. You can take a look at the Post, Term, or User Indexables (which are built into the plugin) for examples. It’s not a small undertaking, however, so keep that in mind.

If you have any other questions, feel free to reach out via Github to ensure a timely response.

Per our pinned post on this support forum, we provide all support through Github. You can file issues at https://github.com/10up/ElasticPress.

The relevance score of each post is part of the JSON object returned by Elasticsearch and can certainly be accessed in the plugin. This filter offers access to the entire Elasticsearch response in WordPress https://10up.github.io/ElasticPress/ep_es_query_results.html

If you have additional issues please feel free to file a Github ticket and we will respond.

Per our pinned post on this support forum, we provide all support through Github. You can file issues at https://github.com/10up/ElasticPress.

It seems this issue has been resolved, but if you have additional issues please feel free to file a Github ticket and we will respond.

Hi @emoteek ,

Per our pinned post on this support forum, we provide all support through Github. You can file issues at https://github.com/10up/ElasticPress.

In order to confirm that self-hosted connections are working, I did the following:

Set up a free trial account on Elastic.co with all default options (IO optimized, basic VMs, etc)
Enter URL for Elasticsearch from value copied in Elastic.co dashboard into WP/ElasticPress settings page
Confirm 401 response (expected as credentials have not been entered)
Set ES_SHIELD value as username:password based on values pasted from Elastic.co dashboard
Run a successful index.
Perform a test search on the front end, confirm I get a 200 result from my Elastic.co endpoint
While Elasticsearch does have a lot of options, this can cause confusion when trying to set up a self-hosted connection. While we do support the plugin side of a self-hosted solution, I do caution you that setup and maintenance of these servers can be quite difficult, which is why we built a service around this (ElasticPress.io) in the first place.

Again, we will 100% stand behind our plugin and fix any bugs that exist in the plugin, but we cannot provide troubleshooting for individual connectivity issues with self-hosted solutions through Github or this forum. We do, however, provide custom consulting if you need to use a specific solution such as Elastic.co or another self-hosted solution like AWS Elasticsearch Service.

Hi @vahanavagyan1 @jagadeeshvarma ,

Per our pinned post on this support forum, we provide all support through Github. You can file issues at https://github.com/10up/ElasticPress.

In order to confirm that the approach in the security tutorial is still working, I followed the following steps:

• Set up a free trial account on Elastic.co with all default options (IO optimized, basic VMs, etc)
• Enter URL for Elasticsearch from value copied in Elastic.co dashboard into WP/ElasticPress settings page
• Confirm 401 response (expected as credentials have not been entered)
• Set ES_SHIELD value as username:password based on values pasted from Elastic.co dashboard
• Run a successful index.
• Perform a test search on the front end, confirm I get a 200 result from my Elastic.co endpoint

While Elastic.co does have a lot of options, this can cause confusion when trying to set up Elasticsearch (which itself is quite complex). While we do support the plugin side of a self-hosted solution, I do caution you that setup and maintenance of these servers can be quite difficult, which is why we built a service around this (ElasticPress.io) in the first place.

Again, we will 100% stand behind our plugin and fix any bugs that exist in the plugin, but we cannot provide troubleshooting for individual connectivity issues with self-hosted solutions through Github or this forum. We do, however, provide custom consulting if you need to use a specific solution such as Elastic.co.

• This reply was modified 5 years ago by vhauri.
• This reply was modified 5 years ago by vhauri.

Hi David,

Thank you for your feedback on the plugin. To clarify, we do not impose any sort of restrictions on your ability to use Autosuggest regardless of whether you self-host, use a cloud provider, or use our ElasticPress.io service. All you need to do is add your Autosuggest endpoint (this is the same as your search endpoint) in the ElasticPress plugin settings under the Autosuggest Feature. We have many, many folks in the WordPress community using Autosuggest quite successfully who host their own infrastructure.

Can you clarify where and how you’ve asked us for support? I see one ticket on Github from you where we responded to your questions https://github.com/10up/ElasticPress/issues/1041 that has been closed for months. We did our best to help you, but ultimately we are unable to provide free support for issues related to server-side problems and we do ask that folks refer to existing Github issues to find questions that have already been answered.

We are also not able to recommend approaches to securing your server and/or exposing Autosuggest endpoints, since privacy is a major concern and we are not qualified to advise you on the best way to secure an Elasticsearch server within your unique infrastructure.

If you feel there is a bug in the current version (2.8.2) that is preventing you from getting Autosuggest working, please provide a Github ticket and include screenshots of the settings page where you’ve configured Autosuggest. This will enable us to pinpoint the issue. Again, if it’s related to the plugin, we will be happy to fix this for free.