Create clean, complete, and up-to-date sitemaps for your WordPress website automatically.
Prioritized issue groups from the latest Plugin Check scan
Security
60
10 issue groups
Maintainability
56
10 issue groups
I18n
44
3 issue groups
Performance
5
2 issue groups
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
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"'>\n'.
Sample message
Missing $domain parameter in function call to __().
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
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Function "wp_admin_notice()" requires WordPress 6.4.0, but your plugin minimum supported version is WordPress 6.0.0.
Sample message
$_POST[$field] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
The %i modifier is only supported in WP 6.2 or higher. Found: "%i".
Sample message
Use placeholders and $wpdb->prepare(); found interpolated variable $table_name at "UPDATE $table_name SET onoroff = %s WHERE name = 'additionalpages'"
Sample message
Simple placeholders should not be quoted in the query string in $wpdb->prepare(). Found: '%s'.
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a non-sanitized input variable: $_POST['post']
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: is_writable().
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
Detected usage of a possibly undefined superglobal array index: $_POST['csg_robots_content']. Check that the array index exists before using it.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
Sample message
In footer ($in_footer) is not set explicitly wp_register_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.
Sample message
Using exclusionary parameters, like post__not_in, 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
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
Unescaped parameter $table_name used in $wpdb->get_var()\n$table_name assigned unsafely at line 16.
Sample message
Attempting a database schema change is discouraged.
Sample message
Use placeholders and $wpdb->prepare(); found $query
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Not analyzed yet.
First score snapshot
v4.6.2
33
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 33 | 175 | 118 | 57 | v4.6.2 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.