Chris Taylor

If you are a WordPress plugin developer the chances are your plugins are available for download from the WordPress plugin repository. As part of that service the nice guys at WordPress show you how many downloads of your plugin you get per day. Very useful, and if you’re like me you check your downloads numbers very often.
However what these stats don’t show you is where your plugin is in use – which sites it is actually being activated on. Seeing that information would allow you to see exactly which sites are using your plugin, when they installed it, and what version the site is running. That is exactly what Plugin Register does.
By including the Plugin_Register class and calling it with some simple code in your plugin, your plugin will prompt the user to register your plugin when they activate it. When they register the plugin, the Plugin Register database on your site will be updated with the name and version of your plugin, and the site name and URL where that plugin has just been activated. A simple call is made to your website to save these details in the Plugin Register table, and you get some great statistics on which site is installing what versions of your plugins.
So, what do you need to put in your plugin? This example code hows you everything you need:
`// include the Plugin_Register class 
require_once( “plugin-register.class.php” );
// create a new instance of the Plugin_Register class 
$register = new Plugin_Register(); // leave this as it is 
$register->file = FILE; // leave this as it is 
$register->slug = “pluginregister”; // create a unique slug for your plugin (normally the plugin name in lowercase, with no spaces or special characters works fine) 
$register->name = “Plugin Register”; // the full name of your plugin (this will be displayed in your statistics) 
$register->version = “1.0”; // the version of your plugin (this will be displayed in your statistics) 
$register->developer = “Chris Taylor”; // your name 
$register->homepage = “http://www.stillbreathing.co.uk”; // your WordPress website where Plugin Register is installed (no trailing slash) 
$register->Plugin_Register(); // set Plugin Register to be called when the plugin is activated
The reports you get include:
<ul>
<li>Graphs showing how many registrations have been made for the last 24 hours, 14 days, 12 weeks and 12 months</li>
<li>A list of all plugins registered, with how many unique versions and unique sites</li>
<li>A list of all versions of a particular plugin, with the number of unique sites</li>
<li>A list of all sites which have registered any of your plugins</li>
<li>Details of what plugins were registered on a particular day</li>
<li>A search, so you can see what sites have got version X of plugin Foo_Bar installed</li>
</ul>
<h3>Privacy</h3>
Registering a plugin is completely up to the user who has just activated it. Plugin Register does NOT automatically send any data back to your website without the user manually clicking a link. Some text is displayed which invites the user to register the plugin, by default it says:
“Please consider registering your use of [your plugin name] to tell [your name] (the plugin maker) you are using it. This sends only your site name and URL to [your name] so they know where their plugin is being used. No other data is sent.”
It is possible to override this default text on a per-plugin basis.

Plugin Register

For Wordpress plugin developers: keep a register of when and where your plugins are activated.

labs64

Easily control the use and monetize your WordPress plugins and themes using PluginPass – a WordPress License Manager backed by <a href="https://netlicensing.io" title="Software License Management" rel="nofollow ugc">Labs64 NetLicensing</a>.
The Plugin is designed to be easy-to-use, which you easily define as a dependency to your plugin or theme, so this takes care of the plugin’s & theme’s features activation and validation.
<h4>Features</h4>
<ul>
<li>Enable the subscription model for the plugin/theme</li>
<li>Sell PRO versions of your plugin/theme</li>
<li>Offer trial/evaluation version on the PRO features (with the fallback to the lite version)</li>
<li>Enable up-selling by offering additional plugin/theme features</li>
<li>Use plugin or theme on the given domain only</li>
<li>License as many plugins/themes as you want</li>
<li>Need more features? – <a href="https://github.com/Labs64/PluginPass/issues" rel="nofollow ugc">Let us know</a></li>
</ul>
<h4>Payment Gateways</h4>
Payment Gateways supported in the plugin:
<ul>
<li>PayPal</li>
<li>Stripe</li>
<li>MyCommerce</li>
<li>FastSpring</li>
<li>Braintree – PLANNED</li>
<li>Authorize.net – PLANNED</li>
<li>2Checkout – PLANNED</li>
<li>SOFORT Banking – PLANNED</li>
</ul>
<h4>Quickstart</h4>
Add this code-snippet to your plugin:
<pre><code>$quard = new \PluginPass\Inc\Common\PluginPass_Guard( $api_key, $product_number, $plugin_folder );
if ($quard->validate( $product_module_number )) {
 // do something
 $quard->open_shop();
}
</code></pre>
Detailed integration instructions, NetLicensing products configuration tips and troubleshooting can be found on plugin’s <a href="https://github.com/Labs64/PluginPass/wiki" rel="nofollow ugc">Wiki page</a>.
<h3>Privacy Policy & GDPR</h3>
This plugin integrating components of an external service – <a href="https://netlicensing.io" title="Software License Management" rel="nofollow ugc">Labs64 NetLicensing</a> (processor). Labs64 NetLicensing is an online license management service provider. License validation requests are processed using plugin or theme developer (controller) NetLicensing account.
By using this plugin validation requests will be sent to the Labs64 NetLicensing in order to verify valid use of the plugin or theme. Personal data may be transferred with these requests such as Unique Identifiers, Plugin and Theme Details, WordPress Instance Name, Domain Name, System Details of the data subject.
The European operating company of Labs64 NetLicensing is: 
Labs64 GmbH 
Radlkoferstr. 2 
81373 Munich, Germany 
Labs64 NetLicensing website: <a href="https://netlicensing.io" rel="nofollow ugc">NetLicensing.IO</a>
The applicable data protection provisions of Labs64 NetLicensing may be retrieved under Labs64 <a href="https://www.labs64.com/legal/privacy-policy/" rel="nofollow ugc">Privacy Policy</a>.
We strongly encourage you to comply with WordPress <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/" rel="nofollow ugc">Plugin Guidelines</a> and General Data Protection Regulation (GDPR) while developing your plugins and themes and interfacing with <a href="https://netlicensing.io" rel="nofollow ugc">Labs64 NetLicensing Services</a>.
For more details on Labs64 NetLicensing data protection provisions visit Labs64 <a href="https://www.labs64.de/confluence/x/vQEKAQ" rel="nofollow ugc">Privacy Center</a>.
<h4>Controller’s Responsibilities</h4>
The controller is the principal party for data collection responsibilities. These responsibilities include collecting individual’s consent, storing of the data, managing consent-revoking, enabling the right to access, etc.
If an individual revokes consent, the controller will be responsible for initiating this request. Therefore, on receipt of this request, it will be responsible to remove the revoked data through NetLicensing vendor account.

PluginPass – WordPress PRO Plugin/Theme Licensing (Public Alpha)

Very useful plugin helping WordPress plugin developers to monerize their works.

Very useful plugin

I was able to enable license management for my plugin with almost no effort. Time spent (all in): 30 min !! Great & Thank you!

Easy and painless integration

PluginPass is a WordPress license manager that makes it easy to monetize your WordPress plugins and themes.

Plugin Register vs PluginPass – WordPress PRO Plugin/Theme Licensing (Public Alpha)