Easy “410 – gone” status code plugin for WordPress: CSV bulk upload, manual & regex entry, 410 option when deleting pages, posts, categories & tags.
Prioritized issue groups from the latest Plugin Check scan
Security
95
10 issue groups
Maintainability
90
11 issue groups
I18n
12
3 issue groups
Repo Compliance
1
1 issue group
Sample message
Short PHP opening tag used with echo; expected "<?php echo $args ..." but found "<?= $args ..."
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"<h2>{$section['title']}</h2>\n"'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$__composer_autoload_files".
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
$_GET['paged'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST[$action]. Check that the array index exists before using it.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found interpolation in unescaped heredoc.
Sample message
Detected usage of a non-sanitized input variable: $_FILES[static::ID]
Sample message
A "translators:" comment must be a "/* */" style comment. Docblock comments will not be picked up by the tools to generate a ".pot" file.
Sample message
Processing form data without nonce verification.
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.
Sample message
Mismatched text domain. Expected 'ultimate-410' but got 'wordpress-seo'.
Sample message
Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "exit_on_http_head".
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
Sanitization missing for register_setting().
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "ComposerAutoloaderInit_ultimate_410".
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "composerRequire_ultimate_410".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$errors'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
Plugin name "Ultimate 410 Gone Status Code" is different from the name declared in plugin header "Ultimate 410".
Sample message
Tested up to: 6.6 < 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.
Not analyzed yet.
First score snapshot
v1.1.7
34
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 34 | 201 | 136 | 65 | v1.1.7 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.