Create unlimited custom post types and custom taxonomies.
Prioritized issue groups from the latest Plugin Check scan
I18n
39
3 issue groups
Security
11
3 issue groups
Repo Compliance
2
2 issue groups
Sample message
A function call to _x() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"ptu-metabox-field--{$field['id']}"'.
Sample message
The $text parameter must be a single text string literal. Found: $label
Sample message
Detected usage of a non-sanitized input variable: $_POST[$field_id]
Sample message
$_POST[$field_id] not unslashed before sanitization. Use wp_unslash() or similar
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
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
Mismatched Requires at least: 5.2.0 != 5.7. "Requires at least" needs to be exactly the same with that in your main plugin file's header.
Not analyzed yet.
First score snapshot
v1.2.9
72
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 72 | 52 | 45 | 7 | v1.2.9 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.