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.

AVATTAVA

Debug Activation Errors 2.0 shows you the issues during plugins activation on WordPress plugins page: plugins.php
A developers’ plugin that allows to debug the ambiguous error message: “The plugin generated ### characters of unexpected output during activation”.
If you notice messages like “headers already sent”, problems with syndication feeds or other issues, activate Debug Activation Errors 2.0 and deactivate any suspicious plugin.
Then, activate the possible culprit again and you will see if there are any issues during its activation. You can repeat this operation as many times as you want…
Whenever you have solved the issues and to stop seeing any messages, you can deactivate our plugin, Debug Activation Errors 2.0
This plugin is not designed to operate on a Multisite install (Network Mode) and we do not guarantee any results in those conditions.
@@@@@ READ CAREFULLY @@@@@
Alongside with the use of Debug Activation Errors 2.0, you should update the file wp-config.php with the below snippet of code:
/** 
 * For developers: WordPress debugging mode. 
 * 
 * Find the line of code >> define( ‘WP_DEBUG’, false ); << and replace it with the 3 lines of code below. 
 * You must set WP_DEBUG to “true” to enable the display of notices during development. 
 * WP_DEBUG_DISPLAY should always be “false”, unless you have a very strong reason to change its value to “true”. 
 * You should have a debug.log file in WordPress, if not, you must create it and set WP_DEBUG_LOG to “true”. 
 * It is strongly recommended that plugin and theme developers use WP_DEBUG in their development environments, with caution. 
 */ 
define( ‘WP_DEBUG’, true ); 
define( ‘WP_DEBUG_DISPLAY’, false ); 
define( ‘WP_DEBUG_LOG’, true );
<h3>Support</h3>
Please, use the WordPress.org forums for community support at https://wordpress.org/support/plugin/debug-activation-errors and if you spot a bug or if you have a suggestion to improve the code functionality, you can contact us at contact@avattava.xyz

Debug Activation Errors 2.0

Debugs errors and shows you the issues during WP plugins activation.

Plugin Register vs Debug Activation Errors 2.0