Smile-SA / elasticsuite

Smile ElasticSuite - Magento 2 merchandising and search engine built on ElasticSearch
https://elasticsuite.io
Open Software License 3.0
760 stars 339 forks source link

How to implement filter block on the frontend? #2631

Closed qumuq-til closed 2 years ago

qumuq-til commented 2 years ago

I've installed Elasticsuite according to the instructions and it appears to work. However I cannot figure out how to enable the multiselect navigation, the block that allows, for example, specifying multiple product sizes in a certain category and filter the product list according to the selection.

I have enabled the Size attribute to be shown in Layered Navigation and that block did show on frontend even before I installed Elasticsuite, and I obviously couldn't select more than 1 option there. However after installing Elasticsuite the same block is still there and I can't figure out how to replace it with Elasticsuite's multiple select block, if it should be done automatically or manually. What should I do to enable it? 1

vahonc commented 2 years ago

Hello @qumuq-til,

Looking at your screenshot, I can assume that you are probably using some kind of custom theme, or you are using some third-party module for filtering in Layered Navigation. Is that so?

You can see how it should look when the ElasticSuite is properly installed on our demo site

BR, Vadym

qumuq-til commented 2 years ago

I'm using a Koller theme https://themeforest.net/item/koller-multipurpose-sections-magento-2-theme/30180585, there are some modules included with it, listed below, but there are no third-party modules that I myself have installed for Layered Navigation, nor any custom modifications were made to the navigation code.

MageWorx_Info
MageWorx_SearchSuiteAutocomplete
Magefan_Community
Magefan_Blog
Magefan_WysiwygAdvanced

Mageplaza_Core
Mageplaza_Smtp

Rokanthemes_AjaxSuite
Rokanthemes_Brand
Rokanthemes_CategoryTab
Rokanthemes_CustomMenu
Rokanthemes_Faq
Rokanthemes_ImageCmsPage
Rokanthemes_Instagram
Rokanthemes_LayeredAjax
Rokanthemes_OnePageCheckout
Rokanthemes_PriceCountdown
Rokanthemes_ProductTab
Rokanthemes_QuickView
Rokanthemes_RokanBase
Rokanthemes_SlideBanner
Rokanthemes_StoreLocator
Rokanthemes_Superdeals
Rokanthemes_Testimonial
Rokanthemes_Themeoption
Rokanthemes_VerticalMenu
Rokanthemes_WidgetSubCategory

Temando_ShippingRemover

I'm also having trouble with AJAX (live) search functionality:

main.ERROR: Catalog Layer has been already created [] []
main.CRITICAL: RuntimeException: Catalog Layer has been already created in /var/www/mag/vendor/magento/module-catalog/Model/Layer/Resolver.php:54

Not sure if the above is a generic error or theme-related.

Either way, could there be an easy way out, such as disabling some module, or overriding an xml file to get the filters to work?

qumuq-til commented 2 years ago

Also, I have three "base" extensions related to Layered Navigation and not sure if those should be enabled or disabled when Elasticsuite extensions are enabled. Those are Magento_LayeredNavigation, Magento_SwatchesLayeredNavigation and Magento_TwoFactorAuth. Disabling them however just removed the filter block entirely from the page and enabling just Magento_LayeredNavigation brings the original single-select block back.

vahonc commented 2 years ago

@qumuq-til,

There is no need to disable standard modules of the Magento because ElasticSuite is fully compatible with them. What can not be said about other third-party modules. From the list of modules you provided, I believe you should disable this module Rokanthemes_LayeredAjax first. You can also try switching to the default Magento (Luma) theme.

Also, please note that compatibility with third-party modules is out of the scope of our Open Source support policy provided here, there is not much we can do for your issue. You'll have to make a choice, ask the support team of the Rokanthemes directly about your problem or resolve these conflicts by yourself.

BR, Vadym

github-actions[bot] commented 2 years ago

This issue was waiting update from the author for too long. Without any update, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away! Thanks for your contribution.