请求在WordPress中添加评论单独/批量拒绝功能及拒绝原因选项

Great question—this is a super common need for multi-moderator WordPress sites, and both approaches you’re considering are totally workable. Let’s walk through each option and how to pull them off:

Option 1: Build a Custom "Rejected" Status with Rejection Reasons #

This is the cleaner, more scalable approach for multi-moderator teams, since it creates a clear distinction between unapproved (pending review) and rejected (already reviewed & denied) comments. Here’s how to implement it:

• Step 1: Register a new comment status
  Add a rejected status to WordPress’s comment system using the register_comment_status hook. This will make it visible in the admin dashboard:

  function register_rejected_comment_status() {
      register_comment_status( 'rejected', array(
          'label' => __( 'Rejected', 'text-domain' ),
          'public' => true,
          'show_in_admin_all_list' => true,
          'show_in_admin_comment_list' => true,
          'label_count' => _n_noop( 'Rejected <span class="count">(%s)</span>', 'Rejected <span class="count">(%s)</span>' ),
      ) );
  }
  add_action( 'init', 'register_rejected_comment_status' );
  

• Step 2: Add a rejection reason dropdown to the comment edit screen
  Create a meta box where moderators can select a pre-defined reason (e.g., "Off-topic", "Spammy content", "Violates guidelines") when rejecting a comment:

  function add_rejection_reason_meta_box() {
      add_meta_box(
          'rejection_reason',
          __( 'Rejection Reason', 'text-domain' ),
          'render_rejection_reason_meta_box',
          'comment',
          'normal',
          'high'
      );
  }
  add_action( 'add_meta_boxes_comment', 'add_rejection_reason_meta_box' );
  
  function render_rejection_reason_meta_box( $comment ) {
      $reason = get_comment_meta( $comment->comment_ID, '_rejection_reason', true );
      ?>
      <select name="rejection_reason" id="rejection_reason">
          <option value="">Select a reason...</option>
          <option value="off_topic" <?php selected( $reason, 'off_topic' ); ?>>Off-topic</option>
          <option value="spammy" <?php selected( $reason, 'spammy' ); ?>>Spammy content</option>
          <option value="guidelines" <?php selected( $reason, 'guidelines' ); ?>>Violates community guidelines</option>
      </select>
      <?php
  }
  
  // Save the rejection reason when updating the comment
  function save_rejection_reason( $comment_id ) {
      if ( isset( $_POST['rejection_reason'] ) && current_user_can( 'edit_comment', $comment_id ) ) {
          update_comment_meta( $comment_id, '_rejection_reason', sanitize_text_field( $_POST['rejection_reason'] ) );
      }
  }
  add_action( 'edit_comment', 'save_rejection_reason' );
  

• Step 3: Add "Reject" to bulk actions
  Let moderators bulk-reject comments directly from the comments list:

  function add_reject_bulk_action( $bulk_actions ) {
      $bulk_actions['reject_comments'] = __( 'Reject', 'text-domain' );
      return $bulk_actions;
  }
  add_filter( 'bulk_actions-edit-comments', 'add_reject_bulk_action' );
  
  function handle_reject_bulk_action( $redirect_to, $action, $comment_ids ) {
      if ( $action !== 'reject_comments' ) return $redirect_to;
  
      foreach ( $comment_ids as $comment_id ) {
          if ( current_user_can( 'edit_comment', $comment_id ) ) {
              wp_set_comment_status( $comment_id, 'rejected' );
              // Set a default reason if not provided, or adjust to prompt for bulk reasons
              update_comment_meta( $comment_id, '_rejection_reason', 'bulk_reject' );
          }
      }
  
      $redirect_to = add_query_arg( 'bulk_comment_count', count( $comment_ids ), $redirect_to );
      return $redirect_to;
  }
  add_filter( 'handle_bulk_actions-edit-comments', 'handle_reject_bulk_action', 10, 3 );
  

• Step 4: Visualize the status in the admin
  Add a custom column or highlight rejected comments to make them easy to spot alongside pending ones. For example, add a column for rejection reasons:

  function add_rejection_reason_column( $columns ) {
      $columns['rejection_reason'] = __( 'Rejection Reason', 'text-domain' );
      return $columns;
  }
  add_filter( 'manage_edit-comments_columns', 'add_rejection_reason_column' );
  
  function render_rejection_reason_column( $column, $comment_id ) {
      if ( $column === 'rejection_reason' ) {
          $reason = get_comment_meta( $comment_id, '_rejection_reason', true );
          echo esc_html( $reason ? ucwords( str_replace( '_', ' ', $reason ) ) : '-' );
      }
  }
  add_action( 'manage_comments_custom_column', 'render_rejection_reason_column', 10, 2 );
  

Option 2: Repurpose the Trash with Disabled Auto-Deletion #

If you want a quicker implementation without adding a new status, you can repurpose the Trash folder to store rejected comments. Here’s what you need to do:

• Disable auto-deletion of trashed comments
  By default, WordPress deletes trashed comments after 30 days. Disable this with:

  function disable_trash_auto_delete() {
      remove_action( 'wp_scheduled_delete', 'wp_delete_posts' );
  }
  add_action( 'init', 'disable_trash_auto_delete' );
  

• Add rejection reason meta to trashed comments
  Use the same meta box code from Option 1 to let moderators add a reason when moving a comment to Trash. This way, trashed comments are clearly marked as rejected (not just deleted) and you have a record of why.

Pros & Cons of Each Approach #

Final Recommendation #

For multi-moderator teams needing clear distinction between pending and reviewed/rejected comments, Option 1 (custom rejected status) is the better choice—it eliminates ambiguity and keeps your workflow organized. If you’re short on time and can train your team to treat Trash as "rejected" instead of "deleted", Option 2 works too.

内容的提问来源于stack exchange，提问作者Jonathan Stegall