Closed KrzysztofWisniewskiAcc closed 1 week ago
Hi @KrzysztofWisniewskiAcc. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
Hi @engcom-Delta. 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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @KrzysztofWisniewskiAcc ,
Verified the issue on 2.4.7 community and commerce edition and we are not able to reproduce this issue.
Steps to reproduce:-
1.Enable js minification 2.Run bin/magento setup:upgrade bin/magento deploy:mode:set production 3.Go to front and open the console, check errors 4.Refresh the page few times
For magento community
For magento commerce
Please refer the attached screenshots and let us know if we missed anything.
Hi @KrzysztofWisniewskiAcc ,
Verified the issue on 2.4.7 community and commerce edition and we are not able to reproduce this issue.
Steps to reproduce:-
1.Enable js minification 2.Run bin/magento setup:upgrade bin/magento deploy:mode:set production 3.Go to front and open the console, check errors 4.Refresh the page few times
For magento community
...
I was able to reproduce the issue in the way you described. When I checked 'disable cache' in firefox, after few refreshes I was able to reproduce it. It was more rare to encounter the issue if 'disable cache' was not checked.
Hi @KrzysztofWisniewskiAcc ,
We Verified the issue on 2.4.7 and 2.4-develop again and we are not able to reproduce this.
Steps to reproduce:-
1.Enable js minification 2.Run bin/magento setup:upgrade bin/magento deploy:mode:set production 3.Go to front and open the console, check errors 4.Disable cache 5.Refresh the page few times
For 2.4.7
For 2.4-develop
Hi @KrzysztofWisniewskiAcc,
We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.
Thanks.
Preconditions and environment
Steps to reproduce
1) Install fresh Magento version of 2.4.7 2) Enable js minification (there are few ways to do it, I edit the config.php/env.php file) ...
3) Run:
4) Now go to front and open the console, errors should be there 5) If errors are not there refresh the page few times,
Best is to use Firefox, as the errors there appear almost always. The errors appear rarely in other browsers.
The first error: The resource from “http://magento.clean/static/version1718361386/frontend/Magento/luma/en_US/mage/common.js” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
These errors do not occur on magento 2.4.5
I did not test this on magento 2.4.6 so it may be that the issue also occurs there.
Expected result
There are no errors in console. The files are not loaded twice. Only minified files are loaded.
Actual result
There are errors in console. Files are loaded twice .min files & their corresponding 'not minified' are being requested (which fails to load as not minified files, don't exists in pub directory after setup:static-content:deploy) .
Additional information
I noticed the issue when upgrading from 2.4.4-p8 to 2.4.7 so not quite sure if this started to happen with 2.4.7 release or 2.4.6
Release note
No response
Triage and priority