-
Notifications
You must be signed in to change notification settings - Fork 340
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
After upgrade to magento 2.3.2 site broken #1442
Comments
Same here, as it seems they removed the Layer-plugin entirely from the source: https://github.com/magento/magento2/tree/2.3.2/app/code/Magento/CatalogInventory/Model/Plugin |
A quick fix for this is to disable the plugin, this would have other consequences regarding the displaying of the stock status, but at least the site isn't down: <?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">
<!--
Temporary Quick-Fix to prevent the site to be down:
https://github.com/Smile-SA/elasticsuite/issues/1442
-->
<type name="Magento\Catalog\Model\Layer">
<plugin name="addStockStatusOnPrepareFrontCollection"
type="Smile\ElasticsuiteCatalog\Plugin\LayerPlugin"
disabled="true"/>
</type>
</config> |
Magento 2.3.2 removed this plugin
Created PR that should fix this issue #1444 |
Layered navigation will still be entirely broken even if you do this. Looks like this commit is what removed the layer plugin and changed the logic: magento/magento2@9ab466d#diff-2ad66624cecd33a368d784f2be936f48 |
#1445 (comment) see this thread |
Thank you @NathMorgan for your PR. as far as I can see, it could do the trick. I did not test it by myself however. @androshchuk can you have a look on this issue and associated PR ? Regards |
Unfortunately #1448 did not work for us and we desperately need to have a working version. When can we expect a fix? |
It's weird, that Magento fellows allowed removal of the code without any prior notice, as pert of minor release. |
Same issue |
What is the issue you are getting after applying the patch? |
Same issue on Vanilla Magento 2.3.2, ES 6.1.8 and Module 2.8.0 |
did you apply this patch and the #1444 patch as well?! |
Hi @southerncomputer, I'll apply the patch and revert further changes that I made in order to solve this. I'll let you know quickly. |
@southerncomputer after reindexing (as I said, fresh install, Data Migration has been done, tho):
|
did you get this error after doing bin/magento indexer:reindex ? |
Yes, exactly. I made some calls to ES to check for active indicies and found only those. The numbers look to small. There are ~6k Products in the DB currently.
|
It sounds like your product indexing is crashing/getting stuck! Might turn on var/log/debug.log and tail it while its doing indexing!
I know elasticsuite builds indexes with a temp name and then renames it as it completes successfully! p.s. i think magento2_product_1_v1 is created from the built-in elasticsearch not elasticsuite! |
Thanks for that hint with the Magento ElasticSearch Engine, that actually was an issue of not setting the Source to ElasticSuite, there should be a check that looks out for correct settings and if not, advises the user to apply correct settings. So generally, after applying both pathes -> it worked. |
Good to know ! I'll work on this one this week. But for me, the plugin can be removed, since the Stock management is now done with a search context filter : |
Fixed by PR #1461 |
Thanks! Could create a new release with this merge? |
Hi, excuse me, how i can implement that XML? Thanks. |
Some problem.
Latest M2. How I can quickly fix that? Thanks. |
@skazhikadyadya I fix like this;
|
@roman204 as far as I know there is no 3.0 version. Where did you find it ? |
It's elasticsuite here... not magesuite... |
@romainruaud |
Preconditions
Magento Version : magento 2.3.2
ElasticSuite Version :2.8.0
Environment :Developer
Third party modules :
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: