-
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
Cart Price Rules: Category selection UI for Conditions do not come up. #6396
Comments
@apurv-anand thank you for your feedback. |
The requested steps are provided. Please update and accept the bug. |
This was fixed in 17788dc, ensure you have this code and also refresh your static files as well as browser cache. |
This is NOT fixed in 2.1.1. The same behavior is now seen under Actions category selection as well. |
Seems to be fixed in 2.1.1 for me. |
@apurv-anand Unfortunately, I could not reproduce the issue as you described it. Can you reproduce this issue on latest version of Magento2? |
2.1.7 still contains this bug; @apurv-anand fix you are describing is present in 2.1.7 and not working. Steps to reproduce:
|
@koenner01 Thank you for your comment, Internal ticket was created MAGETWO-70129. |
The problem seems to be a javascript problem, if I check an unchecked value on an existing condition I get:
|
Commits on MAGETWO-43350 might have a potential fix (haven't tried it yet) |
Internal ticket to track issue progress: MAGETWO-70345 |
M2.1.0
Cart Price Rules: Category selection UI for Conditions do not come up.
Issue
Category selection UI under Conditions does not come up if a rule needs to be edited. The UI will come up only for 1st time. If the rule is saved, and is revisited for editing, the Category selection tree UI wont show up.
Steps:
The categories UI does not pop up again. Clicking on the button does not do anything.
Workaround: Remove all the categories id and the button might work again.
Expected: The category selection UI should properly come up every time the rule is edited.
Ver: M2.1.0
The text was updated successfully, but these errors were encountered: