Commenting on a draft post results in blank page

[sumitbagthariya16]

Hi,

When I submit the comment on draft post it will redirect to the blank page. I have attached video for the more information.

Thanks

[bhaveshkhadodara]

Hi @sumitbagthariya16,

Here we should remove the comment box when the post is draft.

Thanks

[sagarprajapati]

Hi @bhaveshkhadodara , @sumitbagthariya16

I have added patch with above issue solution.

Thanks

[milindmore22]

Patch will not show comment form if post status is not publish. The patch will also take care of pending status.

[sagarprajapati]

Followed the standards

[sagarprajapati]

Updated $post to $post_id

[milindmore22]

Updated patch by passing $post_id as get_post_status parameter

[dhanendran]

@sagarprajapati It's better to have this condition after the first ​`if` condition. Because there might be some chances the $post_id will be null.

if ( null === $post_id )
    $post_id = get_the_ID();

[milindmore22]

added after post_id check as per comment 7

[milindmore22]

@sagarprajapati same thing happens when we have pending status my patch will show comment form only if status is publish.
@dhanendran thanks for suggestions!

[swissspidy]

What @dhanendran said. Also, the code would need somebrackets to follow the ​WordPress PHP coding standards.

However, I don't think hiding the comment form for draft posts is the ideal solution here. Allowing comments on drafts might be desirable under some circumstances (live previews in the customizer, REST API, etc. See also #19739).

Instead of a blank page there should be an actual error message. This means changing wp_handle_comment_submission() accordingly, where there's currently this line: return new WP_Error( 'comment_on_draft' ); (note the lack of error message).

[swissspidy]

@milindmore22 Please note that your patch would break commenting on private posts.

[sagarprajapati]

@swissspidy Thank you so much. This would be great idea.

[mayurk]

Hi @swissspidy

I agree with you. I have prepared a patch with your suggestions. Please check it.

Thanks

[sagarprajapati]

Hi @swissspidy and @mayurk

@mayurk: I also working on this issue. I agreed your patch but we will need to add the proper error message as per swissspidy's suggestions.

I have added the patch with the error message. Please check it.

Thanks

[swissspidy]

Seems like you guys should work together / coordinate on who's updating a patch :-)

39650.4.patch​ is not needed. That would be to big of a change. Adding the message argument to the WP_Error object automatically displays that message when posting the comment. That's why the exit; there is just fine as-is.

39650.5.patch​ does not need to touch wp-comments-post.php either. Also, why adding the error message to every WP_Error object and not just on comment_on_draft (the original scenario described in the ticket)?

The error message should probably only be shown if the user has the capability to read the post, so a current_user_can() check seems to be needed.

[sagarprajapati]

Sorry @swissspidy

I thought that it is not working for all others. I have updated patch with the changes. Please check it.

I have also done unit test for the above patch and here is the result.

C:\wamp\www\wordpress-core>phpunit --group comment
Installing...
Running as single site... To run multisite, use -c tests/phpunit/multisite.xml
Not running ajax tests. To execute these, use --group ajax.
Not running ms-files tests. To execute these, use --group ms-files.
Not running external-http tests. To execute these, use --group external-http.
PHPUnit 5.7.5 by Sebastian Bergmann and contributors.

..............................................................  62 / 339 ( 18%)
.............................................................. 124 / 339 ( 36%)
.............................................................. 186 / 339 ( 54%)
.............................................................. 248 / 339 ( 73%)
.............................................................. 310 / 339 ( 91%)
.............................                                  339 / 339 (100%)

Time: 50.03 seconds, Memory: 90.00MB

OK (339 tests, 657 assertions)

Thank you.

[swissspidy]

needs-unit-tests means some unit tests need to be written for this, not only running the existing tests. See the handbook for a ​list of all trac keywords. Let me know if I can help with that. I might have time to write tests myself next week.

39650.6.patch​ goes into the right direction. The correct capability might be edit_post instead of read_post, but we'll see that with the unit test.

[milindmore22]

Great work with patch @sagarprajapati, Thanks @swissspidy totally forgot that will keep in mind about flow
Guys #19739 does this ticket related?

[swissspidy]

Replying to milindmore22:

Great work with patch @sagarprajapati, Thanks @swissspidy totally forgot that will keep in mind about flow
Guys #19739 does this ticket related?

Yep, it's related and I mentioned it before. Let's see if we can fix both at once.

[swissspidy]

The correct capability might be edit_post instead of read_post, but we'll see that with the unit test.

read_post is fine. map_meta_cap() handles this perfectly.

[johnbillion]

In 40128:

Comments: When commenting on a draft post, display a friendly error message if the user can view the post.

This prevents the unhelpful white screen of death when a user who can view the post (eg. preview it) leaves a comment while the post is in draft.

Props sagarprajapati, milindmore22, mayurk, swissspidy
Fixes #39650

[johnbillion]

#40689 was marked as a duplicate.