Anyone using the Toolkit Product with Multi-Quantity Add function?

[lesliekirk]

I've been working as hard as I can to get the Toolkit Product with Multi-Quantity Add function working and looking good. It's not quite what I'd like it to be but it works. One of the negatives that I'd like to try and fix is how items display in the BASK, INVC and confirmation emails.

The function treats each attribute like a separate product, so if 12 attributes have been added, it will list out 12 times instead of once with 12 attributes. I think this might work okay for those who might want these to be individual products but I'd like to find a way to have them all combined and listed out as one product with attributes.

Here's an idea of how the confirmation email looks (there are more items than the screenshot has)



Is there anyway to put Humpty Dumpty back together again?

[Brennan]

That is a MIva thing and not related to the toolkit multi-add. MIva will always add the same product with different attribute as individual line items. The only way to get what you wanted would be to fake the display on the front end via template code. You would need to loop though the cart and build a new fake product with each of the attributes and display it instead of the real products in the cart.

[lesliekirk]

Okay, I think I get what you are saying. Miva thinks that the custom-basket product has been added 7 different times and doesn't understand that it's just one product. So there isn't any way to trigger something based on the product code? It would be so nice for it to look like this:



It's such a mission impossible to be able to create this build a basket that has the ability to include more than one of the attributes...

[lesliekirk]

That is a MIva thing and not related to the toolkit multi-add. MIva will always add the same product with different attribute as individual line items. The only way to get what you wanted would be to fake the display on the front end via template code. You would need to loop though the cart and build a new fake product with each of the attributes and display it instead of the real products in the cart.

Looking at the product, I see what should be looked for - if the "To", "From", "Message" and "ReceiveDate" are all the same group it as one product. But I'm assuming this can't be done?

[Kent Multer]

Looking at the product, I see what should be looked for - if the "To", "From", "Message" and "ReceiveDate" are all the same group it as one product. But I'm assuming this can't be done?

It can be done; but there's more to it than that. Suppose the customer wants to remove one of these items from the basket, or change the quantity; you'll need to apply that operation to all six products. I've written a number of modules that do this sort of thing. It can probably be done just with template code, but that's not what I'd recommend.

[lesliekirk]

It can be done; but there's more to it than that. Suppose the customer wants to remove one of these items from the basket, or change the quantity; you'll need to apply that operation to all six products. I've written a number of modules that do this sort of thing. It can probably be done just with template code, but that's not what I'd recommend.

That is a huge drawback to Bill's configuration - if you want to add something else to the "custom basket" there is no good way to indicate it's for that one. Although the items are attributes they don't get grouped with the master product. In Bill's configuration he mentions the usage of variants but I haven't tried using them so I'm not sure what impact if any it would have on what I want to do. I guess I need to go to Dream features and beg to have the native ability for attribute quantities in a manner that would group them all to master product.

[lesliekirk]

At this point in time, the store owner has requested that this product be deactivated - "They take so much more time than the standard basket and I'm afraid we can't keep after." I can understand that. I think it's also difficult to actually build the product and to edit it - as there is no way to edit the attributes.

[Bruce - PhosphorMedia]

hindsite 20/20...but this should have been designed as a 'custom' product who's parts are assembled (and tracked via jquery) until all the items are ready to be added to the basket, then, on add to basket the total price is loaded and the individual selections just stored in a text field attribute. If you stored the individual products codes in a hidden attribute, you could even make it editable once you reloaded the custom basket back into the basket creator.

[lesliekirk]

hindsite 20/20...but this should have been designed as a 'custom' product who's parts are assembled (and tracked via jquery) until all the items are ready to be added to the basket, then, on add to basket the total price is loaded and the individual selections just stored in a text field attribute. If you stored the individual products codes in a hidden attribute, you could even make it editable once you reloaded the custom basket back into the basket creator.

Yeah, if I had your mad crazy jquery skills