Magento 2.4.7-p3 Admin Category Does Not Appear as Disabled in Category Tree

[sagarjadav24]

Preconditions and environment

• Magento version - 2.4.7-p3

Steps to reproduce

1. Go to Catalog -> Categories
2. Edit any category
3. Disable category

Expected result

If the Admin disables any category from Catalog -> Categories, it should show as disabled highlighted in the category tree, as in previous Magento versions.

Older Magento version: https://tinyurl.com/2c5y4lp8
Latest Magento Version: https://tinyurl.com/2cyjdkbw

Actual result

If Admin disabled any category from Catalog -> Categories then it is visible as enabled no difference between the enabled category and disabled category.

Ref : https://tinyurl.com/2cyjdkbw

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]

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

• 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.
⚠️ 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-assistant]

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.

[sagarjadav24]

@magento give me 2.4.7-p3 instance

[engcom-Bravo]

Hi @sagarjadav24,

Thanks for your reporting and collaboration.

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

Steps to reproduce

• Go to Catalog -> Categories
• Edit any category
• Disable category

Here 2 categories were disabled and it were highlighted.

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

Thanks.

[hostep]

This was fixed 2 weeks ago in ACP2E-3350: Disabled Categories are no longer have their names grayed out in the category tree

[sagarjadav24]

@engcom-Bravo As per the @hostep comment issue is there but it's already fixed.

[engcom-Bravo]

@hostep Thanks for your Contribution!!.

As per this comment #39357 (comment) we are closing this issue.

Thanks.