You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2019. It is now read-only.
With the current implementation it is still possible for the Collections to be ordered incorrectly.
Example:
If you take the below (simplified) XML. First tax is moved up because of its before clause, then tax is moved down again because of its after clause. This causes grand_total to be in the wrong spot, but at the time that grand_total was checked it was in the correct spot.
Hello @experius-nl I was having exactly the same issue, look at the issue I opened I have included a fix for this problem. This is due to usort working diffrently in PHP 7 and Magento not adding a sort order to the mrsp which causes it to go crazy.
With the current implementation it is still possible for the Collections to be ordered incorrectly.
Example:
If you take the below (simplified) XML. First tax is moved up because of its before clause, then tax is moved down again because of its after clause. This causes grand_total to be in the wrong spot, but at the time that grand_total was checked it was in the correct spot.
Expected sorting order:
[0] => nominal
[1] => tax_subtotal
[2] => subtotal
[3] => shipping
[4] => tax_shipping
[5] => tax
[6] => grand_total
Actual sorting order:
[0] => nominal
[1] => tax_subtotal
[2] => subtotal
[3] => shipping
[4] => grand_total
[5] => tax_shipping
[6] => tax
The text was updated successfully, but these errors were encountered: