Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block selection in widgets that have the same identifier #39692

Open
5 tasks
Yoann-D opened this issue Mar 3, 2025 · 11 comments · May be fixed by #39722
Open
5 tasks

Block selection in widgets that have the same identifier #39692

Yoann-D opened this issue Mar 3, 2025 · 11 comments · May be fixed by #39722
Assignees
Labels
Area: Content Component: Widget Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@Yoann-D
Copy link

Yoann-D commented Mar 3, 2025

Preconditions and environment

  • Magento version => 2.4.7-p3

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

Expected result

The "Block FR" should be displayed

Actual result

The "Block EN" should be displayed

Additional information

No response

Release note

No response

Triage and priority

  • 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”.
Copy link

m2-assistant bot commented Mar 3, 2025

Hi @Yoann-D. 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.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

@engcom-Bravo engcom-Bravo self-assigned this Mar 3, 2025
Copy link

m2-assistant bot commented Mar 3, 2025

Hi @engcom-Bravo. 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: 👇

  • 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- 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!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. label Mar 3, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Mar 3, 2025
@engcom-Bravo
Copy link
Contributor

Hi @Yoann-D,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Image Image

When we are selecting "Block FR" block "Block FR" was only displayed.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Mar 3, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Mar 3, 2025
@Yoann-D
Copy link
Author

Yoann-D commented Mar 3, 2025

Hi @engcom-Bravo

Excuse me, you then have to do "Save an continue Edit", and then the name will change

As for the identifier and the key, it does not know what label to display

If you select the "Block EN" and save, it will show you the label "Block FR"

Otherwise select the "Block FR" it will show you "Block EN"

@Yoann-D
Copy link
Author

Yoann-D commented Mar 3, 2025

Image

Image

Image

Save and Continue Edit

Image

@engcom-Bravo
Copy link
Contributor

Hi @Yoann-D,

Thanks for your Update.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the attached video.

Screen.Recording.2025-03-04.at.3.37.45.pm.mov

When we are selecting "Block FR" still block "Block FR" was only displayed.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@Yoann-D
Copy link
Author

Yoann-D commented Mar 4, 2025

Hi @engcom-Bravo ,

Do the same with Block EN.

I manage to reproduce it on several instances on my side

@engcom-Bravo
Copy link
Contributor

Hi @Yoann-D,

Thanks for your update.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the attached video.

Screen.Recording.2025-03-05.at.11.27.03.am.mov

When we are selecting "Block EN" after saving "Block FR" was displayed.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Component: Widget Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Area: Content and removed Issue: needs update Additional information is require, waiting for response labels Mar 5, 2025
@github-jira-sync-bot
Copy link

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

Copy link

m2-assistant bot commented Mar 5, 2025

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

@Mohamed-Asar
Copy link
Contributor

@magento i'm working on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Content Component: Widget Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants