/V1/products/{sku}/media does not assign roles correctly #21736

giacmir · 2019-03-13T15:01:09Z

When uploading media gallery images via API the last inserted one gets all roles (small_image, base, thumbnail) even if not required to and another image already has them assigned.

Preconditions (*)

Magento 2.3.0
php 7.1

Steps to reproduce (*)

create a new product without images
POST to /V1/products/{sku}/media a payload that includes all the three image types "base", "small_image", "thumbnail"
3.Verify in backend that the new image has all three roles
POST another image to /V1/products/{sku}/media, this time the "types" node should be an empty array

Expected result (*)

The last inserted image should have no roles
2.The first image should have maintained its assigned roles

Actual result (*)

last image has all three roles even if no one was specified.

magento-engcom-team · 2019-03-13T15:01:16Z

Hi @giacmir. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

yes
no

giacmir · 2019-03-13T16:33:52Z

@magento-engcom-team give me 2.3-develop instance

magento-engcom-team · 2019-03-13T16:34:02Z

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

magento-engcom-team · 2019-03-13T16:34:48Z

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

magento-engcom-team · 2019-03-14T08:23:18Z

Hi @engcom-backlog-nazar. 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).
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-engcom-team 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-engcom-team 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
Next steps are available in case you are a member of Community Maintainers.
6. Add label Issue: Confirmed once verification is complete.
7. Make sure that automatic system confirms that report has been added to the backlog.

ghost · 2019-03-14T09:04:45Z

Hi @giacmir thank you for you report, this issue has already fixed in 2.3-develop branch.

giacmir · 2019-03-14T09:08:48Z

Hi @engcom-backlog-nazar I actually tried that on the provided 2.3-develop instance yesterday and reproduced it. Was it fixed today?

ghost · 2019-03-14T09:14:43Z

@giacmir can you share with your payloads ?

ghost · 2019-03-14T09:20:06Z

@giacmir

giacmir · 2019-03-14T09:27:09Z

@engcom-backlog-nazar sure thing:

payload 1

{
  "entry": {
    "media_type": "image",
    "label": "First",
    "position": "0",
    "disabled": 1,
    "types": [
      "thumbnail",
      "image",
      "small_image"
    ],
    "file": "first_file.jpg",
    "content": {
      "base64_encoded_data": "<base64 encoded image goes here>",
      "type": "image\/jpeg",
      "name": "first_file.jpg"
    },
    "extension_attributes": []
  }
}

payload 2

{
  "entry": {
    "media_type": "image",
    "label": "Second",
    "position": "1",
    "disabled": 0,
    "types": [],
    "file": "second_file.jpg",
    "content": {
      "base64_encoded_data": "<base64 data goes here>",
      "type": "image\/jpeg",
      "name": "second_file.jpg"
    },
    "extension_attributes": []
  }
}

Thank you

ghost · 2019-03-14T09:33:38Z

@giacmir this only appears if you set all 3 types, but with 2 types works correct. and only for for first 2 images.

magento-engcom-team · 2019-03-14T09:39:25Z

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98681 were created

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

Al3ks73 · 2019-03-14T12:58:23Z

@magento-engcom-team give me 2.3-develop instance

magento-engcom-team · 2019-03-14T12:58:27Z

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

magento-engcom-team · 2019-03-14T12:59:20Z

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

magento-engcom-team · 2019-03-28T18:54:16Z

Hi @shikhamis11. 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.3-develop branch
Details
- Add the comment @magento-engcom-team 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!

3. Verify that the issue is reproducible on 2.2-develop branch.
Details
- Add the comment @magento-engcom-team 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
4. If the issue is not relevant or is not reproducible any more, feel free to close it.

m2-assistant · 2019-05-04T05:11:52Z

Hi @irajneeshgupta. 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.3-develop branch
Details
- Add the comment @magento-engcom-team 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!

3. Verify that the issue is reproducible on 2.2-develop branch.
Details
- Add the comment @magento-engcom-team 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
4. If the issue is not relevant or is not reproducible any more, feel free to close it.

