One Click Close Comments - ChoosePlugin.com

Version: 2.2.1

Conveniently close or open comments for a post or page with one click.

Author:	Scott Reilly (profile at wordpress.org)
WordPress version required:	4.7
WordPress version tested:	6.8
Plugin version:	3.0
Added to WordPress repository:	12-06-2009
Last updated:	02-04-2021 Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:	98
Rated by:	10
Plugin URI:	https://coffee2code.com/wp-plugins/one-click-...
Total downloads:	160 095
Active installs:	6 000+
Click to start download

From the admin listing of posts (‘Edit Posts’) and pages (‘Edit Pages’), a user can close or open comments to any posts to which they have sufficient privileges to make such changes (essentially admins and post authors for their own posts). This is done via an AJAX-powered color-coded indicator. The color-coding gives instant feedback on the current status of the post for comments: green means the post/page is open to comments, red means the post/page is closed to comments. Being AJAX-powered means that the change is submitted in the background after being clicked without requiring a page reload.

This plugin will only function for administrative users in the admin who have JavaScript enabled.

Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage

Hooks

The plugin exposes one filter for hooking. Such code should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).

c2c_one_click_close_comments_click_char (filter)

The ‘c2c_one_click_close_comments_click_char’ hook allows you to use an alternative character, string, or markup as the plugin’s indicator in the posts listing tables. It is the character that gets color-coded to indicate if comments are open or close, and the thing to click to toggle the comment open status. You can make use of Dashicons by specifying the desired dashicon’s name (with the “dashicons-” prefix). By default this is the comments dashicon, dashicons-admin-comments.

Arguments:

$char (array): The character, string, or markup to be used for display (by default this is dashicons-admin-comments).

Example:

/**
 * Changes the character used as the one-click link to a bullet (solid circle).
 *
 * @param string $char The default character.
 * @return string
 */
function custom_one_click_char( $char ) {
    return '&bull;';
}
add_filter( 'c2c_one_click_close_comments_click_char', 'custom_one_click_char' );

Screenshots
FAQ

I can see the colored comment bubble indicating current commenting status, but why aren’t they clickable?

The commenting status link/button is only clickable if you have JavaScript enabled.

What do the colors of the comment bubble mean?

Green means the post is currently open for comments; red means the post is not currently open for comments.

How can I customize the colors used for the comment bubble?

You can customize the colors via CSS. The class .comment-state-1 applies to comments that are open. The class .comment-state-0 applies to comments that are closed. I recommend my Add Admin CSS plugin to easily add this CSS.

How can I customize the character used to represent commenting status?

By default, commenting status is represented using the comment bubble dashicon, dashicons-admin-comments. You can change this by filtering c2c_one_click_close_comments_click_char. Here’s an example — added to a theme’s functions.php file — to change it to the original bullet (solid circle) character:

add_filter( 'c2c_one_click_close_comments_click_char', function ( $a ) { return "&bull;"; } );

How can I open or close comments when editing a specific post?

WordPress already includes the interface for you to edit the comment status for a specific post. When editing a post, you’ll find the setting in the “Discussion” section; the checkbox is labeled “Allow Comments”.

Why does the comment status indicator indicate that comments are open, when in reality comments are disabled (or vice vera)?

The comment status indicator only reflects the value of the “Allow Comments” setting for the post. In most cases, the indicator will accurately reflect the ability for the user to see the comment form and/or submit a comment.

However, other plugins, the theme, or custom code may affect the visitor’s ability to see the comment form when viewing a post and/or may permit or disable commenting at the time the post is shown to them despite the value of the setting. For instance, you could have another plugin installed which disables comments for a post after one year. After a year, that plugin would disable comments in its own way, but the comment status indicator for the post could reflect that comments are open since technically the post’s “Allow Comments” setting would still be enabled.

Why can’t I see the comment status indicator for certain custom post types?

The comment status indicator only appears for post types that support having comments.

Does this plugin have unit tests?

Yes. The tests are not packaged in the release .zip file or included in plugins.svn.wordpress.org, but can be found in the plugin’s GitHub repository.

Hide FAQ

ChangeLog

3.0 (2025-04-17)

Highlights:

This long-awaited major release improves accessibility by allowing keyboard navigation and interaction, reimplements JS to only use vanilla JS, properly shows (or doesn’t show) mouse cursor as pointer when hovering over comment status toggle, notes compatibility through WP 6.8+, and more.

