Tell me more ×
WordPress Answers is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

I'm new to the WP arena and considering doing some plugin development. In releasing a WordPress plugin, how do you keep from the plugins getting distributed to those who haven't genuinely purchased the plugin?

I guess I'm not entirely clear how plugins like Software Licensing for Easy Digital Downloads keep users from copying the plugin after it's installed and distributing it to other users.

Clarification would be nice.

Thanks.

share|improve this question

3 Answers

up vote 7 down vote

In a nutshell - you can't. PHP code is by nature plain non-compiled text and if someone really wants to copy it they shall.

On top of that licensing considerations often strip whatever small things you can try. If you choose to or have to release under GPL you cannot forbid redistribution or put in technical means for that either.

One practical solution is too restrict access to updates. This doesn't solve redistribution, but this does make sure only paid users are getting latest versions immediately and efficiently. This model is successfully used for some high profile WordPress extensions, for example BackupBuddy

share|improve this answer
The example of restricting updates is exactly what EDD Software Licensing is for. It does allow you to restrict usage of the plugin as well if you want, but the default implementation is for updates. – Pippin Jun 19 at 1:45
up vote 3 down vote

If you've purchased any premium plugins in the past, you'll usually find they require some form of API key to operate. This key would be uniquely generated and assigned to a customer on or after purchase.

The software would require authentication to your API server after it is activated in WordPress install, before the plugin's features would work.

The API server could ensure that no more than X of the same key are being used, as well.

share|improve this answer
1  
But I'd bet this is not hard to disable-- dishonest, but not hard. – s_ha_dum Jun 6 at 18:18
1  
Absolutely, which is why @Rarst's answer is totally valid. Anything that can be built can be unbuilt. So one would have to ask if it's worth it, or if they just want to go Open Source and free themselves, earning karma (cough cough, résumé fodder) instead of money for their efforts. – GhostToast Jun 6 at 18:21
up vote 0 down vote

Why is editing code on an open source plugin, using open source language dishonest???

Isn't the whole point and intent of wordpress OPENSOURCE, this was challenged in court and thrown out because that is the intent of wordpress.

You can't have it both ways. If you want secure code, don't put it in a wordpress plugin and expect to tap into that market and then claim "you can't touch my (open source) code.

share|improve this answer
while I agree with you that it is the intent of the WordPress developers that plugins be licensed under GPL, it is at this point simply their opinion, and it's worth pointing out that plenty of legal professionals do not agree with that opinion. there is no legal precedent which establishes that a WordPress plugin must be licensed under GPL as a derivative work. the "challenged in court" bit you mention never actually happened, there was only threat of lawsuit. – Milo Jun 21 at 5:07
So you are saying Thesis never challenged and lost this? It never went to court, Thesis voluntarily changed their license to GPLv2. – Milo yesterday

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.