Issue-39692 Widget Block Selection issue fix - If block have same identifier

[Mohamed-Asar]

Description (*)

Used block id for widget_parameters instead of block identifier, allowing users to configure blocks with the same identifier across multiple store views.

Fixed Issues (if relevant)

1. Fixes Block selection in widgets that have the same identifier #39692

Manual testing scenarios (*)

1. Create Two Store Views.
2. Create Two CMS Blocks, one for each store view, using the same identifier.
3. Create Two Widgets, one for each store view, and assign the respective CMS blocks.
4. The corresponding CMS block should be displayed in the widget for each store view.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @Mohamed-Asar. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[Mohamed-Asar]

@magento run all tests

[Mohamed-Asar]

@magento run all tests

[Mohamed-Asar]

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Hello @Mohamed-Asar,

Thanks for the contribution!

I guess some of the Functional tests are failing due to the code changes. Please have a look on it.

Thanks

[Mohamed-Asar]

@engcom-Hotel Sure i will check and fix the Functional test issues

[Mohamed-Asar]

@magento run all tests

[Mohamed-Asar]

@magento run all tests

[Mohamed-Asar]

Hi @engcom-Hotel

I fixed the functional test case which is related to this ticket, please review

[engcom-Bravo]

@magento run all tests

[engcom-Bravo]

Hi @Mohamed-Asar,

Thanks for the collaboration & contribution!

✔️ QA Passed

Preconditions:

• Install fresh Magento 2.4-develop

Steps to reproduce

• Create Two Store Views.
• Create Two CMS Blocks, one for each store view, using the same identifier.
• Create Two Widgets, one for each store view, and assign the respective CMS blocks.
• The corresponding CMS block should be displayed in the widget for each store view.

Before: ✖️ 

After: ✔️

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks.

[engcom-Charlie]

@magento run Functional Tests B2B, Functional Tests EE

[engcom-Charlie]

The functional B2B and EE failures are not consistent in recent 2 builds. They are neither part of PR nor failing because of PR changes, seems to be flaky. Hence moving this PR to Merge in Progress.

Functional B2B: Run 1
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39722/86a9fd87949c0d2dfa62d6fbe329ae41/Functional/allure-report-b2b/index.html#categories

Run 2:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39722/b0270503448a141cbd76006ec220c7a2/Functional/allure-report-b2b/index.html#categories/6ca9d315ebd9ab54dbe1fb9148ebdc1f/490265a9f5bf0304/

Functional EE: Run 1
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39722/a37ce6c318ac40da9f7f354726c838e2/Functional/allure-report-ee/index.html#categories/a644910ae0cb11e839a98baa21929b76/236344c8f632dc36/

Run 2:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39722/2200de304f72e2a51958bff8f4961e9c/Functional/allure-report-ee/index.html#categories/6ca9d315ebd9ab54dbe1fb9148ebdc1f/4e1c1f6f9c860fa5/