Remove unwanted blocks from the Gutenberg Block Inserter.
Category Scores
Issues to Review
Prioritized issue groups from the latest Plugin Check scan
Maintainability
8
5 issue groups
Security
5
3 issue groups
Repo Compliance
2
2 issue groups
I18n
1
1 issue group
WARNINGMaintainabilitytrademarked termThe plugin name includes a restricted term. Your chosen plugin name - "Disable Gutenberg Blocks - Block Manager" - contains the restricted term "gutenberg" which cannot be used at all in your plugin name.3
- Category
- Maintainability
- Occurrences
- 3
- Severity
- warning
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Disable Gutenberg Blocks - Block Manager" - contains the restricted term "gutenberg" which cannot be used at all in your plugin name.
WARNINGSecurityInput is not sanitizedDetected usage of a non-sanitized input variable: $_POST['bulk-change']2
- Category
- Security
- Occurrences
- 2
- Severity
- warning
Sample message
Detected usage of a non-sanitized input variable: $_POST['bulk-change']
WARNINGSecurityRequest data is not unslashed$_POST['bulk-change'] not unslashed before sanitization. Use wp_unslash() or similar2
- Category
- Security
- Occurrences
- 2
- Severity
- warning
Sample message
$_POST['bulk-change'] not unslashed before sanitization. Use wp_unslash() or similar
ERRORMaintainabilityMissing direct file access protectionPHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;2
- Category
- Maintainability
- Occurrences
- 2
- Severity
- error
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
WARNINGMaintainabilityerror log print rprint_r() found. Debug code should not normally be used in production.1
- Category
- Maintainability
- Occurrences
- 1
- Severity
- warning
Sample message
print_r() found. Debug code should not normally be used in production.
ERRORSecurityOutput is not escapedAll output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.1
- Category
- Security
- Occurrences
- 1
- Severity
- error
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.
WARNINGMaintainabilityNot In FooterIn footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.1
- Category
- Maintainability
- Occurrences
- 1
- Severity
- warning
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
ERRORI18nMissing Translators CommentA function call to __() 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.1
- Category
- I18n
- Occurrences
- 1
- Severity
- error
Sample message
A function call to __() 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.
ERRORRepo Complianceoutdated tested upto headerTested up to: 5.8 < 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.1
- Category
- Repo Compliance
- Occurrences
- 1
- Severity
- error
Sample message
Tested up to: 5.8 < 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.
WARNINGRepo Complianceplugin header nonexistent domain pathThe "Domain Path" header in the plugin file must point to an existing folder. Found: "languages"1
- Category
- Repo Compliance
- Occurrences
- 1
- Severity
- warning
Sample message
The "Domain Path" header in the plugin file must point to an existing folder. Found: "languages"
Show 1 moreShow less
ERRORMaintainabilitytrunk stable tag1
- Category
- Maintainability
- Occurrences
- 1
- Severity
- error
Sample message
Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.
Score History
First score snapshot
v1.0.9
81
Latest
- Findings
- 16
- Errors
- 6
- Warnings
- 10
- Check
- 2.0.0
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 81 | 16 | 6 | 10 | v1.0.9 | 2.0.0 |