Plugin Compatibility Reporter is a WordPress plugin that enables you report if the plugins that you’re using are working properly. It integrates with the compatibility reporting features of the official WordPress.org plugin directory, and lets you mark plugins as “working” or “broken” from within your WordPress dashboard.
It also tracks how long each plugin has been active on your site and automatically reports plugins that have been active for a while (1 week by default) as compatible – unless, of course, you’ve already marked them as broken. This way you won’t need to waste time on reporting that some plugins work fine.
See also: Why use this plugin?
Requires WordPress 3.4 or later.
- Go to Plugins -> Add New -> Upload and upload the plugin archive to your site.
- Activate the plugin via the “Plugins” page.
- Go to Plugins -> Compatibility Reporter and enter your WordPress.org credentials in the appropriate fields. If you don’t have a WordPress.org account yet, you can get one here.
- (Optional) Change how long a plugin needs to be active before it gets marked as working. The default is 1 week.
- The plugin will now download your existing compatibility votes. This happens in the background and can take up to 10 minutes.
- You should see “Works” and “Broken” links on your “Plugins” page. Click them to report your plugins as compatible or incompatible with your WordPress version. Your current vote (if any) will be displayed in bold.
Why Use It?
The main goal of this plugin is to make the compatibility reports that WordPress.org displays for each plugin more useful. Right now, most plugins only have a handful of votes – not enough to reliably determine if they’re compatible with this or that WordPress version.
Even plugins that have been downloaded millions of times usually have only a couple dozen of compatibility reports for the current version, at best. Why is that, and how does this plugin help the situation?
1. Reporting plugin compatibility is inconvenient.
To be able to vote, you first have to sign up for a WordPress.org account. That’s easy enough and you only need to do it once. Then, when you actually want to report a plugin as working or broken, you need to:
- Go to WordPress.org.
- Remember your username and password.
- Find the plugin you want to vote on. There might be a “Visit plugin homepage” link on the “Plugins” page, but that usually leads to the author’s site, not the WordPress.org listing.
- Find your plugin version in the drop-down list.
- Find your WordPress version in the second list.
- Click “Works” or “Broken”.
Multiply this by the number of plugins you have installed and the number of plugin and WordPress updates, and you’ll see why most people don’t bother with it. This plugin simplifies the process down to clicking a “Works” or “Broken” link on your “Plugins” page. You only have to enter your WordPress.org account details once: when setting up the plugin.
2.There’s little incentive to mark plugins as working.
Of those users who do send compatibility reports, many do it only when a plugin doesn’t work. Even if you deliberately try to avoid this and always report compatible plugins as working, it can get tiresome quickly since new plugin versions are released all the time.
One side-effect of this is that compatibility figures tend to be unfairly biased towards “broken”. For example, take Jetpack which currently has 29 “works” and 8 “broken” votes. I seriously doubt that a plugin that was made by the same folk who run WordPress.com is broken on 8/37 = 22% of sites.
Plugin Compatibility Reporter solves this by automatically marking plugins that have been active for a long time as working. This is based on the assumption that the user wouldn’t leave a plugin active if it was incompatible with their site. Of course, you can always change your vote to “broken” if it turns out that the plugin had a subtle bug that you didn’t notice at first. This plugin will not overwrite your existing reports.
- Users get a better idea of how well any given plugin works with the latest version of WordPress.
- Developers get a more accurate impression of what fraction of users are having problems with their plugin.
- Less time is wasted on reporting plugins that work properly.