Magento2: Product'ss images cache not displayed /regenerated after Flush Catalog Images Caches

[29sunil]

Preconditions (*)

1.Magento 2.3.0

1. Mysql 5.6.41
2. Php 7.1

Steps to reproduce (*)

1. Go on Magento's Backed and click on: Flush Catalog Images Cache

Expected result (*)

1.All product images will show at category list page and detail page

Actual result (*)

1. The image of Catalog of product on frontend and backend are displayed correctly
   1.No apache errors, php or exception thrown
2. We are using this command to regenerate the images ( php bin/magento catalog:image:resize ). But this is not a solution. The client is not able to use this step.

[m2-assistant[bot]]

Hi @29sunil. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@29sunil do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @engcom-qa-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hello @29sunil. Thanks for reporting. We don't clearly comprehend what is wrong with the Actual Result You are facing and where is the discrepancy with the Expected Result: "The image of Catalog of product on frontend and backend are displayed correctly". Do You mean "not correctly" or something like that?

[29sunil]

Hello Team,
Thanks for support
The images of the product shown in the admin section and frontend. but after flush catalog images cache from Magento admin, images are not showing at frontend category page and product page.
To show these images we need to regenerate images using this command.
php bin/magento catalog:image:resize
Print screen: https://prnt.sc/o1rxac
https://prnt.sc/o1rxlb
Website URL: https://www.sofasupply.nl
Right now images are showing at category page and details. Because we have regenerated images.
If there is any server configuration missing then let us know.
which PHP extension is used for image cache at a server.
Thanks

[engcom-Bravo]

@29sunil, please watch the attached video. Have we done everything as You meant?

At the Product detail page images would also be displayed.

[29sunil]

Hello Team,
Thanks for reply
Please check below video and print screen. Please check the website now. Please check category page and details page. Now we need to use this command to generate images.
php bin/magento catalog:image:resize
https://www.sofasupply.nl/woonkamer/tafels/bijzettafels.html

Flush Catalog Images Cache Pregenerated product images files

Print screen: https://prnt.sc/o1spxq
https://prnt.sc/o1snya

Without theme
https://www.loom.com/share/0d5ff2a4426c4d019318c8322a36d382

With theme:
https://www.loom.com/share/98ab3bff5adf47ffb8e9c04286703cbd

[29sunil]

There are more than 3558 product images. Now We have run this command to regenerate imges.
php bin/magento catalog:image:resize

[engcom-Bravo]

Ok, @29sunil, but please point us out what we did incorrectly in our video, what we did not like You mean in Your steps to reproduce. As we understand You want to get the images being regenerated without php bin/magento catalog:image:resize. We didn't use that command and our images remain displayed, probably we miss something?

[29sunil]

Hello Team,
Yes, I see your video. The same thing works at my local system. But we are facing these issues at the live website. if there were any server related issues then let us know. What we suggest to the client regarding these issues. how we solve it.
This is not the right solution ( php bin/magento catalog:image:resize ).
That is the reason we are posting our query here.
Hopefully, the Magento team provide solutions
Thanks

[anthonyhacart]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @anthonyhacart. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @anthonyhacart, here is your Magento instance.
Admin access: https://i-23262-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[29sunil]

Hello Team,
Thanks for sharing instance
This instance working fine with image upload. As i already say that image upload is working fine at our local system.
But we are facing the issue at client server. What are the solutions to this problem?
What we say to the client regarding these issues. its seems that issues are not related to magneto or any premium theme. Because the same thing happens with default and premium theme.

If it is server issues then tell us solutions. what is missing at this server?

[Nazar65]

@29sunil same here https://github.com/magento/magento2/issues/22808 did you upgraded from 2.2 version ?

[29sunil]

Hello Team,
We have migrated data from magento1 to Magento 2. Now, these catalog images issues are generated.
Kindly suggest these issues.
Thanks

[engcom-Bravo]

