Hi @sasilinux , thank you for your report
We've created internal ticket MAGETWO-58849 to address this issue.
Same issue on our installation, CE 2.1.1.
Ronny
@miakusha: this issue was already reported multiple times, all the tickets link to this one: https://github.com/magento/magento2/issues/5323 and that one already has a MAGETWO reference assigned to it, maybe it's best to mark these in your internal ticketing system as duplicates?
@sasilinux , @ronnybremer , @hostep Fix for this issue was delivered to develop branch in the scope of b046944
Closed as already fixed
Does this fix work for 2.1.1 or are we waiting on a port?
@Ctucker9233, This fix will be delivered to 2.1.x in the scope of MAGETWO-59246
No fix in 2.1.2, same issue.
@irenelagno Any idea when that fix will be ready?
Would really like an answer to this too!
No Fix yet?
Technically it has been fixed, its just stalled on the development version. Would be nice to know when these issues are gonna be implemented into the mainline so we don't have to check for them with each magento install/upgrade we do. Especially since this was marked as fixed a month ago.
Most helpful comment
Technically it has been fixed, its just stalled on the development version. Would be nice to know when these issues are gonna be implemented into the mainline so we don't have to check for them with each magento install/upgrade we do. Especially since this was marked as fixed a month ago.