Aaaa... So I just rewrote uc_license_keys a week or so ago...

Sorry, but I never received your posting. I have no idea why. I have another module, uc_addresses, and I seem to get all the messages posted there. I also checked all my email (I don't delete much) and couldn't find your postings.

Regarding your random thoughts:

• Using views sounds like a good idea. I thought about it, but just don't have a great deal of experience with integrating with views. Interested in collaborating on adding views support?
• I'd need to know more.
• The schema so non-programmers can have a working system, Sub-modules could solve the problem, but none exist (yet). It might be possible to refactor the code later to separate functionality. uid is included in the order, but sometimes you'd rather avoid the extra join or database fetch. I think I might have started out without it and then added it to avoid some database operations. Finally, I'm embarrassed to tell you how long my product keys are. My theory is that the database index is going to be a lot smaller if it is based on an integer than the a lengthy product key—and it may operate faster. This is also the reason that I avoided creating a unique index for product keys—it could affect performance. I am not a database guru, though, so I might be wrong.
• Thanks.
• I'm not a uc_license_keys user, but if anyone would like to provide the code for an upgrade path, they would be welcome,
• First, uc_product_keys associates a key with a product in the same way that uc_license_keys associates a key with an SKU. Any of the keys work with the given product. Why not use the SKU? I wanted to allow two products to use keys from the same pool (for example, several betas might use the same beta product key). There are two ways to do this: In the product sequences, I could create a bunch of fields to create associations to products or in each product I could provide an association with one sequence. I prefered the latter. Because products may have variant SKUs in a variety of places, it was simpler to associate the product with a sequence than an SKU with a sequence. Product sequences provide a place to store certain characteristics of a sequence, such as whether it is dynamically generated or imported.

Regarding the multiplicity of Drupal modules dealing with licensing: uc_license_keys is not an official Drupal module, so when I created uc_product_keys, there was no duplication.

It may be possible to rework the code to use the Licensing module. I don't know much about it yet and the author has never contacted me (as far as I know—the email system may be flaky). The description seems to claim it does not duplicate uc_product_keys.

Sorry for the later reply and thanks for your input.

ok, i found the menu to find in readme.txt.

Also, the error seems to be gone once I configured a product key.

I want to use the hook (dynamic gen key) method. But I have no idea where to start in creating my own script. Can you please help?

Would it be possible to do something like this :
1) customer buy product
2) select the item (let say this is new license)
3) then register account and make payment
4) payment approved by payment gateway
-- how does uc_product_keys handle this if payment failed?
5) hook_uc_product_keys_generate_keys() will execute which will actually call an external php script
6) the script will retrieve the key dynamically from license distributor's website
7) the script will return results back to hook_uc_product_keys_generate_keys()
8) the script will also send out email to user and administrator (with complete details of customer's purchases)
-- does uc_product_keys handle this?

Please email replies to my email account if possible. abubin at gmail.com

Thanks.

Sorry for the late response. I am still not getting any notifications when bugs are posted.

1) Please don't attach bug reports to existing, unrelated issues.

2) Did you see the release notes? "A sample extension module is included that should help you extend the module."

3) Product keys are generated only when the order successfully completes (using Ubercart's hook for order completion). There are a bazillion payment systems; you will need to verify that, for your payment system, the Ubercart order completion hook is only called if the payment is made.

4) The sample extension module demonstrates how to do everything you asked for. It's all possible. If you need hand-holding, however, I would be happy to help at my usual rate. :-)

Changing the title back to what this issue originally was for.

It makes it hard to keep track of things if issues get hijacked.

As freixas mentioned before you should create a new issue if you
have an issue that is different to the original post.

Then that will also help other people that have your problem to find
an issue with a possible solution.