Automattic / Automattic/jetpack

Beta test plugin causes false report in WordPress 5.2 Site Health Check

Open
#18,412 1 comment 0 reactions 0 assignees View on GitHub
[Plugin] Beta [Pri] Low Bug
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

Running WordPress 5.2-beta3-45198

When you visit the new Site Health section (Tools > Site Health), it gives recommendations on removing inactive plugins.

I run the Jetpack Beta Tester Plugin, alongside Jetpack it self, and I get a report that I have one inactive plugin, but when visiting the plugin list, they are all active.

Upon checking, I can see that Jetpack has the `jetpack` slug, but as soon as the beta tester plugin is enabled, it is hidden, and a `jetpack-dev` plugin is installed instead.

This hiding of the original plugin only seems to happen on the Plugins screen in wp-admin, and this is why it creates a false positive on the Site Health screen (plugins in Site Health are fetched using the `get_plugins` function).

Contributor guide

Open the contributing guide

Research direction

Start with the Site Health recommendations for inactive plugins and the get_plugins call described in the issue, then compare how the Jetpack Beta Tester Plugin hides jetpack and installs jetpack-dev. Confirm the fix by ensuring active Jetpack plugins are not reported as inactive in Tools > Site Health.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.