Testing patch #6 failed on my fresh Drupal 10.2.7 installation, due to encrypting twice and only decrypting once.
Commenting out the second two encryption lines in the function (password_field_encrypt_decrypt()) fixes it.
This patch #7 includes all the previous patch changes, but with those two lines commented out.
I do not know the issues regarding backwards compatibility, so this patch needs review.
For those not facing those issues, this patch might work for you.
Thank you everybody for your contributions.
We need to establish if this is a connectivity error or not at your end. I suspect the latter.
If you don't follow through with the instructions, and feed back with the results, I can't help.
What was your result? Especially on that last bullet point.
I need your error messages.
You must feed back with as much resulting and helpful information as you can, or I can't diagnose your problem. It only seems to be happening to you.
Hi there. Thank you for your feedback.
Are you using drush or composer? It is recommended to use composer.
It's odd that all your other modules are updating, and only this one is having trouble.
I think this may be a legacy feature used by drush, and I am not well familiar with it.
So if anybody else has experience or suggestions, please chime in with a comment.
I searched the Internet for ideas, and this is what I found
(it seems your connectivity is ok, but I kept these suggestions in the list anyway):
According to release updates.drupal.org, the module has release candidates for Drupal 10.x as per:
https://updates.drupal.org/release-history/commerce_license_content/current?site_key=BdxzqkewtPwHqDZVM_j282uQpl8asJkhovTvMtveld0&version=1.0.0-beta2&list=commerce_license_content%2Ccommerce_license_publish_content
So try the following suggestions:
- Make sure your IP is not blocked by going to https://updates.drupal.org/
- Make sure your Drush recognise your Drupal root as 10.x (check drush status) and whether Drush can access the above endpoint by:
- drush ev 'echo file_get_contents("https://updates.drupal.org/release-history/commerce_license_content/curr...")'
There could be a case that you are behind the firewall or corporate proxy, therefore the certificate could be not valid, so you'll have to configure your PHP's curl library either by importing the right certificate and mark it as trusted, ignoring it (not recommended) or use the non-secured connection to check for the new releases.
Please let us know if you are using composer or not, and how you get on. Thanks.
Code updated and released for Drupal 10.
I have not been able to reproduce the problem as you describe.
The option to buy a license is there in my testing.
Note: As per the documentation. The option to renew is dependent upon the "Allow renewal window" settings, defined on the product variation type.
See: /admin/commerce/config/product-variation-types
The option to renew the license will only appear within the time window set.
Please try again and see if this is your issue.
Bug fix merged with 1.0.x branch.
Cheers! I'm glad you like this module.
Thank you for testing, and feeding back.
You have discovered a bug!
See attached patch for fix.
I am unable to git commit at the moment due to technical difficulties. Patch will be merged at a later date.
** This module is now obsolete. **
Upgrade to the new feature complete version here:
Commerce License Content →
** This module is now obsolete. **
Upgrade to the new feature complete version here:
Commerce License Content →
Patch #332 confirmed working with:
Drupal 7.56, Mysql, (OG) Organic groups 7.x-2.9
Thank you all for your fine work.