-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Can't find category id in category page. #5467
Comments
Hello @duongquyet , thanks for reporting this issue. Internal ticket MAGETWO-55120 has been created. Best, |
Hi, Best regards, David |
Fixed issues: - MAGETWO-58237: Order status history contains wrong data after creation of a Credit Memo - MAGETWO-58386: Eliminate dependencies on modules from lib/Magento - MAGETWO-55120: [GitHub] No category id on the category page #5467 - MAGETWO-55900: [GitHub] Translate messages on password strength #5509 #5883 #5861 - MAGETWO-50412: [GITHUB] Issues with adding groups on attribute set creation page (#3607)
Issue was fixed and delivered into develop branch (see commit 14028aa ) |
@olysenko is this fix safe to merge into a 2.1.2 production environment or should I wait for a backport? |
I think it is better to wait for backport. Expectation is the last month of autamn |
Hi, I have 2.1.5 and the category ID seems to be missing in my adminhtml category pages as well. Has this been fixed and am I missing something? Or is this still a problem in 2.1.5? |
I really do not know what sense it makes to report bugs here. This ticket is now 1! YEAR old in the newest Version of magento 2.1.7 this is still not fixed! Pls do not get me wrong here but i really can not see a benefit of hundreds of hundreds bugs reported here over years and simply a handful is solved. Think about the time everybody spends here reporting bugs and what do you do with these bugs? "internal ticket xyz" merged back port. etc etc. Not helpful at all and loosing community like this! |
I don't see category id in category page.
Do you have any idea?
The text was updated successfully, but these errors were encountered: