Widget visible only on the first category

sheepfy commented 4 weeks ago

Preconditions and environment

Magento version latest 2.4.7-p2

Space is not trimmed out. If you check in the database the query: select * from layout_update where handle = 'catalog_category_view_id_21'; -> it will have 0 rows but this query: select * from layout_update where handle = 'catalog_category_view_id_ 21'; -> will have a correct result.

However, there is not page with the layout catalog_category_view_id_ 21

Image from a database of a fresh installed magento

Steps to reproduce

Create widget with Anchor Categories condition -> select few categories from the list -> save the widget.

Expected result

Widget to be visible on all categories selected

Actual result

Widget is visible only on the first category from the conditions

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”.

m2-assistant[bot] commented 4 weeks ago

Hi @sheepfy. 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.

m2-assistant[bot] commented 4 weeks ago

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

encora-ankit commented 4 weeks ago

@magento give me 2.4-develop instance

magento-deployment-service[bot] commented 4 weeks ago

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

magento-deployment-service[bot] commented 4 weeks ago

Hi @encora-ankit, here is your Magento Instance: https://da30c376a045755b7a8d7d602894995e.instances-prod.magento-community.engineering Admin access: https://da30c376a045755b7a8d7d602894995e.instances-prod.magento-community.engineering/admin_5ed9 Login: d728a49c Password: 81d394ff0cf6

encora-ankit commented 4 weeks ago

@magento give me a new instance, the last one is not working

magento-deployment-service[bot] commented 4 weeks ago

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

magento-deployment-service[bot] commented 4 weeks ago

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

engcom-Bravo commented 3 weeks ago

Hi @sheepfy,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Widget is visible only on the first category from the conditions

Hence Confirming the issue.

Thanks.

github-jira-sync-bot commented 3 weeks ago

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

m2-assistant[bot] commented 3 weeks ago

:white_check_mark: 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.

magento / magento2