Fixing direct usage of Layer to prepare a product collection which th… #356
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ey did not instantiate themselves.
This is mostly related to the
Call to undefined method Magento\Catalog\Model\ResourceModel\Product\Collection\Interceptor::addSortFilterParameters()
error.This error occurs when Magento uses the Layer object as a filter, to prepare an external product collection.
This can be seen especially on
Magento\Catalog\Block\Navigation
:$productCollection = $this->_productCollectionFactory->create(); $this->_catalogLayer->prepareProductCollection($productCollection);
the
$productCollection
is created by the standard product collection factory. Therefore it is not possible to use ElasticSuite method on it when the layer calls the prepareProductCollection.This can be fixed by switching the factory used to the CatalogSearch one, and will then work properly.
Imho, since we cannot ensure which type of collection is sent to the Layer, and since prepareProductCollection is a public method, we should go further on this one.
Let me know @afoucret