[wp-trac] [WordPress Trac] #35214: Custom Comment Types

[WordPress Trac]

#35214: Custom Comment Types
----------------------------+-------------------------------------------
 Reporter:  aaroncampbell   |       Owner:  aaroncampbell
     Type:  task (blessed)  |      Status:  accepted
 Priority:  normal          |   Milestone:  Future Release
Component:  Comments        |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  ui, administration, template
----------------------------+-------------------------------------------
Description changed by SergeyBiryukov:

Old description:

> It's time to take another look at Custom Comment Types. We have a nice
> stable example in post types, but there's a '''lot''' to do here, so
> we'll use this as a centralized tracking ticket for everything. As such,
> I'm sure the description here will be fluid for a while as we figure out
> how much there is to do.
>
> Here's a rough list of things that need to be looked at and addressed:
> * UI/UX - In order for custom comment types to be really useful, we need
> to put some serious thought into the UI/UX surrounding comments in the
> admin.
> * The `comment_type` field needs to start using 'comment' instead of ''
> for comments. This will mean an upgrade routine as well as some back-
> compat work.
> * We need to decide what to do about non-default comment types in various
> admin areas (comments table, recent comments, etc). The thing that makes
> most sense is for `WP_Comment_Query` to be adjusted to only show default
> comment types (comments, pingbacks, and trackbacks) by default.
> Additional comment types would then be handled by whatever plugin or
> theme adds them. Unfortunately, this is a breaking change
> (comment:58:ticket:12668) because right now those areas show all comment
> types. Maybe we can create new management areas to be able to pull these
> out of the default one? Lets put our heads together.
> * A lot of existing functions, like `comment_type()`, will need to be
> fixed to make room for newly registered comment types and their
> registered strings.
>

> Previous tickets for history:
> #25674
> #12668

New description:

 It's time to take another look at Custom Comment Types. We have a nice
 stable example in post types, but there's a '''lot''' to do here, so we'll
 use this as a centralized tracking ticket for everything. As such, I'm
 sure the description here will be fluid for a while as we figure out how
 much there is to do.

 Here's a rough list of things that need to be looked at and addressed:
 * UI/UX - In order for custom comment types to be really useful, we need
 to put some serious thought into the UI/UX surrounding comments in the
 admin.
 * The `comment_type` field needs to start using `'comment'` instead of
 `''` for comments. This will mean an upgrade routine as well as some back-
 compat work.
 * We need to decide what to do about non-default comment types in various
 admin areas (comments table, recent comments, etc). The thing that makes
 most sense is for `WP_Comment_Query` to be adjusted to only show default
 comment types (comments, pingbacks, and trackbacks) by default. Additional
 comment types would then be handled by whatever plugin or theme adds them.
 Unfortunately, this is a breaking change (comment:58:ticket:12668) because
 right now those areas show all comment types. Maybe we can create new
 management areas to be able to pull these out of the default one? Lets put
 our heads together.
 * A lot of existing functions, like `comment_type()`, will need to be
 fixed to make room for newly registered comment types and their registered
 strings.


 Previous tickets for history:
 #25674
 #12668

--

--
Ticket URL: <https://core.trac.wordpress.org/ticket/35214#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform