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

Resizing product images when adding configurable products #27019

Open
chokabass opened this issue Feb 26, 2020 · 15 comments · May be fixed by #31588
Open

Resizing product images when adding configurable products #27019

chokabass opened this issue Feb 26, 2020 · 15 comments · May be fixed by #31588
Assignees
Labels
Area: Product Component: Image Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: PR in progress Reported on 2.3.4 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@chokabass
Copy link

chokabass commented Feb 26, 2020

Preconditions (*)

  1. Magento CE 2.3.4

Steps to reproduce (*)

  1. Image Resizing settings in STORES > Configuration > Advanced > System > Images Upload Configuration
  2. In above settings set: Quality = 90, Enable Frontend Resize = Yes, Maximum Width = 600, Maximum Height = 600. For all these settings "Use system value" is unchecked.
  3. Start adding new configurable product by giving a name, sku and price. Then scroll down to "Configurations" and click "Create Configurations" and fill in some dummy data while adding below image (750x667 original size) under any option of the 2:
    Apply single set of images to all SKUs or
    Apply unique images by attribute to each SKU

8-shaped-cotton-rope-ball

Expected result (*)

  1. Expect to get the image resized accroding to system configuration (600x600)

Actual result (*)

  1. Image gets added but in it's original size (750x667) despite the value set (600x600) in system configuration.
    2.Capture5
@m2-assistant
Copy link

m2-assistant bot commented Feb 26, 2020

Hi @chokablase. 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.4-develop instance - upcoming 2.4.x release

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

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

  • yes
  • no

@magento-engcom-team magento-engcom-team added Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Feb 26, 2020
@AnnaShepa
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-engcom-team
Copy link
Contributor

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

@AnnaShepa AnnaShepa self-assigned this Feb 27, 2020
@m2-assistant
Copy link

m2-assistant bot commented Feb 27, 2020

Hi @AnnaShepa. 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).

    DetailsIf 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.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - 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.

@magento-engcom-team
Copy link
Contributor

Hi @AnnaShepa, here is your Magento instance.
Admin access: https://i-27019-2-4-develop.instances.magento-community.engineering/admin_23be
Login: ca97f9a9 Password: 0c5706e95a3d
Instance will be terminated in up to 3 hours.

@AnnaShepa AnnaShepa added Component: Admin Component: Image Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch labels Feb 27, 2020
@ghost ghost unassigned AnnaShepa Feb 27, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @AnnaShepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-31960 were created

Issue Available: @AnnaShepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Feb 27, 2020
@Rus0 Rus0 self-assigned this Apr 4, 2020
@m2-assistant
Copy link

m2-assistant bot commented Apr 4, 2020

Hi @Rus0. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - 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!

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.


@magento-engcom-team magento-engcom-team added the Reported on 2.3.4 Indicates original Magento version for the Issue report. label Nov 13, 2020
@ajithkumar-maragathavel ajithkumar-maragathavel linked a pull request Jan 8, 2021 that will close this issue
4 tasks
@engcom-Delta engcom-Delta self-assigned this May 29, 2024
Copy link

m2-assistant bot commented May 29, 2024

Hi @engcom-Delta. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

    1. Add/Edit Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - 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!
    1. If the issue is not relevant or is not reproducible any more, feel free to close it.

@engcom-Delta engcom-Delta removed their assignment Jul 5, 2024
@engcom-Hotel engcom-Hotel moved this to Pull Request In Progress in Low Priority Backlog Aug 19, 2024
@engcom-Bravo engcom-Bravo removed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Component: Admin Event: Global-Contribution-Day Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. Triage: Done Has been reviewed and prioritized during Triage with Product Managers labels Oct 4, 2024
@engcom-Bravo
Copy link
Contributor

Hi @chokabass,

Thanks for your reporting and collaboration.

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

Screenshot 2024-10-04 at 13 21 45 Screenshot 2024-10-04 at 13 21 12

Image gets added but in it's original size (2672x1160) despite the value set (600x600) in system configuration.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Area: Product labels Oct 4, 2024
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-13211 is successfully created for this GitHub issue.

Copy link

m2-assistant bot commented Oct 4, 2024

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Product Component: Image Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: PR in progress Reported on 2.3.4 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
Status: Pull Request In Progress
Development

Successfully merging a pull request may close this issue.

9 participants