Backport of #5807: Fix minicart not cleared after order completion

[AntonEvers]

Fixes #4460 Fixes #4416 Fixes #1461 Fixes #4969 Fixes MAGETWO-52593

(cherry picked from commit 9093ce9)

Description

Fixed Issues (if relevant)

1. magento/magento2#<issue_number>: Issue title
2. ...

Manual testing scenarios

1. ...
2. ...

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[ihor-sviziev]

Original #5807 PR wasn't merged, fix was implemented in different way, so it should be done in the same way.
Also looks like it was already fixed in 2.1-develop by #10050

[reijervano]

Guys,

this pull request does not fix the problem!

[CNanninga]

In my experience, this issue does still exist in 2.1.9. #10050 doesn't fix the specific issue wherein the mini-cart still shows its old contents after completing an order.

Whether the appropriate implementation or not, this PR does fix it. (Though you must implement the same template change in additional templates if your theme or a custom extension is overriding the order success page.)

[AntonEvers]

I fully agree that this PR is not the proper solution. But as a hotfix it's ok. I'd rather see that not only POST and AJAX calls can invalidate the cart cache but also regular page requests. Let's work on a proper solution from here. I was asked to backport this by the Magento developers.

[vkublytskyi]

@ajpevers as original PR #5807 was closed and not merged into develop branch and I was not able to reproduce linked issues on 2.1-develop branch I close this PR. If the issue is still valid, please provide steps to reproduce for actual 2.1 version to reopen this PR.

[AntonEvers]

Hi @vkublytskyi,

Can you please contact @vrann on this issue? He asked me on 1 september: [8:54 PM]
@anton.evers Hi! would you be interested to make a backport this issue to 2.1? #5807

Thanks,

Anton