What is the recommended indexer mode for an instance with a large number of products?
With respect to the indexer mode suitable for the Magento installation with a large number of products, it is recommended setting indexers in Update by Schedule mode. This will ensure that no timeouts appear when any settings related to indexers in the backend are saved.
Related Articles
The Automatic Related Products module does not return any related products on the product/category pages or in cart. How to fix that?
There are several reasons why the related block might be missing from the front-end. To make sure the issue is not related to the rule settings, follow the instructions below, Step 1: Make sure your products have Stock Status = In Stock, since ...
Generating a feed returns an error "There are no products to generate the feed". How to fix this issue?
This is one of the common errors, yet the troubleshooting process is quite simple. First, double-check the settings in the General and Conditions tabs in order to make sure that those configurations are valid and do not contradict each other. General ...
Where can I find the Microsoft Clarity Consent Mode settings?
Since v.2.16.0 of GDPR (Cookie Consent) extension, we have added compatibility with Microsoft Clarity Consent Mode feature. In order to obtain the consent mode functionality, 'amasty/module-clarity-consent-mode' should be installed. The module is ...
How products are sorted in the related block when the Source Type is set to “Bought Together”?
With Source Type set to Bought Together in the related rule, products will sorted based on their frequency of being purchased together, i.e. by the number of purchases. For instance, if customers buy product X alongside product Y more frequently than ...
Generating a feed returns an error: "Something went wrong: Couldn't lock indexer. Reindex in progress". How to fix?
This message indicates that during the generation of the feed, its indexers are currently in progress, in the Processing status. Before proceeding with the next steps, please make sure to update the extension to version 4.0.0, where we significantly ...