CMS Static Block Widget saves the block identifier instead of block ID

[jansentjeu]

Preconditions and environment

• Magento version 2.4.7
• Make sure you have multiple stores configured

Steps to reproduce

1. Go in admin to Content -> Blocks
2. Create new block for a store
3. Create another block for another store with the same identifier
4. Go in admin to Content -> Widgets
5. Add new widget with type CMS Static Block
6. Click on the tab Widget Options in the sidebar
7. Select the block you created in step 3 (the block with the highest ID)
8. Save the widget
9. Check the saved block in the widget

Expected result

The block from step 3 is saved in the widget (the block with the highest ID)

Actual result

The block identifier is saved in the database instead of the block ID. This will automatically load the block with the lowest id. In this case, that is the block from step 2

Additional information

This issue was introduced by the change in this commit. This should be reverted. The way the code was before is correct.

Release note

No response

Triage and priority

• [X] 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”.

[m2-assistant[bot]]

Hi @jansentjeu. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[jansentjeu]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[m2-assistant[bot]]

Hi @engcom-Dash. 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: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-deployment-service[bot]]

Hi @jansentjeu, here is your Magento Instance: https://15208ca800c1614cebc706b4a62d55df.instances-prod.magento-community.engineering Admin access: https://15208ca800c1614cebc706b4a62d55df.instances-prod.magento-community.engineering/admin_9898 Login: b7ce3bb8 Password: a16c0211c6e5

[jansentjeu]

@engcom-Dash Reproduced on 2.4.x. I'm not able to add the label.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Dash]

Hi @jansentjeu

Thanks for reporting and collaboration.

Verified the issue on Magento 2.4 dev instance and the issue is reproducable.

CMS Static Block Widget saves the block identifier instead of block ID

Preconditions and environment :

1. Magento version 2.4.7
2. Make sure you have multiple stores configured

Steps to reproduce :

1. Go in admin to Content -> Blocks
2. Create new block for a store
3. Create another block for another store with the same identifier
4. Go in admin to Content -> Widgets
5. Add new widget with type CMS Static Block
6. Click on the tab Widget Options in the sidebar
7. Select the block you created in step 3 (the block with the highest ID)
8. Save the widget
9. Check the saved block in the widget

Please refer the attached screenshots.

Block identifier "1234" in "Widget parameter column" instead of block id:

Widget in admin:

Block identifiers in admin:

[github-jira-sync-bot]

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

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[digitalrisedorset]

@magento I am working on this