[priyanka_kethireddy]

10 months, 3 weeks ago #34199

Hi Team, We are getting below errors with the plugin, currently we are using wordpress version 6.2.2 and plugin version 22.9. Previously the wordpress version was 6.2, we didn’t have these errors, Is that because of the wordpress version update? Can you look into the errors?

wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient::execute_wpsolr_query called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/classes/engines/class-wpsolr-abstractsearchclient.php (1206)

wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient::get_results_data called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/classes/ui/widget/class-wpsolr-widget-facet.php (56)

Elasticsearch\Connections\Connection::process5xxError called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php (336)

Elasticsearch\Connections\Connection::Elasticsearch\Connections\{closure} called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/react/promise/src/FulfilledPromise.php (28)

in React\Promise\FulfilledPromise::then called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/ezimuel/ringphp/src/Future/CompletedFutureValue.php (65)

in GuzzleHttp\Ring\Future\CompletedFutureValue::then called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/ezimuel/ringphp/src/Core.php (341)

in GuzzleHttp\Ring\Core::proxy called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php (345)
in Elasticsearch\Connections\Connection::Elasticsearch\Connections\{closure} called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php (241)

in Elasticsearch\Connections\Connection::performRequest called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Transport.php (110)

in Elasticsearch\Transport::performRequest called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Client.php (1929)

in Elasticsearch\Client::performRequest called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Client.php (1353)

in Elasticsearch\Client::search called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/classes/engines/elasticsearch_php/class-wpsolr-searchelasticsearchclient.php (113)

in wpsolr\core\classes\engines\elasticsearch_php\WPSOLR_SearchElasticsearchClient::search_engine_client_execute called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/classes/engines/class-wpsolr-abstractsearchclient.php (1166)

in wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient::execute_query called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/classes/engines/class-wpsolr-abstractsearchclient.php (1116)

in wpsolr\core\classes\engines\WPSOLR_AbstractSearchClient::execute_wpsolr_query called at /code/wp-content/plugins/wpsolr-pro-gd/wpsolr/core/classes/ui/class-wpsolr-query.php (508)

[wpsolr]

10 months, 3 weeks ago #34201

It looks like a connection issue with Elasticsearch.