Name the screen, not the plugin, in the page heading "WP-PluginsUsed" as the h1 duplicated the sidebar entry. The heading says what the screen is now -- Plugins Used -- matching Ban Options, Manage Ratings, Stats and the rest. STANDARDS.md 4.1: the prefix belongs in the menu title, never in the heading. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018W7cKqYNL1gUFTi38VRHaX
Correct the record on wp_get_sites(), here and in the CI comment This plugin repeated a claim that runs through the whole collection: that wp_get_sites() was removed in WordPress 5.1 and that calling it fatals. Neither is true. It was deprecated in 4.6 and still ships in ms-deprecated.php, which is loaded for multisite only -- so on a single site it merely looks absent. What it actually does is worse than a crash: it returns only the first 100 sites, so network activation and uninstall quietly did their work on a hundred sites and reported success. Comments, docblocks, assertion messages and the test method names that encoded the false version are all corrected to say that. No behaviour changes -- the code already used get_sites() with 'number' => 0. The CI matrix comment carried the same claim and moves with the shared template. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018W7cKqYNL1gUFTi38VRHaX
Stop claiming what the reader is upgrading from The Upgrade Notice said the floors moved 'up from 6.0 and 7.4', or advised anyone 'still on PHP 7.4' to move. Both are wrong about the version actually on wordpress.org. Queried against plugins.svn.wordpress.org, the released readmes declare WordPress 2.8 to 5.5, and fifteen of the nineteen declare no Requires PHP at all. Three plugins had ended up asserting three different predecessors, none of them right - and telling a reader who may be on 5.6 that they are on 7.4 is worse than saying nothing, because it reads as confirmation they are fine. What the notice can state truthfully is the requirement, the consequence and how to check: an older site is not offered the update, and Site Health reports the PHP version. That holds wherever the reader is coming from.