Allows you to easily upgrade for testing the next versions of WordPress.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
14
6 issue groups
I18n
1
1 issue group
Repo Compliance
1
1 issue group
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wp_beta_tester_add_admin_bar_menu".
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "WordPress Beta Tester" - contains the restricted term "wordpress" which cannot be used at all in your plugin name.
Sample message
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "WP_Beta_Tester".
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "CORE_UPGRADE_SKIP_NEW_BUNDLED".
Sample message
Tested up to: 6.9 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.
Sample message
Unexpected markdown file "CHANGES.md" detected in plugin root. Only specific markdown files are expected in production plugins.
Sample message
Plugin Updater detected. Detected code which may be altering WordPress update routines. Detected: _site_transient_update_core
Not analyzed yet.
First score snapshot
v4.0.0
97
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 97 | 16 | 1 | 15 | v4.0.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.