Changes between Initial Version and Version 2 of Ticket #64049
- Timestamp:
- 09/29/2025 08:40:10 PM (8 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #64049 – Description
initial v2 1 1 When updating a comment via the REST API we currently fail comment updates in the `WP_REST_Comments_Controller::update_item` method if the updated content is `empty()`. On REST comment creation and within traditional comment updates via `wp_handle_comment_submission` we respect the return value of the `allow_empty_comment` filter and permit empty comment content when this filter is set. 2 2 3 My understanding of the history here is that allowing empty commentspermits moderation by allowing inappropriate comment content to be deleted without removing the content entity itself; or alternatively (and as discussed in #43177) to permit comments to be saved which only contain metadata and do not have any "content" in the traditional sense.3 My understanding of the history here (see #62684) is that allowing comments to be edited to become empty permits moderation by allowing inappropriate comment content to be deleted without removing the content entity itself; or alternatively (and as discussed in #43177) to permit comments to be saved which only contain metadata and do not have any "content" in the traditional sense. 4 4 5 5 This may also unblock certain actions for editorial comments within the block editor.