Following on from a question I had a couple months back (Disable certain Combination Variations), I now actually need to do it, and i'm kinda stuck a bit.
What i need to do is this:
Add a product with all its options. Disable certain variations from control panel. Set a price for a certain variation. Give a particular variation a description field Prevent users from selecting a particular variation on the front end (obeying the disabled variation option on the front end). Display description for a particular variation. Charge variation price.
It looks like I can do a lot of this with the stock section. I could use the SKU field for the description. Ok, its a hack, but it'd work.
I could also use the 'limit stock' button to disable a variation , but then, this kind of means that i'm using what may in future be a useful feature, so i'd like to avoid that.
My thinking is to replicate the 'stock' section in a way, with its own table, with all the fields i need.
So, I'm thinking hooks aint gonna cut it. I'm thinking that I probably am best to look at this as a new expression engine fieldtype that just so happens to require store to run.
I guess i'm just looking for any thoughts, or perhaps even a bit of confirmation that a new ee fieldtype would be the best way to approach this (and then using hooks to override product pricing).... because a big concern is whether or not i'll actually be able to do the frontend stuff too.
I obviously want to do this in a way that means it can be reused... (and not get overwritten every time store release an update)
To furnish this question with a little more info about the original problem, here's my original question.
I'm selling a series of products, one of which is configurable. It has four options, but not all combinations are available, and different combinations will result in a different price.