Completely disables comments functionality from backend and frontend. Just install it, nothing to configure!
| Code | Message | Location | Category | |
|---|---|---|---|---|
| ERROR | plugin_header_no_license | Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license. | — | Plugin Repo |
| ERROR | outdated_tested_upto_header | Tested up to: 5.7 < 6.8. 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. | — | Plugin Repo |
| WARNING | trademarked_term | The plugin name includes a restricted term. Your plugin name - "WpSimpleTools Disable Comments" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| WARNING | trademarked_term | The plugin slug includes a restricted term. Your plugin slug - "wpsimpletools-disable-comments" - contains the restricted term "wp" which can be used within the plugin slug, as long as you don't use the full name in the plugin name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| WARNING | 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. | 46:9 | Security |
| WARNING | mismatched_plugin_name | Plugin name "Disable Comments" is different from the name declared in plugin header "WpSimpleTools Disable Comments". | — | — |
| 11/13/2025, 7:27:05 PM | 10s | 99 | 2 | 4 |