__group__ ticket summary owner _component _version priority severity milestone type _status workflow _created modified _description _reporter Candidates for Closure 53310 All Comments are not visible in comment section in WordPress Backend Post Section Comments 5.7.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-05-31T15:25:09Z 2021-06-25T07:21:03Z "All Comments are not visible in comment section in WordPress Back-end Post Section - Ex : 1. If I have 104 Comment in My Post then I am able to see only latest 100 comment 2. If I have 21 Comment in Post then I am able to see only 20 comments **Reference Video Link:** https://www.loom.com/share/45c015457f81401ea4cabbb562c5ef34 **Note : This issue occurs in Backend post section**" shailu25 Candidates for Closure 48724 Button text type when editing a comment Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2019-11-19T12:21:37Z 2019-12-05T05:29:09Z "When editing a comment in wp-admin the button to update says ""Update How"" instead of Update Now. As per attached screenshot. (on latest WordPress 5.3)" tchburn Candidates for Closure 52875 If a post is in trash related comments cannot be removed or trashed Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2021-03-21T08:27:43Z 2023-03-29T18:53:32Z Comments to trashed or removed posts need to be visible with a clear note in the 'In response to' column that they are related to the trashed/removed post. oglekler Candidates for Closure 43946 Inconsistent encoding of comment_content Comments 4.9.5 normal normal Awaiting Review defect (bug) new reporter-feedback 2018-05-03T10:50:13Z 2018-05-04T12:39:24Z "The contents of the comments.comment_content field in the WordPress database are stored inconsistently depending on whether the user creating the comment was logged in or not. {{{ > select comment_ID, comment_content, comment_type from wp_comments where comment_ID > 7; +------------+-----------------------------------------------------+--------------+ | comment_ID | comment_content | comment_type | +------------+-----------------------------------------------------+--------------+ | 8 | This is a good & strong comment (comment, anon) | | | 9 | This is a good & strong comment (comment, auth) | | +------------+-----------------------------------------------------+--------------+ }}} In the example above, comment 8 was left by an anonymous user, and comment 9 was left by an authenticated user. Notice how the comment_content field has been HTML-escaped for ID 8, but not for ID 9. === Steps to reproduce: * Install a fresh copy of WordPress * As the site administrator, navigate to the default ""hello-world"" post * Leave a comment including characters that should be escaped when output to HTML, e.g. & * Log out * Navigate to the default ""hello-world"" post * Leave a comment including characters that should be escaped when output to HTML, e.g. & Compare the contents of the two comments in the wp_comments table. " leewillis77 Candidates for Closure 51589 Missing whitespace between comment reply title and cancel comment reply link Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2020-10-21T17:55:10Z 2020-11-08T15:13:16Z "Hi, There's a missing whitespace between the comment reply title and the cancel comment reply link. This results in: ""Reply to A WordPress CommenterCancel reply"". The {{{cancel-comment-reply-link}}} is wrapped in {{{}}} tags. In file comment-template there's a whitespace before the opening tag: {{{'cancel_reply_before' => ' ',}}} But somehow it's being ignored in comment form. Stripped perhaps? Was not able to find what causes this. More info here: https://wordpress.org/support/topic/cancel-comment-reply-link-in-comments-form/." Guido07111975 Candidates for Closure 41788 PHP Fatal error: Call to a member function has_cap() on a non-object in wp-includes/comment.php Comments 4.8.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-09-03T22:16:34Z 2020-12-14T19:20:14Z "{{{#!php if ( ! empty( $commentdata['user_id'] ) ) { $user = get_userdata( $commentdata['user_id'] ); $post_author = $wpdb->get_var( $wpdb->prepare( ""SELECT post_author FROM $wpdb->posts WHERE ID = %d LIMIT 1"", $commentdata['comment_post_ID'] ) ); } if ( isset( $user ) && ( $commentdata['user_id'] == $post_author || $user->has_cap( 'moderate_comments' ) ) ) { }}} If get_userdata() returns false, this code can lead to a fatal error." kirbyde Candidates for Closure 58723 Remove deprecated parameter tests in comments_link() Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2023-07-06T06:50:47Z 2023-08-27T10:29:05Z "In `comments_link()`, two unused parameters are checked if they're not empty. If they are, only a deprecation warning is shown for a WordPress version of the distant past. I suggest removing the parameters altogether. If we _must_ keep these deprecation warnings, at least use `if ( $deprecated )` instead of `if ( ! empty( $deprecated ) )` for the former is about 2.7x faster while achieving the same." Cybr Candidates for Closure 54621 Unsaved comment warning without any changes made when click on Publish, Update or Preview Buttons Comments 4.6 normal major Awaiting Review defect (bug) assigned reporter-feedback 2021-12-14T14:42:58Z 2022-03-18T16:47:44Z "Hi Team, I got unsaved comment changes warning without any changes made in the content of the custom post type post, here is screenshot: https://i.imgur.com/PQmirDL.png I see new codes are added in the WordPress core file: wp-admin/js/edit-comments.js And there is some condition issue, the code is have strict equality comparison operator to undefined ID which is not present in the custom post type: #replyrow Screenshot: https://i.imgur.com/kAHNkrs.png Please review it. Thanks" askaryabbas Candidates for Closure 58604 title_reply_to Value of comment_form() Function Isn't Working Comments 6.2.2 normal major Awaiting Review defect (bug) new reporter-feedback 2023-06-22T18:37:20Z 2024-01-10T11:48:50Z "Hello everyone, friends; I encountered a problem when customizing the comment form. If I add the **title_reply_to** value to the **comment_form()** function, get the **reply_to_text** value in the **get_comment_reply_link()** function. Has anyone had this problem before? Or am I experiencing this problem due to an error? {{{#!php '...', ); $args = array( 'title_reply' => __('Leave a Reply', 'xxx'), // This value works 'title_reply_to' => __('Leave a Reply to %s', 'xxx'), // This value doesn't work 'title_reply_before' => '

', // The problem is when I add an icon to this value 'title_reply_after' => '

