📦Main Features
Translation improved and added for German 🇩🇪 and Dutch 🇳🇱 !
As the Elasticsuite only consists of people of variable fluency in French and English, we have pretty much relied on the community for additional language translations.
A huge shout-out to @lewisvoncken who provided a huge contribution which not only improved and expanded the German translation but also added a brand new Dutch translation !
We’ll try to get the ball rolling and address the gap between Elasticsuite Open Source and Elasticsuite Premium in that regard.
Changing your store language stemmer
Over the years, we’ve noticed some issues with the default language stemmers used in Elasticsuite where, sometimes, the stemmers would not recognize properly the plural form of a word (for instance irregular french plural or some legitimate italian plurals) or would provide the same stem for quite different words (collection and collectivité in french).
That led to the introduction of the stemmer_override analyzer step which allows a developer to add some stemming rules to address those issues.
But since another approach sometimes used by Elasticsuite end users was simply to test and switch to another available language stemmers, we’ve decided to make it possible from the Magento Admin.
In the Stores > Configuration, at the store view level, it will be now possible for you to select a different stemmer than the one Elasticsuite uses if ElasticSearch/OpenSearch provides several for your language, that is for: Dutch, English, Finish, French, Galician, German, Hungarian, Italian, Norwegian (Bokmal and Nynorsk), Portugueuse, Russian, Spanish and Swedish.
The configuration is available, at the store view level only, at Stores > Configuration > Elasticsuite > Analyzers settings > Language stemmer configuration (don’t forget to perform a full re-index after changing the setting).
Slightly better UX on the indices grid
On a UAT or Staging environment where the Elasticsearch/OpenSearch cluster is shared by many Magento instances, it can be cumbersome to locate and inspect your live indices in the Elasticsuite > System > Indices grid if you have to scroll down 5 screens to reach them.
This release includes two small improvements
- the ability to filter indices by their name (and not only their alias)
- the ability to hide all the external indices
💻 Technical
- [BehavioralData] ( 💎 Elasticsuite Premium) Collect data according to search.max_buckets
- [Catalog] Default sort direction system config settings 2.10 feature
- [Catalog] Feature Category Sort By Direction with Default Sort Direction Config #3333, add system config settings for Default Sort Direction
- [CatalogOptimizer] (2.11.9 only) Allow category limitation for third party containers
- [CatalogOptimizer] (2.11.9 only) Category preview for third party containers
- [Core] Fixing some extra quotes in i18n files
- [Core] Elasticsuite client exposes cluster info/settings
- [Recommender] (2.11.9 only) Allow optimizer category preview for recommender containers even when they are the only containers selected for an optimizer
- [Tracker] Prevent events with empty or null tracker visitor/session identifiers to be indexed
Fixes
- [Analytics][Tracker] Handle rare case where tracker indices are empty
- [Catalog] Fix Manual sort gets set back to automatic sort #2948 fallback to the last known valid product positions
- [Catalog] (2.11.9 only) Show the ‘is_filterable_in_search’ independently of ‘is_searchable’ in product attribute edit scree
- [Core] Fix Condition currency is not supported #3334, adding support currency condition
- [Core] Fixes “Error: Call to a member function setName() on null” – on partial word search #3359 Query name set error if fuzziness and phonetic disabled
- [Indices] Status ‘unknown’ when stats fails + logging failures
- [Optimizers] Fallback to root category for category preview if not root category is selected for a virtual category
- [Recommender] (2.11.9 only) ( 💎 Elasticsuite Premium) Fix optimizer preview recommender
- [Recommender] (2.11.9 only) ( 💎 Elasticsuite Premium) Make optimizer filter compatible with native
- [Tracking] Add query id in GraphQL search response to make Autocomplete optimizers work properly