Hi John
What you are doing sounds interesting, and I am sure you are not the only one who would like do something like this.
I have a couple of things to say about this. One is that the value of the attributes seems to get passed around in the product id field. While this was always curious to me, I have never had the need to go and see exactly how this worked , or why it was done this way. I figured it was a hash of some information that was stored elsewhere, or some clever arrangement of the attribute values in a determined sequence.
That may be why you can't see any attribute values in session variable. Try looking at the productid of a product in the cart, with attributes, and of a product without attributes, and I think you will see what I mean.
If I am right, you may have to delve into the mystery of that, to do what you want.
The second thing that I have to say is, do you need to do it this way? My first approach would be to create a product to represent each bundle, and then decrement the relevant component product's inventories once the transaction had gone through. Of course this will only work if there are no attributes on the bundled products that need the customer to consciously set. But if only the main product in the bundle has attributes, then perhaps this might be a simpler solution that also does the job?
That is my 2c worth. I am interested in seeing how you get on.
Justin






Bookmarks