', 'fields' => apply_filters('comment_form_default_fields', $fields) ); comment_form($args); }}} " metinmete Candidates for Closure 45998 Comments trashed after reply Comments 5.0.3 normal normal Awaiting Review enhancement new reporter-feedback 2019-01-16T02:58:34Z 2019-01-16T16:42:52Z "I found A Bug into your software. Which is Whenever I click on **Approve and Reply** option in comments, then it's automatically trashed.. Please Fix it." pkkarn Candidates for Closure 60533 The comment tree is old – maybe it’s worth changing it? Comments normal normal Awaiting Review enhancement new reporter-feedback 2024-02-13T19:54:34Z 2024-02-20T02:26:48Z "Maybe it’s worth considering a new approach to comments on WordPress? It’s about the tree – the rooting of comments. Currently it may be level 10. And later there is no reply button – because they usually get narrower. Or maybe it’s worth ending this rooting and switching to something – where every statement will be treated as a response. Completely without roots and their depth – which has been causing problems in long conversations for years. Maybe it would be worth creating it like on the forums – i.e. on a completely different system, without this limitation. Isn’t it worth thinking about? Sometimes conversations are long and it’s a real pain to keep talking to anyone on WordPress. Because – either they are becoming narrower – or the comment ends after the 10th comment – because it cannot be moved as a child. It is probably worth changing it to some other approach, more known from forums – where the number of comments and conversations as – answer to answer does not matter how many of them there are." Danishsard Candidates for Closure 43183 wp-comments-post.php endpoint support for OPTIONS Comments normal normal Awaiting Review enhancement new reporter-feedback 2018-01-30T17:13:04Z 2019-07-01T12:24:37Z "Under some circumstance we may need cross-posting from one domain to another (without the wp-json API). At least lets preflight requests flow normally https://github.com/WordPress/WordPress/pull/338 " drzraf Tickets Needing Feedback 36885 "When one uses custom callback function for comment list, ""Reply"" link would not show" Comments normal normal defect (bug) new reporter-feedback 2016-05-19T00:59:34Z 2019-06-04T19:37:59Z "It took too much time, but found the issue here in wp-includes/comments-template.php in get_comment_reply_link function. The OR conditions are likely to be true I imagine in many combination of situations although I am not too sure what combination causes bad things to happen. {{{ if ( 0 == $args['depth'] || $args['max_depth'] <= $args['depth'] ) { return; } }}} Well and good to check this, but why would the reply as well as login link disappear if any of it is true? Sorry if I am not getting this as I should. " remedy17 Tickets Needing Feedback 35503 "Dashboard page: comment status in ""Activity"" group box shows incorrect" Comments 4.4.1 normal trivial feature request new reporter-feedback 2016-01-17T21:54:34Z 2019-06-04T19:33:54Z "'''STEPS TO REPRODUCE''': log in (subscriber user), create new comment for post, log in (administrator user), approve comment on Dashboard page using ""Activity"" group box, click ""Approved (1)"", click ""Go back one page"" in browser. '''EXPECTED RESULT''': comment status - Approved '''ACTUAL RESULT''': comment status - Unapproved This problem was found in browsers Firefox 44.0b9, Chrome 47.0.2526.111 m" antonrinas Tickets Needing Feedback 34475 get_comment_link incorrect page number in returned url. SergeyBiryukov Comments 4.3.1 normal normal Future Release defect (bug) reviewing needs-unit-tests 2015-10-28T16:36:42Z 2019-10-03T22:15:05Z Since 4.3 core update the get_comment_link function returns incorrect page numbers for paginated comments. Have tried using default twentyfifteen theme with no plugins enabled and issue still persists. Property118 Tickets Needing Feedback 36564 Last Modified for Comments Comments 4.4 normal trivial Future Release enhancement new needs-unit-tests 2016-04-17T20:44:59Z 2017-02-12T10:37:16Z "Related #28463, #19495. Posts have a last modified and last modified gmt, but comments have no such thing. There are several proposals indicating a need for comment revision, or tracking when the comment is first created. Wanted to explore the idea of having last modified and last modified gmt stored as comment meta triggered by update_comment as a simple, low impact way of adding this feature that could be used by a variety of plugins. This could be implemented by plugin hooking to edit_comment, but if such a feature is to be useful, it needs a standard storage format." dshanske Tickets Needing Feedback 33735 Reduce Duplication and Improve Comment Notification Email Functions SergeyBiryukov Comments low normal Future Release enhancement reviewing needs-unit-tests 2015-09-04T22:55:04Z 2021-01-27T19:20:55Z "Had touched on this in #33587. wp_notify_postauthor and wp_notify_moderator have some duplicative code that could be eliminated and simplified. The functions for notification also lack a filter similar to the one for displaying the comment text. Proposing the function to show the comment in text form in the notification be separated out into its own function with a filter, and the default text be improved somewhat. " dshanske Tickets with Patches 40143 Comment template functions don't check for comment existence Comments normal normal Future Release defect (bug) new needs-unit-tests 2017-03-13T16:59:35Z 2024-02-08T16:10:20Z "Discovered during debugging an issue with Circle Lite theme, which uses [https://themes.trac.wordpress.org/browser/circle-lite/1.0.9/comments.php?marks=55#L42 comment_text( true )] in `kopa_comment_callback()` function. That, while being an invalid usage (the function treats `true` as a comment ID), causes an inconsistent behaviour, depending on the existence of the comment: * If the comment with ID 1 exists, the function returns its text, as expected. That's obviously not what the author of the theme intended, but still the correct behaviour of the function. * If the comment with ID 1 does not exist, the function returns the text of the current comment in the loop instead of an empty string. What happens is `get_comment( $comment_ID )` returns null (as expected), but then null is passed to `get_comment_text()`, which treats it as the current comment. After investigating more, it looks like most of comment template functions are either affected in a similar way or cause an undefined property notice when passed a non-existing comment ID. Let's bring some consistency here." SergeyBiryukov Tickets with Patches 36409 Comments number is wrong Comments normal normal defect (bug) new needs-unit-tests 2016-04-04T14:21:26Z 2019-06-04T19:35:47Z "Hi, the comment number return the number of approved comments, this means all approved comments even those are replies to unapproved comments, for example if a user post comment and people replied to it, then the admin decide to hide this parent comment by disapproving it, the comment number will decrease only by one and keeping counting the hidden replies So there are two option to fix that : 1. Hold/Disapprove all children when disapproving the parent. 2. Recalculate the comment number and excluding comments has an unapproved parent. Regards, Sidati" sidati Tickets with Patches 13792 Invalid reply link from comment admin when comment nested level > max Comments 2.9.2 normal normal Future Release defect (bug) reopened needs-unit-tests 2010-06-09T07:05:56Z 2017-07-31T16:17:39Z "I have a blog with nested comments enabled, max depth of 4. When the last level comment is posted, it no longer contains a Reply link. However, in the Comment admin, the Reply link is still present. If used, this new reply will show up at the very bottom of the comment list once posted (even if other newer regular comments are entered, this new reply will still show up at the very bottom). The bug is, basically, that Comment admin doesn't respect the max nested value." archon810 Tickets with Patches 45498 Wrong order of arguments in call_user_func() for Walker_Comment::start_el() SergeyBiryukov Comments normal normal Future Release defect (bug) reviewing needs-unit-tests 2018-12-06T16:52:14Z 2019-01-16T05:46:01Z "Arguments order for rendering all types of comments is `$comment, $depth, $args` except for the custom callback: `call_user_func( $args['callback'], $comment, $args, $depth );` This causes every custom callback to throw an error when you use `$args` and `$depth` as you'd expect. For example, `comment_reply_link()` inside callback can not be used like it's suppose to be used, like so: {{{#!php 'div-comment', 'depth' => $depth, 'max_depth' => $args['max_depth'], 'before' => '
', 'after' => '
' ) ) ); }}} You need to replace `$depth` and `$args`, like so: {{{#!php 'div-comment', 'depth' => $args, 'max_depth' => $depth['max_depth'], 'before' => '
', 'after' => '
' ) ) ); }}} " milana_cap Tickets with Patches 19739 Filters to allow comments on draft & trash post_status posts Comments 3.3 normal normal Future Release enhancement new needs-unit-tests 2012-01-04T19:01:18Z 2023-03-02T15:52:31Z "I'd like to use comments on draft posts as part of an editorial workflow. Will this be as easy as adding a filter to fire before the current comment_on_draft action that can be checked before exiting? I'll try that and add a patch if it looks good. Related #13276. Not relevant to #18630, I think." cyberhobo Tickets with Patches 41339 WP_Comments_Query::__construct() should allow a 'status__not_in' parameter Comments 4.9 normal normal Future Release enhancement new needs-unit-tests 2017-07-15T19:47:02Z 2017-07-30T15:24:18Z "`WP_Comments_Query::__construct()` (and hence, `get_comments()`) currently allows a `status` parameter to get comments with a specific status. It would be useful to also allow `$status__not_in` to exclude comments with specific stati. Related: #41338" pbiron Unpatched Bugs 60281 Cannot unset comment_notes_before Comments 3.0 normal normal Future Release defect (bug) new needs-unit-tests 2024-01-18T12:11:15Z 2024-01-18T17:02:39Z "I want to reorder comment fields by unsetting and setting them back in my chosen order. Here's my code: {{{ function my_reorder_comments_fields( $fields ) { $comment_notes_before_field = $fields['comment_notes_before']; $comment_field = $fields['comment']; $author_field = $fields['author']; $email_field = $fields['email']; $url_field = $fields['url']; $cookies_field = $fields['cookies']; unset( $fields['comment_notes_before'] ); unset( $fields['comment'] ); unset( $fields['author'] ); unset( $fields['email'] ); unset( $fields['url'] ); unset( $fields['cookies'] ); $fields['author'] = $author_field; $fields['email'] = $email_field; $fields['comment_notes_before'] = $comment_notes_before_field; $fields['cookies'] = $cookies_field; $fields['comment'] = $comment_field; return $fields; } add_filter( 'comment_form_fields', 'my_reorder_comments_fields' ); }}} Result - https://imgur.com/a/ebY1HBW You can see that `$fields['comment_notes_before']` remains on top. To prove the point, I changed my code to just unset all fields: {{{ function my_unset_comments_fields( $fields ) { unset( $fields['comment_notes_before'] ); unset( $fields['comment'] ); unset( $fields['author'] ); unset( $fields['email'] ); unset( $fields['url'] ); unset( $fields['cookies'] ); return $fields; } add_filter( 'comment_form_fields', 'my_unset_comments_fields' ); }}} Result: https://imgur.com/a/B5wNngj So `$fields['comment_notes_before']` isn't getting unset while all other fields do." bugnumber9 Unpatched Bugs 35805 Reverse page order in wp_list_comments() with newest comments first boonebgorges Comments 4.4.2 normal normal defect (bug) reviewing needs-unit-tests 2016-02-12T00:21:26Z 2019-06-04T19:34:45Z "Hey there, since wp 4.4 there were lots of bugs in the wp_list_comments()-function. Some of them are already fixed, now I found another one. If you change the comments order from default (oldest first) to newest first, the page order is wrong (reverse page order). == Example == You have 4 pages by sending following param you get these pages: {{{ page=1 -> 4 page=2 -> 3 page=3 -> 2 page=4 -> 1 }}} == How I call this function == Inside the post-loop I'm calling: {{{#!php
}}} And comments-content.php has following part: {{{#!php $cpaged, // Variable defined before, default: 1 'per_page' => 2 ) ); ?> }}} PS: In ticketing system the version 4.4.2 is not available :-)" Ninos Ego Unpatched Bugs 34110 WordPress Trackback Bug when Comment Pagination is Enabled Comments normal normal defect (bug) new needs-unit-tests 2015-10-01T11:40:36Z 2019-06-04T19:32:40Z "Hi, I just find a comment bug with wordpress which I think is there for a ling site, may be since v2.7+ but never actually fixed. '''Bug Details/ Reproduce process''' Inside your theme while fetching your comments after {{{ have_comments() }}} try to fetch comments only by using {{{ wp_list_comments( array( ""type"" => ""comment"") ) }}} and then below check if trackback exists and if they do print the trackbacks separately using {{{ wp_list_comments( array( ""type"" => ""pings"") ) }}} Now add a bunch of comments on any of your blog post which also have some trackbacks. Add more than 60 - 70 comments on that post. and from settings enable comment pagination option. So that comments get divided into several comment pages. If you are thinking this is never going to happen in real life, let me tell you I have blog posts which has more than 2.500 comments in it and none of them are spam comments. Now, after you enable the comment pagination, visit your blog page link i.e. example.com/some-post/ and you will see the trackbacks below your comments as it should show up now start navigation through your comment pagination, you will see the following - Trackback is showing on the normal blog post link Trackbacks also showing for /comment-page-1/ But when you will move further from comment page 1 you will only see the heading i.e. Trackback or whatever you have set, but not the actual trackbacks. This problem is also present in genesis theme, earlier I though it was a genesis bug but while developing a non genesis wordpress there I understood that it is actually a wordpress core bug." isaumya Unpatched Bugs 39566 WordPress ignoring previously approved comment for some comment authors rachelbaker Comments 4.7 normal major Future Release defect (bug) assigned needs-unit-tests 2017-01-12T15:41:04Z 2018-10-08T02:36:17Z "I seem to have a reproducible bug with the option ""Comment author must have a previously approved comment"". My client has a site that heavily uses guest commenting. They have selected the option ""...must have previously approved comment"". This works well most of the time, however more frequently some guests (identified by email) are being flagged as not having a previously approved comment even though they do. For one author (email) in question I am able to replicate this every time. - All other possible comment moderation disabled. - Comment as the guest in question, comment moderated. - Log in as admin, approve the comment. - Comment a second time as the guest, comment moderated again (shouldn't be) - Disable the option ""must have previously approved..."" - Comment a third time, now the comment is approved automatically. - Re-enable option ""must have previously approved..."" - Comment a forth time, the comment is moderated. This appears to be a bug to me, and I can reproduce it every time. Not sure how to troubleshoot this further from here." rperrett Unpatched Enhancements 20597 Allow WP_Comment_Query::query to filter by category Comments 3.4 normal normal enhancement new needs-unit-tests 2012-05-02T03:35:35Z 2019-06-04T19:23:03Z "The attached patch allows WP_Comment_Query::query to accept three additional arguments: * `cat` * `category__in` * `category__not_in` The resulting comments are then filtered by these category arguments as well as any other arguments. These arguments work the same way as their `WP_Query` counterparts. I would appreciate advice on the appropriateness of using `INNER JOIN` (as I have done here) to join in the taxonomy tables to the query." sambauers Unpatched Enhancements 39084 Introduce singular capabilities for managing individual comments Comments normal normal Future Release enhancement new needs-unit-tests 2016-12-04T22:14:50Z 2017-07-14T19:41:15Z "As we did in #35614 for taxonomy terms, singular capabilities should be introduced for approving, unapproving, spamming, unspamming, editing, and deleting individual comments. This would allow fine-grained cap checks such as current_user_can( 'edit_comment', $comment_id ) and current_user_can( 'approve_comment', $comment_id )." johnbillion Unpatched Enhancements 17020 Some comment queries are not filterable Comments 3.1 normal normal enhancement new needs-unit-tests 2011-04-02T16:56:32Z 2019-06-04T19:22:21Z "Although WP_Comment_Query::query() is fully filterable, some supplemental comment queries are still unfilterable. The submitted patch adds the following hooks: * function get_approved_comments() - query filter 'get_approved_comments_query' * function wp_dashboard_recent_comments() - query filter 'dashboard_recent_comments_query'" kevinB Tickets Needing Feedback 16365 Comment transition for new comments Comments 3.1 normal minor enhancement new needs-docs 2011-01-24T21:07:46Z 2019-06-04T19:22:11Z "As far as I can tell wp_transitions_comment_status() does not get called for new 'comments' based on my testing and review of comment.php in wp-includes. There is a similar transition for posts that gets called for new 'posts' including hooks like 'new_to_publish' and 'new_to_private'. I feel that there should be a similar hook to this form comments so that plugins can hook into new comments differently from comments moved from one existing status to another (like comment_unapproved_to_approved'." MattyRob Unpatched Bugs 40901 get_comments_number_text() third argument not used in certain situations Comments normal normal Future Release defect (bug) new needs-docs 2017-06-01T13:43:43Z 2019-06-21T13:02:54Z "`comments_number()` is a wrapper for echoing `get_comments_number_text()`. Reference: https://codex.wordpress.org/Function_Reference/comments_number The 3rd parameter's description: Text to display when there is more than one comment. % is replaced by the number of comments, so '% so far' is displayed as ""5 so far"" when there are five comments. This doesn't seem to work as expected. In particular, the parser doesn't look just for '%' but also for strings with spaces in front or behind this sign, after which it processes it in a illogical way. For example, this code {{{ ... }}} results in: `Read on 2 komentarze...` (""komentarze is a Polish translation of ""comments"", which is ok). Where's the ""so far"" string? Now another example with text before the % sign: {{{ ... }}} The result is bizarre: `Read on2 komentarze...` With some testing it seems that some strings passed as the 3rd argument are being kept, but it's totally illogical and requires review. If this is somehow intended, it should be explained in the Codex. So far, even the Codex example doesn't work as intended. I also checked that I'm not using any `comments_num*` filters. Workaround: use `get_comments_number()` with conditional code." eclare Tickets Awaiting Review 43695 $depth and $args are switched when using custom callback in wp_list_comments() Comments 4.9.5 normal normal Awaiting Review defect (bug) new has-patch 2018-04-05T05:55:31Z 2021-11-26T11:12:27Z "For the custom function I am using the [latest function from walker](https://github.com/WordPress/WordPress/blob/master/wp-includes/class-walker-comment.php#L343) as a base. When you use custom callback in comments.php template: {{{#!php 'comment', 'format' => 'html5', 'style' => 'ol', 'short_ping' => true, ]; // Use our custom callback if it's available if( function_exists( 'custom_render_comment' ) ){ $args['format'] = 'custom'; $args['callback'] = 'custom_render_comment'; } wp_list_comments( $args ); }}} The arguments that get passed to custom_render_comment function are switched: {{{#!php NULL [""max_depth""]=> string(1) ""5"" [""style""]=> string(2) ""ol"" [""callback""]=> string(21) ""faeiv2_render_comment"" [""end-callback""]=> NULL [""type""]=> string(7) ""comment"" [""page""]=> int(0) [""per_page""]=> int(0) [""avatar_size""]=> int(32) [""reverse_top_level""]=> bool(false) [""reverse_children""]=> string(0) """" [""format""]=> string(6) ""faeiv2"" [""short_ping""]=> bool(true) [""echo""]=> bool(true) [""has_children""]=> bool(true) } } var_dump($args): int(1) */ } }}} The result is this error: {{{ Warning: array_merge(): Argument #1 is not an array in [...]/wp-content/themes/mytheme/inc/render-comment.php on line 56 }}} I haven't found any mention of switching arguments in the WordPressCodex. The fix is easy, just switch those variables, but I think it should be addressed somewhere in the documentation." vincurekf Tickets Awaiting Review 52514 Admin dasboard load verry slow at some active plugins - WP Advanced Comment Comments 5.6 normal major Awaiting Review defect (bug) assigned has-patch 2021-02-12T19:23:20Z 2021-02-12T19:23:20Z Hello. When some plugins are active, it takes very long to load the main dashboard and the query times are very long. Example, wp advanced comment. Take a look on fresh install wordpress and activate this kind of plugins. attosoftonline Tickets Awaiting Review 57513 All the comments not showing properly in edit posts Comments normal normal Awaiting Review defect (bug) new has-patch 2023-01-20T10:27:56Z 2023-01-20T10:27:56Z "We have found that not all comments load when show more comments click on edit post. e.g. Consider there are 23 post comments in one post then if we click on show more posts then after showing 20 posts button will hide 3 left comments not be shown. Please check the below screenshot. Edit Post: https://share.cleanshot.com/VjDCLQ9XLvcvXg65qPHd Comment list: https://share.cleanshot.com/rVrLqjFdLK6YzBznPzmG" aniketpatel Tickets Awaiting Review 40164 Apace HTTP 414 error on deleting comments in bulk Comments 4.7.3 normal normal Awaiting Review defect (bug) new has-patch 2017-03-15T15:41:13Z 2017-03-15T21:23:12Z "Bit of an edge case, but I just had to delete 3000 comments from a WP site I took on and I was doing them in 200's (so not to over run the server and so I can check for any legitimate comments). Doing this, the first 200 comments were ""spanmmed"" fine, but then you do the next 200, it generates a 414 error as the url becomes something like: {{{ /wp-admin/edit-comments.php?s=&comment_status=moderated&pagegen_timestamp=2017-03-15+15%3A31%3A06&_total=200&_per_page=200&_page=1&paged=1&_ajax_fetch_list_nonce=ef4afc8347&_wp_http_referer=%2Fnew-site%2Fwp-admin%2Fedit-comments.php%3Fcomment_status%3Dmoderated%26paged%3D1%26spammed%3D200%26ids%3D814%2C365%2C2177%2C813%2C2021%2C812&_wpnonce=461233332d&_wp_http_referer=%2Fnew-site%2Fwp-admin%2Fedit-comments.php%3Fcomment_status%3Dmoderated%26paged%3D1%26spammed%3D200%26ids%3D814%2C365%2C2177%2C813 }}} Basically for every process it duplicates the url and if you have 100+ ID's in each request, it passes a really long url string 1) Is there a reason why all the comment ID's are passed to the url? 2) Can this be amended so in edge cases, so the 414 error isn't generated as it can and will frustrate some people." garethgillman Tickets Awaiting Review 49869 Apply comment field filters to backend Comments normal normal Awaiting Review defect (bug) reopened has-patch 2020-04-10T16:21:27Z 2024-03-07T01:13:41Z "Recently, I had to work on an internally consuming WP project. I am a bit surprised how WP filters are mainly affecting only visual side, instead of applying to backend functions. so, for example: {{{ add_filter('comment_form_default_fields', 'website_remove'); function website_remove($fields) { if( isset($fields['url']) ) unset($fields['url']); return $fields; } }}} it only removes 'url' input field from output of comment form. So, what is the point of that, if it can be simply achieved by css `display:none`. ? the intention is clear, that it should REMOVE ""url"" parameter from comment system at all. However, at this moment, even if people use 'comment_form_default_fields' filter to remove `url`, it is almost meaningless - anyone in front-end form can just insert `url` field (i mainly say bots, but also typical user can just insert ""url"" parameter in browser ""inspect element"") and submit form and in backend, in `wp-includes/comment.php :: wp_handle_comment_submission` still accepts the `url` field. In parallel of the fact that WP advocates ""never trust user input"", the filters should be applied firstly and mostly to backend functions in my mind. I firmly reckon that the filters (in any other WP form too) should be applied in both front-end and back-end functions for same parameter. So in backend, the same filter should be applied to comment fields ( in `wp-includes/comment.php :: wp_handle_comment_submission`): {{{ $comment_data = apply_filters('comment_form_default_fields', $comment_data, true); }}} the third parameter is indication whether the filter is in BACK-END (true) or FRONT-END (false). So, in front-end output of comments (`wp-includes\comment-template.php`, function `comment_form`) the filter can now be: {{{#!php * Validation errors: 200. I agree completely w/bpetty. This isn't a 4xx error: the request was understood and the client received a response. I don't think this is right. Sure the request was understood, but it was understood to be incorrect. Should they not be 400 (Bad Request)? The argument against 400 was this [https://core.trac.wordpress.org/ticket/11286#comment:21 comment]: > The HTTP Specification says that 400 is for when ""the request could not be understood by the server due to malformed syntax"". So whilst this might be an appropriate response for invalid inputs (e.g. bad email address), I don't think it should be used in wp-includes/comment.php for duplicate comments and comment flooding. There 403 is more appropriate. Nothing here specifically arguing against using 400 for invalid fields. Also, more recently the REST API sends 400 status code responses in `\WP_REST_Comments_Controller::create_item()` for these errors: * `rest_comment_exists` * `rest_invalid_comment_type` * `rest_comment_content_invalid` * `rest_comment_author_data_required` * `comment_author_column_length` * `comment_author_email_column_length` * `comment_author_url_column_length` * `comment_content_column_length` * `comment_flood` The exceptions are `comment_duplicate` which returns [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/409 409] (Conflict), and the generic DB error `rest_comment_failed_create` which returns with a 500 error code, as expected. For the length errors, a [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/413 413] (Payload Too Large) code may be more specific. Also, for comment flooding, what about the status [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429 429] (Too Many Requests)? The REST API should perhaps be updated to use this instead of 400. All this to say, to align with the REST API the comment form submission errors should use 400+ error codes instead of 200." westonruter Tickets Awaiting Review 46713 Comment reply link uses inconvenient eventlistener Comments 5.1 normal normal Awaiting Review defect (bug) new has-patch 2019-03-29T09:04:48Z 2023-06-17T02:01:37Z "When comment-reply.js was rewritten recently the behavior of the reply-button changed. It now seems to use 'touchstart' as eventlistener which makes it really ""touchy"" to use on mobile. It's almost impossible to use scroll now since you always trigger the touchstart event which opens the reply-box." szandman Tickets Awaiting Review 40293 Comment template - warning Comments 4.8 normal normal Awaiting Review defect (bug) new has-patch 2017-03-29T07:15:59Z 2017-10-11T11:29:50Z "Hi, in the `comments_template` function, you are entering a divide-by-zero condition at line '''1379''' of the `wp-includes/comment-template.php` file. The line described above is like this. {{{#!php }}} I believe this will solve. {{{#!php }}} I'm using a default install with theme Twenty Seventeen. Thank you!" victorfreitas Tickets Awaiting Review 46963 Comments meta box offset bug for custom comment types Comments normal normal Awaiting Review defect (bug) new has-patch 2019-04-17T13:13:39Z 2019-04-30T09:57:56Z "There is a conflict in the 'comments' meta box when used in combination with custom comment types. The `Show more comments` link loads duplicates, without an offset due to this line of code: https://github.com/WordPress/WordPress/blob/72979b167d913bf49745fa737654bdf6d13168de/wp-admin/js/post.js#L99 {{{ this.st = jQuery('#the-comment-list tr.comment:visible').length; }}} For custom comment types, the `comment` class may not exist. See how comment classes are generated here: https://github.com/WordPress/WordPress/blob/03240dd3f4442546562824bc6a10ed7c197bd6b2/wp-includes/comment-template.php#L466 {{{#!php comment_type ) ) ? 'comment' : $comment->comment_type; }}} You can see an example of this with WooCommerce which uses a comment type named 'review' (https://github.com/woocommerce/woocommerce/issues/23313). Because the comments out output without the `comment` class and instead they have a `review` class, the JS code fails to set the correct offset. Possible solutions: - Output `comment` class for custom comment types in addition to their custom class. - Revise jquery selector to be more generic e.g. count the `tr` elements instead." mikejolley Tickets Awaiting Review 60161 Comments on pages where comments are not allowed Comments 6.4.2 normal normal Awaiting Review defect (bug) new has-patch 2023-12-28T10:15:28Z 2024-02-15T08:26:09Z Recently I’ve had comment moderation requests on a site where comments are not allowed (both in the Settings > Comments and in the page Settings). I don’t know how these comments are submitted. The targetted page is the Privacy Policy page. is0ph Tickets Awaiting Review 58058 Fix PHP open and close tag placement in /wp-admin/comment.php LineNo 175 Comments normal normal Awaiting Review defect (bug) new has-patch 2023-04-02T10:55:40Z 2023-04-02T16:29:51Z This PR fixes a PHP open and close tag placement issue on line 175 of the WordPress file /wp-admin/comment.php. The original code embeds a multi-line PHP snippet within an HTML block, but the PHP open tag is not on a line by itself. The updated code moves the PHP open tag to a new line so that it is on a line by itself, as required by best practices. This improves the readability and maintainability of the WordPress core codebase. moinrrahmed Tickets Awaiting Review 58014 Invalid Post ID when updating a comment in editing Comments 6.2 normal normal Awaiting Review defect (bug) new has-patch 2023-03-29T19:10:59Z 2023-04-04T16:23:33Z "== Bug Report === Description Invalid Post ID when i update a comment Content of the post: the comment made in front-end on a lorem post created by hand no feature image. Content of the comment: A test is when you are made to make little drawings to see if you are not crazy. I just try to add the word: ""Really"" at the end of the comment === Environment - WordPress: 6.2 - PHP: 7.4.1 - Server: Apache/2.4.43 (Unix) - Database: mysqli (Server: 8.0.16 / Client: mysqlnd 7.4.1) - Browser: Chrome 111.0.0.0 (Linux) - Theme: Twenty Twenty-Three 1.1 - Language : FR - MU-Plugins: None activated - Plugins: * WordPress Beta Tester 3.3.7 === Steps to Reproduce 1. Go to `Posts > Add New` and create a new post. 2. On the frontend, add a comment. 3. Click `Edit`. 4. Add a word. 5. Click `Update`. x. 🐞 Bug occurs. === Expected Results 1. ✅ The post must be updated and the word added. === Actual Results 1. ❌ I have the error message : **Invalid Post ID** 2. ❌ Checking the content after the error. The content has not changed." wplmillet Tickets Awaiting Review 58544 Need to verify safe website URL in comment form Comments normal normal Awaiting Review defect (bug) reopened has-patch 2023-06-15T12:18:00Z 2023-06-21T20:50:17Z "Hello, We need to verify the website URL in the comment form and It should be safe before inserting into the database." hiren1094 Tickets Awaiting Review 55891 "Please add an action for additions within the ""comment-metadata"" div" Comments 6.0 normal normal Awaiting Review defect (bug) new has-patch 2022-06-01T09:06:43Z 2023-10-04T12:49:19Z "I would like to add additional data to the "".comment-metadata"" div, and there is no way to do that. If I want to display the extra info for admins only, I can use the 'comment_text' filter, but that's a nasty hack, and obviously only shows up for users who are able to edit comments, so it doesn't help the general case. I suggest adding an action just before or just after the call to edit_comment_link in class-walker-comment.php around line 460 (and also 360?)" jwz Tickets Awaiting Review 60475 Possible incorrect type for $comment_id in get_comment_author filter Comments 6.0 normal normal Awaiting Review defect (bug) new has-patch 2024-02-08T15:44:40Z 2024-02-21T11:41:00Z "After r52818 the `$comment_id` param of the `get_comment_author` filter, which is [https://core.trac.wordpress.org/browser/trunk/src/wp-includes/comment-template.php?rev=56687#L47 documented as numeric string], may be an `int`, in case a non-existing comment ID is passed to the `get_comment_author` function. The topic has been briefly discussed in https://core.trac.wordpress.org/ticket/54379#comment:8 mentioning that the numeric string type is here for compatibility. I'm attaching a patch containing a fix for the issue, as well as a PHPUnit test demonstrating the behaviour." david.binda Tickets Awaiting Review 57615 Various comment functions reporting error when `get_comment()` returns `null` Comments normal minor Awaiting Review defect (bug) new has-patch 2023-02-02T21:14:08Z 2023-03-08T16:06:06Z "While working on #53290 I noticed that if the function `get_comment_author_link()` is called with no value passed into it or if an invalid comment ID is passed into the function an error is thrown on the return filter: {{{ Trying to get property 'comment_ID' of non-object wp-includes/comment-template.php:242 }}} While gathering information to report this I also noticed several other functions in the same file, `wp-includes/comment-template.php` will suffer from the same or a similar issue: + `comment_author()` + `get_comment_author_email()` + `comment_author_email()` + `get_comment_author_IP()` + `comment_author_url()` + `get_comment_excerpt()` + `comment_excerpt()` + `get_comment_type()` Some of the functions in this file, `get_comment_author()` for example, store the comment ID as a variable and pass that into the return filter: `$comment_ID = ! empty( $comment->comment_ID ) ? $comment->comment_ID : $comment_ID;` I'm currently working on writing tests since most of the functions I'm mentioned don't have existing test coverage. I'm also uploading a patch with my proposed solution. If this seems like the right direction to go I'll add changes to the remaining functions and update the patch (and tests)." thomasplevy Tickets Awaiting Review 48027 WP_Comment fields (e.g. user_id) have wrong types Comments normal minor Awaiting Review defect (bug) new has-patch 2019-09-12T09:37:44Z 2019-09-16T04:27:51Z "WP_Comment objects retrieved e.g. with get_comment have wrong types for some member variables, e.g. user_id. Example: {{{#!php class TestInsertBug extends \WP_UnitTestCase { public function test_insert() { $comment_id = wp_insert_comment( [ 'user_id' => 1, ] ); $comment = get_comment( $comment_id ); // will fail because $comment->user_id is a string $this->assertSame( $comment->user_id, 1 ); } } }}} The constructor of WP_Comment just applies the data to the variables, without setting/fixing the types (as e.g. WP_User does for the ID)." cneumann Tickets Awaiting Review 41826 WP_Comment_Query can generate negative offset in LIMIT clause Comments 4.9 normal normal Awaiting Review defect (bug) new has-patch 2017-09-07T11:40:49Z 2017-09-08T19:03:35Z "The {{{paged}}} argument in {{{WP_Comment_Query}}} was introduced in #38268 There's a problem with the {{{paged}}} as 0 case. '''Example:''' When the {{{paged}}} is 0 and {{{number}}} is 2, {{{WP_Comment_Query}}} generates the LIMIT clause: {{{ LIMIT -2, 2 }}} instead of {{{ LIMIT 0, 2 }}} According to the MySQL documentation, the offset in the LIMIT clause shouldn't be negative: https://dev.mysql.com/doc/refman/5.7/en/select.html I think we should handle it in the same way as in {{{WP_Query}}}, where the 0 case is treated as the default, that is 1. " birgire Tickets Awaiting Review 56499 count() used in the loop condition Comments lowest normal Awaiting Review defect (bug) new has-patch 2022-09-02T12:40:53Z 2022-09-21T15:22:51Z The use of count() inside a loop condition is not allowed; assign the return value to a variable and use the variable in the loop condition instead. krunal265 Tickets Awaiting Review 53639 "Ability to add checkboxes to ""Email me whenever"" section" Comments normal normal Awaiting Review enhancement new has-patch 2021-07-10T14:50:22Z 2022-06-02T11:26:29Z "In wp-admin > Settings > Discussion, there is a section ""Email me whenever"". The 2 options in this section are: - Anyone posts a comment - A comment is held for moderation There's currently no way for a plugin to add more checkboxes to this list." henry.wright Tickets Awaiting Review 39505 Add an option to add custom classes to comment_reply_link() Comments 4.7 normal normal Awaiting Review enhancement new has-patch 2017-01-06T14:08:03Z 2017-01-06T18:45:38Z In many cases, I want to add custom classes to comment reply link. I can use js or handle comment link string. But it's better if have an option to add custom classes to link via PHP. truongwp Tickets Awaiting Review 44485 Allow some functions from comments-template.php to accept a comment or post ID Comments normal normal Awaiting Review enhancement new has-patch 2018-07-01T14:11:57Z 2018-07-01T14:11:57Z "Nowadays, it's not uncommon to have to use some templating functions outside of the loop. Most of them already accepts a comment or post ID (get_permalink, ...). But, that's not the case for some functions related to comments. I did a small update of the file to allow that." tristanleboss Tickets Awaiting Review 57106 Allowing comment form error pages Comments normal normal Awaiting Review enhancement new has-patch 2022-11-14T14:27:08Z 2022-11-14T15:21:43Z "Current status quo: As of now, it is not possible to have customized a customized validation for forms (covered in #57105 ) And every single error will either end in a wp_die() or an exit. Proposal: Instead of always ending in `wp_die()` we could forward to the referer page, including the error_message and the $_POST data, to prefill the form (especially with the comment, since these would be really painful if lost). `comment_form()` would require an enhancement to show errors. This idea is still in progress, I'll provide a working proof of concept later, but I wanted to open this for discussion. Note: Will also need some kind of representation for the Rest API." apermo Tickets Awaiting Review 39133 Check email length in is_email() Comments 4.8 normal normal Awaiting Review enhancement new has-patch 2016-12-07T05:38:44Z 2020-07-17T14:50:12Z "In reference to this ticket - https://core.trac.wordpress.org/ticket/38506#comment:12 It would be better to check email length within the is_email() itself instead of validating it at various other places. " PranaliPatel Tickets Awaiting Review 54473 Comments listing screen in wp-admin doesn't expose if a comment was left by a logged in user Comments normal normal Awaiting Review enhancement new has-patch 2021-11-19T05:34:17Z 2021-11-20T00:26:35Z "When viewing wp-admin/edit-comments.php it's not possible to determine if comments are being left by an ""anonymous"" user, or by a logged in user, despite this being stored in the comments table. This is particularly useful for Sites where users need to be logged in to comment, or for sites with public registration enabled (such as WordPress.org). Using #meta5485 as an example, spammers can register and then leave spam comments on posts, but it's not immediately visible what their user login is, or have any link to their profile - Having a link directing the moderator to the users profile, in addition to being able to spam just the comment, would be greatly beneficial for those use-cases. There's already a bit of information overload on the comments listing author section, so perhaps for logged in users the information shown might be able to be adjusted/minified/etc. There might not be any reason to display the Email address for example." dd32 Tickets Awaiting Review 41110 "Display full content of ""Pending"" comment on WP Dashboard" Comments 4.8 normal normal Awaiting Review enhancement new has-patch 2017-06-21T05:42:37Z 2017-06-21T06:23:25Z """Recent Comments"" widget in WP dashboard displays a list of Pending and recent comments. A ""Pending"" comment has all the action items - approve, reply, edit, trash, spam. But, these items are of no use, because the complete comment text is not visible. It will be good to display the full content of the ""Pending"" comments. OR Add a toggle to display the full content without having to go to ""Comments"" page. " puneetsahalot Tickets Awaiting Review 57314 Update all references to wp/v2 to namespace field in class-wp-rest-comments-controller.php Comments normal normal Awaiting Review enhancement reopened has-patch 2022-12-11T18:11:02Z 2022-12-12T11:17:55Z This is a very minor change to make it easier for other classes to extend this class and define their own namespace. ihenetudan Tickets Awaiting Review 58156 finetune wp_update_comment_count Comments normal normal Awaiting Review enhancement new has-patch 2023-04-19T05:42:00Z 2023-07-08T22:20:01Z "there is a @todo in {{{function wp_update_comment_count}}} and I see no reason for not changing the code, which would make it a bit more effective. current: {{{#!php if ( $do_deferred ) { $_deferred = array_unique( $_deferred ); foreach ( $_deferred as $i => $_post_id ) { wp_update_comment_count_now( $_post_id ); unset( $_deferred[ $i ] ); /** @todo Move this outside of the foreach and reset $_deferred to an array instead */ } } }}} new: {{{#!php if ( $do_deferred ) { $_deferred = array_unique( $_deferred ); foreach ( $_deferred as $i => $_post_id ) { wp_update_comment_count_now( $_post_id ); } $_deferred = array(); // for clarity, it is not even needed } }}}" Presskopp Tickets Awaiting Review 18630 Custom Comment Validation Error Comments 3.3 normal minor Awaiting Review feature request new has-patch 2011-09-09T19:49:33Z 2022-07-15T15:49:43Z "One of the things that bugs me about WordPress is not being able to customize the wp_die() function that is called on comment form validation. I have seen some people sugget core hacks, eek. I'm hoping that a hook is added to allow overriding of the default wp_die(). Maybe even a new template file wp_error.php that would be called first. I haven't found a lot of discussion on this in trac just #11286 and #10551" bandonrandon Tickets Awaiting Review 52283 Reply to comments via emails Comments normal normal Awaiting Review feature request new has-patch 2021-01-12T17:51:17Z 2021-02-02T08:18:11Z "Following up the discussion I had with @AudrasJB about exploring this interesting feature (I understood it was discussed during latest development chat), here are the results of my searches/tests. ==== WordPress Core’s Post via email feature ==== [[Image(https://cldup.com/PdoTXB08-2.png)]] First, I remembered WordPress was including this feature: the first thing I did was testing it! NB: in order to test emails, I’ve set my local [https://gist.github.com/loziju/66d3f024e102704ff5222e54a4bfd50e Postfix configuration to use Gmail] as a relay). === My thoughts about the feature:=== 1. I was surprised we need to visit `site.url/wp-mail.php` to get the mails. I was expected a WP Cron task to be scheduled. 2. Sending an email with Gmail to the mail server is adding a post with a title but without content. 3. The `POP3()` class (in `src/wp-includes/class-pop3.php`) could enjoy some improvements and possibly use [https://www.php.net/manual/en/book.imap IMAP functions] if available into the WordPress server config. ==== Introducing a Comment via email feature ==== For the rest of this ticket, please note I chose a specific use case to run my tests: **Replying to a post author notification**. I believe this notification is a good first candidate for the feature, as post authors are not any given user of the site: the site has their emails and **we can control the post author email before inserting the comment reply to avoid the spam risk**. === Identifying the incoming email is a reply to a comment === I’ve explored if there was an email header available to transport some information from the post author notification to the reply sent to the Mail server used by the WordPress site. The only one available seems to be the `References:` one. [[Image(https://cldup.com/L5sdLdl4Sr.jpg)]] The format of this reference must be like this `<.*@site.url>`. Most of the time, we’ll get this reference and will be able to use it most of the time (75% according to my tests). So I’ve edited the `wp_notify_postauthor()` function to include references about the author, post and comment and override the `Reply-To:` header so that replies are sent to the WordPress mail server (the one we can set into the Settings > Writing > Post via email section). For the references, I tried to use a meaningful format, just like GitHub does: `` === Extracting the comment reply interesting parts === This is the most difficult part of the feature. Some information are available into the reply email headers but we need to extract the content of the reply out of the email body (mostly multipart) and only it. It will require a lot of tests with different Email Softwares & Online services because there’s not a standardized way of delimiting the reply. I’ve tested with Apple Mail, Gmail (online), Outlook (online), GMX (online). I’ve looked for already existing parsing script on GitHub and found, to ease the job: - [https://github.com/daniele-occhipinti/php-email-parser Plancake Email Parser] (GPLv3) - [https://github.com/willdurand/EmailReplyParser EmailReplyParser] (MIT License) - [https://github.com/zbateson/mail-mime-parser MailMimeParser] (BSD 2-Clause “Simplified”) For my tests, I’ve decided to go with Plancake, even if I had to edit some parts of it, it was pretty easy to use. Using it, I was able to easily extract: - The author email (`From:` header) - The references about the author, the post, and the parent comment (`References:` header) - The reply date (`Date:` header) The only issue was with Apple Mail: the references are broken the site URL part is missing, so I had to fallback on the comment permalink (included into the quoted comment below the reply) and use a Regex to extract the parent comment permalink and validate this parent comment, the post and the author. For the body content, I was able to easily extract the plain text content of multipart emails or recreate it for `text/html` only emails (eg: GMX) using the `wp_kses()` function. But then, I had to use some complementary Regex to only get the reply text. My first target was the real `smtp.sender` email that is used by every tested Email services (Gmail, Apple Mail, Outlook, GMX) to inform when and by who the comment was made. As we don’t know what's the smtp.sender for sure (in my case it’s the Email I use to relay localhost to Gmail), I’ve used a Regex to search for **<**`emailformat`**>**. If not found I fallback to the first line of the quoted notification that looks like `> some translated text ""Post Title""`. Finally I’m looking for more than two hyphens (usually used over the email signature) or underscores (used by Outlook). All this is done into the `src/wp-mail.php` before the code used to post via email for simplicity. So if you plan to apply the attached patch to test, you’ll need to go to this url `site.url/wp-mail.php` to fetch commment replies made via emails. It’s working ! [[Image(https://cldup.com/w64Mz6V_cv.jpg)]] === My thoughts about the feature: === - It’s a great way to improve/promote try to bring back more conversations into WordPress comments - We should probably use 2 different Mail Server accounts if it is used to Post via email to take no risk a comment content might be wrongly used to create a post and vice versa. - According to the above point, an option to activate the feature could be added to the Discussion settings. Into the patch, I’m using a filter. - We should use a scheduled WP Cron Job to fetch emails. - We could take this opportunity to improve the `POP3()` class, I’ve tested IMAP functions and it’s easing the way to extract email parts (See [https://www.php.net/manual/en/function.imap-fetchbody.php imap_fetchbody]) - We should provide support the feature completely for post author notifications focusing on code to extract the comment content from emails and to insert comments. - We should include hooks to make it possible to use services like JetPack, Mailgun, Sendgrid or any other ones for huge site needs. The attached patch is there to have a first proof of concept. It should be improved. Thoughts, feedbacks & patch improvements are very welcome. 👋" imath Tickets Needing Feedback 17913 Site-level comment options may override individual post settings. Improve help/docs. Comments normal normal Future Release enhancement new has-patch 2011-06-27T20:46:43Z 2019-11-18T18:11:40Z "Post comments may be automatically closed for a site's posts if site option 'close_comments_for_old_posts' is true and the post was published before 'close_comments_days_old' days ago. These two options are set in options-discussion and override the 'comment_status' of an individual post. The edit posts screen's comment meta box displays comments open/close status, allowing publishers to open or close comments for a single post. It's possible the site-level discussion settings will override the individual post yet we still might display a different post comment status than the site settings allow. 1. Enable site-level option to close comments on articles ( wp-admin/options-discussion.php#close_comments_for_old_posts ) 1. Enter a days value of 1 for maximum impact 1. Edit a post published over a day ago 1. View the Discussion meta box ( #commentstatusdiv ) 1. Interact with the 'comment_status' field I would like to better communicate expected failure and let the post author or editor know this particular setting has been overridden at the site options level. If the current user can manage options I might you could link to the override in the options page. I created a new test blog, set comments to auto-close after a day, and checked allow comments in the post screen. I was wondering why comments_open() was false for the post when I was looking at a checked box on the post screen." niallkennedy Tickets Needing Feedback 36424 graphically visualize if comments are closed (in wp-admin/edit.php) Comments normal normal Future Release enhancement new has-patch 2016-04-06T08:08:36Z 2018-03-12T17:02:29Z "it would be nice if the pages or posts list would not only show the number of comments per page but if it also could show a symbol if comments for this particlar page or post are closed. proposal: - the lock symbol https://developer.wordpress.org/resource/dashicons/#lock - or https://developer.wordpress.org/resource/dashicons/#edit combined with a kind of ""forbidden"" sign/strike, similar to https://developer.wordpress.org/resource/dashicons/#hidden " pixelverbieger Tickets Needing Feedback 16252 Allow comment reparenting to fix poor threading Comments normal normal Future Release feature request new has-patch 2011-01-15T23:12:25Z 2023-11-23T06:26:37Z "For the OCD among us, it would be super nice to be able to edit the comment_parent, to properly thread comments made in the wrong place/threading order. Choose your own UI, but even just a numeric editor in the Quick Edit area would be a huge enhancement." Otto42 Tickets with Patches 46017 """Mine"" comment count isn't updated when replying to or moderating a comment." Comments 5.1 normal normal Future Release defect (bug) new has-patch 2019-01-17T02:59:49Z 2019-01-24T04:40:53Z "To reproduce: - Visit `/wp-admin/edit-comments.php`. - Click Reply on a comment. - Type some text in the comment, click Reply. The ""All"" and ""Approved"" counts update as expected, but the ""Mine"" count doesn't." pento Tickets with Patches 12104 'moderate_comments' capability by itself should grant the user the permission to See/Edit all comments from the Comments menu. Comments 3.0 normal normal Future Release defect (bug) new has-patch 2010-01-31T22:25:24Z 2021-11-08T19:10:31Z "I tried to create a Comment Moderator role today and realized it wouldn't work. My intention was to create a role for people who can't write or edit posts, but can keep an eye on the comment threads. I created the role like so: {{{ #!php add_role('moderator', 'Moderator', array( 'read' => 1, 'moderate_comments' => 1, )); }}} ... then created a new user with that role. When I logged in as my test user, I realized that it was for all intents and purposes a Subscriber. I couldn't see any admin panels but the Dashboard, my profile, and the Tools. I went poking around in edit-comments.php and discovered that it's checking for another capability altogether: {{{ #!php if ( !current_user_can('edit_posts') ) wp_die(__('Cheatin’ uh?')); }}} I double-checked wp-admin/includes/menu.php and it agreed that 'edit_posts' was the minimum capability to see this page, so I tried adding 'edit_posts' to my new role, and I still couldn't get there. Later on in edit-comments.php, when actually trashing a comment, there is a check for 'moderate_comments', but it's a moot point: this screen doesn't even show up in the admin menu, and if you navigate directly to it, you'll get the ""You do not have sufficient permissions to access this page"" message. I thought it was entirely possible I'd missed some finer point of creating roles, so I redid it with Justin Tadlock's excellent Members plugin, and that didn't work either. This behavior might be intentional, but if so, I'm not following the logic. I know roles are due for an overhaul in the next version or two." sillybean Tickets with Patches 40319 Apostrophe in commenter's name prevents comment_whitelist setting from working. Comments 4.0 normal normal Future Release defect (bug) new has-patch 2017-03-30T18:30:04Z 2020-03-20T05:26:22Z "If a commenter has an apostrophe in their name, and they have a previously approved comment, and the comment_whitelist setting is enabled (""Comment author must have a previously approved comment""), the commenter's comment will always end up in moderation. The cause of this can be traced to r38738. If the name has an apostrophe, it will be slashed; the author name was previously included directly in the SQL, with the slash properly escaping the apostrophe, but when the query was updated to use `prepare()`, the author name was not unslashed. Affects 4.7, 4.7.1, 4.7.2, 4.7.3, and trunk. I've attached a patch that addresses the issue by unslashing the two `expected_slashed` parameters." cfinke Tickets with Patches 54149 Audit `get_comment()` response checks. hellofromTonya Comments 5.9 normal normal Future Release defect (bug) assigned has-patch 2021-09-21T02:14:44Z 2022-09-27T16:55:50Z "There are currently 164 calls to `get_comment()` across 36 files in the codebase (see attached file), with more pending with at least one upcoming PR. Some of these calls check the response of `get_comment()` in one of the following ways: {{{#!php comment_ID ) {... if ( ! empty( $comment->comment_ID ) {... }}} Some do not check the response at all. A [https://wordpress.slack.com/archives/C02RQBWTW/p1630738445035900 discussion on Slack] between myself and @jrf led to the suggestion that we audit the use of `get_comment()`. @hellofromtonya suggested two alternative checks on the response: {{{#!php PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability ""edit_post"" against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /wordpress/wp-includes/functions.php on line 3827 Ideally, `WP_Comment_Query` should bypass comments associated to non-existing post types as well. In the attached patch I've introduced both `post_type__in` and `post_type__not_in` which accepts an array of post type string names. I've also added the default value for `post_type__in` to `get_post_types()`, as by default you'd never want to query for non-existing data any way, but this allows the query to be overwritten via filters, or directly with a new construct for those who have the need. I am wondering if the use of `post_type = 'any'` would need to short-circuit the new arguments to avoid breaking BC (current tests all pass with the patch applied though) ? Related #16956 What this looks like (from #34918): [[Image(http://crosseyedeveloper.com/wp-content/uploads/2015/12/commentcap.jpg)]] It also shows up on the Dashboard in the comments widget: [[Image(http://crosseyedeveloper.com/wp-content/uploads/2015/12/commentcap21.jpg)]]" Clorith Tickets with Patches 35501 "Dashboard page: incorrect work of ""Activity"" group box bottom counters" adamsilverstein Comments 4.4.1 normal normal Future Release defect (bug) assigned has-patch 2016-01-17T21:22:17Z 2019-01-10T22:26:26Z "STEPS TO REPRODUCE Create new post, add comment through front end, go to dashboard page, click showed up menu items Approve/Unapprove/Spam/Trash in different combinations: - click ""Approve"" and quick click ""Trash"", - click ""Unapprove"" and quick click ""Trash"" - quick click ""Approve"" twice EXPECTED RESULT: bottom counters ""All"", ""Pending"", ""Approved"", ""Spam"", ""Trash"" counts correct. ACTUAL RESULT: see attachment." antonrinas Tickets with Patches 26596 Edit comments from wpAdmin don't process well radio button fields Comments 2.7 normal normal defect (bug) new has-patch 2013-12-13T08:38:04Z 2019-06-04T19:24:43Z "I'm filtering for 'wp_comment_reply' to add a custom radio button selector in the wpAdmin comments. Then the ajax request don't send this field value, always send the last one, checked or not. wp-admin/js/edit-comments.js process all INPUT fields as a text (except type button) I attach the patch to allow radio buttons but doesn't works for checkbox." corretge Tickets with Patches 11248 Paged wp_list_comments() should always output something boonebgorges Comments 2.9 normal normal defect (bug) assigned has-patch 2009-11-24T06:00:23Z 2019-06-04T19:21:40Z "Enable comment paging on your blog and visit `http://yourblog.com/a/single/post/comment-page-999999/`. Note no comments will be displayed. There's situations where the comment form will redirect you back to the wrong page (for example if you mess with the type parameter and exclude pings). The Walker should detect if there's no comments to be displayed on the requested page and if that's the case, then display the latest page that actually has comments." Viper007Bond Tickets with Patches 22301 Performance problem with Recent Comments widget Comments 2.8 normal normal defect (bug) new has-patch 2012-10-29T06:07:14Z 2019-06-04T19:23:37Z "When a comment is posted (or the status of a comment changes), the `widget_recent_comments`cache item is invalidated, which the Recent Comments widget uses to populate the widget content. On the next widget display, it will call `get_comments()` to repopulate the cache. The problem occurs when you have a very large number of comments, the MySQL query will use the `(comment_approved, comment_date_gmt)` index, but if MySQL has to scan too many rows in an index, it'll switch to table scan instead. As the `comment_approved` column is mostly the same value, this will almost always happen. This is compounded by the query occurring on every page load until the cache is re-populated - if the query takes 60 seconds to run, there could potentially be hundreds of instances of the same query running. So, we need a solution that either hides or eliminates how slow this query can be, and only runs it (at most) once per new comment. After discussing this with @matt, we have a couple of ideas: 1. Move this query to a `wp_schedule_single_event()` call, which has the bonus of ensuring only one is scheduled at any given time. The downside is that it may cause the cache to be outdated on a low traffic site. 2. Keep a queue of recent comments in cache, and push a new one onto the queue when posted. This avoids the query entirely, but there would be a race condition if two comments were posted at nearly the same time - one of them could be left out of the queue entirely." pento Tickets with Patches 28314 cancel_comment_reply_link() is unflexible - respond_id & post check Comments 3.9.1 normal major defect (bug) new has-patch 2014-05-20T13:03:57Z 2019-06-04T19:25:49Z "There are two found problems with the function {{{ cancel_comment_reply_link() }}} 1. You cannot define a custom respond id like #respond-POSTID. The respond id (#respond) is hardcoded. So the anchor is not working anymore, if you use a custom respond_id in your theme. 2. If you include the comments on the blogs page (loop) you have comment areas as much as posts. Now you answer to a comment of a specific comment (for example: http://example.com/blog/?replytocom=210#respond-821). This is working fine, just that the cancel_comment_reply_link() is going active for all posts and shows a cancel message under each comment area. It should check for the specific comment area/post and return the message just for the affected comment area/post. If you want I can create a patch for this two bugs :-) Best regards, Ninos" Ninos Ego Tickets with Patches 37103 get_comments_number_text() should not replace '%' in post title Comments 4.2 normal normal defect (bug) new has-patch 2016-06-14T20:06:02Z 2019-06-04T19:38:56Z "Background: #13651 1. Create a post titled ""Hello % world"". 2. Add a couple of comments. 3. `comments_popup_link()` will produce the following output: {{{ 2 Comments on Hello 2 world! }}} Note ""Hello 2 world!"" instead of ""Hello % world!"", due to `get_comments_number_text()` treating `%` as a comments number. Reproduced with 4.5.2 and Twenty Sixteen. Technically introduced in [31388]." SergeyBiryukov Tickets with Patches 47413 nested paragraphs in comment post errors Comments 4.5 normal normal Future Release defect (bug) reviewing has-patch 2019-05-28T05:32:48Z 2021-05-15T22:42:25Z "Line 30 in ‘wordpress/wp-comments-post.php’: {{{#!php ' . $comment->get_error_message() . '

' }}} An example of the Html code generated: {{{

ERROR: please fill the required fields (name, email).

}}} The reason is that in function **_default_wp_die_handler**, line 3072 in ‘wordpress/wp-includes/functions.php’ (WordPress 5.2.1), there already is a paragraph tag. {{{#!php $message

"" }}} I would suggest removing the paragraph in ‘wp-comments-post.php’. Simply: {{{#!php get_error_message() }}} ought to do. " tnbnicer Tickets with Patches 20302 Allow comment_form() to add attributes to
tag Comments 3.3.1 normal normal enhancement new has-patch 2012-03-25T15:48:53Z 2019-06-04T19:22:55Z "The standard method to allow Google Analytics to track comment submissions as a 'goal' is to add a piece of JavaScript code wrapped in an 'onsumbit' attribute: http://www.optimisationbeacon.com/analytics/track-blog-comments-in-google-analytics/ http://code.google.com/apis/analytics/docs/tracking/eventTrackerGuide.html We want something like the following: {{{ }}} However the current arguments submitted to comment_form() do not provide for adding attributes to http://codex.wordpress.org/Function_Reference/comment_form I was forced to perform a workaround in which the onsubmit code was inserted by JavaScript on the fly at runtime. So this is request to alter comment_form() such that arguments accepted provide for 'onsubmit' or other custom attributes to be appended on the tag." psbook Tickets with Patches 30979 Check for context menu before closing commentReply SergeyBiryukov* Comments normal normal Future Release enhancement accepted has-patch 2015-01-11T14:40:41Z 2021-08-27T13:34:20Z "Login to WP-Admin, go to the comments section and ""Quick edit"" or ""Reply"" to a comment. Bring up the context menu either with a right-click or the menu key, press ESC and the context menu and the comment box will close. [[Image(https://i.imgur.com/xnhrZDr.png)]] I understand that this is the expected behaviour but this can be frustrating at times. If you bring up the context menu while typing a long reply but decide not to autocorrect and press ESC to close the context menu everything you've typed so far is gone :( The ""Compose email"" section of both Gmail and Outlook.com close themselves when ESC is pressed but don't if the context menu is open. So I thought WordPress should also have the same behaviour. The patch checks for a right click or menu key press before doing `commentReply.revert()`." jesin Tickets with Patches 20487 Comment search isn't customizable Comments 3.2.1 normal normal enhancement new has-patch 2012-04-18T23:32:07Z 2019-06-04T19:23:01Z "*cross-posted to the wp-hackers mailing list last night* I work on a large news oriented WP site and first off, it actually scales remarkably well. We keep users, comments, and actual posts all in WordPress. However, due to our size, administering comments is causing us issues at the moment. Our last outage was caused by one of our comment moderators doing a simple comment search in the admin. The query took 16 seconds to execute, the next query locked, and, with our traffic, the DB couldn't handle the resulting queued traffic. Staying away from discussions of ""you should use Disqus"" or, ""you need more X for your mysql server,"" I think there is significant opportunity to improve the way WP handles comment searching. Every comment search takes the following form: SELECT * FROM wp_comments WHERE ( comment_approved = '0' OR comment_approved = '1' ) AND (comment_author LIKE '%TERM%' OR comment_author_email LIKE '%TERM%' OR comment_author_url LIKE '%TERM%' OR comment_author_IP LIKE '%TERM%' OR comment_content LIKE '%TERM%') ORDER BY comment_date_gmt DESC LIMIT #; As we can all see, this is a beast of a query. Even when the term is clearly an specific term (say an email or IP), or when the intent of the admin is known (e.g. clicking the IP link on a specific comment). Furthermore, there are no hooks activated in this process for plugins to use to say create an advanced comment search plugin. One might expect hooks like those activated in post search to be activated here, like ""parse_request"" and ""get_search_query."" Waxing philosophical, as posts, comments, and users are the three basic types of data to be stored and displayed in WP, one would expect them to have similar interfaces and functionality. They each have basic functionality of being able to retrieve a single item, a list (in full or in part), search for an element, or edit a single entry. For this reason I don't understand why each of their functionality isn't derived from something like an abstract class or an interface. The architecture here is also difficult in that you are not able to replace or extend a single class to change the functionality. Back on target. I propose that we add functionality by which we'll be able to search by exact match in addition to the existing full wildcard (left, right, or full wildcard is probably excessive) as well as specifying the field to search. This would allow my earlier use case of searching by IP to look for an exact match in the ""comment_author_IP"" field only, not searching the fulltext of every comment. This functionality can be created simply by: 1. Adding ""search_type"" and ""search_field"" to the WP_Comment_Query::query_vars data structure in wp_includes/comment.php 2. Replacing WP_Comment_Query::get_search_sql with something more robust, able to understand these new properties and construct the query on their basis 3. Upgrading WP_Comments_List_Table::prepare_items to accept the new queries and add them to the data structure it creates 4. Either modifying WP_List_Table::search_box to have some options of advanced search, or dropping a hook so that a plugin can easily modify it 5. Modifying the WP_Comments_List_Table::column_author to supply the correct query string to indicate an IP search If I can figure out a way to make this more similar to the signature of posts and users, or at least add some hooks at the right places, I can do that as well. This will add efficiency for everyone--particularly those who have lots of comments. I modified our core for this functionality today and we will fully QA it tomorrow. I made it on 3.2.1 as that is what we're running right now, and there are minimal changes in the affected files and functions between 3.2.1 and 3.3.1 and even the nightly. I can submit a patch as long as it passes our QA--how should I do that, off the nightly? Thanks, -Kenton Jacobsen" brokentone Tickets with Patches 13363 Edit Comments: Pending > Approving shouldn't make them disappear from screen wonderboymusic Comments 3.0 normal normal Future Release enhancement assigned has-patch 2010-05-11T23:35:45Z 2023-11-16T17:40:18Z "Edit Comments: Pending > when clicking Approve the comments shouldn't just disappear from the screen. They should collapse and have an undo status like when you trash or spam a comment. ENV: WordPress trunk r14573 (3.0-beta2-14565) " lloydbudd Tickets with Patches 23634 New hook for adding content after each comment chriscct7 Comments normal normal Future Release enhancement assigned has-patch 2013-02-26T19:29:57Z 2017-10-23T14:56:06Z "Similar to #18561 (which is for a new ""after post"" hook) add a hook that fires after each comment output with {{{wp_list_comments}}}." lancewillett Tickets with Patches 23233 Radio Button instead of Checkboxes on Comment Moderation option? Comments 3.5 normal normal enhancement reopened has-patch 2013-01-18T16:26:23Z 2019-06-04T19:23:51Z "Hi! I've been a loyal Wordpress user for years. This is nothing urgent, but something that may improve the user experience. In Settings > Discussion > Before a comment appears, there are two options: ""An administrator must always approve the comment "" and ""Comment author must have a previously approved comment"" Perhaps I have missed something here, but aren't these options pretty much either/or? If the first box is checked, it's rather irrelevant if the second box is checked, because the first checkbox would override it? If I'm correct, shouldn't this be changed from a both/and checkbox to an either/or radio button?" danielmount Tickets with Patches 47595 Re-evaluate whether comment form should still get the HTML5 novalidate attribute Comments 3.6 normal normal Future Release enhancement new has-patch 2019-06-24T08:15:42Z 2024-01-12T14:59:01Z "Given a theme that declares theme support for `html5` via: {{{#!php $field ) { echo apply_filters( ""comment_form_field_{$name}"", $field ) . ""\n""; } do_action( 'comment_form_after_fields' ); ?> }}} I think it is better that added meta fields should be displayable for all users (logged in and not logged in), or even to add a parameter to let the developer decide which extra fields are shown to logged or not logged users. " maorb Tickets with Patches 34690 when user login is required to comment, there should be a link to registration Comments normal normal enhancement new has-patch 2015-11-15T19:12:17Z 2019-06-04T19:33:05Z "Right now when user login is required the login form only shows a message about the need to login, but if registration is open, there is no reason not to send the visitor directly to the registretion page. At the very least the default text of the link to the login page should be changed to some thing like ""Login or Register"" when registration is open." mark-k Tickets with Patches 21834 Comment History Comments normal normal feature request new has-patch 2012-09-07T20:30:47Z 2021-11-07T21:35:36Z "This ticket provides a simple patch for comment history in core. ''The Problem'': In at least a few places: ([comment:ticket:9117:10], [comment:ticket:15534:4], [comment:ticket:9495:3]) Nacin has mused about the desirability of introducing comment history to core, citing Akismet’s implementation as a model for how this might be done. There are good reasons for wanting this, as comment history could serve as a solid underpinning for a variety of other features such as more informative moderation emails, some indication of why a message was marked as spam, and even comment versioning. The idea is that to implement any of that, we really should have basic comment versioning in core, a la Akisment. ''The Solution'': Our goal was to expand the API so as to reproduce and streamline the basic history functionality provided by Akismet, port and tweak Akismet’s nice history UI, and keep the change set minimal. Comment history API: * added simple functions to /wp-includes/comment.php to get and update comment history. These in turn use existing comment_meta functions. UI: * there’s now a comment history meta box on the comment edit screen. It looks just like Akismet’s. This was implemented as a real meta box. A sorting function is also included. History Events: * this patch supports the following history events, each of which has a nice, plain-english (internationalizable) history message, which always includes the user responsible for the action and a timesince. * edit_comment (“edited by user”) * trashed_comment (“trashed by user”) * untrashed_comment (“un-trashed by user”) * comment_unapproved_to_approved (“user approved this comment”) * comment_approved_to_unapproved (“user unapproved this comment”) * spammed_comment (“user marked this comment as spam”) * unspammed_comment (“user marked this comment as ham”) ''Next steps'': Here’s what we’d think of doing next if this were to be introduced into core: * support more history events and provide more detail. In particular, support events where the comment is spammed as a result of a blacklist word or other reason. * include some of this detail in moderation emails ''Note'': * the Akismet plugin should be updated to use this new API instead of its own history functions * meta boxes on edit comment did not work properly until this: http://core.trac.wordpress.org/ticket/21499 (in 3.5) ''Who we are'': This patch comes from [http://profiles.wordpress.org/bbrooks Ben Brooks], [http://profiles.wordpress.org/mattoperry Matt Perry] and [http://profiles.wordpress.org/natebot Nathan Letsinger]. Enjoy" mattoperry Unpatched Bugs 11734 trackback_rdf() for IDN (xn--) Domains produces invalid HTML Comments 3.1 normal normal defect (bug) new has-patch 2010-01-06T01:10:55Z 2019-06-04T19:21:42Z "Hello The trackback_rdf() function from wp-includes/comment-template.php wraps the ""..."" output inside """" HTML comments, probably to be safe as not all Browsers understand them. When using Wordpress 2.9.1 on a site with an international domain name [1] that contains special characters like German ""Umlauts"" like äöü, this domain name is written as e.g. xn--tst-qla.de for täst.de. Now the output of trackback_rdf() suddenly gets a ""--"" which is the SGML/HTML comment separator mark [2]. Firefox 3.5.6 e.g. sees this as the end of the comment and therefore shows the final ""-->"" as text to the user. As the whole RDF tag is supposed to be invisible for the user, it's a bug in Wordpress :-( Here is an real world example output: {{{

}}} Sadly I have not yet come up with a solution. PHPs urlencode() does not escape a double dash - which is ok as its usually perfectly valid. Maybe someone with RDF experience has a good idea. bye, -christian- [1] http://en.wikipedia.org/wiki/Internationalized_domain_name#Example_of_IDNA_encoding [2] http://htmlhelp.com/reference/wilbur/misc/comment.html " lathspell Tickets Awaiting Review 55309 Incorrect post comment count after deleting comment with replies Comments 5.9.1 normal normal Awaiting Review defect (bug) new dev-feedback 2022-03-03T16:29:07Z 2022-03-03T17:50:55Z "If you move a comment to the trash, and that comment has sub-comments, none of those comments are visible (which is desired) but post->comment_count is reduced by 1 rather than by the total number of comments that have now been hidden. For example: post has 1 comment with 3 replies. Comment count is 4. Delete the first comment. Now no comments are visible but comment count is 3. The first comment has comment_approved set to 'trash' but the other 3 comments are still '1'. Perhaps the right fix is that when trashing a comment, all of its sub-comments are also trashed explicitly rather than implicitly." jwz Tickets Awaiting Review 40352 WP REST API, Comments Not Triggering 'comment_post' Comments 4.7 normal normal Awaiting Review defect (bug) new dev-feedback 2017-04-04T06:50:37Z 2019-11-26T14:44:32Z "Hello, I’ve noticed that when comments are created using the WP API that notification emails are not sent out to the author of the post or moderators. (When testing, If I add the comment via the admin interface, it works as expected). On debugging, I noticed that the filter ‘comment_post’ is not being called when inserted via the API. For now, I used the following workaround: {{{#!php function mytheme_comment_inserted($comment_id, $comment_object) { wp_notify_postauthor( $comment_id ); } add_action('wp_insert_comment','mytheme_comment_inserted'); }}} I already posted on the support forum here: https://wordpress.org/support/topic/wp-api-comments-not-sending-notifications/#post-8987973 and it was suggested this could be intentional behaviour but that this also could, in fact, be reported as a bug? Thanks! Chris" stickypixel Tickets Awaiting Review 46243 WordPress Comments Core Query Comments 5.0.3 normal normal Awaiting Review defect (bug) new dev-feedback 2019-02-13T03:48:45Z 2021-03-26T16:16:24Z "Hello, **Issue:** We have over 400K+ posts and I saw this slow query on any WordPress area on each page. We had 2M+ comments. **Question:** This Query is working on all pages on Dashboard or Settings, Plugin section and any sections why does it? It should works on only all Posts list? **Solution:** I have noticed that Header Bar has Comments Icon and that has displayed the Pending Comments count. I have tried to disable it via custom Filter for following. {{{ function admin_bar_remove_comments(){ global $wp_admin_bar; $wp_admin_bar->remove_menu('comments'); } add_action( 'wp_before_admin_bar_render', 'admin_bar_remove_comments' ); }}} **Slow Query:** {{{ SELECT comment_approved, COUNT( * ) AS total FROM wp_comments GROUP BY comment_approved }}} **Environment Information:** WP Version 5.0.3 (also tested 4.9.8) Theme: Twenty Seventeen (other themes) Plugins: Query Monitor Thanks." Uranbold Tickets Awaiting Review 58375 Turn comments off by default for attachment pages (or make is easier to do so without code) Comments normal normal Awaiting Review enhancement new dev-feedback 2023-05-22T14:49:42Z 2023-05-25T07:09:59Z "If a new user is installing WordPress the first time, it lasts some time until the first spam comment appears. Typically, they now disable comments on **Settings -> Discussion**. First problem: this is just disabling the comments for ''future'' posts. Now they learn about bulk editing posts, which works fine. But the website is now online for some time and more media is uploaded, and now the spam comes to the next open comment form: **on attachment pages**. Not sure if attachment pages follow the setting from the discussion page, but there will be many media items with open comments. Now we have the second problem: On the grid view, there is no way to disable the comments at all (you need to follow a link to get to the single media edit page). On this page you need to customize the screen options to enable the meta box, and now you can disable the comments for ''this'' media item. This has to done manually for every media item with open comments (but there is no way to see if the comments are open - so you need to edit every media item). This could be a real pain for websites with many media items. **I would recommend changing the behavior and have comments on attachment pages turned off by default.** I think it will be easier to educate theme developers to turn them on again if the theme uses them (e.g. photography themes) as documented here: https://make.wordpress.org/core/2015/07/06/comments-are-now-turned-off-on-pages-by-default/ This is already discussed in the comments on this post. Related tickets: #12991 and #21391 Another way could be to use the idea of this comment: https://core.trac.wordpress.org/ticket/12991#comment:22 If turning the default to off is not possible, we could use the bulk edit to enable/disable the comment/pingback/trackback feature. The need for such a feature could be seen in the plugin directory, as there are more than one plugin for disabling comments on attachment pages (and more): https://wordpress.org/plugins/disable-comments/ https://wordpress.org/plugins/smart-attachment-page-remove/ https://wordpress.org/plugins/disable-comments-rb/ https://wordpress.org/plugins/comments-plus/ https://wordpress.org/plugins/disable-comments-on-attachments/ https://wordpress.org/plugins/disable-comments-by-click5/ https://wordpress.org/plugins/no-page-comment/ https://wordpress.org/plugins/stop-media-comment-spamming/ https://wordpress.org/plugins/disable-comments-wpz/ https://wordpress.org/plugins/disable-post-comments/ https://wordpress.org/plugins/close-comments-on-media-attachment/ These add up to more than a million active installations." zodiac1978 Tickets Awaiting Review 43792 get_comment_excerpt filter should tell if the comment was shorted or not Comments normal normal Awaiting Review enhancement new dev-feedback 2018-04-17T22:14:58Z 2019-01-16T06:50:09Z "The design I am currently working on has long comments shortened to 100 words, and a 'show more' / 'show less' link is added. I only want to add the 'show more' text if the comment has been shortened. There is a filter before get_comment_excerpt() returns that I can use to add my link. However it does not pass along information about whether or not the comment was shortened. As a workaround I can check if the comment ends in ""…"", but it would make sense to add a boolean value to the filter arguments to make this easier/cleaner." mattkeys Tickets Awaiting Review 41760 wp_list_comments callback params Comments normal normal Awaiting Review enhancement new dev-feedback 2017-08-30T18:44:15Z 2017-08-31T09:05:53Z "In `wp-includes/class-walker-comment.php`, methods `comment()` and `html5_comment()` have following order of @params: `$comment, $depth, $args`. However, when you try to modify comment markup using `callback` argument for `wp_list_comments()`, order of params is `$comment, $args, $depth`. Is it possible to make the same order of params?" milana_cap Candidates for Closure 60693 """Previously approved comment"" for logged out users bug" Comments 6.4.3 normal normal Awaiting Review defect (bug) new dev-feedback 2024-03-05T14:30:41Z 2024-03-07T17:00:03Z "When ""Comment author must have a previously approved comment"" is checked in the discussion settings, comments made by registered users who are logged out, go to moderation every time. The check comment function looks for previous comments under their user id but if they have only commented while logged out, no id is recorded. This bug has caused our users and our team major frustration. Can someone please address? Thanks!" jmorti Candidates for Closure 46642 Comment form content textarea shouldn't be a required field Comments 5.1 normal major Awaiting Review defect (bug) new dev-feedback 2019-03-25T17:40:00Z 2020-01-23T11:07:04Z "there's a note on the top of the comment form that states: "" Required fields are marked "" and the comment