Quantity discounts - incorrect cart total

[tbaquatics]

I have a quantity discount on item x, buy 1 and it's $10, buy 5 and it's $8.

Add 5 to the cart, says $40 on the line item, but total says $50 in cart. Any ideas how to correct? 1.3.8a and standard built in qty discounts.

[Ajeh]

Are you using the built in Quantity Discounts or an add on?

Are you using Priced by Attribute?

[tbaquatics]

Are you using the built in Quantity Discounts or an add on?

Are you using Priced by Attribute?

Built in. No pricing by attribute on this item.

[Ajeh]

Odd ...

What are your settings on the Discount Quantities that you are using?

In the Products Price Manager, what are you using for the ...
Discount Type:
Discount Priced from:

[tbaquatics]

Odd ...

What are your settings on the Discount Quantities that you are using?

In the Products Price Manager, what are you using for the ...
Discount Type:
Discount Priced from:

Actual price, and 4 different levels.

[Ajeh]

Also check the Known Bug Fixes for v1.3.8 ... all should be applied and #24 is often related to issues with Attributes on a Product ...

[ChrisR]

Also check the Known Bug Fixes for v1.3.8 ... all should be applied and #24 is often related to issues with Attributes on a Product ...

Have version 1.3.8a installed.
Using price table for quantity discounts, as well as min qty set to 10 and units to 5. I also have attributes for 2 different colours. When you add 10 items to the basket and choose a colour and then add another 5 items to the basket with another colour it tkaes the fits 10 at the price for ten and then the next 5 of different colour get the price for 10 and more, but the original 10 stay as they are. If you then add 15 more to either quantity to move into the next qty dicount bracket both quantities move up one bracket.
It is on this product http://totallyautomated.eu/index.php...roducts_id=177

I have tried your fix linda from known bugs 1.3.8 #24 but it bomed my site out and not sure why and if after getting it working again I want to try the fix again. Perhaps this fix is not good for 1.3.8a

Any clues to how to fix it.

thanks
Chris