Dependent Attributes: To specify a charity

[LilleyPadGifts]

Has anyone made a add-on, plug-in, whatever-ya-wanna-call-it ... to allow for Dependent Attributes?
I found some posts regarding this but they were from 2009 and before.

[mc12345678]

Has anyone made a add-on, plug-in, whatever-ya-wanna-call-it ... to allow for Dependent Attributes?
I found some posts regarding this but they were from 2009 and before.

Stock by attributes offers choices of values dependent on previous selection when using dropdowns, with showing only the selections that remain available going down that path (or out-of-stock if so desired to show). I believe there is a commercial version that does something similar.

[lat9]

You can see a demo of one of those commercial ones here.

[LilleyPadGifts]

Ok, but that affects what is shown below....the images... right? I would be using it to choose text for a field that would print on the order.
I don't want to change what they see, meaning the attributes wouldn't change what products they see. Does that make sense?

[lat9]

It sounds like you don't need dependent-attributes, if your attributes are "simply" to supply those text inputs to allow the customer to customize their product.

[LilleyPadGifts]

Well, I was hoping it would allow a long drop list to be more managable. My customers give 20% of their purchases to a team, charity, cause, that is preregistered on my site. Youth Sports alone causes the list to be a mile long, so I was hoping this plug-in would allow the list to be easier to get through. It would allow sub-cats, sub-sub cats....etc....

[LilleyPadGifts]

Understood the first part of that but not the last paragraph. And yes it has to be on every product. This is a option per product, NOT per total sale.

[LilleyPadGifts]

I really thought that Dependent Attributes sounded like what I needed.

[mc12345678]

I really thought that Dependent Attributes sounded like what I needed.

Yes in a small part. In order to get to the one team member, being able to filter down through the options is related to dependent attributes. How that is implemented is kind of the discussion right now.

See, populating the database to allow this grouping of attributes to be singly applied to all product, well, basically that takes a lot of database space.

What I believe is being suggested and it can be implemented a number of ways is to offer something that can be selected by the shopper (yes it could use a product that has the dependent attributes, but that has to be worked into the shopping flow). Things of consideration is that, typically if someone is logged in, they have their "normal" benefactor (affiliate), but there may come a time when one of the children takes up a different sport, or one comes of age, etc... to where a shopper may have multiple from which to choose just to support their own home. Anyways, there are a number of ways to implement it all, there's existing plugins that can be repurposed (I believe that was lat9's suggested path as well.) and there are some things that may need unique customization. I mean if you were okay with a fily making one purchase per "child" you could enforce the "choose your child" product and all purchases would go to that one purchase on that order.

[LilleyPadGifts]

There isn't a "normal" benefactor. No, I would not be happy with that at all.
I think I understand to a point what you are suggesting but when a customer comes to the site to order they might order 5 different things with 20% of each item going to 5 different registered groups. It needs to be in one order ...meaning they are not going to buy one, check out, buy another.... and the only actual work of that choice is to print those choices per item on their order when we print it out and when they print it out.
What are the results of a huge database? Slow to load? Won't load at all?????