Hi again @29sunil. The GitHub issue tracker is intended for Magento Core technical issues only. If You are not able to reproduce it on a vanilla instance locally or on other server like the one we provided You with ( https://i-23262-2-3-develop.instances.magento-community.engineering) its not an issue relevant for this repository. Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this issue. Also as You migrated from magento1 You may post Your issue on the specially opened for such issues repository https://github.com/magento/data-migration-tool. With that we are closing this issue here. Thank You for applying.

[zolthan]

We can reproduce this issue with a Magento 2 Apache instance. In the pub/.htaccess the following lines are missing in the section <IfModule mod_rewrite.c> in about line 150 before the final rewrite rules for existing files:

############################################
## Rewrite for non-existing files, directories and links in media

    RewriteCond %{REQUEST_URI} ^/media
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-l
    RewriteRule media/(.*) get.php?$1 [L]

@engcom-Bravo could you please reopen this ticket? An Apache installation doesn't process the media files through pub/get.php. For nginx the directives in line https://github.com/magento/magento2/blob/ee6bc3729e85ed1f1b5cd7c0eb9a3800bdd274c5/nginx.conf.sample#L136 ff are taking care of the processing.

[engcom-Bravo]

Hi @zolthan. Would You please describe the steps You make on a vanilla Magento instalation in order to reproduce the issue. Thank You.

[zolthan]

Hi @engcom-Bravo ,
we just have an Apache setup and clear the image cache via backend.

Afterwards any calls to the cached files (that currently don't exist) are running on a 404 error as there is no rewrite rule in pub/.htaccess to catch media requests and redirect them to pub/get.php where the image processing takes place.

After running bin/magento catalog:images:resize the requests for product images on the category page succeed.

Best Sebastian

[engcom-Bravo]

@zolthan I would yet have two questions to You (probably with the obvious answers but):

1. Are You running Your Magento in the Production mode and
2. Is Your Mageento root directory is configured to be "pub"?

[zolthan]

Yes and yes. It makes no difference in which mode Magento is running in this case.

Am 19.06.2019 um 18:57 schrieb engcom-Bravo [e-mail]:

@zolthan I would yet have two questions to You (probably with the obvious answers but):

Are You running Your Magento in the Production mode and
Is Your Mageento root directory is configured to be "pub"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[engcom-Bravo]

@zolthan, when I asked You to provide the the steps to reproduce You described the essence of reproduction. But I need the concrete and detailed steps that lead to reproduction. At least watch my video above. I did not replenish .htaccess with any rewrite conditions and everything works as expected. I just followed the steps provided by the issue reporter. Yes pub/media/catalog/product/cache is deleted as it is supposed to be after Flush Catalog Images Caches, but it is successfully regenerated when You for example first enter the catalog on the Frontend. So please tell what I'm missing in the video or doing something not as You mean. Thank You.

[hostep]

I also did some quick testing myself as well and couldn't reproduce the problem. I was using Apache 2.4.39 and PHP 7.2.19
Magento was in production mode and pub was used as documentroot.

I could see the get.php file being called by simply putting a die(); statement in there and noticing the image not being generated. After removing the die();, the image got generated.

So it looks like everything works and there is no bug. Maybe there is some weird Apache configuration going which causes your issue @zolthan?

[zolthan]

It could be a crappy Apache config. The server with the mentioned problem is not managed by us, so I can‘t see the complete configuration.

But what I don’t understand is, how the redirect to get.php is working without the redirect? For nginx there is an explicit redirect. Could you show M.E. how that works?

Am 20.06.2019 um 11:33 schrieb Pieter Hoste [e-mail]:

I also did some quick testing myself and couldn't reproduce the problem. I was using Apache 2.4.39 and PHP 7.2.19
Magento was in production mode and pub was used as documentroot.

I could see the get.php file being called by simply putting a die(); statement in there and noticing the image not being generated. After removing the die();, the image got generated.

So it looks like everything works and there is no bug. Maybe there is some weird Apache configuration going which causes your issue @zolthan?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[hostep]

@zolthan: the rewrite is in the pub/media/.htaccess file, maybe you accidentally deleted that file?

[zolthan]

Thank you @hostep you did it. Some automated deployment processes removed the additional htaccess files in pub.

So I'm out here. Everything is working fine now.

[hostep]

Excellent!

@29sunil: you might have the same problem then? Did this discussion above help you as well?