-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mini Search Form requiring header-wrapper container #297
Comments
Hello @webshopessentials I'm afraid but we cannot provide support for third-party modules integration. I have studied what you describe and for me the problem is clear : the Infortis team made the "header-wrapper" block disappear, and they should fix this so you will be able to retrieve any blocks that are child of this one. As a workaround you may try to include the ElasticSuite mini search box elsewhere in your layout : on a container which you are sure that is displayed on the Infortis theme. You just have to add this syntax where you want to include the block :
|
Hi @romainruaud, thank you for taking the time to look into my issue. Unfortunately the Infortis team informed me that they do not support third party modules ;) |
Hi @romainruaud , can you please provide any more insight into adding the elasticsuite mini search box elsewhere on a layout in the latest elasticsuite version. This is applicable information for both custom themes as well as adding the search autocomplete box anywhere else on any layout. The layout file located in vendor/smile/elasticsuite/src/module-elasticsuite-core/view/frontend/layout/default.xml looks like this in the version I have installed.
After attempting to edit the layout in my custom theme file in app/design/frontend/Smartwave/custom/Smartwave_Porto/layout/default.xml with only the line The search autocomplete box does not properly load any styles and links are not clickable. After viewing the current version default layout file in
But I am currently getting an error like this in var/report preventing frontend from showing at all:
What is the correct approach to add the autocomplete block to another place on the layout besides header-container in the current version. Has this changed since your previous answer? Thank you for any and all suggestions! |
Hi, |
I have Magento 2.2 with Elasticsuite & Ultimo theme and I'm trying to get the search box to display while using both. I have tried all the suggestions but I must be missing something. I do not mind modifying the Ultimo theme, Any suggestions would be helpful. |
I am currently having a hard time to get elasticsuite up and running in combination with a 3rd party Magento 2 theme. This is my first time to get an Magento 2 shop up and running, so please bear with me as I am not too experienced with some of the new concepts used.
The theme used is Ultimo from Infortis. After some debugging with the comments provided here from @nikonratm I discovered the following:
In the file
app/design/frontend/Infortis/base/Magento_Theme/layout/default.xml
several elements are moved to the container "base-header-container", header-wrapper being one of them.<move element="header-wrapper" destination="base-header-container" />
In the same file I also read the following comment:
But elasticsuite seems to rely on the header-wrapper container when I look at
vendor/smile/elasticsuite/src/module-elasticsuite-core/view/frontend/layout/default.xml
:and in the referenced form.mini.phtml the following is stated as comment:
So it seems that the Elasticsuite module tries to override the default mini search box functionality by making use of the header-wrapper element that is available in the default Magento 2 Theme. But the header-wrapper container is not available as such in the Infortis Ultimo Theme. And because the theme is quite "fluid" because of a lot of floating elements creating a custom module (solution which worked out for @nikonratm, but unfortunately not for me) turned out to be disastrous for the layout of the theme.
I have submitted a request for support to the Ultimo Theme developer as I read the following in
app/design/frontend/Infortis/base/Infortis_Base/templates/html/header.phtml
But pending on the answer from the developer, does anybody of you here have a bright idea how this can be resolved? Any help is highly appreciated.
The text was updated successfully, but these errors were encountered: