[wp-trac] [WordPress Trac] #45516: Auto Draft title issue for custom post types

[WordPress Trac]

#45516: Auto Draft title issue for custom post types
-------------------------------------------------+-------------------------
 Reporter:  rajanit2000                          |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Posts, Post Types                    |     Version:  5.0
 Severity:  minor                                |  Resolution:
 Keywords:  has-screenshots has-test-info has-   |     Focuses:
  patch has-unit-tests needs-copy-review         |  administration
-------------------------------------------------+-------------------------
Changes (by SirLouen):

 * keywords:  has-copy-review has-screenshots has-test-info has-patch has-
     unit-tests =>
     has-screenshots has-test-info has-patch has-unit-tests needs-copy-
     review


Comment:

 Replying to [comment:68 wildworks]:
 > This is the best approach I can think of at the moment, but considering
 there's only half a day left until the RC1 release and there are differing
 opinions, my personal opinion remains unchanged: I still believe this
 ticket should be postponed to version 7.0 or a future release.

 So here the discussion goes back to `(no title)`.

 I had to read through the whole ticket conversation to understand the
 motivations of the participants:
 https://core.trac.wordpress.org/ticket/45516?replyto=68#comment:15

 Basically, `(no title)` seems to be insufficient. The problem with `(no
 title)` is that it's currently being used to specify, **"The post doesn't
 have a title but can have a title"**.

 This is why they decided to step into an alternative, and several copy
 alternatives were proposed until they settled down with `(no title
 supported)`.

 About the:

 > - Front end: Nothing is displayed as a title.
 > This is the best approach

 Isn't this contradictory? You are commenting in the beginning.

 > Basically, existing data should be output on the front end even if there
 is no support for that post type.

 And then you say that in the front end nothing should be displayed as a
 title.

 Anyway, again, as I said and is crucial, this is content for **another
 ticket**.

 We are focusing here just on the administration display.

 Replying to [comment:69 mosescursor]:
 > The term `supported` feels misused here. The Post may noy just have a
 title but can get a title. When you set supported makes an impression that
 a title can not be used which is wrong

 You are not correct on this point, Mr. Sebunya. This is exactly what it
 means: a title cannot be used because at one point, you created that post
 without title support (not having title support means that you cannot add
 a title).

 @wildworks was dubious with "''What happens if the title supports are
 returned''". This is a tricky question. The same goes for other title
 static options like `Auto Draft`. What happens if the post was edited but
 the title was never updated? Is it still an `Auto Draft`?. Given the
 nature of static titles, we cannot switch them once settled for the first
 time. They are just an indication of the current status when they are set,
 and they can become obsolete the minute after.

 Replying to [comment:68 wildworks]:
 > I feel that applying the patch will only make the symptoms worse on the
 front end. This is the main reason I'm hesitant to apply the patch.

 I don't understand how it can worsen it. How can `(title not supported)`
 be worse than `Auto Draft`? `Auto Draft` is misdirecting, while `(no title
 supported)` is aligned with the problem. This patch is softening this
 issue. Leaving things unchanged means that we can't add incremental
 improvements, and we prefer to leave things broken than things “less
 broken”.

 My concern here is that we are not giving solutions, and I'm providing a
 solution.

 The answers are like, "''I don't like your solution, but I'm not really
 sure what I like''".

 This is a problem because, as we are now, we are leaving this ticket
 orphaned without a solution or a direction. And my task is to get tickets
 from this component to a final resolution. And I have not heard any
 convincing criteria to avoid `(no title supported)` yet.

 I'm going to bring @marybaum to the conversation, as she is the copy
 master. :)

 So here we start the "Copy Review" part 2

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