Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We are experiencing an issue on our website where images are not displaying correctly #39370

Open
5 tasks
wiwuae opened this issue Nov 15, 2024 · 8 comments
Open
5 tasks
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report.

Comments

@wiwuae
Copy link

wiwuae commented Nov 15, 2024

Preconditions and environment

  • Magento version
  • Anything else that would help a developer reproduce the bug

Steps to reproduce

Navigate>Catalog
image

Expected result

Page is not responding

Actual result

We are experiencing an issue on our website where images are not displaying correctly, also there have an account issue

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Nov 15, 2024

Hi @wiwuae. 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.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

Copy link

m2-assistant bot commented Nov 15, 2024

Hi @engcom-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: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Nov 15, 2024
@wiwuae
Copy link
Author

wiwuae commented Nov 15, 2024

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

@engcom-Bravo
Copy link
Contributor

Hi @wiwuae,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the attached video.

Screen.Recording.2024-11-18.at.09.21.25.1.mov

We are able to upload the images and save the product successfully.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible and also please check if any third party modules causing this issue.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Nov 18, 2024
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Nov 18, 2024
@wiwuae
Copy link
Author

wiwuae commented Nov 18, 2024

How much time does it take to update?

@engcom-Bravo
Copy link
Contributor

Hi @wiwuae,

Thanks for your update.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.we are able to upload images and images are displaying correctly and pages are working fine.Could you please verify if any third party modules causing this issue.

Thanks.

@Serfe-com
Copy link

Hi @wiwuae For the image that you are displaying the issue you are seen is a security breach or misconfiguration. You should not be able to see the directory listing of the server when requesting the contents of the page. You are seen https://github.com/b374k/b374k when requesting the contents, which means that the site as a bad configuration or a security problem on that url and the server is compromised.

Please, take the required considerations to remediate this immediately.

@engcom-Bravo
Copy link
Contributor

@Serfe-com Thanks for your Contribution!!!.

Hi @wiwuae,

We tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Could you please refer this comment #39370 (comment) and please let us know if you are still facing any issue.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

3 participants