Page 1 of 1

Add To Cart - Quantity Update To Wrong Product After Paging

Posted: Mon Mar 03, 2008 9:04 am
by M3NTA7
I believe this is a bug, and if so, it's a bad one.

v7 RC2 ASP.NET 2
IE 7 (not sure about other browsers)
CategoryGrid2.ascx (not sure about other templates)

Description:
When Add To Cart is used in conjuction after paging to different pages, the quantity of existing products in the cart are updated instead of new parts being added to the cart. This occurs when the product on page 2+ is in the same position on the page that the original product was selected from. From what I've seen, this occurs in any position that is relative to previously added products.

Scenario:
Using a category with multiple pages.
On page 1: click Add To Cart on first product.
Click page 2 button to navigate to second page
On page 2: click Add To Cart on first product on page(this is a different product)

Actual Results:
1 Product is listed in the basket, BUT the quantity is 2.

Expected Results:
2 DIFFERENT products should now be in the basket instead of 1 product with a QTY of 2.

Hopefully I've described this clearly. If you need any more information on this, please let me know.

Thanks,
Glen

Posted: Mon Mar 03, 2008 9:08 am
by Shopping Cart Admin
Hello Glen,

From your description this is working as intended. Unless the product is different* the QTY will be added to the previous basket line item.

* e.g. Option differences, line item message (product template), etc.

The Product is Different

Posted: Mon Mar 03, 2008 9:15 am
by M3NTA7
That's the case, it's a different product with a different SKU.

So, from what I've described, it's a bug and is NOT working as expected. :) :cry:

The customer would select DIFFERENT PRODUCTS, and be charged and shipped ONE PRODUCT.

That's what the problem is. That's why I used the word DIFFERENT in my expected results.


Thanks,
Glen

Posted: Mon Mar 03, 2008 9:31 am
by Shopping Cart Admin
Hello,

I've been able to replicate the issue and I've posted it to our bug reporting system. In the future please post all possible bugs to our ABLECRM system, thank you.