Does ElasticSuite work with Magento 2.3?
Yes.
“If your project is based on Magento 2.3.x, you can start working with ElasticSuite today using the latest 2.7.x release”
Hello @deckside,
As confirmed by @djenvert and indicated in the README, ElasticSuite works with Magento 2.3 starting from the 2.7.0 release.
You can install the latest 2.7.x release with composer require smile/elasticsuite ^2.7.0.
Regards,
Hi @rbayet @djenvert but i getting this error when i php bin/magento setup:upgrade .how to fix it? thank you
Fatal error: Uncaught Error: Cannot instantiate interface Magento\InventorySalesApi\Api\StockResolverInterface in /home/XXX/public_html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php:50 Stack trace:
installed no problem for magento 2.3 with "composer require smile/elasticsuite ^2.7.0" .
Duplicate of https://github.com/Smile-SA/elasticsuite/issues/1222 ?
Hello Guys,
Anyone have a news about this issue ?
Thank's
In my opinion it's most probable to happen on an upgrade from Magento 2.2 to Magento 2.3.
That's why it's not detected by our Travis build (which does process a full install on a stock Magento 2.3.0 from scratch).
When you upgrade from 2.2 to 2.3 via composer, there are some bundled scripts which arbitrary disable the Inventory modules. In this case, since the Inventory modules are disabled, the StockResolverInterface cannot be instantiated.
I let @rbayet dig more on this one, but imho this is a good part to dig on.
@romainruaud Your hunch is correct.
Make sure you have the following enabled:
php bin/magento module:enable Magento_Inventory Magento_InventoryApi Magento_InventoryCatalogApi Magento_InventorySalesApi Magento_InventoryConfigurationApi Magento_InventoryReservationsApi Magento_InventorySourceDeductionApi Magento_SalesInventory Magento_InventorySales Magento_InventoryMultiDimensionalIndexerApi Magento_InventoryIndexer Magento_InventoryConfiguration Magento_InventoryCatalog Magento_InventoryReservations Magento_InventoryReservationsApi
Then you should be able to run setup:upgrade
Hello,
Any news?
I have this issue:
Fatal error: Uncaught Error: Cannot instantiate interface MagentoInventorySalesApi\ApiStockResolverInterface in /home/XXX/public_html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php:50 Stack trace:
Thank's
According Magento :
"MSI is enabled for all fresh installations, and gets disabled for upgrade from early Magento versions to 2.3 unless it’s switched on manually"
So yes, issue is confirmed.
If you are upgrading, you should enable MSI modules manually. But this also require you to ensure to report any customization on CatalogInventory modules to MSI modules.
I'm afraid as an extension provider we'll have to deal with an ugly hybrid support between "Magento and MSI", and "Magento with MSI disabled" since the both versions can exists.
I have all the modules copied from elasticsuite-master/src into /app/code/ but when I try to enable the module, I keep getting - Unknown module(s): 'Smile_ElasticsuiteCore'
I'm running the following command.
/usr/local/php71/bin/php-cli bin/magento module:enable --clear-static-content Smile_ElasticsuiteCore
What am I missing here?

Is there no way to have the MSI disabled and still have elasticsuite?
@pedrosousa13 actually, there is no way to achieve such things.
I'm considering it, but for me it's unclear what is the future of the legacy CatalogInventory module.
It's a lot of (ugly) code to write to support both "Magento with MSI" and "Magento without MSI" and we should nearly consider these instances as additional versions of Magento (we already have to consider both CE and EE versions).
To be honest, it's quite a pain for us they implemented it this way, even if I understand there could be issues with BC for merchants having already highly customized the CatalogInventory module...
From a quick benchmark, disabling MSI modules improves response times by 25% for headless REST API calls…
It would be great to see a path to support both implementations indeed.
PR #1382 contains necessary deprecation mechanism to work without MSI modules.
Please everybody note the following two things :
We did not want to provide such things and intentionally discarded such a deprecation mechanism when we wrote MSI support.
Legacy implementation of Magento_CatalogInventory will be removed by Magento. We don't know when, but all merchants and integrators should rather begin using MSI for now instead of relying on legacy CatalogInventory.
Since our community has spoken, I reconsidered my position about this topic and provide this support for now.
Regards
Thanks for your openness! It will make the migration path much smoother.
Most helpful comment
@romainruaud Your hunch is correct.
Make sure you have the following enabled:
php bin/magento module:enable Magento_Inventory Magento_InventoryApi Magento_InventoryCatalogApi Magento_InventorySalesApi Magento_InventoryConfigurationApi Magento_InventoryReservationsApi Magento_InventorySourceDeductionApi Magento_SalesInventory Magento_InventorySales Magento_InventoryMultiDimensionalIndexerApi Magento_InventoryIndexer Magento_InventoryConfiguration Magento_InventoryCatalog Magento_InventoryReservations Magento_InventoryReservationsApiThen you should be able to run setup:upgrade