Port to Drupal 8

This module can be ported at any time. License content entity type + License type plugin type (use the PluginBundle API that ships with Commerce 2.x and is used by payment methods as an example).

What do you think of splitting the "license" functionality (reference to a user and another licensed entity) into a separate module? commerce_license could then act as a connector between license and commerce, but developers could use license in conjunction with different ecommerce solutions or perhaps with no ecommerce solution.

I think there's not enough functionality there to get any benefits from such a split.
D8 entity types are cheap enough that enough can just write their own licence entity type with different (non-Commerce) semantics.

The following features could be split into a non-commerce-specific module:

• The license entity type
• User reference
• Expiry date and time
• Expires automatically
• Licensed entity
• Status
• Default views
• Licenses by status
• Licenses referencing a particular entity
• Licenses belonging to a particular user
• Cron processing to update status of expired licenses
• Node access control via licenses

I've started work on this separate module because I am certain that I want these features, but I am not yet certain what commerce solution I will use. I could use inline entity forms to bake this directly into a commerce checkout process, or I could simply implement endpoints that grant or revoke licenses via webhooks from a third party service.

Initial work is here: https://github.com/grasmash/drupal-license. When I've implemented all listed features, I will move it to d.o. For now, I've simply defined the entity type.

I've moved my work-in-progress to the Licensing module:
https://www.drupal.org/project/licensing

I'd like to build the D8 version in such a way that it can be easily integrated with Commerce. Please let me know what I can do to that effect. I think it's in our best interest to promote collaboration over competition and focus on one module to provide licensing functionality.

Is this something being actively worked on still @grasmash?

Hey anne, not terribly sure what the plan is. I have done a bit of work on two modules that fulfill this functionality. The first being https://github.com/cmcintosh/commerce_license which focuses just on the Digital product rights aspect of things (ie access / roles). In addition to that module I have another module where I am specifically handling the subscription aspect of things, https://github.com/cmcintosh/commerce_subs

The version of license i built automatically handles things when orders are complete meaning, the users are not awarded the Role / digital good until the transaction is marked complete. Ping me on skype if you want to chat more about what i got I could use more hands to make it more stable.

@cmcintosh The version of commerce_license you have provided works fairly well albeit a few bugs. Can we possibly get a accessible dev branch started and I would be happy to provide some contributions as well. I believe this pretty much takes care of 95% of the use cases.

The module was tested on a copy of a high volume live Drupal 8 Commerce site which we forked to a dev branch to test this module. The site relies heavily on roles for limited period access to software applications hosted internally within the framework.

Sounds like a good plan, it has been a while since working on D.O repos, I think we will need to get bojanz to open up the branch and then I can create a patch against that with what I have on the Github repo.

Also, feel free to post issues over there that you found. It is still a very rough workup on License so I am sure there are lots to be done as of yet. Also if your looking for time based products I also have another repo for this called https://github.com/cmcintosh/commerce_subs which handles awarding licenses on a recurring nature. It too is still rough and i am actively working on it this / next week.

Idea is to have things like conditions for allowing users to be able to purchase the subscriptions, etc.

So am I correct in understanding that the subs module is essentially the license module with conditional checking on recurring purchases? In most use cases the product itself is redundant if a role is established or visa versa.

If bojanz will open a branch relatively soon it may be more efficient to propose a patch subsequently to your initial as the bugs are mostly minor in nature and occur in specific use cases. Would be easier to track them all initially and start fresh with development moving forward. I will likely be up for significant time on progressing this as it is a necessity to our project.

I believe for recurring billing in D7 for commerce license is
https://www.drupal.org/project/commerce_license_billing

How commerce_sub is different form this one ?

They pretty much fill the same roll, the big difference being that not only is it for Digital goods ie licenses, additionally it can be used for physical (standard) commerce products. In addition to that I am utilizing the Field plugin system in Drupal 8 to allow for extending the functionality.

Commerce sub will allow you to use the UI to create a subscription plan by selecting Products / Licenses. Setting conditions on who can purchase the subscription(atm in development), and will generate unique invoices for each billing cycle. Additionally I have some controls for manually re-subbing the customers when needed.

Because the subscription is setup to create multiple order invoices, you could also refund specific invoices or a series of invoices.

Sounds Good. Thumbs up :D

I've looked at https://github.com/cmcintosh/commerce_license but it appears to be a copy of the commerce_product module, and it doesn't use entity_bundle_plugin for license types. So I fear that we won't be able to use much of that code.

I did take a lot from the commerce_product module. Im using the Drupal Plugin api for extending the type of things to be able to license. It would be good to chat a bit more later on, and maybe share some links to exactly the structure we are looking towards. This first draft i did was mostly because it was something I needed for a project so I am open for suggestions / direction on things.

Ill read through, https://bojanz.wordpress.com/2013/07/19/entity-bundle-plugin/ a bit more and refactor things around that.

Mixed up the comment & summary fields, ignore this comment.

Transferring notes from a conversation I had with Kazanir.
This architecture matches the D7 one, and might evolve in time.

The best example for bundle plugins in D8 is payment method types in the commerce_payment module.

We're making an official port of this based on long experience using it in production and designing around various use cases. I'll open another meta thread for tracking various sub-issues and also gathering feedback. In addition to our plans for unified recurring module (bringing together Commerce License Billing and Commerce Recurring) we feel like this module still has a place and shouldn't be generalized in the way that was discussed upthread.

The basic module scaffolding, which does not yet even work, is in the 8.x-2.x branch. New issues forthcoming.

Ok sounds good, so then i guess ill leave you to it then. Seems like my help is not wanted here.

@Kazanir were you able to create the meta with sub-issues? I'm struggling to find it - thanks!

Any status on a working recurring/subscription system on D8? Is there another thread with more updated info?
+1 sub

@plato1123 bojanz and mglaman mentioned in slack that work is underway, but I don't think a meta-thread exists yet.