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

Category URL rewrites cannot be created for categories under level 3 #36973

Closed
github-jira-sync-bot opened this issue Mar 6, 2023 · 9 comments
Labels
Evaluated 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. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.

Comments

@github-jira-sync-bot
Copy link

Issue:
When creating category URL rewrites, the category tree only loads upto level 3 categories.

Steps to reproduce:

  • Create a category tree which has more than 3 levels of sub categories (Women > Tops > Jackets > Jackets Sub)
    !image-2023-03-01-15-18-30-394.png|width=831,height=311!
  • Try to create a URL Rewrite for that level 4 "Jackets Sub" category.

Actual result:
Category tree only displays upto level 3 categories.
!image-2023-03-01-15-20-01-449.png|width=924,height=328!

Expected result:
Category tree should display categories that are level 4 or below.

Additional information:
app/code/Magento/Catalog/Block/Adminhtml/Category/AbstractCategory.php::
getRoot() is called via app/code/Magento/UrlRewrite/view/adminhtml/templates/categories.phtml with no $recursionLevel so the default recursion level is taken as 3.

@github-jira-sync-bot github-jira-sync-bot added Evaluated 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. Progress: ready for dev Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Mar 6, 2023
@github-jira-sync-bot
Copy link
Author

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1703

@m2-assistant
Copy link

m2-assistant bot commented Mar 6, 2023

Hi @github-jira-sync-bot. 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:


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.

@m2-community-project m2-community-project bot added this to Ready for Development in High Priority Backlog Mar 6, 2023
@Kannakiraj123
Copy link
Contributor

@magento I am working on this

@m2-community-project m2-community-project bot moved this from Ready for Development to Dev In Progress in High Priority Backlog Mar 7, 2023
@m2-community-project m2-community-project bot moved this from Dev In Progress to Pull Request In Progress in High Priority Backlog Mar 7, 2023
@Kannakiraj123 Kannakiraj123 removed their assignment Mar 8, 2023
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Ready for Development in High Priority Backlog Mar 8, 2023
@lakshmana49
Copy link
Contributor

@magento I am working on this

@m2-assistant
Copy link

m2-assistant bot commented Mar 8, 2023

Hi @lakshmana49! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

@lakshmana49
Copy link
Contributor

@magento add to contributors team

@m2-assistant
Copy link

m2-assistant bot commented Mar 8, 2023

Hi @lakshmana49! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

@lakshmana49
Copy link
Contributor

This issue is under development by an internal team. The fix will be delivered to the mainline according to our processes once done, and the status of this issue will be updated. If there are any incomplete Pull Requests to this issue and the community code will be re-used, all original commits will be preserved.

@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in High Priority Backlog Apr 14, 2023
@hostep
Copy link
Contributor

hostep commented Apr 15, 2023

Seems to be fixed by: 0aea996

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Evaluated 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. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Development

No branches or pull requests

4 participants