Page 1 of 1

Displaying kit products different from 7.0.2->7.0.3

Posted: Mon Nov 09, 2009 10:56 am
by jdarby
Just updated our dev site to 7.0.3 today and noticed that the way kit products are displayed is much different.

On basket.aspx nstead of grouping the kit into one item, as it technically should be, AC is displaying the Kit item (with the total price of all the components, our kits are setup with a price of $0.00) and then below it, looking like separate items, are the kit components with their individual prices. This ends up showing the total cost twice in the Price column but the subtotal is correct. This same style of breaking the kit down into its components and double-listing them is carried on throughout the rest of the checkout.

Below shows the difference between the 7.0.2 and 7.0.3 on basket.aspx

Image

Re: Displaying kit products different from 7.0.2->7.0.3

Posted: Mon Nov 09, 2009 11:27 am
by jdarby
Also, I have all of my kits set to be viewed as "Bundle", not "itemized" but they still show up this way. If I switch it to "itemized", the Kit item's price goes to $0.00 and it does now show the components under the Kit line item. It is still broken into 3 separate line items.

Re: Displaying kit products different from 7.0.2->7.0.3

Posted: Mon Nov 09, 2009 11:55 am
by jdarby
....and it also gives the customer the option for Multi-Address shipping when there is only one bundle in the cart. So, one bundle, 3 line items, 2 line items are components and 1 is the kit item. When I click multi-address shipping, it displays it as one line item, one shipment.

Re: Displaying kit products different from 7.0.2->7.0.3

Posted: Mon Nov 09, 2009 12:10 pm
by compunerdy

Re: Displaying kit products different from 7.0.2->7.0.3

Posted: Mon Nov 09, 2009 12:16 pm
by jdarby
http://dev584194.hyattathomeservices.co ... d-P10.aspx

Give that one a try. All of my kits are setup the same way.

Re: Displaying kit products different from 7.0.2->7.0.3

Posted: Mon Nov 09, 2009 5:07 pm
by compunerdy
If that kit is set to display as a bundle then I would think some custom coding is making it not work correctly.