Category URL rewrites cannot be created for categories under level 3

[github-jira-sync-bot]

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]

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[bot]]

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:

• @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.

[Kannakiraj123]

@magento I am working on this

[lakshmana49]

@magento I am working on this

[m2-assistant[bot]]

Hi @lakshmana49! :wave: 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]

@magento add to contributors team

[m2-assistant[bot]]

Hi @lakshmana49! :wave: Thank you for joining. Please accept team invitation :point_right: here :point_left: and add your comment one more time.

[lakshmana49]

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.

[hostep]

Seems to be fixed by: https://github.com/magento/magento2/commit/0aea99659a5f072165940033bce4a3a76b33c2ea