2.10.16

📦 Features

In this release we introduced the ability to export and import attributes configurations (by @vahonc in #2937)

You will now be able to proceed with exporting the attributes configuration fields related to elasticsuite : "is searchable", "is filterable", "search weight", etc... from the Stores > Attributes > Products grid.

Then you can proceed to the modifications you need, and you can re-import your file through System > Import > choose 'Elasticsuite Product Attributes' and then re-import your file.

This is intended to help the merchants by saving a lot of time at the start of a project, to configure everything in the exported file "offline", and then reimport it once it's ready. This is way more easy than going through all the attributes one by one.

What's Changed

• Fix filter rendering. by @Nuranto in #2942.
• Fix #1985 Ensure proper loading of virtual categories rules. by @romainruaud in #2931
• Fix #1985 Ensure proper loading of virtual categories rules. by @romainruaud in #2933
• Prevent failures when using empty values in multiselect. by @romainruaud in #2938
• Fix #2934 by renaming test file by @romainruaud in #2939
• Feature #2911, allow to export/import attributes configuration from admin by @vahonc in #2937

Full Changelog: 2.10.15.1...2.10.16

2.11.1.1

What's Changed

• Improve MLT query. by @romainruaud in #2920
• Add Breezefront note by @fvlasie in #2921
• Fix #2913, undefined array key "date" for elasticsuite tracker event index by @vahonc in #2923

New Contributors

• @fvlasie made their first contribution in #2921

Full Changelog: 2.11.1...2.11.1.1

2.10.15.1

What's Changed

• Improve MLT query. by @romainruaud in #2920

Full Changelog: 2.10.15...2.10.15.1

2.11.1

📦 Features

In this release we introduced various improvements for relevance and UX (#2886) :

Boost on "spans" (aka boost on beginning of the fields)

We introduced a mechanism allowing to boost results that contains the search terms in the beginning of their values.

This feature is disabled by default and has to be enabled in the Elasticsuite > Relevance Configuration > Span Match Configuration.

Then it must be enabled on the targeted attributes (most of time, "name" will be the only targeted).

Eg :

• without this feature, customers are searching for "laptop" but in result page they view first "Bag for laptop","Cleaning set for laptop"
• with this feature enabled on "name" attribute : the products having a name beginning with "Laptop" will have an higher score

Allow to disable "norms"

By default with Elasticsearch, the score of a given field depends on the field length. You can now disable this on attribute level, in Stores > Attributes > Product > Attribute Edit page > Storefront properties > Advanced Elasticsuite Configuration > Disable norms : Yes

Eg :

• with norms enabled (default behavior) on the "name" field, a customer search for "dress", a product named "red dress" will have an higher score than a product named "red dress with long sleeves" (for the "name" field).
• with norms disabled : these 2 products will have the same score for the "name" field.

Attribute configuration screen refactoring

Due to huge number of parameters in the Stores > Attributes > Product > Attribute Edit page > Storefront properties we decided to split the search related configurations into three different fieldsets :

• Search configuration
• Layered navigation configuration
• Advanced Elasticsuite configuration

🐛 Fixes

• Fix cron error "Deprecation functionality: creation of dynamic property" by @Shiriaev in #2875
• Prevent thesaurus to apply on a query that already contains the expan… by @romainruaud in #2883
• Fix #2862, add 'category_uid' to the aggregation in the GraphQl response by @vahonc in #2884
• Enhanced reference fields (sku) matching when fuzzy searching by @rbayet in #2881
• Fix #2873, DateTime exception for ElasticSuite Indices by @vahonc in #2885
• Fix numerical-only synonims by @udovicic in #2894
• Feature #2882, allow to choose 'score_mode' and 'boost_mode' for optimizers from admin by @vahonc in #2889
• Fix setup when using table prefix by @romainruaud in #2902
• Relevance improvement by @romainruaud in #2886
• Remove erratic plugin of Magento_InventoryCatalog by @romainruaud in #2903
• Fix #2892 Optimizer schema by @romainruaud in #2904
• Refactoring the Attribute configuration options. by @romainruaud in #2905
• Refactoring the thesaurus wordings. by @romainruaud in #2906

New Contributors

• @Shiriaev made their first contribution in #2875
• @udovicic made their first contribution in #2894

Full Changelog: 2.11.0...2.11.1

2.10.15

📦 Features

In this release we introduced various improvements for relevance and UX (#2886) :

Boost on "spans" (aka boost on beginning of the fields)

We introduced a mechanism allowing to boost results that contains the search terms in the beginning of their values.

This feature is disabled by default and has to be enabled in the Elasticsuite > Relevance Configuration > Span Match Configuration.

Then it must be enabled on the targeted attributes (most of time, "name" will be the only targeted).

Eg :

• without this feature, customers are searching for "laptop" but in result page they view first "Bag for laptop","Cleaning set for laptop"
• with this feature enabled on "name" attribute : the products having a name beginning with "Laptop" will have an higher score

Allow to disable "norms"

By default with Elasticsearch, the score of a given field depends on the field length. You can now disable this on attribute level, in Stores > Attributes > Product > Attribute Edit page > Storefront properties > Advanced Elasticsuite Configuration > Disable norms : Yes

Eg :

• with norms enabled (default behavior) on the "name" field, a customer search for "dress", a product named "red dress" will have an higher score than a product named "red dress with long sleeves" (for the "name" field).
• with norms disabled : these 2 products will have the same score for the "name" field.

Attribute configuration screen refactoring

Due to huge number of parameters in the Stores > Attributes > Product > Attribute Edit page > Storefront properties we decided to split the search related configurations into three different fieldsets :

• Search configuration
• Layered navigation configuration
• Advanced Elasticsuite configuration

🐛 Fixes

• Prevent thesaurus to apply on a query that already contains the expanded query by @romainruaud in #2883
• Fix #2862, add 'category_uid' to the aggregation in the GraphQl response by @vahonc in #2884
• Enhanced reference fields (sku) matching when fuzzy searching by @rbayet in #2881
• Fix numerical-only synonims by @udovicic in #2894
• Feature #2882, allow to choose 'score_mode' and 'boost_mode' for optimizers from admin by @vahonc in #2889
• Fix setup when using table prefix by @romainruaud in #2902
• Relevance improvement by @romainruaud in #2886

New Contributors

• @udovicic made their first contribution in #2894

Full Changelog: 2.10.14...2.10.15

2.11.0

📦 What's Changed

In this new major version we added compatibility with :

• Magento 2.4.6
• Elasticsearch 8.x
• Opensearch 2.x

So if you plan to migrate your project to Magento 2.4.6 you should use this release and the upcoming releases on the 2.11.x branch.

🐛 Fixes

• Make jQuery ajax request for autocomplete cacheable by @lumnn in #2467
• Fixed typo in variable name by @prog08 in #2851
• Fixes #2130 Convert Schema Scripts to DB Schema XML by @pykettk in #2148
• WIP : ES8 compatibility by @romainruaud in #2852
• Feature magento 246 by @romainruaud in #2854
• IsDiscount for configurable and grouped products with optimized performance by @Bashev in #2677
• [Layered Attribut] #1203199 - Add customer group in is_discount filter by @PierreGauthier in #2855
• Fix issue #2856: Pagination, sorting and limit on virtual category tree by @Bashev in #2857
• [Layered Attribut] #1203199 - Fix Interface Typing by @PierreGauthier in #2858
• [Layered Attribut] #1203199 - Fix Interface Typing by @PierreGauthier in #2859
• [Virtual Category] Unset virtual category root before setting it #1203860 #2829 by @PierreGauthier in #2860
• Fix rendering issue with multiple slider filters by @frank-bokdam in #2863
• Fix issue #2853 - Add additional logic to map parent and child ids. by @Bashev in #2865
• Add missing propertymapping for eav attribute creation/updates by @brosenberger in #2804
• Use coverage modifier in adminhtml by @romainruaud in #2867
• Set proper key for catalogsearch_fulltext index. by @romainruaud in #2868
• Fixing Datetime issues by @romainruaud in #2869

New Contributors

• @prog08 made their first contribution in #2851
• @pykettk made their first contribution in #2148
• @frank-bokdam made their first contribution in #2863
• @brosenberger made their first contribution in #2804

Full Changelog: 2.10.13.3...2.11.0

2.10.14

📦 What's Changed

• Fixed typo in variable name by @prog08 in #2851
• IsDiscount for configurable and grouped products with optimized performance by @Bashev in #2677
• [Layered Attribut] #1203199 - Add customer group in is_discount filter by @PierreGauthier in #2855
• Fix issue #2856: Pagination, sorting and limit on virtual category tree by @Bashev in #2857
• [Layered Attribut] #1203199 - Fix Interface Typing by @PierreGauthier in #2858
• [Layered Attribut] #1203199 - Fix Interface Typing by @PierreGauthier in #2859
• [Virtual Category] Unset virtual category root before setting it #1203860 #2829 by @PierreGauthier in #2860
• Fix rendering issue with multiple slider filters by @frank-bokdam in #2863
• Fix issue #2853 - Add additional logic to map parent and child ids. by @Bashev in #2865
• Add missing propertymapping for eav attribute creation/updates by @brosenberger in #2804
• Use coverage modifier in adminhtml by @romainruaud in #2867
• Set proper key for catalogsearch_fulltext index. by @romainruaud in #2868

New Contributors

• @prog08 made their first contribution in #2851
• @frank-bokdam made their first contribution in #2863
• @brosenberger made their first contribution in #2804

Full Changelog: 2.10.13.3...2.10.14

2.10.13.3

🐛 Fixes

• [Search Merchandizing] Filter boost and use search merchandising in autocomplete by @PierreGauthier in #2837
• [Optimizer] Sort by boost weight in admin grid by @PierreGauthier in #2844
• [Search Merchandizing] Set search query to load optimizers by @PierreGauthier in #2845
• Prevent adding null queryFilters on ProductsListPlugin by @pomppa in #2848

New Contributors

• @pomppa made their first contribution in #2848

Full Changelog: 2.10.13.2...2.10.13.3

2.10.13.2

🐛 Fixes

• Fixing the maximum width of the index select dropdown by @vahonc in #2843

Full Changelog: 2.10.13.1...2.10.13.2

2.10.13.1

📦 Improvements

• Adding support of extended_bounds for date_histogram by @romainruaud in #2833

Full Changelog: 2.10.13...2.10.13.1