gdarko / digital-license-manager Goto Github PK
View Code? Open in Web Editor NEWExtendable License Manager for WordPress and WooCommerce π
License: GNU General Public License v3.0
Extendable License Manager for WordPress and WooCommerce π
License: GNU General Public License v3.0
License key delivery is broken in the latest version. Downgrading to version 1.4.3 fixes it
Hi i think it would be a good feature to add the variable product support
Like you would be able to sell license with different options using only a single product
For example if you have different options of a single type of product
Once you leave it blank you get an error:
"Expires In shoudld be positive integer value larger than 1 that represents number of days"
Hi there, just checking out your plugin. I see it says 'Compatible with WooCommerce for selling licenses but also works without it.' but there seems to be no information as to how to use it without WooCommerce. Is that with the Pro Version and your software manager? Or is that with any cpt, or via the rest api. Any specific place to start digging? Thanks
Hey, I wanted to thank you for this great tool! I however ran across something which im unsure of.
I have a generator for a trial version which has a 14 day expiry period which is attached to an item on woocommerce to automatically generate licenses. However, when these licenses are generated they are set to expire at "Never".
From what I can tell this isnt something explicit to the pro version and is perhaps a bug? This is on version 1.6.1.
After payment succeeds, the order is stuck in the processing, and needs to be manually make it completed.
Add new parameters to the API list endpoint to filter license keys by order_id, product_id, user_id, status, etc
From Imber Development:
It would be amazing to have product_id, user_id, and order_id parameters in the /wp-json/dlm/v1/licenses endpoint. This would make finding a license key by product id or user id a lot easier than going through all keys and manually sorting them.
AbstractResourceRepository::delete()
calls $wpdb->prepare()
with an already prepared query, via AbstractResourceRepository::sqlINValues()
and no placeholders. This causes wpdb::prepare()
to log a "doing it wrong" warning.
I can think of two different solutions to fix this issue.
$sqlQuery = $wpdb->prepare( "DELETE FROM {$this->table} WHERE {$this->primaryKey} IN (" . $ids . ")" );
$sqlQuery = "DELETE FROM {$this->table} WHERE {$this->primaryKey} IN ($ids)";
$ids = implode( ',', array_map( array( $this, 'sqlINValues' ), $ids ) );
$sqlQuery = $wpdb->prepare( "DELETE FROM {$this->table} WHERE {$this->primaryKey} IN (" . $ids . ")" );
$sqlQuery = $wpdb->prepare(
"DELETE FROM {$this->table} WHERE {$this->primaryKey} IN ($placeholders)",
$ids
);
If this were not a WordPress plugin, I would choose solution 1, but since WordPress strongly encourages using core APIs, solution 2 is recommended.
@gdarko, let me know if you want me to submit a pull request to fix this issue.
The expiration date/time is displayed inconsistently, which can be confusing.
When wp_dlm_licenses.expires_at
= '2023-08-15 04:00:00.0' and
get_option( 'gmt_offset' )
= '-5.0'get_option( 'date_format' )
= 'F j, Y'get_option( 'time_format' )
= 'g:i a'These pages display:
Page | Display |
---|---|
License Manager -> Licenses | August 14, 2022 |
License Manager -> Licenses -> Edit license | 2022-08-15 |
My account -> Orders -> View | August 15, 2023 |
My account -> Licenses | August 14, 2023 |
My account -> Licenses -> View | August 14, 2023 |
"$date, $time $timezone"
.'date_format'
option.'time_format'
option.'timezone_format'
option:
' T'
and run it through apply_filter()
, or'dlm_timezone_format'
option in the "License Manager -> Settings -> General" page with a link to the WordPress documentation on date and time formatting.An alternative solution is to add a 'dlm_expiration_format'
option to the "License Manager -> Settings -> General" page with a link to the WordPress documentation on date and time formatting and let users set the entire format.
An extra nice feature would be to allow the user to specify the current WordPress date and time formats using merge codes like {{DATE_FORMAT}}, {{TIME_FORMAT}} T
.
If this sounds good, I would be happy to submit a pull request with either solution.
Hello,
is there anyway to make the expiry starts once the user activating the license instead of on purchase
Thanks
Hi,
This is a feature request to start showing license keys in order meta data for easy access trough WooCommerce rest API.
The endpoint does not work if you add your consumer key and secret as parameters.
Caused by that line of code as it tries to use the parameters for the query.
Also, it responds with no results for your query if you try to use parameters per_page and page, only parameters like order_id work.
Documentation for HTTP basic auth is incorrect
Header name: Authentication -> Authorization
Header value: Bearer -> Basic
Just an idea for your License manager.
Could a form be placed on a page via shortcode to see if a license is valid or not, that anyone can check. Better still, have a button in the user account area, so the owner can report a license as stolen, or select from a list of configurable status's created in admin.
Redirect to a new page after licence valid status showing some of the owners details from meta. Or, if reported as stolen, redirect to another page to report it.
Just a couple of possible additions to your plugin which would be really useful to our needs,
Thanks
Dave
Apparently WooCommerce supports paginate
parameter in WC_Product_Query
/ wc_get_products
that i didn't noticed earlier.
Hello iam getting this error in my account
Warning: Undefined array key "classes" in /wp-content/plugins/digital-license-manager/templates/woocommerce/dlm/my-account/licenses/partials/table-activations-row-actions.php on line 38
Warning: Undefined array key "disabled" in /wp-content/plugins/digital-license-manager/templates/woocommerce/dlm/my-account/licenses/partials/table-activations-row-actions.php on line 58
Hi , i installed and tried the plugin but when i tried it , it does not deliver the license one the automatic mode and i have to use the status mode to deliver the license
Hello,
Iβve encountered an issue while utilizing your pluginβs REST API endpoints, specifically when interacting with the β/licenses/{license_key}β endpoints. It appears that when the {license_key} contains certain special characters such as β@β, β/β, or others, it disrupts the API request flow, leading to an unexpected error:
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
Steps to Reproduce:
Use a {license_key} containing special characters like β@β, β/β, etc.
Make a request to any of the βlicenses/{license_key}β endpoints via the REST API.
Expected Behavior:
The API should be able to process requests with {license_key} values containing special characters without encountering routing or handling issues.
Additional Notes:
I attempted to address this by using encodeURIComponent() to encode the special characters within the {license_key} before making the request. However, the issue persisted.
The list endpoint just returns the following error:
{
"code": "data_error",
"message": "No licence keys found for your query.",
"data": {
"code": 404
}
}
The API keys are correct and there are license keys.
Hi, first of all thank you for this great product. I'm using it successfully, but it would be wonderful if it could show the variation details of licenses after a checkout.
For example I have "My cool product" with two different variations. If I order two variations it's indistinguishable which license key is associated to which variation.
In 2023 almost everything that jQuery does can be done with Javascript. This issue will keep track of the progress of removing jQuery form the plugin completely.
Unfortunately the new developer of License Manager for WooCommerce plugin decided to illegally steal our code and incorporate it into their plugin License Manager for WooCommerce. There are two attempts so far by the team behind License Manager for WooCommerce to publish a new version with our code while removing copyrights and not attributing at all.
First back in August 2023 when they published 2.3-beta and now again in November with version 3.0+.
All attempts are reported and recorded. I am sorry that this happens but we aim to protect our IP rights.
Don't get me wrong, we have no issues with proper forking. But our indications tell something different, apparently they started to see the traction and the impact of our plugin and want to suppress it by stealing our code.
Initially we forked License Manager for WooCommerce because Drazen Bebic, the original author abandoned it before he sold the plugin to the current team behind. I am sure you remember that there were no updates for around a year before he let it go.
To give some more context. I used License Manager for WooCommerce and contributed to the project with code, i am one of the early adopters of License Manager for WooCommerce.
Most likely nothing valuable. The plugin is still abandoned even after the takeover by the new team. If you see the big picture, there are no features so far, the only added "feature" is the malicious Freemius addon. No HPOS support yet, PHP warnings remain, all the old problems remain like stock synchronization, etc. Now in 3.0+ as gratis to their beloved users they introduced a lot more issues by incorrectly stealing our code.
Only "compatibility checks" with WooCommerce and WordPress that increments its version. Oh and they reorganized the menu.
In meanwhile, we rewrote our Digital License Manager plugin from scratch. There is not a lot left from the old License Manager for WooCommerce. The code we choose to keep properly attributes and restores copyright to the original owner (See example).
We updated the database structure, made Activations in separate table, added HPOS support, rewrote and separated the business logic, rewrote the Rest API, introduced Gutenberg blocks, created PDF Certificates feature, Ditched jQuery, developed migration tools that allows you to migrate from LMFWC and a lot more cool stuff.
Also we created WooCommerce Subscriptions support in the Pro version. Many new features are in the pipeline, like Reports.
Because, it probably makes sense to steal our code in the most illegal way possible. Our code is nice and clean, well tested with unit tests. We have a lot more features and much better database organization. They have no clear path about future development. The only goal is to milk more money from their plugin with 6k+ active installs obtained on old glory.
In this case, it really makes sense to pass it unnoticed on WP.org plugin repository, but here they failed.
Besides that, they are also targeting our WooCommerce Subscriptions support feature in their premium version as well because once you have large chunks of the free version of Digital License Manager, you can easily adopt that feature.
If you are interested to migrate your data to Digital License Manager, read more here:
Migrate from License Manager for WooCommerce
I will keep this thread updated
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.