develop branch.In admin panel Stores -> configuration -> Catalog -> Catalog -> Product Image Placeholders. Attach new picture for "base image".
New product image placeholder should be new uploaded image.
There are still old placeholder.
But take a look, that in meta data there are correct new placeholder path
Hi @rawick
Thank you for such a good issue description. I could easily reproduce the bug and created MAGETWO-53036 ticket to fix it.
Thanks,
Kateryna.
This issue appeared to be resolved in 2.1.2 but is back in 2.1.3.
Confirmed issue in 2.1.3
I'm getting it on 2.1.2
I am also getting it on 2.1.2;
my v 2.1.2 was installed on October 6th with composer, but still has the old lines as seen in the fix in vendor/magento/Block/Product/View/Gallery.php
So looks like getDefaultPlaceholderUrl() is also called in the getUrl() function of Magento/Catalog/Helper/Image.php on Line 519.
May or may not be the core issue, and not sure what the submission process is, so just posting here.
For whatever reason this fix was pushed to develop branch but never made it into the 2.1 branch.
This is still an issue in 2.1.4
Thanks for the update in this folks. I can confirm the product page does not work in CE v2.1.4. Other pages like the category page will work. So for now what we've done is overwrite the base placeholder images themselves in our theme. So create this folder path:
app/design/frontend/[VENDOR]/[THEME]/Magento_Catalog/web/images/product/placeholder
Then in the placeholder folder you need:
image.jpg
small_image.jpg
thumbnail.jpg
Obviously to overwrite base via the Admin Panel > Stores > Configuration > Catalog would be ideal but at least we have a workaround for now.
It's such a shame we don't get to see where all these tickets end up. For example where is MAGETWO-53036? It sometimes feels like we're getting to the final hurdle but somehow not reaching the finish line.
Laters.
Tadhg :-)
Thanks for sharing the workaround tadhgbowe!
This is still an issue in 2.1.7
Me too, as this fix has been sat in 'develop' since 25 July, do we have any idea when it will go live?
This is still an issue in 2.1.8
@OlehWolf thank you for your report.
The fix for this issue is already fixed in 2.2.0 release
Most helpful comment
Confirmed issue in 2.1.3