UPSTREAM FIX

magento2-39480: Grouped product quantity validation runs only after a page reload

Community fix magento2-39480 merged into magento/magento2 on 2025-07-02, released in 2.4.9; applies cleanly to 17 releases from 2.4.7 to 2.4.8-p5.

Grouped product quantity validation runs only after a page reload edited

Pull request title: Magento 2.4.7 minAllowed missing product order qty
Pull request: magento/magento2#39480
Issues: #39142 human, #39479 human
Author: @Mohamed-Asar
Merged: 2025-07-02
Fixed in: 2.4.9
Reported on: 2.4.7-p2
Categories: Catalog/Product, Shopping Cart
Components: magento/module-catalog-inventory, magento/module-grouped-product, magento/module-wishlist

Labels

Area: Product, Cart & Checkout
Component: Catalog, GroupedProduct
Priority: P2
Severity: —
Reported on (labels): 2.4.7-p2, 2.4.7-p3

Issue

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

Description

input type="number" name="qty" id="qty" min="0" value="0.6" title="Aantal" class="input-text qty" data-validate="{"required-number":true,"validate-item-quantity":{"maxAllowed":999}}" /

Steps to reproduce

1. View product (on product page)
2. View Source
3. Search (CTRL + F) maxAllowed

Expected result

input type="number" name="qty" id="qty" maxlength="12" value="0.5" title="Aantal" class="input-text qty" data-validate="{"required-number":true,"validate-item-quantity":{"minAllowed":0.5,"maxAllowed":10000}}" /

Actual result

input type="number" name="qty" id="qty" min="0" value="0.6" title="Aantal" class="input-text qty" data-validate="{"required-number":true,"validate-item-quantity":{"maxAllowed":999}}" /

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 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean	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: test files do not apply to this releaseunit: could not run before, could not run after
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 releaseunit: 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: 94.3%. Probability it is security relevant: 0.8%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 85.0%, refactor 7.0%, feature 6.3%, tests_only 0.8%, dependency 0.5%, docs_only 0.4%	67.7%
Area	frontend	frontend 52.2%, catalog 31.6%, checkout 10.6%	29.7%
Reported version	2.4.7-p3	2.4.7-p3 48.7%, 2.4.7 8.9%, 2.4.7-p2 7.7%	24.4%
Scope	1.55 of 2	2 62.8%, 1 29.3%, 0 7.9%	23.0%
Risk	0.97 of 2	1 73.2%, 0 15.1%, 2 11.7%	35.8%
Worth backporting	1.56 of 2	2 64.9%, 1 25.9%, 0 9.2%	24.6%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-39480/ 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-39480

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/39480
Issue: https://github.com/magento/magento2/issues/39142
Issue: https://github.com/magento/magento2/issues/39479
Author: @Mohamed-Asar
Source commit: 188fae40b48175854d805b20bb3455922a0bf3b1
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.