Github repo?

@wpify what are you looking for to solve?
Have you read this thread I posted 7-ish months ago?

https://www.ads-software.com/support/topic/subscription-renewal-created-new-license-keys-each-month/

In that thread it was mentioned this issue was solved, but we’re still issuing many many license keys each (recurring) month to existing users, which is not good obviously as they’re getting an extra key each month.

You have some similar to change in mind?

@botprophet Yes, in the git repo there was a branch with almost complete subscriptions support, but the repo seems to be gone now..:/

I probably should have (maybe I have though) downloaded it when it was there ??

I’m sure he didn’t just abandoned his work, he was pretty passionate about it. I hope he’s fine and just busy, ready to make it up-to-date when he feels ready to do so.

A free plugin does not make it a priority to update though, even though I’m sure lots of people would love to pay $10-$100 for it. It has an almost perfect rating, it’s just a great plugin.

Again, let’s hope he’s well and will get back soon.

ps. I don’t know how github’s repos work, but it’s kinda strange that just disappeared.

Maybe they’re not gone, he just might like to finish them in peace ??

Feb/March 2021
“11 contributions in private repositories”

• This reply was modified 3 years, 6 months ago by botprophet.
• This reply was modified 3 years, 6 months ago by botprophet.
• This reply was modified 3 years, 6 months ago by botprophet.

March is the time when it went down. Hope he’s well and will come back here.

Hello @wpify @botprophet @vasikgreif

thank you for your messages ??

I took the repository down because I needed to split the codebase. There are some news in regards to the plugin which I will publish via Newsletter in due time, but you might as well hear from it here and now.

I have been contacted by the WooCommerce team and asked if I would like to publish a paid version of my plugin on WooCommerce.com, to which I agreed.

This does not mean that this plugin will be abandoned. It does mean that this plugin will receive only limited feature updates. The WooCommerce version will include the Subscriptions integration.

This new version is not yet completed, but is under active development. If you want to stay up to date, then please subscribe to the newsletter at https://www.licensemanager.at

Should you have any questions feel free to ask ??

Hi Drazen, thanks for the update. I’ll be happy to pay for the PRO version of the plugin, do you have any timeline on when it will be available?

Thanks
Václav

There’s still tons to do, and summer time is just around the corner. In an ideal world I would say it’s gonna be ready in July/August, but realistically it will probably not be done before September/October.

I’ve not yet decided on the price, but I’m currently thinking of $99,99 / year.

The WooCommerce.com version will feature:

• Priority Support (All questions will be answered within 48h).
• Completely overhauled plugin code.
• Custom post types for licenses and license generators instead of custom tables.
• WooCommerce Subscriptions integration.
• Overhauled REST API (all routes will be available via WooCommerce REST API).
• REST API logging (To track license activations, deactivations and such).
• License redeem confirmation.

I will implement more features if the time frame will allow it, otherwise all new features will be available in new updates.

Hi Drazen,
thanks for the details. Price is no issue, but I’m strictly against CPT for licenses. We started with your plugin specifically because it doesn’t use CPT.

The main goal here should be performance and scalability. We need to support hundreds of thousands licenses, and using CPT for this is a very bad idea and a dealbreaker for anything larger than few thousands licenses.

Thanks
Václav

@vasikgreif

WordPress uses a BIGINT(20) for the primary key in the wp_post table, which is absolutely enough for everything, including hundreds of thousands of licenses and many more.

I would just like to know what your concerns are?

Sure. There are two main issues:
– polluting the posts table
– polluting the meta table

Most of the plugins, including Woocomerce, use CPT and meta for storing the data. Lots of clients use ACF to store additional data. I worked on many sites with more than 10 million of meta rows, querying that is really slow and impossible to optimize. That’s why WooCommerce started to develop (and unfortunately not finished) switching to flat tables.

For anything data heavy, CPT and metadata is a bad structure,and I don’t see any real advantage of doing that, except of the fact that with CPT you don’t have to develop custom ui.

@vasikgreif I havent considered this to be honest. Perhaps you are correct and it would make more sense to keep the licenses in their own table.

Would love to hear more input on this.

@drazenbebic Easy Digital Downloads has been spending the last few years moving from CPT to custom tables for performance reasons as well.