Frontend 3rd level of submenu not accessible

[stradd]

Preconditions (*)

1. Magento 2.4-develop

Steps to reproduce (*)

1. Install Magento 2.4-develop with sample data;
2. Go to Catalog - Categories;
3. Go to Women / Tops / Brass & Tanks;
4. Ad a new subcategory (Test for example);
5. Save;
6. Go to Homepage;
7. Main Menu -> Woman >Tops Brass & Tanks;

Expected result (*)

The new submenu is next to Brass & Tanks
Example 2nd level: Image link

Actual result (*)

The new submenu is at the top and cannot be reached.

Additional Information

Example: #28198 (comment)

[m2-assistant]

Hi @stradd. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@stradd do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @ajijshekh123. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[ajijshekh123]

@magento give me 2.4-develop instance

[magento-engcom-team]

Magento instance deployment temporary unavailable due to service maintenance.

[ajijshekh123]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @ajijshekh123, here is your Magento instance.
Admin access: https://i-28198-2-4-develop.instances.magento-community.engineering/admin_4dab
Login: 48c96a0a Password: 46247c1ed8bf
Instance will be terminated in up to 3 hours.

[ajijshekh123]

Hello @stradd,
This issue has been fixed in the latest Magento 2.4 instance. Please update your Magento version it will automatically fix the issue.

See attached screenshot:

This issue is the same as the below issue.
#25589

Let me close this issue.

Thanks.

[stradd]

I'm not sure it's the same issue. The category is displayed, but at the top and is inaccessible.


As can be seen in the picture, this is only the case with the third sub-level.

[ajijshekh123]

Right, @stradd,
I can't able to access the 3rd level category.
See attached the video:

Thanks.

[m2-assistant]

Hi @engcom-Alfa. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[engcom-Alfa]

The issue is reproducible on fresh 2.4-develop

Actual Result:

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-34375 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[kishorenagalingam]

@magento I am working on this

[magento-engcom-team]

Hi @stradd. Thank you for your report.
The issue has been fixed in #28260 by @kishorenagalingam in 2.4-develop branch
Related commit(s):

• a06e9c04f6abf257863d7abe115b567f3fd2a035
• d0bcebae8741211afbefabef597ce6d4b556d8c5
• 4d4e07fb1a858569a3bd7de8cf448369d6444254
• b2af00b26c9ae67611f8081404cea85b86c7584c
• 1abb42315d606199c68ce69743c2e6289ba522fe
• c1b71d93911c39ad365efe25d9116c8311ecd77d
• 84bfc0bfd309e4bda64bbf4baea66b37fe98e000

The fix will be available with the upcoming 2.4.1 release.