I am getting this errow when I try to build the index:
{“error”:{“root_cause”:[{“type”:”mapper_parsing_exception”,”reason”:”Mapping definition for [post_modified_object] has unsupported parameters: [path : full] [fields : {week={type=integer}, dayofweek_iso={type=integer}, month={type=integer}, hour={type=integer}, year={type=integer}, dayofweek={type=integer}, m={type=integer}, day={type=integer}, dayofyear={type=integer}, minute={type=integer}, second={type=integer}}]”}],”type”:”mapper_parsing_exception”,”reason”:”Failed to parse mapping [post]: Mapping definition for [post_modified_object] has unsupported parameters: [path : full] [fields : {week={type=integer}, dayofweek_iso={type=integer}, month={type=integer}, hour={type=integer}, year={type=integer}, dayofweek={type=integer}, m={type=integer}, day={type=integer}, dayofyear={type=integer}, minute={type=integer}, second={type=integer}}]”,”caused_by”:{“type”:”mapper_parsing_exception”,”reason”:”Mapping definition for [post_modified_object] has unsupported parameters: [path : full] [fields : {week={type=integer}, dayofweek_iso={type=integer}, month={type=integer}, hour={type=integer}, year={type=integer}, dayofweek={type=integer}, m={type=integer}, day={type=integer}, dayofyear={type=integer}, minute={type=integer}, second={type=integer}}]”}},”status”:400}
]]>When I search for keywords, it (maybe) also including the terms from Related Products
On few occasions, these are not really relevant for “Search” , but works fine for browsing similar products.
How can we exclude results from related products?
Is there a way we can define weight for title, content, tags, brands etc?
Thanks
]]>When I search, the woocommerce price slider filter does not show up.
Otherwise, it used to show updated, min & max price range for Search Results
Please let me know
]]>Hi ,
Does the plugin support WordPress multisite? i.e indexing all the posts in all the sites of a network? And searching for a term through the entire network?
]]>When I turn on ElasticSearch, my Disqus comments appear on EVERY page, regardless of the status of the setting for allowing comments. Turning off ES makes the problem disappear.
Also, some short codes get ignored — see https://www.xeroshoes.com/faq vs. the staging site where we’ve turned off ES — https://xeroshoes.staging.kinsta.com/faq
Looking forward to your help.
THANKS
]]>Hi,
In list of my custom_type, if started elasticsearch (and plugin show the message ES indexer: enabled) don’t are present any result.
If I stopped elasticsearch service (and plugin show the message Es indexer: enabled to connect) in the list return too see the correct result (same post of custom_type)
where is the problem for you?
Hi,
I have installed the plugin in my site and i’ve seen a problem with the custom post type. Explain more…
In the file taxonomy-(custom-taxonomy-).php i have a loop for the all object of custom-type…
if the result are found in DB (without Elasticsearch) the loop found all the result, having a normal behavior.
But if take the result from Elasticsearch in the $post variable not exist anyone object of the custom-type but all object are the default (post) type.
It is as wordpress not recorgnize the custom if the result come from Elasticsearch plugin.
For bypass this problem have add the next snippet before the loop
$args = array(‘post_type’ => “my-custom-post-type”);
query_posts($args);
//loop
if ( have_posts() ) :
…
…
On this mode the loop return again the post for my scope.
This is a workaround. For optimal solution what’s the your’s advice
I have just installed your plugin, but I can’t get it to work.
When I try to index my site’s content via the “Elasticsearch Indexer Dashboard”, but the process gets stuck with this error message :
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [post_modified_gmt_object] has unsupported parameters: [path : full] [fields : {minute={type=integer}, dayofweek_iso={type=integer}, second={type=integer}, dayofyear={type=integer}, month={type=integer}, year={type=integer}, dayofweek={type=integer}, m={type=integer}, day={type=integer}, hour={type=integer}, week={type=integer}}]"
}
],
"type": "mapper_parsing_exception",
"reason": "mapping [post]",
"caused_by": {
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [post_modified_gmt_object] has unsupported parameters: [path : full] [fields : {minute={type=integer}, dayofweek_iso={type=integer}, second={type=integer}, dayofyear={type=integer}, month={type=integer}, year={type=integer}, dayofweek={type=integer}, m={type=integer}, day={type=integer}, hour={type=integer}, week={type=integer}}]"
}
},
"status": 400
}Do you understand what is going on ? I’m an elasticsearch noob…
The website has a lot of content in custom post types, could it be related ?
]]>Hi,
I’m glad that I found your plugin ??
It works very well in my case, but I would like to disable fuzzy search.
Is this possible by using a filter?
Right if I search for “Set Fire to the Rain” I get more than only the product with that name. Actually I’m see pagination links for the complete shop with 25K of products.
Hi Mikael,
After a lot of reworking, we got 120,000 Woocommerce products indexed and page loads have come down from 3 weeks to 3 seconds. We deactivated some widgets and plugins and could see the speed increase as we did so. But we’re still seeing 200 – 300 SQL Selects/Inserts/Updates, much of it to the options table (mainly inserts/updates).
Having looked at your code, you’re trying to hijack WP-Query as often as possible but it looks like some post_types may be problems, such as nav_menu_item.
The profiler works really well (great when you get to the bottom and see 1 Elastic query!) but any ideas on tracking these remaining SQL statements?
BTW, brilliant plugin! Have now given up on my SOLR plugin!
Regards,
David Q
Installed and indexed. When searching on the frontend, we just get an error from Guzzle:
Fatal error: Uncaught exception ‘Guzzle\Http\Exception\ClientErrorResponseException’ with message ‘Client error response [status code] 400 [reason phrase] Bad Request [url] https://127.0.0.1:9200/boltons-1/post/_search’ in /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/guzzle/guzzle/src/Guzzle/Http/Exception/BadResponseException.php:43 Stack trace: #0 /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/guzzle/guzzle/src/Guzzle/Http/Message/Request.php(145): Guzzle\Http\Exception\BadResponseException::factory(Object(Guzzle\Http\Message\EntityEnclosingRequest), Object(Guzzle\Http\Message\Response)) #1 [internal function]: Guzzle\Http\Message\Request::onRequestError(Object(Guzzle\Common\Event), ‘request.error’, Object(Symfony\Component\EventDispatcher\EventDispatcher)) #2 /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/symfony/event-dispatcher/EventDispatcher.php(164): call_user_func(Array, Object(Guzzle\Common\Event), ‘request.error’, Object(Symfony\C in /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/GuzzleConnection.php on line 277
]]>Everything is installed and working from what I can tell. With this plugin and elasticsearch I have been able to expand my search results to include a Custom Post Type Title, however the search is not returning any results from a custom field (multi-line text) associated with this CPT. Is there a way to add this custom field to be indexed by elasticsearch?
]]>Hi,
when the plugin is activated, does it replace the WP default search?
Is it possible to activate the autocomplete feature of elastic search?
Thank you in advance!
]]>Hello,
I installed your plugin. And all went fine. I can make searchs and I see it brings more results then the wp_query.
But I am getting a strange conflict. My menu has some categories. And the categories are loading a page that I created. All categories pages are getting this page.
All others page like frontpage, posts, page and woocommerce seems fine.
I tried to save error_log in php.ini but I am not getting any error.
What I am doing wrong?
Best
]]>Hi;
I need filter products for any category and any parameters. I could not results.
I’ll like help.
Hello,
Just installed the updated version (tried to do an update and it deleted the old version and then failed saying “folder already exists” – deleted the folder in the plugins directory and it installed perfectly) and I’m getting this error when I try to Reindex –
`
The stream or file “/var/www/html/wp-content/plugins/elasticsearch-indexer/../../uploads/logs/elasticsearch.log” could not be opened: failed to open stream: No such file or directory’
Normally I would try and create that path/directory but since it doesn’t tell me exactly where it’s supposed to be … ??
Rob
]]>Hello,
Just installed ElasticSearch and wanted to try out your plugin. I donwloaded, unzipped, uploaded to the plugins folder and the I got stumped already – on Github it says run “composer install” inside the directory.
How? ??
Is there a way to run the “composer.json” file?
I tried activating the plugin without running the composer – but I got errors of course.
Thanks!
Rob