Magento2: Magento is no refreshing the cart page if you delete a product from cart side block

[ADDISON74]

Preconditions

1. Magento CE 2.1.8
2. Apache 2.4.10, PHP 7.0.23 w/ opcache, Percona MySQL 5.3.37-82-2

Steps to reproduce

1. Add a product to cart
2. Go to cart page
3. Delete the product from cart side block

Expected result

1. Cart page should be refreshed partially via AJAX showing no products

Actual result

1. Cart page still shows the product in cart, even the cart side block is empty
2. If you reload the page it will be empty as it should be

Before Deleting the product

After Deleting the product

[orlangur]

Observed system behavior is correct. Asynchronous actions performed via AJAX, like removing item in cart sidebar, must not cause a full page reload. Are there any pages behaving like this in core currently?

Shopping cart page may be AJAXified though using some extension or your custom implementation, for your particular store you may even implement full page reload as you suggest, but this is not something which needs to be changed in core.

[ADDISON74]

Please check Magento 1.9.3.6 behavior related to this issue. Removing the item from cart side block the page will update according to your action, without any reloading.

This is a bug and creates confusion. Once you delete the product from cart side block AJAX should do the job removing that product from cart page. If you consider this a correct behavior just hide cart side block if the current page is cart page.

[orlangur]

Removing the item from cart side block the page will update according to your action, without any reloading.

Is sidebar updated via AJAX in 1.9.x? Is main content area of shopping cart page updated via AJAX as well?

What would be really confusing to user is full page reload when he interacts with cart sidebar block.

[korostii]

What would be really confusing to user is full page reload when he interacts with cart sidebar block.

So you're saying that main content area should be updated without page reload by the same piece of JS? That makes perfect sense.

[orlangur]

should be updated without page reload

@korostii, _could_ be updated. For core such behavior seems to be a feature request, there are quite a lot of AjaxCart extensions in the market though.

[korostii]

I mean it's pretty strange to take aim at the specific solution suggested in the bug report, instead of discussing the issue itself.

Cart content is getting out of sync with the minicart - that's clearly a bug. Whether there are 3rd-party extensions "fixing" this or other known workarounds is irrelevant.

[ADDISON74]

This is a bug. It is clear to me Magento Team doesn't want to check Magento 1 for this behavior. If they could check they will see immediately this issue. Normally Magento 2 should keep all features available from Magento 1. This one is a bug, trust me I played thousands of times with Magento 1 and I saw this issue in version 2 from the very beginning.

Maybe it is better to find an extension, or keep it close, but disappointing loyal people who would like to find Magento 2 same like Magento 1.

[orlangur]

Ok, let's @magento-engcom-team decide whether it's a bug or a feature request.

[orlangur]

@ADDISON74, for the record

Expected result
Cart page should refresh and shows no product

Such behavior looks like a poor UX to me. Removing item from minicart staying on Shopping Cart page is quite a nonrealistic scenario. Proper expected result is updating page main content via AJAX or something.

[magento-engcom-team]

@ADDISON74, thank you for your report.
We've created internal ticket(s) MAGETWO-84614 to track progress on the issue.

[Microguru]

This error is still their in magento 2.5.5
Cart product count is not getting updated ,when cart item is remove programmatically .

[Ctucker9233]

@magento-engcom-team A year later and still no fix?

[orlangur]

@Ctucker9233 such scenario is still quite nonrealistic. I don't see this issue got much upvotes, isn't it?

Cart product count is not getting updated ,when cart item is removed programmatically

@Microguru looks like you're not invalidating private data accordingly.

[Ctucker9233]

@orlangur Just wondering what was up with this, since its old and still open. If it's a non-issue, why is it still open?

[orlangur]

@Ctucker9233 refreshing the whole page would be really lame UX, so, expected result here in description is wrong. Looks like just nobody bothered to fix current behavior - as I mentioned earlier, this scenario is quite nonrealistic.

[ADDISON74]

If nobody was bothered to fix this issue it doesn't mean it is fixed by default. As an engineer I have to analyze all aspects that could potentially create trouble without letting my users to discover them. This means being a pro. Thanks God this is not aircraft industry!

I will recommend to all my clients continuing using Magento 1 as much as they can. There a many wrong UX aspects in Magento 2 really annoying and not fixed yet. This one is a long time bug and should be fixed by now. Remember, Magento 1 is dealing with this out of the box!

@orlangur: If you are satisfy by this non-realistic scenario I am really sorry I reported it before. As you can see other people are finding my post. Anyway many sorry. It is easy to contest, trying finding votes, than admitting the real facts. This attitude made me to stop reporting bugs in Magento 2. Believe me I report daily bugs in many places but never find such of attitude.

[orlangur]

@ADDISON74,

There a many wrong UX aspects in Magento 2 really annoying and not fixed yet

Reloading the full page would be a poor UX compared to current one.

There is nothing to sorry about, did you elaborate a kind of fix maybe if you faced with it on real projects?

I didn't say a word that this issue should not be fixed, just that there are much more important ones, for example https://github.com/magento/magento2/issues/3625.

Every report matters and also it is important to vote to highlight some of them.

[aKalisch]

@ADDISON74 it‘s bad layout and ux to have a shopping cart sidebar on the actual shopping cart ;-)

Maybe just remove the sidebar if you are at the cart page as stated above.

[ADDISON74]

@Kalisch: Magento 2 Team should provide a solution not me. I gave up Magento 2 which in my opinion is far away from Magento 1 in many aspects. I reported this issue because in Magento 1 is working out of the box (RWD theme). End of story.

You mentioned it is a bad layout and UX to have a shopping cart sidebar visible in cart page. Please let me know how many online stores do you know which are hiding the cart sidebar when visiting the cart page. Just for improving my knowledge.

[m2-assistant[bot]]

Hi @ravi-chandra3197. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @ADDISON74. Thank you for your report.
The issue has been fixed in magento/magento2#22478 by @ravi-chandra3197 in 2.3-develop branch
Related commit(s):

• 60a465c9c83d4b2c33583f1028bf29f9143c516c
• c08dffb1d32d3c5786076bcf51c50fae622ede66
• 7d481bdfa764e6f8a20a9381c26f1b3696fe199f
• ce6c2288f0a386bb79688e7e6d3232e519ec2ae3
• b370b1e5f0005f17ebbe6e637cdb65b51f9710ea
• bcd75f44e9c9e126571ddb126ea6a7bb3ab5c9fb
• 73b96122f3df5c99dfc25a809a725e54e2039998
• 49936baec526f950e3b6d3affd67e85299bc4fad
• aa7ac82dfd96e4410695cb0cda1bb44e0c65b0a4

The fix will be available with the upcoming 2.3.4 release.