Skip to content
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

2.1.1 Promotional Cart Rule Conditions issue #6911

Closed
dapdx opened this issue Oct 6, 2016 · 11 comments
Closed

2.1.1 Promotional Cart Rule Conditions issue #6911

dapdx opened this issue Oct 6, 2016 · 11 comments

Comments

@dapdx
Copy link

dapdx commented Oct 6, 2016

In Magento 2.1.1 there is an issue with the Promotional Cart Rules conditions. The top Apply run only if the following conditions are met works fine. But below when you go to add the conditions to apply the rule to specific products the field does not retain the selection.

Preconditions

  1. Magento 2.1.1, PHP 7

Steps to reproduce

  1. Create Promotional Cart Price Rule
  2. Go down to "Apply the rule only to cart items matching the following conditions"
  3. Choose Category
  4. Choose a category in the drop down menu
  5. Hit the green Check mark to apply the selection
  6. The selection should be save, but instead just shows "..."

Expected result

  1. The selection should show "Category is 11"

Actual result

  1. Shows "Category is ..."
@SerhiyShkolyarenko
Copy link
Contributor

@dapdx thank you for reporting!
AFIU you mean "Actions" tab on step 2. I tried these steps on the latest develop branch and I see "Category is 4" after step 5. Do you have the same result on the latest develop?

@dapdx
Copy link
Author

dapdx commented Oct 20, 2016

Yah, I've upgraded to 2.1.2 and still have this issue. If I know the category number I can enter it and it works, but if I use the selector box, which brings up the list of categories and I select the category I want, it doesn't save. I think it's an issue with the selector function.

@SerhiyShkolyarenko
Copy link
Contributor

reproduced on v. 2.1.2, but it's fixed in develop branch.

@Ctucker9233
Copy link

@SerhiyShkolyarenko is there a commit reference?

@SerhiyShkolyarenko
Copy link
Contributor

SerhiyShkolyarenko commented Oct 25, 2016

It was fixed in MAGETWO-55184. Commits: 911ec93 and a86eda3.

@SerhiyShkolyarenko
Copy link
Contributor

closing as duplicate of #5526

@Ctucker9233
Copy link

@SerhiyShkolyarenko Will MAGETWO-55184 be included in 2.1.3?

@SerhiyShkolyarenko
Copy link
Contributor

Yeah, it seems to be. Internal issue for backporting to 2.1 is MAGETWO-58321.

@Ctucker9233
Copy link

@SerhiyShkolyarenko Ok, I'll wait and see.

@SerhiyShkolyarenko
Copy link
Contributor

@Ctucker9233 sorry, it was wrong info. MAGETWO-55184 IS devilered to 2.1.3 branch too. So, you'll see it soon.

@Ctucker9233
Copy link

@SerhiyShkolyarenko Excellent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants