Page 1 of 1
Child Kit Items
Posted: Tue Apr 12, 2011 7:22 pm
by sloDavid
Is there a reason why child products (those which are part of another product's kit) cannot themselves be a kit? In the admin panel, when I view the child product and click the Kit/Bundle link in the left nav, I don't see the ability to add child products -- even as hidden auto-included products. I only see the list of parent products.
I'm building this for a manufacturer who would really like to nest products, many of which are hidden, so that they can track the inventory stock level of the component parts. Any ideas?
Re: Child Kit Items
Posted: Mon May 02, 2011 2:47 pm
by skhvatkov2010
The logical guess it would be because it would be possible to link products recursively and the code would have to have a way to detect that and deal with it, or risk creating indefinite loop.
Perhaps some kind of a KitProductItemLevel property could be used so the parent would always get an item level of X, and children would get x+1, x+2, etc. and the logic could use it to prevent items with lower level being added as a child to the higher level preventing recursion.
This is exactly what we need for our project, by the way, it would have made it a lot easier and make a lot more sense if it was implemented, even if for a fixed number of levels (I'd take even 1 more level, although we would need 2 more to make it fit our model perfectly).
I have not thought about it much, since we do not have the source code, but if I saw it I might get a better idea of how it could be done.
Re: Child Kit Items
Posted: Mon Jul 11, 2011 2:24 pm
by sloDavid
Eh, it should be easy enough for the software to know that there's an ancestor/descendant relationship already and so prohibit a new relationship. I think I'm going to make a request.