Prioritized issue groups from the latest Plugin Check scan
Security
67
6 issue groups
Maintainability
45
15 issue groups
Performance
3
1 issue group
I18n
2
2 issue groups
Sample message
Detected usage of a non-sanitized input variable: $_GET['_wpnonce']
Sample message
$_GET['_wpnonce'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
Detected usage of a possibly undefined superglobal array index: $_SERVER['REQUEST_URI']. 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 '$minify_inline_css_js'.
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "CE_BASE".
Sample message
unlink() is discouraged. Use wp_delete_file() to delete a file.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: is_writable().
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$e'.
Sample message
Using exclusionary parameters, like exclude, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "ce_action_cache_by_url_cleared".
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: rmdir().
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
Writing files using ABSPATH may be problematic. Consider using wp_upload_dir() instead if storing user data or generated files.
Sample message
Plugin folders are deleted when upgraded. Do not save data to the plugin folder using file_put_contents(). Detected usage of constant WP_CONTENT_DIR. Use wp_upload_dir() to get the uploads directory path or save to the database instead.
Sample message
Detected usage of tax_query, possible slow query.
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "$cache_enabler_constant_name".
Sample message
var_export() found. Debug code should not normally be used in production.
Sample message
Processing form data without nonce verification.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: readfile().
Sample message
A function call to esc_html__() 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
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
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.
Not analyzed yet.
First score snapshot
v1.8.16
35
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 35 | 119 | 44 | 75 | v1.8.16 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.