Closed
Description
Preconditions (*)
- Magento 2.4-develop
Steps to reproduce (*)
- Create a Product
- Assign Image 1 to product and set to be visible on product page
- Assign Image 2 to product and set to be hidden on product page
- Save the product
Expected result (*)
- View the product page, only Image 1 should be visible
- pub/media/catalog/cache folder should contain resized Image 1's
- pub/media/catalog/cache folder should contain resized Image 2's
- Clear image cache
- Run php bin/magento catalog:images:resize
- pub/media/catalog/cache folder should contain resized Image 1's
- pub/media/catalog/cache folder should contain resized Image 2's
Actual result (*)
- Only Image 1 is visible on product page ✅
- Image 1 is present in cache in resized states ✅
- Image 2 is present in cache in resized states ✅
- Cache is cleared ✅
- Image resize command processes 1 image, not 2 ❌
- pub/media/catalog/cache folder should contain resized Image 1's ✅
- pub/media/catalog/cache folder does not contain resized Image 2's ❌
Images that are hidden from the product page are not processed by the image resize command. They should be. Just because they are hidden from the product page, doesn't mean they won't be used elsewhere.
Magento is written so that hiding the product image, actually sets it to disabled.
IMHO setting a product image to disabled, and setting it to be hidden on product page are two very different settings, but magento currently treats them as the same.
The confusion stems from the hidden setting being stored in the database as the field disabled. A hidden image is NOT a disabled image, and should still be processed, just not displayed on the product page, otherwise, what is the point of the hidden setting?
Additional Information
Metadata
Metadata
Assignees
Labels
The issue has been fixed in 2.4-develop branchGate 3 Passed. Manual verification of the issue completed. Issue is confirmedA defect with this priority could have functionality issues which are not to expectations.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branchIssue related to Developer Experience and needs help with Triage to Confirm or Reject it
Type
Projects
Status
Done