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.

Chip Bennett

This Plugin remains compatible with the latest version of WordPress, but I am no longer keeping up with any MBP Plugins.
MaxBlogPress plugins require a two-step registration/activation process, as well as a forced opt-in to an email-list subscription, in order to use them. This plugin circumvents those requirements, enabling unrestricted use of the plugins.
Note: this plugin does not install any other plugins. If you wish to use any MaxBlogPress plugins supported by cbnet MBP Auto-Activate, you must install them separately.
Note 2: This Plugin is not an endorsement for MaxBlogPress Plugins, but rather a proof-of-concept to demonstrate why it is futile to force users to jump through Plugin-registration and email-list-subscription hoops just to use Plugin functionality. It appears that some or all of MaxBlogPress Plugins are now released under a non-GPL-compatible license that restricts code modification. Use them at your own risk.
This plugin currently supports the following MaxBlogPress plugins:
<ul>
<li>Different Posts Per Page</li>
<li>DealDotCom Widget</li>
<li>Unblockable Popup</li>
<li>Ping Optimizer</li>
<li>Stripe Ad</li>
<li>Psychic Search</li>
<li>Favicon</li>
<li>SEO Post Link</li>
<li>Banner Ads</li>
<li>Duplicate Post Checker</li>
<li>Multi Author Comment Notification</li>
<li>Optin Form Adder</li>
</ul>
This plugin now also supports the following MaxBlogPress Revived plugins:
<ul>
<li>Front Page By Category</li>
<li>AdSense Deluxe Revived</li>
<li>Flash Fader Revived</li>
<li>Links Manage Widget</li>
<li>Banner Ads</li>
<li>Ajax Post Listing</li>
<li>Random Image</li>
<li>Access By Category</li>
<li>Captcha For Comment</li>
<li>Affiliate Image Tracker</li>
<li>Image Organizer</li>
<li>Easy Custom Fields</li>
<li>Post Ordering</li>
<li>Post Image</li>
<li>Post List By Category</li>
<li>Exerpt Listing</li>
</ul>

cbnet MBP Auto-Activate

Automatically activate MaxBlogPress plugins, without registering and without subscribing to the MaxBlogPress email list.

Plugin Register vs cbnet MBP Auto-Activate