Problems with price scope and config.php #33559

t-heuser · 2021-07-22T10:02:35Z

Preconditions (*)

Magento 2.4.2
Atleast 2 store views
1 product which is assigned to atleast 2 store views
Price scope is set to global

Steps to reproduce (*)

Set price scope to website in app/etc/config.php

Initial:

'price' => [
     'scope' => null,
],

New:

'price' => [
     'scope' => 1,
],

Execute bin/magento app:config:import
Clean magento cache bin/magento cache:clean

Expected result (*)

When I now save different product prices for each website it should save the values for each website

Actual result (*)

The price only gets saved for the Default website

Solution

The underlying problem is that in the table catalog_eav_attribute the value for is_global is '1' (= global scope) for the price attribute if you set the price scope to website via the config.php. This leads to \Magento\Catalog\Model\Product\Attribute\Backend\Price::Magento\Catalog\Model\Product\Attribute\Backend::afterSave() not saving the price for each store as it thinks price is a global attribute.

When changing the price scope to website via adminhtml (as seen in the DevDocs the column is_global in the table catalog_eav_attribute is set to '2' (=website scope) for the price attribute and everything works as supposed.

So the solution would be to set the is_global column in the table catalog_eav_attribute to '2' or '1' for the price attribute when changing the price scope via the config.php file.

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

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

The Severity is S1 as now I have to goto every database we have and set the value is_global in the table catalog_eav_attribute to '2' for the price attribute, which is something I definitly don't want to do in production environments. I cannot set the price scope via adminhtml as it's blocked as the config value is present in the config.php. So there is a workaround for this but it's wonky as hell.

The text was updated successfully, but these errors were encountered:

m2-assistant · 2021-07-22T10:02:37Z

Hi @oneserv-heuser. 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.

Please, add a comment to assign the issue: @magento I am working on this

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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

t-heuser · 2021-07-22T10:03:31Z

I can confirm that this issue also exists on a vanilla magento instance.

mrtuvn · 2021-07-23T09:55:26Z

just curiously have you import correct price scope ? Would be great if you can share file config.php in description
['system']['default']['catalog']['price']['scope']

t-heuser · 2021-07-23T10:13:03Z

@mrtuvn What exactly do you mean? Yes, the value I've changed has the path ['system']['default']['catalog']['price']['scope']. Before the value was null and now it's 1. 1 is also the value which the option in the select for the configuration of the price scope has.

m2-assistant · 2021-07-29T06:47:23Z

Hi @engcom-November. 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.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-November · 2021-08-02T11:17:06Z

Verified the issue on Magento2.4-develop branch and the issue is reproducible:

Steps to reproduce:

Magento Setup 2 Store views (Ref Guide)
Create/Edit a product and assign to both the Stores (Admin - Catalog - Products) and save
Set the price scope to 'Global' (Admin - Stores - Configuration - Catalog - Catalog - Price - Price Scope - Global) and Save
Set the price scope to "Website" in your Magento root/app/etc/config.php

'system' => [
        'default' => [
                'catalog' => [
                        'price' =>[
                             'scope' => 1
                         ]
                 ]
         ]
],

Execute bin/magento app:config:import
Clean magento cache bin/magento cache:clean
Admin - Verify Price scope is changed to Website - Price scope is changed to Website.
Navigate to Admin - Catalog - Products - Edit the same product - Change the scope to new Store view - Change the Price and Save
Issue: User is able to save the product but price is not getting changed. Default Price is displayed.
User is able to save different price only when scope is set to "All Store Views"
For Scope "Default Store View" and "New Store View" - New Price saved is not getting updated.

magento-engcom-team · 2021-08-02T11:41:10Z

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

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

rmsundar1 · 2021-08-08T13:22:38Z

@magento give me 2.4-develop instance

magento-deployment-service · 2021-08-08T13:22:40Z

Hi @rmsundar1. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service · 2021-08-08T13:27:01Z

Hi @rmsundar1, here is your Magento Instance: https://706799b32292bd52a7fbf116c841b8e5-2-4-develop.instances.magento-community.engineering
Admin access: https://706799b32292bd52a7fbf116c841b8e5-2-4-develop.instances.magento-community.engineering/admin_9f06
Login: 22754a69
Password: 6ddd52e584b9

zamu87 · 2023-06-30T19:21:58Z

Same problem in magento 2.4.6-p1

engcom-Bravo · 2025-01-31T07:56:37Z

Hi @t-heuser,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is still reproducible.Kindly refer the screenshots.

User is able to save the product but price is not getting changed. Default Price is displayed.

Hence Confirming the issue.

Thanks.

github-jira-sync-bot · 2025-01-31T07:57:29Z

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

m2-assistant · 2025-01-31T07:57:32Z

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

Sathakathulla-S · 2025-04-24T13:28:51Z

@magento I'm working on this

m2-community-project bot added the Issue: ready for confirmation label Jul 22, 2021

engcom-November self-assigned this Jul 29, 2021

m2-community-project bot removed the Issue: ready for confirmation label Aug 2, 2021

magento-engcom-team unassigned engcom-November Aug 2, 2021

engcom-Hotel added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Aug 3, 2021

m2-community-project bot added the Progress: ready for dev label Aug 3, 2021

rmsundar1 added a commit to rmsundar1/magento2 that referenced this issue Aug 9, 2021

Fix price attribute scope change with app:config:import magento#33559

52bd6cb

rmsundar1 mentioned this issue Aug 9, 2021

Fix price attribute scope change with app:config:import #33559 #33717

Closed

5 tasks

m2-community-project bot assigned rmsundar1 Aug 9, 2021

m2-community-project bot added Progress: PR in progress and removed Progress: ready for dev labels Aug 9, 2021

m2-community-project bot added Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Dec 9, 2021

m2-community-project bot unassigned rmsundar1 Oct 20, 2022

m2-community-project bot removed the Progress: PR in progress label Oct 20, 2022

m2-community-project bot added the Progress: ready for dev label Oct 20, 2022

engcom-Hotel added this to High Priority Backlog Aug 19, 2024

engcom-Hotel moved this to Ready for Development in High Priority Backlog Aug 19, 2024

magento-ct-gh-projects-svc removed this from High Priority Backlog Jan 15, 2025

engcom-Bravo added 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 Area: Catalog labels Jan 31, 2025

m2-assistant bot assigned Sathakathulla-S Apr 24, 2025

Sathakathulla-S linked a pull request Apr 25, 2025 that will close this issue

Problems with price scope and config.php issue fixed #39865

Open

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problems with price scope and config.php #33559

Problems with price scope and config.php #33559

t-heuser commented Jul 22, 2021

m2-assistant bot commented Jul 22, 2021

t-heuser commented Jul 22, 2021

mrtuvn commented Jul 23, 2021

t-heuser commented Jul 23, 2021

m2-assistant bot commented Jul 29, 2021

engcom-November commented Aug 2, 2021 •

edited by engcom-Hotel

Loading

magento-engcom-team commented Aug 2, 2021

rmsundar1 commented Aug 8, 2021

magento-deployment-service bot commented Aug 8, 2021

magento-deployment-service bot commented Aug 8, 2021

zamu87 commented Jun 30, 2023

engcom-Bravo commented Jan 31, 2025

github-jira-sync-bot commented Jan 31, 2025

m2-assistant bot commented Jan 31, 2025

Sathakathulla-S commented Apr 24, 2025

Problems with price scope and config.php #33559

Problems with price scope and config.php #33559

Comments

t-heuser commented Jul 22, 2021

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

Actual result (*)

Solution

m2-assistant bot commented Jul 22, 2021

t-heuser commented Jul 22, 2021

mrtuvn commented Jul 23, 2021

t-heuser commented Jul 23, 2021

m2-assistant bot commented Jul 29, 2021

engcom-November commented Aug 2, 2021 • edited by engcom-Hotel Loading

magento-engcom-team commented Aug 2, 2021

rmsundar1 commented Aug 8, 2021

magento-deployment-service bot commented Aug 8, 2021

magento-deployment-service bot commented Aug 8, 2021

zamu87 commented Jun 30, 2023

engcom-Bravo commented Jan 31, 2025

github-jira-sync-bot commented Jan 31, 2025

m2-assistant bot commented Jan 31, 2025

Sathakathulla-S commented Apr 24, 2025

engcom-November commented Aug 2, 2021 •

edited by engcom-Hotel

Loading