License Manager for WooCommerce

I am admittedly accustomed to a faster response time to a problem, but once we got things going they stayed on top of it until it was fixed. The plugin itself has worked great.

Excellent internal logic and an API system that works flawlessly.

Great work, thank you for everything.

It took me a while to get everything working correctly. Unfortunately, I started by watching a point and click setup video, which only confused me. That approach just doesn’t work for how my brain operates and I knew better! I should have gone straight to the developer documentation and GitHub files from the start.

Overall, this plugin does exactly what it claims to do. Once I wrapped my head around the process and properly configured my own plugin to call the API correctly, it works great.

Once I read through the Developer API documentation and got my own plugin to activate successfully, everything’s been fairly smooth!

The only issue I am having is that:

The documentation doesn’t show a true reactivation endpoint that reuses existing tokens. The /activate/ endpoint always creates new activation records. I do not like the clutter in the activation page everytime I deactivate and activate. I am trying to figure out how to activate on the same token so I don’t get all the clutter. This is not clear to me or maybe it is not a function?

• This topic was modified 4 months, 2 weeks ago by jlc1964.
• This topic was modified 4 months, 2 weeks ago by jlc1964.
• This topic was modified 4 months, 2 weeks ago by jlc1964.
• This topic was modified 4 months, 2 weeks ago by jlc1964.

I have not access to plugin after installation.

• This topic was modified 7 months, 1 week ago by Grafiman.

First of all: we have not tested this plugin with themes or plugins for WordPress. So it may well be that it works well with wordpress-stuff.

We wanted to use this plug-in to validate the licenses of our software.
The way this plug-in was programmed is really miserable. The programmer obviously didn’t want to over-implement a single line of code and decided for the most trivial of implementations.
For example: there is a value for ‘expires_at’ and a value for ‘valid for days’. But both fields exclude each other instead of the plugin is calculating the other value. So on the client side you first have to check which value comes back and then of course you have to implement two checks, one for each possible value.
The plugin obviously does not perform any calculations, but only transmits static data from the database. A well-made plugin, where the programmer also thinks about the implementation, would return a calculated value for ‘days_remining’, regardless of which value was entered in WordPress.

We purchased the pro-version but will give this plug-in up now. The example I described is just one trap you fall into when you have to query the API response yourself.

• This topic was modified 1 year, 1 month ago by lazy4.