WordPress / WordPress/plugin-check

Include specific checks for plugins that declare Multisite compatibility

Open
#1,010 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

[Team] Plugins
Dominant language
PHP
Stars
362
Forks
126
Avg merge
1d 23h
Merged PRs (30d)
22

Description

The Problem

As a WordPress Multisite administrator, I frequently encounter plugins that claim Multisite compatibility, but fail to work correctly or introduce issues when activated on a Multisite network.

I understand the Plugin Check Plugin (PCP), at this stage, does not have any specific checks to validate a plugin's claim of Multisite compatibility.

The main issues are:

  • Wasting time installing, testing, and debugging plugins that are advertised as compatible but are clearly not.
  • Users becoming wary of these claims, even when a plugin might genuinely be compatible.
  • Developers not realizing their plugin has Multisite issues until users report them.

Possible Solution

I suggest enhancing the Plugin Check Plugin (PCP), gradually over time, to include specific checks for plugins that declare Multisite compatibility.

I understand that comprehensive functional testing of all Multisite scenarios is incredibly complex. However, integrating some static analysis checks for common Multisite development patterns and potential pitfalls within PCP would be a significant step forward. This would help flag common issues improving the overall quality of plugins available to the large Multisite community.

Currently, the alternative is manual testing by Multisite users, which is time-consuming, prone to error, and reactive rather than proactive.

Developers also tend to rely on user bug reports to highlight problems, which is cumbersome & often ineffective. Adding Multisite compatibility to PCP should help encourage developers to test their plugins appropriately for WordPress Multisite.

Thank you for considering this enhancement.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name files, tests, or an entry point. Start by reviewing the Plugin Check Plugin's existing static checks and how plugins declare Multisite compatibility, then identify a narrowly scoped common pattern to validate. Done should include an agreed check, coverage for its expected behavior, and documentation of the finding.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
devtools, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.