Magento 2.3.4-p2 issue on changing media_gallery attribute to Global "SQLSTATE[42S22]: Column not found: 1054 Unknown column 'attribute_id' in 'where clause' query was: DELETE FROM catalog_product_entity WHERE (attribute_id = '268') AND (store_id IN(1, 10, 13))"

[kamranzafar1]

Preconditions and environment

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

Steps to reproduce

In Admin Panel Navigate to (Admin->STORES->Attributes->Product) search Attribute Code (media_gallery) click on record and edit this attribute. Then change the attribute scope (ATTRIBUTE INFORMATION -> Properties -> Advanced Attribute Properties -> Scope) change it to website and click on Save Attribute (it is working fine). Now change the scope back to Global and click on Save Attribute. (Not able to change)

Expected result

Should be able to change media_gallery attribute's scope to Global. If its scope is Website or Store View

Actual result

Not able to change the attribute's scope. (SQLSTATE[42S22]: Column not found: 1054 Unknown column 'attribute_id' in 'where clause', query was: DELETE FROM catalog_product_entity WHERE (attribute_id = '268') AND (store_id IN(1, 10, 13)))

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”.

[m2-assistant[bot]]

Hi @kamranzafar1. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• 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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://593bff370b05880d97426a89f080afc6.instances.magento-community.engineering Admin access: https://593bff370b05880d97426a89f080afc6.instances.magento-community.engineering/admin_7457 Login: f7e9516b Password: 4016bc7fc401

[kamranzafar1]

[kamranzafar1]

when trying to change back the scope from storeview to Global, got error above in attached image.

[m2-assistant[bot]]

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

• 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.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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

Hi @kamranzafar1 ,

We are checking the issue in 2.4-develop branch and we are getting actual result...we are not able to change scope.

In Admin Panel we are trying to change scope but we are not able to change. For reference kindly check the screenshot which is attached below.

ScreenShots:

Steps We Follwed by: 1.Install Magento instance 2.Go to Stores 3.Click Attribute 4.Go to Product 5.search Media_gallery Attribute 6.Click Attribute Information 7.Click Advanced Attribute 8. Trying to Change the scope 9. We are not able to change the scope

We are getting actual results.

Let us know if we are missing anything!

Thanks!!!

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

:x: Something went wrong. Cannot create Jira issue.

[github-jira-sync-bot]

:x: Something went wrong. Cannot create Jira issue.

[github-jira-sync-bot]

:x: Something went wrong. Cannot create Jira issue.

[engcom-Hotel]

Hello @engcom-Dash,

As per our discussion, we need to recheck this issue according to the main description.

Thanks

[kamranzafar1]

@engcom-Hotel @engcom-Dash Any update on the issue?

[m2-assistant[bot]]

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: :point_down:

• [ ] 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.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.

[engcom-Bravo]

Hi @kamranzafar1,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop branch but could not able to reproduce the issue.we are not able to change the scope of the media_gallery attribute.it is by default we can't change.

Note : we can't able to change scope to either Website or Storeview when it is in Global for this attribute.

Please try to reproduce in latest 2.4 develop branch.

Please Provide us exact steps to reproduce this issue.

Thanks.

[engcom-Bravo]

Hi @kamranzafar1,

We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.