Closed twiking closed 7 years ago
@twiking, thank you for reporting!
Internal ticket MAGETWO-47858 was created
Is there any update on this issue?
Hi Is there any update on this?
Hi, this issue is not reproducible(fixed) on develop branch. For now it is all update
Hello @olysenko,
I don't exactly get what you are saying. Is the problem solved in develop branch? I'm currently running Magento CE 2.1.2 in development mode and encounter the same problem.
@wigman Yes this problem is solved in develop branch, but not in 2.1
@olysenko ok, great. would you happen to know the commit where it was fixed? That way I can cook up a patch. Thanks a lot!
yes, please post a link to the known commit ... some of us cannot wait for the major patch release.
Please, someone know the patch or the commit about that ?
Can we please get a commit reference; Like @spyrule said, some of us CANNOT wait for the slow machine of the major releases.
This is a pressing issue and causing real problems for clients.
Ok I looked into this further (because we cannot wait on official Magento response) and the commit where this issue is fixed is https://github.com/magento/magento2/commit/49d7b065efa
Any update on this? It still persists in Magento 2.1.4
Since this has a commit from 6 Jul 2016: When is this gonna be released?
Not released with Magento 2.1.6...
Conditions are actually saved, but does not restored when edit the widget. Any update on this? Issue still persist in Magento ver. 2.1.7
Yes same issue in Magento ver 2.1.7. Also condition not properly work on frontend. Any update on it?
@twiking, thank you for your report. We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue. We tested the issue on 2.3.0-dev, 2.2.0, 2.1.9
@magento-engcom-team we can confirm, that the issue is fixed in our project with 2.1.9. thank you.
Steps to repeat
Expected result: The defined conditions should be shown. Actual result: The defined conditions are not shown.
The conditions are saved correctly. Confirmed by looking at the source
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36. JS errors: None