Details:

Change: Improve accessibility
- Change: Use a semantic button instead of a span
- New: Allow comment state buttons to be navigable by keyboard
- New: Allow keyboard control by having the spacebar toggle comment state when toggle is focused
Change: Reimplement JavaScript to use vanilla JS and discontinue use of jQuery
Change: Prevent UI cues indicating comment status might be changeable to users who cannot change them (they never could)
- Change: Prevent cursor from changing to pointer when comment status cannot be changed
- Change: Prevent asynchronous JS submission of request to toggle comment status
Change: Prevent display and use of comment status indicator for post types that don’t support comments
Change: Improve nonce handling
- Change: Generate a unique nonce per post rather than a generic nonce
- Change: Store nonce in ‘data-nonce’ attribute rather than ‘id’
- Change: Use unused private static class variable ‘nonce_field’ as base for nonce field key and value
Change: Use result of update to recognize if the comment status didn’t get changed for some reason
Change: Ensure AJAX response is only ever an integer
Change: Remove any markup potentially introduced in a string translation
Fix: Restore changing mouse cursor to a pointer on hover
Change: Assign additional generic class of ‘comment_state’ to indicator markup
Change: Reset field_title variable in reset() and use reset() during initialization
Change: Use update() rather than query() for making SQL update request
New: Add inline documentation to class variables
New: Add recommendation for Add Admin CSS plugin for adding the CSS suggested in FAQ entry related to customizing indicator
New: Add DEVELOPER-DOCS.md and move hooks documentation into it
Change: Discontinue unnecessary explicit loading of textdomain
Change: Prevent unwarranted PHPCS complaints
Change: Tweak some text in the FAQ section, including fixing a typo
Change: Note compatibility through WP 6.8+
Change: Note compatibility through PHP 8.3+
Change: Tweak installation instruction
Change: Reduce number of ‘Tags’ in readme.txt
Change: Remove development and testing related files from release packaging
Unit tests:
- Fix: Allow tests to run against current versions of WordPress
- Hardening: Prevent direct web access to bootstrap.php
- Change: Restructure unit test directories
  - Change: Move bin/ into tests/
  - Change: Move tests/bootstrap.php into tests/phpunit/
  - Change: Move tests/test-one-click-close-comments.php into tests/phpunit/tests/
- Change: Remove ‘test-‘ prefix from unit test files
- Change: In bootstrap, store path to plugin file constant
- Change: In bootstrap, add backcompat for PHPUnit pre-v6.0
- Change: Rename phpunit.xml to phpunit.xml.dist per best practices
- New: Add composer.json for PHPUnit Polyfill dependency
- Change: Explicitly define return type for overridden methods
New: Add a few more possible TODO items

2.7.1 (2021-04-01)

New: Add a unit test
Change: Note compatibility through WP 5.7+

2.7 (2020-08-02)

Highlights:

This recommended release updates its JavaScript, streamlines markup output, adds unit testing, adds a TODO.md file, updates a few URLs to be HTTPS, notes compatibility through 5.4+, and other minor behind-the-scenes improvements.

Details:

New: Extract code for determining click character into new get_click_char()
New: Add unit tests
New: Add reset() for resetting memoized variables
New: Add TODO.md and move existing TODO list from top of main plugin file into it (and add items to it)
Change: Improve output of markup
- Remove encompassing span only shown for users authorized to toggle comment status
- Add ‘title’ attribute to primary span to indicate current state
- Change text to not indicate that comment staus can be toggled when user does not have that capability
Change: Update JavaScript
- Change: Migrate use of deprecated .live() to .on()
- Change: Handle removal of a previously encapsulating span
- Change: Remove unused code
- Change: Update code syntax
Change: Allow class to be defined even when loaded outside the admin
Change: Return ‘-1’ to Ajax requests that don’t result in the comment status being toggled
Change: Add $and_exit argument to toggle_comment_status() to prevent exiting in order to facilitate unit testing
Change: Refactor add_post_column() to be more concise
Change: Add inline docs for deprecated filter one-click-close-comments-click-char
Change: Switch to use of strict equality operator instead of simple equality operator
Change: Note compatibility through WP 5.4+
Change: Update links to coffee2code.com to be HTTPS

Full changelog is available in CHANGELOG.md.

Hide ChangeLog