-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
ValueError: imagecolorsforindex(): Argument #2 ($color) is out of range #37890
Comments
Hi @adarshkhatri. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
@magento give me 2.4-develop instance |
Hi @adarshkhatri. Thank you for your request. I'm working on Magento instance for you. |
Hi @adarshkhatri, here is your Magento Instance: https://892b1bf92acda450368c3091b377fd78.instances-prod.magento-community.engineering |
Hi @engcom-Bravo. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Bravo, here is your Magento Instance: https://892b1bf92acda450368c3091b377fd78.instances-prod.magento-community.engineering |
Hi @adarshkhatri, Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop instance with EE edition and the issue is not reproducible.Kindly refer the attached video. Steps to reproduce
Page is loading without any errors. f8fdc542-765e-4b11-9b7f-85a41e263123.mp4Kindly recheck the behaviour on Magento 2.4-develop instance with EE edition and elaborate steps to reproduce if the issue is still reproducible. Thanks. |
Hi @adarshkhatri, Kindly provide latest update on this comment #37890 (comment) still you are working on this issue if you are able to reproduce the issue please elaborate the steps to reproduce.Please let us know still if you are facing any issue. Thanks. |
Hi @adarshkhatri, 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. |
@magento give me 2.4-develop instance |
Hi @adarshkhatri. Thank you for your request. I'm working on Magento instance for you. |
Hi @adarshkhatri, here is your Magento Instance: https://892b1bf92acda450368c3091b377fd78.instances-prod.magento-community.engineering |
@magento give me 2.4.6-p2 instance |
Hi @adarshkhatri. Thank you for your request. I'm working on Magento instance for you. |
Hi @adarshkhatri, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
@magento give me 2.4.6-p2 instance |
Hi @adarshkhatri. Thank you for your request. I'm working on Magento instance for you. |
Hi @adarshkhatri, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
@magento give me 2.4.6-p2 instance |
Hi @adarshkhatri. Thank you for your request. I'm working on Magento instance for you. |
Hi @adarshkhatri, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
same here, although I can upload the image in the admin but the error appeas in the exception.log and the image does not show in the fronend, also the error appears when throwing the resize command "bin/magento catalog:image:resize". |
I can replicate this on 2.4.6-p3 Magento. Removing all image roles from the image stopped the error. Nothing with the image appears to be wrong |
It seems they have made some changes, I haven't tested but it seems it will fix the issue. |
Preconditions and environment
Steps to reproduce
Go to any product,
Expected result
Page should load without any error.The page
Actual result
Page breaks while loading. Error thrown on system:
Additional information
The big problem with this is that we don't know which image is throwing the error. Spent good amount of time to pinpoint the product that had this image.
And surprisingly, the image loads in FE just fine.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: