If I set a URL alias for the cart page, then removing an item from the cart causes 2 messages instead of 1:

<product> removed from your shopping cart.
<product> successfully removed from cart.

Any idea what might be causing this?

Steps to reproduce:

  1. Create a URL alias for the cart page e.g. basket
  2. Add an item to your cart (takes you to /basket)
  3. Remove the item from you cart (the URL stays on /basket)


longwave’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

The text "successfully removed from cart" does not appear in Ubercart core, so I suspect this is caused by some custom configuration or a contributed module.

jackocnr’s picture

Project: Ubercart » Ubercart AJAX Cart
Version: 6.x-2.7 » 6.x-2.0
Component: Cart/checkout » Code
Category: support » bug
Status: Postponed (maintainer needs more info) » Active

You are right, it's being caused by Ubercart ajax cart module. Moved accordingly.

jackocnr’s picture

Status: Active » Closed (duplicate)

[Removed by user]

jackocnr’s picture

Version: 6.x-2.0 » 6.x-2.x-dev
Status: Closed (duplicate) » Active

This is still a problem with 6.x-2.x-dev

stewart.adam’s picture

Issue tags: +6.x-2.2 blocker

Tagging for 6.x-2.2 blocker.

thtas’s picture

I've worked around this by turning off the remove message by manually setting the DB variable


doesn't look like this setting has a UI element in the admin page yet

stewart.adam’s picture

I'd like to get a smaller than planned 6.x-2.2 release out shortly to fix some bugs and unfortunately I do not think I will have enough time to investigate this by then. I am bumping this to 6.x-2.3 blocker. In the mean time thtas's suggestion in #6 is a viable workaround.

stewart.adam’s picture

Status: Active » Fixed
Issue tags: -6.x-2.3 blocker +6.x-2.2 blocker

Turns out some refactoring I did inadvertently got rid of this message, so looks like this will be in 6.x-2.2 after all.

Latest dev should not cause duplicate remove messages. I will be releasing 6.x-2.2 stable shortly.

Automatically closed -- issue fixed for 2 weeks with no activity.