irajneeshgupta · 2019-05-04T05:11:58Z

I am working on this at #dmcdindia1

irajneeshgupta · 2019-05-04T05:58:23Z

@magento-engcom-team give me 2.3-develop instance

magento-engcom-team · 2019-05-04T05:58:29Z

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

magento-engcom-team · 2019-05-04T05:59:36Z

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

irajneeshgupta · 2019-05-04T06:07:28Z

This issue has already been resolved in 2.3.1

engcom-Golf · 2021-02-19T08:53:23Z

Hi @giacmir, I could not reproduce this issue on 2.4-develop branch
It was probably fixed with changes in PR #18952
Will close this ticket.

magento-engcom-team · 2021-02-19T08:55:05Z

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

Please feel free to comment or reopen according to the Issue reporting guidelines
the ticket if you are still facing this issue on the latest 2.x-develop branch. Thank you for collaboration.

magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 13, 2019

ghost self-assigned this Mar 14, 2019

ghost closed this as completed Mar 14, 2019

ghost reopened this Mar 14, 2019

ghost added Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Mar 14, 2019

magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Mar 14, 2019

magento-engcom-team unassigned ghost Mar 14, 2019

shikhamis11 self-assigned this Mar 28, 2019

shikhamis11 removed their assignment Apr 10, 2019

irajneeshgupta self-assigned this May 4, 2019

magento-engcom-team added the Event: dmcdindia1 label May 4, 2019

irajneeshgupta removed their assignment May 11, 2019

sdzhepa added the Progress: ready for dev label Mar 26, 2020

m2-community-project bot removed the Progress: ready for dev label Sep 3, 2020

m2-community-project bot added the Progress: ready for dev label Sep 24, 2020

sdzhepa added Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it and removed Progress: ready for dev labels Oct 29, 2020

gabrieldagama added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Nov 12, 2020

m2-community-project bot added Progress: ready for dev labels Nov 12, 2020

gabrieldagama added this to the 2.5 milestone Nov 12, 2020

engcom-Golf closed this as completed Feb 19, 2021

github-jira-sync-bot added Progress: done and removed Progress: ready for dev labels Feb 19, 2021

/V1/products/{sku}/media does not assign roles correctly #21736

/V1/products/{sku}/media does not assign roles correctly #21736

Comments

giacmir commented Mar 13, 2019

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

Actual result (*)

magento-engcom-team commented Mar 13, 2019 • edited by giacmir Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

giacmir commented Mar 13, 2019

Uh oh!

magento-engcom-team commented Mar 13, 2019

Uh oh!

magento-engcom-team commented Mar 13, 2019

Uh oh!

magento-engcom-team commented Mar 14, 2019

Uh oh!

ghost commented Mar 14, 2019

Uh oh!

giacmir commented Mar 14, 2019

Uh oh!

ghost commented Mar 14, 2019

Uh oh!

ghost commented Mar 14, 2019

Uh oh!

giacmir commented Mar 14, 2019

Uh oh!

ghost commented Mar 14, 2019 • edited by ghost Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

magento-engcom-team commented Mar 14, 2019

Uh oh!

Al3ks73 commented Mar 14, 2019

Uh oh!

magento-engcom-team commented Mar 14, 2019

Uh oh!

magento-engcom-team commented Mar 14, 2019

Uh oh!

magento-engcom-team commented Mar 28, 2019

Uh oh!

m2-assistant bot commented May 4, 2019

Uh oh!

irajneeshgupta commented May 4, 2019

Uh oh!

irajneeshgupta commented May 4, 2019

Uh oh!

magento-engcom-team commented May 4, 2019

Uh oh!

magento-engcom-team commented May 4, 2019

Uh oh!

irajneeshgupta commented May 4, 2019

Uh oh!

engcom-Golf commented Feb 19, 2021

Uh oh!

magento-engcom-team commented Feb 19, 2021

Uh oh!

magento-engcom-team commented Mar 13, 2019 •

edited by giacmir

Loading

ghost commented Mar 14, 2019 •

edited by ghost

Loading