UPSTREAM FIX

magento2-39992: New price attributes getting Store View scope instead of the price scope

Community fix magento2-39992 merged into magento/magento2 on 2026-01-31, released in 2.4.9; applies cleanly to 6 releases from 2.4.8 to 2.4.8-p5.

Fixes new price attributes getting Store View scope instead of the price scope edited

Pull request title: Incorrect Scope Assigned to Price Attributes at Creation
Pull request: magento/magento2#39992
Issues: #39986 human
Author: @rogerdz
Merged: 2026-01-31
Fixed in: 2.4.9
Reported on: 2.4.6
Categories: Catalog/Product, Price/Tax
Components: magento/module-catalog

Labels

Area: Pricing
Component: Attributes
Priority: P2
Severity: —
Reported on (labels): 2.4.6

Issue

Title and steps come from the upstream issue and pull request.

Description

When a price attribute is created and saved for the first time, its scope is incorrectly set to Store View, regardless of the configured setting.

Steps to reproduce

1. Navigate to Stores > Configuration > Catalog > Catalog > Price > Catalog Price Scope and set the value to either Website or Global.
2. Create a new custom attribute of type Price.
3. Check the attribute scope in the admin grid or directly in the database (It will be Store View).

Expected result

The price attribute scope should match the value set in the configuration: Stores > Configuration > Catalog > Catalog > Price > Catalog Price Scope either Website or Global).

Actual result

When a price attribute is created and saved for the first time, its scope is incorrectly set to Store View, regardless of the configured setting.

Taken from the upstream issue.

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

Line	Code match per tag	Tests
2.4.6	2.4.6 conflict 2.4.6-p1 conflict 2.4.6-p2 conflict 2.4.6-p3 conflict 2.4.6-p4 conflict 2.4.6-p5 conflict 2.4.6-p6 conflict 2.4.6-p7 conflict 2.4.6-p8 conflict 2.4.6-p9 conflict 2.4.6-p10 conflict 2.4.6-p11 conflict 2.4.6-p12 conflict 2.4.6-p13 conflict 2.4.6-p14 conflict 2.4.6-p15 conflict	2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7	2.4.7 conflict 2.4.7-p1 conflict 2.4.7-p2 conflict 2.4.7-p3 conflict 2.4.7-p4 conflict 2.4.7-p5 conflict 2.4.7-p6 conflict 2.4.7-p7 conflict 2.4.7-p8 conflict 2.4.7-p9 conflict 2.4.7-p10 conflict	2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: no test data
2.4.8	2.4.8 clean 2.4.8-p1 clean 2.4.8-p2 clean 2.4.8-p3 clean 2.4.8-p4 clean 2.4.8-p5 clean	2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: test files do not apply to this releaseintegration: could not run before, could not run after
2.4.9	2.4.9 conflictcontains the fix	2.4.9: no test data

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 97.5%. Probability it is security relevant: 0.7%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 95.4%, feature 1.7%, refactor 1.3%, tests_only 0.9%, dependency 0.4%, docs_only 0.3%	89.4%
Area	catalog	catalog 88.7%, admin 7.3%, framework 1.4%	76.3%
Reported version	2.4.6	2.4.6 26.4%, 2.4.8 9.2%, unspecified 6.4%	7.9%
Scope	0.61 of 2	0 54.4%, 1 30.0%, 2 15.7%	11.5%
Risk	0.55 of 2	0 65.3%, 2 20.6%, 1 14.1%	23.3%
Worth backporting	1.58 of 2	2 67.0%, 1 23.6%, 0 9.4%	27.0%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-39992/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Bundle README (what the ZIP ships)

# magento2-39992

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/39992
Issue: https://github.com/magento/magento2/issues/39986
Author: @rogerdz
Source commit: 213c887147fa26ca3e04d2504aa7286ac247060f
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.