Subscription license extension issue

Hi, please use the following forum for support.

https://support.tipsandtricks-hq.com/forums/forum/wp-estore-forum

Thank you.

• This reply was modified 2 years, 4 months ago by mbrsolution.

Are you saying the problem is in your eStore plug-in?

in any case it doesn’t matter, you close the ability for customers to post on that form after one year, a few years ago.

Although when I purchased the eStore there was no such limitation at purchase time, it was retroactively implemented changing the purchase agreement one sidedly. Which I wouldn’t say it was your best moment.

Regardless you’re saying it’s an eStore plug-in issue?

There maybe bit of confusion in terms of what that integration does So let me clarify a couple of things first.

These two plugins are completely two separate plugins. It was originally created to tackle two different purposes. The license manager is really for a developer to just take something opensource and use it as a base and then add to it according to their particular needs. There is simply no uniform way to deal with license key handling for all different types of platforms and projects out there. Every user will have a different setup with their project. Some customization is almost always needed.

In regards to eStore, what we have is a simple option in eStore that does the following:
https://www.tipsandtricks-hq.com/ecommerce/integrate-wp-estore-with-software-license-manager-plugin-3731

What it says on the above document is what we claim this integration does (nothing more). It just creates a key after a product is purchased.

Over time we have added a few bells and whistles to this plugin but it is still nowhere near perfect to be able to handle all kinds of licensing management type of stuff.

What you are asking now is the ability to handle subscription payments in a way that can recognize an existing license and extend it’s expiry date. That will require a new feature to be added. From the top of my head, there are some challenges there in terms of being able to identify which license key a particular payment is for. estore allows anonymous checkout (meaning there is no user login process in place which could be used to identify an account and associate license keys to). So this won’t be a trivial implementation.

`first thanks for the detailed response, I was actually thinking about it in a way simpler terms, without the anonymous check out

If a payment processor like PayPal sends a notification to eStore when a recurring payment is processed, then that information would be used to find the client in the license manager and extend the expiration date field, that’s it.

I was assuming that that’s the way it works since there is a subscription feature with an expiration date field

But you’re right, anonymous checkouts make the whole thing complicated

Does PayPal even send anything back to eStore when a recurring payment is charged? or fails?

• This reply was modified 2 years, 4 months ago by YaronE.

Did you have a chance to take a look at my last comment?

—- probably missed my question, so I’m adding it again in case you missed it

—————————– start
first thanks for the detailed response, I was actually thinking about it in a way simpler terms, without the anonymous check out

If a payment processor like PayPal sends a notification to eStore when a recurring payment is processed, then that information would be used to find the client in the license manager and extend the expiration date field, that’s it.

I was assuming that that’s the way it works since there is a subscription feature with an expiration date field

But you’re right, anonymous checkouts make the whole thing complicated

Does PayPal even send anything back to eStore when a recurring payment is charged? or fails?