UPSTREAM FIX

magento2-39722: Wrong block selected in widgets when blocks have the same identifier

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

Wrong block selected in widgets when blocks have the same identifier edited

Pull request title
Block selection in widgets that have the same identifier
Pull request
magento/magento2#39722
Issues
#39692 human
Author
@Mohamed-Asar
Merged
2025-04-29
Fixed in
2.4.9
Reported on
2.4.7-p3
Categories
Content
Components
magento/module-cms

Labels

Area
Content / CMS
Component
Widget
Priority
P2
Severity
—
Reported on (labels)
2.4.7-p3

Issue

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

Description

The "Block EN" should be displayed

Steps to reproduce

Since the last update where you save the identifier instead of the block_id, we encounter a problem of selection of blocks in the widgets.

We have several blocks per country, which have the same identifier, so when we select a block it is the last created that is selected.

Example:

Block FR => identifier = test
Block EN => identifier = test

When I select the "Block FR", it is the Block EN that is selected.

![Image](https://github.com/user-attachments/assets/7b93cbed-84e3-47bf-9245-de19c9b1f84f)

Expected result

The "Block FR" should be displayed

Actual result

The "Block EN" should be displayed

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.

LineCode match per tagTests
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: fails before, passes afterunit: fails before, passes 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: fails before, passes afterunit: fails before, passes 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.8%. Probability it is security relevant: 0.7%.

Show the model's answers and probabilities
QuestionAnswerProbabilitiesConfidence
Change kindbugfixbugfix 94.5%, refactor 2.0%, tests_only 1.5%, feature 0.9%, dependency 0.6%, docs_only 0.5%87.1%
Areaadminadmin 72.2%, frontend 12.3%, other 7.2%47.8%
Reported version2.4.7-p32.4.7-p3 61.1%, 2.4.7 6.4%, 2.4.7-p4 2.4%37.2%
Scope0.64 of 20 47.0%, 1 42.5%, 2 10.5%11.9%
Risk0.37 of 20 66.6%, 1 29.6%, 2 3.8%30.0%
Worth backporting1.69 of 22 74.9%, 1 19.4%, 0 5.8%40.2%

Download

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

Packages (1): magento/module-cms
Bundle README (what the ZIP ships)
# magento2-39722

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/39722
Issue: https://github.com/magento/magento2/issues/39692
Author: @Mohamed-Asar
Source commit: 3dd14f9b588a401b571306df96eba707657ff7fb
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.

Sources

Łukasz Bajsarowicz
Built by

Łukasz Bajsarowicz, e-commerce architect

Magento and Adobe Commerce architecture, upgrades, performance and audits for merchants and agencies since 2015; magento.watch is the tooling I use on those projects.

Open source, maintained on weekends.