Comment Cleaner — Bulk Delete & Disable Comments

Delete, export, import, and manage WordPress comments with bulk tools and comment-control settings.

v7.0royalnavneetUpdated 2026-04-14Added Aug 23, 201520k+ installs94% rating
37
Score
204
Errors
78
Warnings
+0
Change

Category Scores

Security0
Repo89
Performance100
Maintainability68

Top Issues by Category

i18n176
maintainability52
security52
repo_compliance2

Issues Details

282 issues found in latest scan

ERROR172
WordPress.WP.I18n.NonSingularStringLiteralDomain

The $domain parameter must be a single text string literal. Found: NAV_DELETE_COMMENTS_TEXT_DOMAIN

WARNING20
WordPress.DB.DirectDatabaseQuery.DirectQuery

Use of a direct database call is discouraged.

WARNING17
WordPress.DB.DirectDatabaseQuery.NoCaching

Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().

WARNING15
WordPress.DB.PreparedSQL.InterpolatedNotPrepared

Use placeholders and $wpdb->prepare(); found interpolated variable $date_filter at "DELETE FROM $wpdb->comments WHERE comment_approved = '0' AND comment_type = 'comment' $date_filter"

ERROR14
PluginCheck.Security.DirectDB.UnescapedDBParameter

Unescaped parameter $date_filter used in $wpdb->get_var()\n$date_filter assigned unsafely at line 752.

WARNING12
WordPress.Security.ValidatedSanitizedInput.MissingUnslash

$_GET['nav_export_message'] not unslashed before sanitization. Use wp_unslash() or similar

ERROR7
WordPress.DateTime.RestrictedFunctions.date_date

date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.

WARNING4
WordPress.Security.ValidatedSanitizedInput.InputNotSanitized

Detected usage of a non-sanitized input variable: $_FILES['import_file']['error']

WARNING4
WordPress.Security.ValidatedSanitizedInput.InputNotValidated

Detected usage of a possibly undefined superglobal array index: $_FILES['import_file']['error']. Check that the array index exists before using it.

WARNING3
WordPress.PHP.DevelopmentFunctions.error_log_error_log

error_log() found. Debug code should not normally be used in production.

ERROR3
WordPress.WP.AlternativeFunctions.file_system_operations_fclose

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().

WARNING2
WordPress.Security.SafeRedirect.wp_redirect_wp_redirect

wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.

ERROR2
WordPress.WP.AlternativeFunctions.file_system_operations_fopen

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().

ERROR2
WordPress.WP.I18n.MissingTranslatorsComment

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.

WARNING1
PluginCheck.CodeAnalysis.DiscouragedFunctions.load_plugin_textdomainFound

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.

ERROR1
WordPress.Security.EscapeOutput.OutputNotEscaped

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$csv'.

ERROR1
WordPress.WP.I18n.UnorderedPlaceholdersText

Multiple placeholders in translatable strings should be ordered. Expected "%1$s, %2$s", but got "%s, %s" in 'No comments found between %s and %s'.

ERROR1
outdated_tested_upto_header

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.

ERROR1
plugin_header_no_license

Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.

Latest Snapshot

Findings

282

Errors

204

Warnings

78

Score History

First score snapshot

First scan completed Jun 20, 2026

v7.0 · Plugin Check 2.0.0 · Model 2026.06-mvp-static-v2

Jun 20, 2026

v7.0

37

Latest

Findings
282
Errors
204
Warnings
78
Plugin Check
2.0.0
Model
2026.06-mvp-static-v2

Related Plugins