Comment Cleaner — Bulk Delete & Disable Comments

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

v7.0royalnavneetUpdated Added 20k+ installs94% rating
37
Score
204
Errors
78
Warnings
+0
Change

Category Scores

Security0
Repo89
Performance100
Maintainability68

Issues to Review

Prioritized issue groups from the latest Plugin Check scan

282 findings

I18n

176

4 issue groups

Maintainability

52

6 issue groups

Security

52

7 issue groups

Repo Compliance

2

2 issue groups

ERRORI18nNon Singular String Literal DomainThe $domain parameter must be a single text string literal. Found: NAV_DELETE_COMMENTS_TEXT_DOMAIN172
Category
I18n
Occurrences
172
Severity
error

Sample message

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

WARNINGMaintainabilityDirect QueryUse of a direct database call is discouraged.20
Category
Maintainability
Occurrences
20
Severity
warning

Sample message

Use of a direct database call is discouraged.

WARNINGMaintainabilityNo CachingDirect database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().17
Category
Maintainability
Occurrences
17
Severity
warning

Sample message

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

WARNINGSecurityInterpolated SQL is not preparedUse placeholders and $wpdb->prepare(); found interpolated variable $date_filter at "DELETE FROM $wpdb->comments WHERE comment_approved = '0' AND comment_type = 'comment' $date_filter"15
Category
Security
Occurrences
15
Severity
warning

Sample message

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"

ERRORSecurityDatabase parameter is not escapedUnescaped parameter $date_filter used in $wpdb->get_var()\n$date_filter assigned unsafely at line 752.14
Category
Security
Occurrences
14
Severity
error

Sample message

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

WARNINGSecurityRequest data is not unslashed$_GET['nav_export_message'] not unslashed before sanitization. Use wp_unslash() or similar12
Category
Security
Occurrences
12
Severity
warning

Sample message

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

ERRORMaintainabilitydate datedate() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.7
Category
Maintainability
Occurrences
7
Severity
error

Sample message

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

WARNINGSecurityInput is not sanitizedDetected usage of a non-sanitized input variable: $_FILES['import_file']['error']4
Category
Security
Occurrences
4
Severity
warning

Sample message

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

WARNINGSecurityInput is not validatedDetected usage of a possibly undefined superglobal array index: $_FILES['import_file']['error']. Check that the array index exists before using it.4
Category
Security
Occurrences
4
Severity
warning

Sample message

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

WARNINGMaintainabilityerror log error logerror_log() found. Debug code should not normally be used in production.3
Category
Maintainability
Occurrences
3
Severity
warning

Sample message

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

Show 9 more
ERRORMaintainabilityfile system operations fclose3
Category
Maintainability
Occurrences
3
Severity
error

Sample message

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

WARNINGSecuritywp redirect wp redirect2
Category
Security
Occurrences
2
Severity
warning

Sample message

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.

ERRORMaintainabilityfile system operations fopen2
Category
Maintainability
Occurrences
2
Severity
error

Sample message

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

ERRORI18nMissing Translators Comment2
Category
I18n
Occurrences
2
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.

WARNINGI18nDiscouraged text-domain loading1
Category
I18n
Occurrences
1
Severity
warning

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.

ERRORSecurityOutput is not escaped1
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 '$csv'.

ERRORI18nUnordered Placeholders Text1
Category
I18n
Occurrences
1
Severity
error

Sample message

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'.

ERRORRepo Complianceoutdated tested upto header1
Category
Repo Compliance
Occurrences
1
Severity
error

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.

ERRORRepo Complianceplugin header no license1
Category
Repo Compliance
Occurrences
1
Severity
error

Sample message

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

Score History

First score snapshot

v7.0

37

Latest

Findings
282
Errors
204
Warnings
78
Check
2.0.0

Related Plugins

Simply Disable Comments

6k+ active installs

100
Bulk Delete

30k+ active installs

96
Disable Comments

10k+ active installs

94
WP Bulk Delete

100k+ active installs

69
Disable Comments

100k+ active installs

42