Plugin and Theme Policy

Users can ask for plugins, and pay for the pleasure, but we set a pretty high bar.

Here’s a checklist of the sorts of tests we perform for evaluating whether to add or remove a plugin or theme in our WordPress multisite network:

  1. Compatibility with Multisite: We need to ensure that the plugin explicitly states compatibility with WordPress multisite installations.
  2. Active Maintenance: We need to check if the plugin is actively maintained by looking at its update frequency. Regular updates indicate that the developers are actively addressing issues, maintaining and improving compatibility.
  3. Recent Updates: We will need to verify when the plugin was last updated. A recent update is a good sign that the plugin is actively supported and compatible with the latest WordPress versions.
  4. WordPress Version Compatibility: Confirm that the plugin is compatible with the latest version of WordPress, as we’re always running on the latest and greatest.
  5. Reviews and Ratings: We will look at user reviews and ratings in the WordPress plugin repository. We pay attention to both the overall rating and recent reviews to gauge the current state of the plugin, and examine carefully the reasons for negativity.
  6. Support Forums Activity: We will check the support forums for the plugin on to see if there are recent support threads and whether issues are being addressed by the developers, and promptly.
  7. Documentation: Evaluate the availability and quality of documentation provided with the plugin.
  8. Test Environment: We will set up a test environment where we can safely evaluate the plugin’s functionality without affecting our live site.
  9. Conflicts with Existing Plugins or Themes: We weill need to research potential conflicts with other plugins or themes in you multisite network.
  10. Performance Impact: We may need to assess the performance impact of the plugin by testing it in our development environment. We have found plugins that significantly slow down our site or consume excessive resources and removed them.
  11. Security Vulnerabilities: We check for any reported security vulnerabilities associated with the plugin. Vulnerable plugins pose a risk to the security of our multisite network.
  12. Feature Set and Customization Options: Evaluate whether the plugin’s features align with our overall requirements. We consithat der e.g. whether it offers the flexibility and customization options we (or you) need for your multisite network without additional payment (many “freemium” plugins often work very well, but some are just adverts for a premium package, which is not always compatible or unreasonably bloated with features, which we cannot support and the developer would only support if we purchased the premium package).

By systematically going through these tests, we can make informed decisions about which plugins to add to our network, reducing the risk of compatibility issues and potential problems down the line.

We will consider requests more positively if they meet these criteria and we think the tool will also give a benefit to the wider community of our users. We certainly do not wish to create an burden on future users and admins, who might need significant support to unwind a complex arrangement.

You will need to be a standing order paid up plan.

If you want a plugin to be considered we require payment of an upfront £75 evaluation fee, which is non returnable.

You should also provide us with answers to as many of the questions above as well as a reasoned argument as to why you cannot do what you want to do without a plugin.