It is still existing the 2.1.6 version too
It is still existing in the 2.1.7 version too
@thdoan please, format this issue according to the Issue reporting guidelines: with steps to reproduce, actual result and expected result.
@thdoan, Thanks for reporting this issue.
We've created internal ticket MAGETWO-70446 to address this issue.
Is there already an update or patch for this? Still happens in 2.1.7
@thdoan, thank you for your report.
The issue is already fixed in develop branch, 2.2.0, 2.1.9
And can you say where it is fixed? Because I won't upgrade anymore because each time everything is broken.
@magento-engcom-team : Can you say in which files this has been fixed?
hi, I am also looking for a solution on this. Is there any patch that we can apply on Magento version 2.1.x without upgrading to 2.2.0. ?
@magento-engcom-team : can you let us know where this has been fixed? Closing without reaction or helping people on 2.1.x is not what we want. It seems that you close all issues with saying: it's fixed in 2.2.x ...
@AlexanderHuyghebaert
Please let me know whether this issue has been fixed? since i am using magento 2 version 2.1.7 i am also looking for the solution api level. please help me
thanks
Since Magento does not support a fix, I made a fix myself. I've created cronjob that checks the prices of the child products and sets the final price in the index table
Any information on where this fix was applied? Currently on M2.1.10 and have the exact same issue.
@magento-engcom-team Can you let us know which files this has been fixed? I am using 2.1.7, I cant upgrade, give some info for the files so i can fix them
@magento-engcom-team any help please?
@magento-engcom-team tnx for the support. kappa
Most helpful comment
@magento-engcom-team : can you let us know where this has been fixed? Closing without reaction or helping people on 2.1.x is not what we want. It seems that you close all issues with saying: it's fixed in 2.2.x ...