Releases: Smile-SA/elasticsuite
2.3.3
✅ Fixed
-
A bug (#337) which occured when moving categories and using Flat Categories (e095340)
-
Several performance improvements for Virtual Categories (b9abaae, befc3b2, b044a9b)
-
Removing "position" column of the category/product grid since they are not relevant anymore : Product sorting is made via the drag-and-drop product sorter. (f731141)
-
Setting internal elasticsuite fields as "protected" : this prevent to create attributes using "reserved" values for attribute_code field which could lead to issues by overriding internal fields used by elasticsuite (eg. if you create an attribute with the attribute_code "stock" or "category") (f92a5b3)
-
Fixing an issue (#347) related to Magento EE website scoped permissions (7e81ec4)
-
Potential issues when using directly the Catalog Layer (eg. via
$layerResolver->get()
) : in some cases, the retrieval of product collection from the layer was not returning the proper collection type. (#356)
ℹ️ Misc
- We added an "issue template", to ensure we are able to resolve our community members issues with the maximum informations from them.
2.3.2
✅ Fixed
- An issue occuring when using dropdown or multiple select attributes on advanced search. (#313)
- The attribute edition screen now prevent to set an attribute to "Displayed in autocomplete : Yes" if this attribute is not "Filterable in search : Yes".
- The attribute edition screen now authorizes to set boolean attributes as "Filterable" and "Filterable in Search".
- The number of results belonging to an attribute on the autocomplete box is now hidden. (#308)
2.3.1
ℹ️ New Features
- Added the ability to easily add custom attributes into product panel of autocomplete results (#302)
✅ Fixed
2.2.7
2.3.0
ℹ️ New features :
The new version of Smile Elastic Suite comes with the following new features :
- Introducing the Optimizers feature : you are now able to create boosts based on rules like Boost all products that are in stock / discounted or Boost all products for Men
- Adding special attributes to the virtual rules (for virtual categories and optimizers) : this allow to build rules based on only discounted products or only in stock products and only products with images.
- Attributes Autocomplete : Attributes are now displayed in autocomplete results. (#141)
- Advanced Search Compatibility : ElasticSuite is now fully compatible with the Advanced Search feature. (#226)
- Show less/more into facets : Customers are now able to display all values for a facet if they wish. (#221)
- Support of HTTP Authentication for ElasticSearch (#212)
- Filters are now rendered via a JS component on search result and navigation pages (#191)
- Support for "min_doc_count" in histogram aggregations. (#189)
- Support for bulk update operations (#159)
✅ Fixed
- Huge improvement of indexing process, which will result in more light and faster rebuilt indexes (#164)
- Better price rendering for products in the autocomplete (now manages special price, flat taxes, etc ...) (#207)
- An issue on virtual categories when using "Flat Categories" index. (#231)
- Keyboard navigation in the autocomplete result box (#193)
- Correct display of special characters in the autocomplete result box (#192)
- Products thumbnails in autocomplete box are not rendered with full size image anymore (#177)
- Proper implementation of index durability (#176)
- Better performances for facet display (#165)
- Correct appliance of visibility into the autocomplete box (#276)
- An issue for the mapping of sortable but not searchable fields (#277)
- An issue where choosing to display "all" products per page on Front-Office was not properly applied (#250)
2.2.6
2.1.4
2.2.5
Therefore, it is mandatory to migrate to this version of ElasticSuite if you are using Magento 2.1.3.
Please also note that this version remains compatible with others prior Magento 2.1.x version
✅ Fixed :
- #255 : Slight refactoring of the Relevance Configuration. This part was affected by a non-backward compatible change made by Magento into core classes.
2.2.4
✅ Fixed :
- #223 an issue on virtual categories : This issue could occurs if you are using a custom script/module which loops over a category collection and save them, without having previously loaded their "virtual rule" attribute. This one is considered as a major issue since it can result to data loss by overwriting the previous Virtual Category Rule by an empty one.
- potential XSS vulnerability #224
2.1.3
✅ Fixed :
- #223 an issue on virtual categories : This issue could occurs if you are using a custom script/module which loops over a category collection and save them, without having previously loaded their "virtual rule" attribute. This one is considered as a major issue since it can result to data loss by overwriting the previous Virtual Category Rule by an empty one.
- potential XSS vulnerability #224