Just beginning to investigate a project that might use this module. The client will be selling single and multiple user licenses.
Is it possible to have 2 licenses attached to one product, which can be selected using product attributes??
Many thanks.

Comments

rainbreaw’s picture

rainbreaw commented

Subscribing: I have a project that needs to be able to do this.

hixster’s picture

hixster commented

Yes, it would seem from a bit of digging that this isn't possible at the moment.
Ideally, I'd like an attribute that has options like 1 user, 3 user license and to then be able to choose a sequence based on that choice.
I'm sure this crops up quite a lot with software license sales as essentially all the product information is the same, there would be no sense in having duplicate products in the CMS, just to support a different license file on each.

Freixas, any suggestions on how to get started with the above?

On anther note, I think my issue is compounded by the fact we're also using uc_multi_price to sell products in different regions.

freixas’s picture

freixas commented

Disk space is cheap. My advice is that you make these separate products. It works for Newegg and others, so it isn't as though you'll be the only one doing this.

If you really want to go the attribute route, you might be able to make this work, but only if you use dynamically created product keys. When you specify dynamic keys, the system provides you with a bunch of information and you return the specified number of keys. You maybe be able to track down the selected attribute and use that information to decide which kind of key to generate. You could also use other hooks to expand the various key displays to report whether this was a single-user or 3-user key (see the sample extension included with uc_product_keys).

The keys would all appear to come from the same sequence, which shouldn't be a problem as long as you also include the type (1-user, 3-user).

The keys don't actually have to be dynamically generated. For instance, you could simply fetch them from a database. You would wind up duplicating a lot of the code I wrote or it might be possible to actually call the code somehow. If the keys are in a database, it's nice to have stock tracking.

Or you could make them separate products and save yourself a lot of time...

hixster’s picture

hixster commented

Freixas, many thanks for the prompt and comprehensive response. You're right - it's going to be way easier to manage these are separate products, i'd almost come to the same conclusion just when i saw your post.
Many thanks for the cool module and all your hard work.

Best regards

freixas’s picture

freixas commented

You're welcome. As for the prompt response--you got lucky and caught me on the rare day that I had time to respond :-)

When I wrote this, I considered associating keys with SKU's, which would have given you the capabilities you wanted. I decided against it for reasons now lost in the mists of time, but which I suspect involved a lot of added complexity. From a customer and maintenance (avoiding maintaining duplicate descriptions) it seems like a nice feature to add and maybe some inspired person will donate a patch.

I'll leave the request active for that reason. I don't have it on my roadmap; right now, I have to find time for Ubercart 3 and Drupal 7,

freixas’s picture

freixas commented
Status: Active » Closed (won't fix)

Closed due to no activity in over 2 weeks.