Magento – Magento2 Blank category list page after migration

category-listingcategory-productsmagento2magento2-migration-toolmedia-images

We successfully migrated a huge multi-store site from magento-1.9.3 to magento-2.1.6 last week using Magento migration tool. After migration, we notice that categories are not listing any products although products are there all set in admin. Also we reindexed everything but the issue still remain there until we put the media folder from magento1.9.3 to migrated magento2.1.3/pub/ directory.

We've checked this issue and it seems that Magento\Catalog\Block\Category\View::getProductListHtml() function returns empty product listing html when there is not media with product images.

The case is not same with other magento stores as having a blank media only replaces the placeholders images. My question is, why it is necessary for me to place the old media folder will all images in order to render the products list successfully under categories?

PS: permissions are set properly for pub, no custom module is overriding any class, all the commands (static content, reindex, cacha clean, di compilation) ran completely.

Best Answer

As suggested by @DhadukMitesh, the issue was that there were some custom placeholder images set from backend.

Stores > Setting > Configuration > Catalog > Catalog > Product Image Placeholders

After removing those placeholders from admin OR putting the placeholder images in media directory worked for me.

Related Solutions

Magento2 Reindex Error – No Such Entity

In addition to Raphael:

I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps). Alter the construct of the exception for now (the file is \lib\internal\Magento\Framework\Exception\NoSuchEntityException.php)

$trace = debug_backtrace();
var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$trace[1]['line'] .')';
die();

After that go up one stack and check the arguments given (the args are also available in the debug backtrace, but dumping magento objects isn't really browser friendly).

Came to the conclusion, that it was in the storeGroupRepository where it couldn't find the group id. Dived into the store tables and saw a few lines in the store table that were referencing a store_group that wasn't in the store_group table(store group not exist in relevant table).

Removed the faulty store lines and the error has been gone ever since.

But, keep in mind that it can also be in a different table/other reason. for example website, store itself or store group in this case. So that is always a little search you have to perform yourself.

Also found out that there were quite a lot of references to these stores and also removed them manually in the db. This can be a tedious work but it will solve the problem.

And don't forget to remove your hacks.

Magento 2 Catalog Cache – How to Fix Image Regeneration Issues

You should try using the image resize command to pre-generate all necessary resizes.

php bin/magento catalog:image:resize

This command gets all the images sizes that have been defined in the theme XML and pregenerates the images in their correct folders.

You can also check the command documentation for more information http://devdocs.magento.com/guides/v2.1/frontend-dev-guide/themes/theme-images.html

Related Topic