CensusPlugin profiles › Disable Comments

Disable Comments – Remove Comments & Stop Spam [Multi-Site Support]

Figures from the Plugin Directory Census · as of 28 Aug 2026

1M

Active installs, lower bound

Group: 1,000,000+ installs

29

Days since the last release

Group median: 8

4.7

out of 5, from 280 ratings

Group median: 4.7 (10+ ratings)

no threads

Support threads, two months

Group: 71.9%

Full profile on wordpress.orgShow on the mapCompare with your own plugins

What is Disable Comments and who is behind it?

Disable Comments is a WordPress plugin in the “Admin and backup” field, made by WPDeveloper. It has been listed in the directory since 27 May 2011, so for 15 years. WPDeveloper has 12 plugins with at least 10,000 installs in the census. With 1,000,000 to 1,999,999 active installs it belongs to the 1,000,000+ installs group; its last release came 29 days before the reference date, and it is tested up to WordPress 7.0.

This is how the author describes the plugin on wordpress.org:

“Disable comments site-wide or by post type, delete existing comments in bulk, and block comment spam via REST API and XML-RPC. Multisite ready.”

Self-description on wordpress.org, retrieved on 10 Sept 2026

When was Disable Comments last released?

The last release of Disable Comments came 29 days before the reference date; the group median is 8 days.

Disable Comments · 29 days today1 month3 months1 year3 years10 years
Each dot is a plugin in the 1,000,000+ installs group, placed horizontally by days since its last release, on a logarithmic scale. The dashed line marks 365 days.

How many installs does Disable Comments have?

Disable Comments had 1,000,000 to 1,999,999 active installs on the reference date. Within its group, 28 plugins had a higher band and 38 plugins the same band.

The API reports installs only as a lower bound with one significant figure: 1,000,000 means at least 1,000,000 and at most 1,999,999.

Which WordPress version is Disable Comments tested with?

No directory notice: tested up to WordPress 7.0, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 3.0% of the group.

How does Disable Comments compare with its group?

The group holds 67 listed plugins. 80.6% of them had a more recent last release than Disable Comments; 1.5% had no release for more than 365 days.

FigureDisable CommentsGroup, 67 plugins
Days since the last release29median 8
Rating4.7 (280)median 4.7 (10+ ratings)
Support threads marked resolvednot stated71.9%
Tested up to7.065.7% on 7.1
Requires PHP7.0most often 7.4 (49.3%)

All values on the reference date

Slugdisable-comments
AuthorWPDeveloper
Active installs1,000,000 to 1,999,999
Last release29 days before the reference date
Tested up toWordPress 7.0 · core on the reference date: 7.1
Requires WordPress5.0
Requires PHP7.0
Rating4.7 out of 5 from 280 ratings
Support threads, two monthsnone in the window
Listed since27 May 2011
Total downloads34,520,483, updates included
Tagsdelete-comments, disable-comments, remove-comments, spam-protection, stop-spam

Tags

TagPlugins with 10,000+ installs and this tagRank by installsMedian days since release
delete-comments2145
disable-comments3160
remove-comments3160
spam-protection10126
stop-spam1129

Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.

Class of 2011

Disable Comments has been listed since 27 May 2011. Of the 107 plugins with 10,000+ installs added in 2011, 79.4% released within the 365 days before the reference date.

Same group, shared tags

Not a recommendation; the same figures for comparison. Alphabetical.

PluginActive installsLast releaseRating
Antispam Bee700,000 to 799,9995 days before the reference date4.8 (226)
CF7 Apps300,000 to 399,99922 days before the reference date3.8 (135)
Disable Comments100,000 to 199,99993 days before the reference date3.8 (24)
Titan Anti-spam & Security50,000 to 59,9998 days before the reference date4.5 (369)
WP Armour400,000 to 499,99953 days before the reference date5.0 (1,434)

Do you maintain Disable Comments?

If you maintain Disable Comments, you can link to this profile, for example from your readme or your website. Both snippets show this badge:

Disable Comments in the Plugin Directory Census 01/2026

HTML

<a href="https://hafenstudios.com/en/census/plugins/disable-comments/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="Disable Comments in the Plugin Directory Census 01/2026" width="220" height="40"></a>

Markdown

[![Disable Comments in the Plugin Directory Census 01/2026](https://hafenstudios.com/census/plugins/badge-en.svg)](https://hafenstudios.com/en/census/plugins/disable-comments/)

The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.

A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.

How to cite

hafenstudios (2026): Disable Comments – Remove Comments & Stop Spam [Multi-Site Support], profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/disable-comments/

Source and status

All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.

Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.