Releases: Smile-SA/elasticsuite
2.8.17
🐛 Fixes
- Fix #2448 ensure effective collection reloading 2.8.x by @rbayet in #2472
- Feature #2431 Opt. zero product position indexing 2.8.x by @rbayet in #2478
- Feature #2437 Allow indexing 0 and false values (2.8.x) by @rbayet in #2480
- Fixes #2434 Support false/zero value in catalog rules (2.8.x) by @rbayet in #2487
Full Changelog: 2.8.16.1...2.8.17
What's Changed
- Fix 2448 ensure effective collection reloading 2.8.x by @rbayet in #2472
- Feature #2431 Opt. zero product position indexing 2.8.x by @rbayet in #2478
- Feature #2437 Allow indexing 0 and false values (2.8.x) by @rbayet in #2480
- Fixes #2434 Support false/zero value in catalog rules (2.8.x) by @rbayet in #2487
Full Changelog: 2.8.16.1...2.8.17
2.10.9.1
2.9.10.1
2.10.9
Changes
🚀 Going forward
This release is the first pavement of a bigger plan for ElasticSuite. We decided to commit more resources to the maintenance and development of your favorite Magento module. That means, starting this version, we’ll include a completely optional telemetry module to understand how you are using this extension and where to focus our effort in improvement.
We know this kind of announcement can make some uncomfortable, that’s why we want to be completely transparent about what we plan to collect and how, available here.
On the first launch after the upgrade, you’ll see a lightbox offering you the opportunity to support this effort or not. Deactivation of the telemetry service will have no impact on the quality of the module, which will continue to serve you as always.
📦 Functional
Adaptative Price Slider
Starting from this release, we added an adaptative Price Slider (#2371 #2372).
This feature, which is disabled by default, can be enabled through Stores > Configuration > Elasticsuite > Catalog Search > Enable Adaptative Slider.
If enabled, when necessary to support the presence of outlier values in the navigation context (for instance, a very high price amidst a majority of low prices), the price slider behavior changes so that the middle of the slider range corresponds to the median price instead of the price at the middle of the range.
This is particularly useful when browsing a page (category or search results) that contains a high number of products within the same price range, and some "outliers" really far of the average price. Eg : a search result page with 99% of products between 10$ and 20$, and two products having prices of 900$ and 1000$.
Visual Merchandiser (Magento Commerce)
- Adding product from SKU has been added by @PierreGauthier in #2319 and #2330
UX refactoring of the optimizer screen :
- Refactoring of proportionals boost operators by @botisSmile and @rbayet #2318 #2334 #2351 #2354 #2362 #2367
- Fix fieldset order by @botisSmile in #2334
Page Builder compatibility :
- Fix proper appliance of sort orders. by @romainruaud in #2361 #2397
- Prevent side effect when building widgets conditions based on virtual… by @romainruaud in #2391
- Support pre-existing PageBuilder widgets (2.9.x) by @rbayet in #2342
💻 Technical
- Fixing the appliance of "is_discount" rules across differents customer groups by @rbayet in (#2401)
- Add exclude in term aggregation by @PierreGauthier in #2336
- Add min_doc_count in term aggregation by @PierreGauthier in #2363
- Prevent rejection of documents with large description (2.8.x) by @rbayet in #2378
- Change tracking API definition by @romainruaud in #2364
- Fix category uid mapping by @romainruaud and @JeroenVanLeusden in #2347
- Rework send tag function to be compatible with native JS (mad… by @botisSmile in #2360
- Fixes #2316, added salt to id of the row element by @vahonc in #2359
- Fix issue #2387 with multiselect condition save by @illidar in #2388
- Fixes #2368, avoid use 'match' as an identifier by @vahonc in #2386
- Fix for #2383 : Redirect to product page if only one result doesn't work in case of void return type in the controller by @vahonc in #2395
New Contributors
- @hbarza made their first contribution in #2344
- @clawfire made their first contribution in #2376
- @illidar made their first contribution in #2388
Full Changelog: 2.10.8.1...2.10.9
2.9.10
Changes
🚀 Going forward
This release is the first pavement of a bigger plan for ElasticSuite. We decided to commit more resources to the maintenance and development of your favorite Magento module. That means, starting this version, we’ll include a completely optional telemetry module to understand how you are using this extension and where to focus our effort in improvement.
We know this kind of announcement can make some uncomfortable, that’s why we want to be completely transparent about what we plan to collect and how, available here.
On the first launch after the upgrade, you’ll see a lightbox offering you the opportunity to support this effort or not. Deactivation of the telemetry service will have no impact on the quality of the module, which will continue to serve you as always.
📦 Functional
Adaptative Price Slider
Starting from this release, we added an adaptative Price Slider (#2371 #2372).
This feature, which is disabled by default, can be enabled through Stores > Configuration > Elasticsuite > Catalog Search > Enable Adaptative Slider.
If enabled, when necessary to support the presence of outlier values in the navigation context (for instance, a very high price amidst a majority of low prices), the price slider behavior changes so that the middle of the slider range corresponds to the median price instead of the price at the middle of the range.
This is particularly useful when browsing a page (category or search results) that contains a high number of products within the same price range, and some "outliers" really far of the average price. Eg : a search result page with 99% of products between 10$ and 20$, and two products having prices of 900$ and 1000$.
Visual Merchandiser (Magento Commerce)
- Adding product from SKU has been added by @PierreGauthier in #2319 and #2330
UX refactoring of the optimizer screen :
- Refactoring of proportionals boost operators by @botisSmile and @rbayet #2318 #2334 #2351 #2354 #2362 #2367
- Fix fieldset order by @botisSmile in #2334
Page Builder compatibility :
- Fix proper appliance of sort orders. by @romainruaud in #2361 #2397
- Prevent side effect when building widgets conditions based on virtual… by @romainruaud in #2391
- Support pre-existing PageBuilder widgets (2.9.x) by @rbayet in #2342
💻 Technical
- Fixing the appliance of "is_discount" rules across differents customer groups by @rbayet in (#2400)
- Add exclude in term aggregation by @PierreGauthier in #2336
- Add min_doc_count in term aggregation by @PierreGauthier in #2363
- Prevent rejection of documents with large description (2.8.x) by @rbayet in #2378
- Change tracking API definition by @romainruaud in #2364
Full Changelog: 2.9.9.1...2.9.10
2.8.16
Changes
🚀 Going forward
This release is the first pavement of a bigger plan for ElasticSuite. We decided to commit more resources to the maintenance and development of your favorite Magento module. That means, starting this version, we’ll include a completely optional telemetry module to understand how you are using this extension and where to focus our effort in improvement.
We know this kind of announcement can make some uncomfortable, that’s why we want to be completely transparent about what we plan to collect and how, available here.
On the first launch after the upgrade, you’ll see a lightbox offering you the opportunity to support this effort or not. Deactivation of the telemetry service will have no impact on the quality of the module, which will continue to serve you as always.
📦 Functional
Adaptative Price Slider
Starting from this release, we added an adaptative Price Slider (#2371 #2372).
This feature, which is disabled by default, can be enabled through Stores > Configuration > Elasticsuite > Catalog Search > Enable Adaptative Slider.
If enabled, when necessary to support the presence of outlier values in the navigation context (for instance, a very high price amidst a majority of low prices), the price slider behavior changes so that the middle of the slider range corresponds to the median price instead of the price at the middle of the range.
This is particularly useful when browsing a page (category or search results) that contains a high number of products within the same price range, and some "outliers" really far of the average price. Eg : a search result page with 99% of products between 10$ and 20$, and two products having prices of 900$ and 1000$.
Visual Merchandiser (Magento Commerce)
- Adding product from SKU has been added by @PierreGauthier in #2319 and #2330
UX refactoring of the optimizer screen :
- Refactoring of proportionals boost operators by @botisSmile and @rbayet #2318 #2334 #2351 #2354 #2362 #2367
- Fix fieldset order by @botisSmile in #2334
Page Builder compatibility :
- Fix proper appliance of sort orders. by @romainruaud in #2361 #2397
- Prevent side effect when building widgets conditions based on virtual… by @romainruaud in #2391
- Support pre-existing PageBuilder widgets (2.9.x) by @rbayet in #2342
💻 Technical
- Fixing the appliance of "is_discount" rules across differents customer groups by @rbayet in (#2399)
- Add exclude in term aggregation by @PierreGauthier in #2336
- Add min_doc_count in term aggregation by @PierreGauthier in #2363
- Prevent rejection of documents with large description (2.8.x) by @rbayet in #2378
- Change tracking API definition by @romainruaud in #2364
Full Changelog: 2.9.9.1...2.9.10
2.10.8.1
🐛 Fixes
- Fix explode parameter to be string by @Coosos in #2322
- Fix Wrong casing (typo) in LayeredNavAttribute namespace by @peterjaap in #2327
2.9.9.1
🐛 Fixes
- Fix explode parameter to be string by @Coosos in #2322
- Fix Wrong casing (typo) in LayeredNavAttribute namespace by @peterjaap in #2327
2.8.15.1
🐛 Fixes
- Fix explode parameter to be string by @Coosos in #2322
- Fix Wrong casing (typo) in LayeredNavAttribute namespace by @peterjaap in #2327
2.10.8
Changes
📦 Functional
-
Page Builder compatibility :
- Using virtual categories in Page Builder now works as expected thanks to @PierreGauthier in #2304
- Page Builder widgets will also now use ES queries internally.
-
UX refactoring of the optimizer screen :
- Moving and separating the preview into the available contexts (category view / search) by @botisSmile in #2294
- Boost score editing has been improved with a slider by @botisSmile in #2302
- General UX and display of optimizer form fields by @botisSmile in #2309
-
Hardlink in footer (#2273) can now be disabled through the back-office thanks to @vahonc in #2297
🐛 Bug fixes
- Fixing an issue when using
category_uid
in GraphQL queries (@JeroenVanLeusden #2315) - Properly fetching autocomplete configuration from store scope (@aamant #2314)
- Fixing an issue (#2280) with GraphQL schema (@romainruaud #2284)
- Fixing an issue (#2281) when installing from scratch (@romainruaud #2285)
- Fixing an issue (#1890) with improper focus in autocomplete (@vahonc #2300)
- Fixing an issue (#2261) when using flat categories with virtual categories (@vahonc #2298)
💻 Technical
- Ability to define custom tokenizers from XML by @gusdemayo in #2222
- Added a REST endpoint for tracker (useful for headless integration) by @botisSmile in #2275
- Allow to configure field mapping from di.xml, authored by @sky-hub in #2121 and extended by @botisSmile in #2272 and #2274
- Allow to enable tracking on website scope by @PierreLeMaguer in #2310